From idea to a working product, in weeks, not quarters.
A senior engineer, embedded, shipping. I build MVPs and complete SaaS products for founders who need to move now, without hiring a team, and without gambling on a rewrite six months in.
Founders who need something real, in front of users, quickly.
You’ve got a validated idea, or a paying customer waiting on a pilot, or a pitch coming up that needs more than a Figma prototype. You don’t have twelve months and £500k to hire a team.
What you need is one senior engineer who has shipped this kind of product before, will make the sensible technical calls without a committee, and will hand you back a codebase your next hire can actually work with.
That’s what this is.
Boring tech. Small surface area. Ship every week.
-
01
Scope tightly
Cut the MVP down to the smallest thing that proves the idea. Everything else waits.
-
02
Platform agnostic
As happy in Vercel and Next.js as I am in Ruby on Rails or .NET. Right tool for the job, not the tool I happened to learn last.
-
03
Ship weekly
A staging URL from week one. You use it, you push back, we adjust. No four-month reveals.
-
04
Hand over cleanly
Tests, documentation, deploy scripts. The codebase your first engineering hire can pick up on day one.
Two shapes. Pick the one that fits.
Idea to first paying users
Six to twelve weeks. We scope the smallest useful product, I build it, we get it in front of real users. Deployed, tested, documented.
Discuss an MVP →Ongoing product engineering
Weekly rate. I work as your senior engineer, shipping features, making architectural calls, mentoring your team if you have one, until you don’t need me any more.
Discuss embedded work →A short list of expensive mistakes I’ll talk you out of.
-
Microservices in a v1.
One process. One database. Split it when you have real load, not before.
-
A native app when a web app works.
React Native only if you actually need the phone’s hardware. Otherwise a mobile-friendly web app ships in a third of the time.
-
A bespoke design system.
Use a proven component library. Your customers care what the product does, not that the buttons are hand-crafted.
-
Rewriting the working thing.
If there’s already code, we improve it incrementally. Rewrites almost always cost twice what you expect and ship without the edge cases the old code handled.