FAQ
The questions founders actually ask.
Grouped into four sets: positioning, process, commercial, and trust. If yours isn't here, it goes in the Fit Check form.
Positioning
What this is, who it's for, who it isn't.
What exactly is the Sprint?
A productised service for solo founders who have a software idea but no technical co-founder. I translate the idea into a focused first product, build it on a proven foundation, deploy it, and hand it over: fixed price, in days, no equity. The service sits in the gap between agencies, freelancers, and no-code, and is deliberately none of them.
Who is this for?
Domain experts with money, a painful workflow, and a simple first product idea. Consultants productising their expertise, small business operators replacing a spreadsheet, founders who don't want to spend their first 18 months hiring. People who have thought enough about the idea to describe it on one page.
Who is this not for?
Founders building a marketplace, social network, or full multi-tenant SaaS in v1. Founders without budget who want equity-based work. Founders who can't reply within a working day. Anyone who needs an NDA before the first conversation. The Sprint says no to most ideas. The alternative is saying yes to the wrong ones.
Process
What happens during the sprint.
What does “working first product” actually mean?
Deployed. Database-backed where it needs to be. Usable end-to-end by an early user. Limited enough to ship in days, structured enough to keep building on. The smallest version of your idea that produces evidence; not a polished SaaS, not a throwaway prototype.
Will I be on calls every day?
No. The build itself is mostly heads-down. You'll have a kickoff once scope is locked, async check-ins during the sprint, and a handover session at the end. The model only works because nobody is sitting in three-hour planning meetings.
What technology will it be built in?
Boring, well-supported, AWS-hosted. Typically a TypeScript stack on container or serverless compute, with a managed Postgres database. Specific choices depend on the workflow; the Blueprint includes the call and the reasoning. The aim is code any competent developer can pick up later, not a clever stack only I understand.
How can you build a real product in 5–10 days?
Because the build doesn't start from zero. Sprints run on a small library of reusable architectures and patterns I've assembled over years of doing this work: authentication, billing, admin, common workflows, AWS deployment, observability. The novel part of your product is the workflow that makes it yours; everything around it is well-trodden ground. Reusing the well-trodden ground is what creates the speed and removes the risk of v1 surprises.
Will I own the code?
Yes, fully. On handover the repository is in your account and the architecture is documented well enough that any AWS-literate developer can pick it up. No proprietary glue, no licensing tricks, no “bring it back to me for changes”. Where the deployment lives is a separate conversation: by default it's set up so you can take ownership of the AWS account on day one if you want, and ongoing hosting and maintenance can be arranged separately if you don't.
Commercial
The money, the contract, the small print.
How does payment work?
Blueprint is paid upfront (£950). The remaining sprint balance is split: 50% at sprint start, 50% before handover. UK bank transfer or Stripe. Invoiced from a UK limited company. VAT added where applicable.
Is the Blueprint refundable?
No. The work happens whether the answer is build, validate first, or walk away. The point of the Blueprint is to make the right call, not to bet on a particular outcome. If the answer is “don't build”, that recommendation is exactly what saved you the rest.
Do you take equity?
No, and I'm not interested. The whole point is fixed-price work that doesn't put your cap table at risk. If you want a co-founder, the answer is to find one. If you want the first build done now, this is what I do.
What happens if the build runs over?
It's my problem, not yours. The price doesn't change. If something turns out harder than the Blueprint anticipated, scope flexes: something gets cut to keep the date and the price intact. You'll be told the moment a trade-off comes up, and you make the call in minutes.
What if I want changes after handover?
Most founders book an Iteration Sprint within 60 days of going live. £3,950 buys five days of focused changes once real users have touched the product. You can also take the codebase elsewhere; the handover is structured so a new developer can pick it up cleanly.
Trust
The questions you'd ask if I were sitting across a table.
Who does the work?
Me. One senior technical operator with a long career behind a co-founder-shaped role, working alongside a tightly-supervised AI coding stack. No team, no junior staff, no offshore relay. You'll meet me during the Blueprint, and I'll do the build. The site is intentionally low-key on personal branding because the offer is the offer; I'd rather you judge me on the Blueprint than on a LinkedIn headline.
How do I know you can actually deliver this?
The honest answer: you don't, until you've seen the Blueprint. The Blueprint is the trust signal. It costs less than a week's freelance rate and shows whether I understand your problem before any build money is on the table. If the Blueprint doesn't impress you, walk. If it does, the rest is on the same model.
What if you say my idea is a fit, then you fail to deliver?
Two protections. First: scope is locked in writing before any code, so the deliverable is binary; either the workflow is live or it isn't. Second: the final 50% is paid before handover, not after, only because you'll have seen the working product. If I miss handover, that final payment is conditional. The Sprint runs on its reputation, and reputation is the only asset that compounds in this market.
Why don't I just hire a developer?
If you have a clean brief, a tight scope, and the technical judgement to manage the build, hire a developer. You'll save money. The Sprint exists for the founders who don't have any of those things, and who don't want to spend three months acquiring them before writing the first line of code.
If your question isn't here, the Fit Check is the next step.
Five-minute form. Written reply within two working days. No call until there's something concrete to discuss.
Check if your idea fits