Looking for someonewho builds SaaSthat still holds upwhen things get real?
Looking for someonewho builds SaaSthat still holds upwhen things getreal?
What I've Built
E-Commerce Platform
Checkout for one of Europe's largest ecommerce players - thousands of orders a day, 1M+ users.
1.5 years on a team where every deploy touched real money. Small calls had a way of turning into expensive ones.
Claro
Marketplace where each vendor runs their own shop - separate subdomain, payouts through Stripe Connect, tenant data kept apart.
Next.js 15, Payload CMS 3, tRPC v11. Vendors can prompt Claude in admin for draft product copy - Zod has to pass before anything saves.
Dotty
Invoice flow for freelancers - you issue invoices and invites, clients pay by card in their own portal, status updates without the email thread.
Supabase auth, Postgres triggers for roles, 5 Edge Functions live. Stripe charges plus signed webhooks. Haiku drafts overdue reminders - the API key never hits the browser.
The most expensive mistakes don't throw errors. You don't notice them until the revenue is wrong.
I learned that building checkout systems for over a million users. 1.5 years where downtime wasn't an option. You get a feel for what looks fine but will bite you later.
I bring that mindset to whatever I'm building - production architecture, not just the interface. What's on the screen and what happens the first time real traffic shows up.
I'm in Los Angeles, shipping my own products and taking maybe one or two client projects a year. I do best when you want someone who'll push on the plan when it matters - not just close tickets.
Aga Kadela
How I Work
I question the brief
Most problems look technical from the outside. Before anything else, I push back on what we're actually trying to solve - because I've seen what happens when nobody does.
You know where things stand
You hear about what's going on before you have to ask. If something changes, I tell you - not in the next standup, now.
I know when not to build
I'll tell you straight when something isn't worth the engineering. If there's a simpler path nobody said out loud, I'll say that too. Sometimes the answer is honestly to wait.
You leave with something you can own
Not just a codebase. Decisions and context too (so whoever picks this up in six months knows what they're looking at).
Get in touch
The right fit shows up maybe once or twice a year. Usually it's someone with a real problem, a clear picture of what they want to ship, and they need a technical owner - not another layer of management.
If that's you - tell me what you're building.