Scoping that removes things
We start by identifying the single riskiest assumption and cutting everything that does not test it. Expect us to argue for a smaller build than you arrived with.
Software Development
From idea to launched product in weeks.
A fixed-price, fixed-timeline first version built around the one thing your product must prove. You get something real in users' hands while the question is still worth answering, and you own every line of it.
The riskiest thing a founder can build is everything.
First versions fail for a predictable reason: too much. Every feature that seems essential goes in, launch slips two quarters, money runs out before anyone learns whether the core idea works. The feature that would have proved it shipped alongside forty that did not matter yet.
An MVP is not a cheap version of the real product. It is an instrument for answering one question (will people use this, and will they pay) with the smallest thing that can answer it credibly.
So the most valuable part of this engagement is usually the scoping. We are direct about what to cut, and we hold a fixed price and a fixed timeline so the budget is knowable up front. Founders do not need another open-ended engineering bill.
How an MVP engagement runs
A fixed price and a fixed date
Both agreed before we start. You know exactly what it costs and when it lands, which is the part most agencies will not commit to.
Weekly demos, not status reports
Every week you see the product running. No surprises at the end, and space to redirect while redirecting is still cheap.
Built to survive success
A prototype that cannot handle its first hundred users is a liability. We use the same stack as our full builds so a working MVP can be extended rather than thrown away.
Analytics from day one
Instrumented before launch so you can answer 'is this working' with data. An MVP that ships without measurement has skipped the entire point.
Everything in your name
Repository, hosting, domains, and third-party accounts all set up under your ownership. If you never speak to us again, nothing breaks.
Everything handed over.
Listed explicitly so there is no argument later about what was in scope.
- Launched MVP deployed to production
- Full source code in your Git organisation
- Analytics instrumented on the core funnel
- All infrastructure and accounts under your ownership
- Technical documentation and handover session
- A prioritised list of what we deliberately left out, and when to revisit it
- 30 days of post-launch bug fixes at no charge
Honest scope
Is this right for you?
We would rather lose the enquiry than take on work we are the wrong people for.
A good fit if…
- You can name the single most important thing your product must prove
- You are prepared to launch something narrower than your full vision
- You can give quick feedback. This pace needs a responsive founder
- You want to own the codebase and keep building after launch
Not for…
- Founders who cannot cut scope. A fixed price requires a fixed scope, and if everything is essential this is the wrong engagement
- Products needing regulatory approval or certification before launch
- Anyone seeking a technical co-founder or equity arrangement. We are a paid vendor and are clear about that
- Ideas whose core value is unproven hardware or research; software is not the risk you should be spending on first
Ways to start
Pick an entry point.
Larger engagements vary enough that a headline number would mislead, so those are quoted after a free call. We always tell you what drives the number.
Launch Pilot
Proving one core loop, at a fixed price, with a fixed date.
Quoted
A fixed price and fixed date, both agreed before we start
6 weeks
- Scoping workshop to identify the riskiest assumption
- One core user journey, built and launched
- Authentication, hosting, and analytics
- Weekly demos
- 30 days of post-launch fixes
- Native mobile apps
- Payments beyond a standard Stripe checkout
Full MVP
A first version with several journeys, ready to put in front of investors or paying users.
Quoted
Priced after the scoping workshop
3-4 months
- Multiple user journeys
- Payments and subscription billing
- Admin tooling so you can run the business
- Design included
- 30 days of post-launch fixes
Post-Launch Development
Building on what the first users actually told you.
Quoted
Monthly, priced on the share of the team you reserve
Rolling monthly
- A reserved share of the team each month
- Feature development driven by real usage
- Maintenance and security updates
- Monthly planning and review
Questions, answered.
Is the fixed price genuinely fixed?
Yes, for the scope agreed in the scoping workshop. That is the trade: the scope is fixed too. If you decide mid-build to add something outside it, we quote that separately rather than absorbing it quietly and cutting corners elsewhere, which is how fixed-price projects usually go wrong.
Do you take equity instead of payment?
No. We are a paid vendor and we think that is the healthier arrangement for both sides. It keeps our incentive on delivering your product well rather than on managing a position in your company. It also means you keep your cap table clean.
What if we get traction and need to keep building?
That is the intended outcome, and the MVP is built for it: same stack, same standards as our full builds, so it extends rather than needing a rewrite. You can continue with us on a monthly basis, hire your own team around the codebase, or bring in another agency. The documentation and handover exist to make all three real options.
Can you help decide what belongs in the MVP?
That is the most valuable part of the engagement, and the scoping workshop is where it happens. We work back from the single riskiest assumption in your business and cut everything that does not test it. Founders often tell us afterwards that the cutting mattered more than the code.
Start with a free conversation.
Thirty minutes, no pitch. We will tell you what we would do, what it would take, and whether you need us at all.