Taking new projects— Booking for Q4 2026
I help foundersbuild, scale, and leadengineering.
Fast, high-quality technical execution — from the first commit to a team that ships without me.
Hover any node. This is the shape of what I build — and the order I build it in.
- Years building software
- 9+
- Users reached by products I've built
- 100M+
- MVPs through to production scale
- 0→1
- US / EU / GCC overlap
- Remote
Products & platforms/6
Three ways I work
with founders
Most engagements start in one of these and grow into another. You don't need to know which — that's what the first call is for.
Senior engineering, without the org chart
You're not hiring a resource to be briefed. You're hiring someone who has run this before and will tell you what they think.
- 01
The architect and the builder are the same person
No handoff gap between the person who designs the system and the person who writes the code. Decisions get made with full context, and they get made once.
- 02
Minimal hand-holding
Give me the problem, the constraints and access. You get back a plan with trade-offs, then working software on a weekly cadence — without managing me.
- 03
Built for real scale
9+ years on products and platforms reaching over 100 million users. Load, cost and failure modes are part of the first design conversation, not a later surprise.
- 04
Straight answers
If what you're asking for is the wrong thing to build, you'll hear it in week one — along with the cheaper option. I'd rather lose scope than lose your trust.
Four steps, no surprises
The same shape whether it's a two-week audit or a six-month build. You always know what's happening and what it costs.
- 01
Scope call
30 minutes
What you're building, what's blocking it, and what 'done' looks like. If I'm not the right person, I'll say so and point you somewhere better.
- 02
Plan and proposal
Days, not weeks
Architecture, milestones, timeline and a fixed scope with a fixed price. You see the trade-offs I'm making and why, in language you can take to your board.
- 03
Build and demo
Weekly cadence
Working software every week, a demo you can click, and direct access to me. No status theatre, no waiting until the end to find out where we are.
- 04
Handover or scale
Your call
Documented, tested and deployable — plus a team that can run it. I stay on to scale it if that helps, and I'm easy to stop working with if it doesn't.
Proof, not promises
Role, challenge and outcome. Client specifics stay confidential — the engineering doesn't.
◆ Engagement record
Partially withheld
- Ident
- Dream11
- Surface
- Fantasy sports platform at national scale
- Class
- Consumer
- Focus
- scale
- Role
- Lead Mobile Developer | React Native
- Scale
- Awaiting client sign-off
- Outcome
- Awaiting client sign-off
- Stack
- Awaiting client sign-off
Delivery trace
Shape of delivery shown. Client architecture not published.
Awaiting client sign-off. Ask me directly and I’ll walk you through the parts I’m free to discuss.
Short version
- Based
- Remote — Global
- Overlap
- US · EU · GCC
- Focus
- SaaS · AI · Consumer Tools
I'm an engineering leader who never stopped building. Over 9+ years I've taken products from empty repository to production at scale, and led the teams that kept them there — work that has reached more than 100 million users.
I work with founders and small teams as an outside senior engineer: designing the architecture, writing the code that matters most, and leaving behind something a team can own. Remote and global, with overlap across US, EU and GCC hours.
How I think about the work
The MVP scope question nobody asks
Most MVP scopes are argued over features. The question that actually decides whether you ship is a different one entirely.
Where AI actually earns its place in a product
A practical test for whether an AI feature belongs in your product — and the three shapes that tend to survive contact with real users.
The mental model that makes Server Components click
Server Components stop being confusing once you stop thinking about where code runs and start thinking about when it runs.
The things founders ask first
Defined services — audits, sprints, fractional leadership — have a fixed price you'll see before we talk. MVP and complex builds are quoted after a short paid discovery, because a number given before the scope is understood is a number that gets renegotiated later.
Remote-first with reliable overlap for US, European and GCC teams. Async by default, with a standing weekly call and availability for anything that can't wait.
Often. You get plain-language explanations of every technical decision, and someone who will tell you when an idea is expensive before you commit to it.
Yes. That's a large part of the Scale and Lead work — reviewing what exists, raising the standard, and making an existing team faster rather than replacing it.
A one-to-two week audit or product sprint. It's a low-risk way to see how I work before committing to anything longer.
Yes, before any detail is shared. Nothing about a client engagement appears on this site without their agreement.
Tell me what you're building.
A 30-minute call. You'll leave with a straight read on scope, sequencing and what it takes to get there — whether or not we work together.
Typically replies within one business dayor press⌘ K