Most developers show you what they built.I show you how it breaks.
I design and build the parts of a product where one mistake costs money or trust: AI that answers from your data, payments, crypto, who sees what. From a first MVP, or from a half-finished app someone else started.
I made up a company.
Then I broke it.
Northwind Studio is fictional. The demos are live: press the buttons, then read the code that stops it.
Northwind gets paid.
Northwind gets paid in crypto.
Northwind keeps a secret.
Northwind gets audited.
Three ways to
work with me.
Audit
An app that exists, often built fast or with AI tools, and you're not sure it holds.
A written report, findings ranked by what they'd cost you, and what I'd fix first.
Build
Founders who need a working first version, or a product stuck at 80%.
Architecture written down first, weekly working releases, the repo in your name from day one.
Stay on
After launch, when you need one person who owns the system.
I keep it running, review what others ship, and tell you early what will break.
I work solo.
I don't ship solo.
When a project needs more hands, I bring people I've shipped with before.
30+ shipped.
Four with the full story.
30+ shipped · 3 current clientsEvent Ticketing: Payments Rebuilt
Stripe wired without payment status tracking. Worked in demos. Would have failed on the first busy on-sale.
What I didRebuilt the money path: the order exists before Stripe, idempotency at three levels, reconciliation on read.
- 8 weeks
- audit to MVP
- ~30k
- tickets a year, first venue
- Nov 2026
- ticket sales launch
Membership Platform, California
A community organization with nothing digital. Membership, payments, store, events and delivery had to exist in three months.
What I didShipped membership, store, events and payments as one platform in three months — and still run it.
- 3 months
- idea to production
- 3k+
- monthly members
- $50k+
- monthly store turnover
Crypto-to-Card Platform
Users load crypto and spend it through virtual cards. The backend had to exist first: KYC, compliance, transactions, card issuance.
What I didBuilt the payment backend from zero: deposits, balances and card issuance, reconciled against the issuer.
- 5 months
- zero to live
- 300
- users at launch
- 2k
- transactions a month at launch
Real Estate CRM, Limassol
About 80 agents ran the busiest agency in the city on ten Telegram groups and a set of spreadsheets.
What I didReplaced the groups and spreadsheets with a native CRM and bots that post listings and triage leads.
- 80
- agents off Telegram
- ~1 hour
- lead response, from about half a day
- 2.5 years
- in production
I think
out loud.
Selected pieces from things I've shipped — what worked, what almost broke, and what I'd do differently.
When traditional payment rails aren't available, you build your own
“payments worked. Consistently”
Name scope creep directly — don't absorb it silently
“no surprises is better than no scope creep”
Don't replace what works — extend it
“the best integration is the one your users don't notice”
'We have backups' means nothing without verification
“We crossed that line”
Translate architecture into business risk language
“stakeholders understood why the mitigation worked — because they had been part of the decision”
Three environments or you're gambling with production
“nobody on the team questioned the cost of maintaining staging”
Three steps.
That's it.
Free 30-min call.
Tell me the business problem, not the stack. I'll say honestly if I'm the right person.
A written plan in 48 hours.
Scope, price, what I'd do first.
Weekly working releases.
You see progress in the product, not in status reports.
The short
version.
My longest-running client — big business, can afford whoever he wants. I asked him once, half-joking, why he's still paying me when he has smarter engineers in his network. He said: “Because you ship. When you say it'll be done Friday — it's done Friday. You don't disappear. You don't show up with excuses. You just do the work.”
That changed how I think about this craft. The startup world is full of brilliant engineers who disappear mid-project. Founders aren't actually shopping for the smartest engineer — they're shopping for the one who'll still be there in six months, answering messages and shipping on schedule.
I'm not the most brilliant engineer you can hire. I'm the one who'll still be here Monday morning. BSc in Computer Science from Kyiv Polytechnic. Based in Barcelona, covering EU and US East Coast timezones.
I started at 14. Nine years later I still like the part most people skip: finding where it breaks.
I take on 2–3 clients at a time.
Every engagement gets deep focus.
“When you say it'll be done Friday — it's done Friday. You don't disappear. You just do the work.”
— CEO · US events organization
Timeline