MVP Development — ship the right thing in 6 weeks
Fixed-scope MVP builds for founders — auth, payments, the one feature that matters, in production, in six weeks.
Most MVPs fail before launch for the same reason: scope. The founder lists 14 features they need "to launch", an agency or contractor agrees, and four months later they're 40% done and out of money. We do the opposite. We help founders ruthlessly cut scope to the one thing that proves the hypothesis, ship it in six weeks, get it in front of paying users, and decide whether to double down or kill it. Every MVP we ship is real software, not a prototype: auth, payments, the core feature, a deploy pipeline, and a polished marketing surface. It's not the full product — it's the version of the product that lets you find out whether the market actually wants it. We've taken MVPs from blank repo to first paying customer for solo founders, funded teams, and corporate intrapreneurs. The hard part is never the build — it's saying no to the features that would feel good to ship and don't actually prove anything. We'll do that part with you.
About this service
What an MVP actually is
Not a prototype, not the full product
An MVP isn't a Figma click-through, a landing page, or a paid waitlist. Those are validation experiments — useful, cheaper, do them first if you can. An MVP is the version of the real product with enough working software to be charged for, used by strangers, and learned from. If you can't charge for it, it's not an MVP — it's a demo.
An MVP also isn't the full product. The full product has SSO, audit logs, role hierarchies, advanced reporting, and the seven secondary features the founder thinks of as obviously necessary. The MVP has none of those. The MVP has the one thing that proves you should build the rest.
How we cut scope
The conversation most agencies won't have with you
Our discovery call is unusual because half of it is us telling you which features not to build. We ask the same five questions every time: what's the one job a user hires this product to do; what would a user actually pay for; what's the manual workaround they're using today; what would they have to lose to switch; and what would convince you to walk away. If we can't answer those clearly together, building anything is premature.
We've walked away from MVP engagements on that call. We've also taken funded six-figure builds and convinced the founder to ship a £15k MVP first and pocket the rest. Either way, the conversation pays for itself.
After the MVP
Three honest outcomes
After six weeks, one of three things happens. The signal is strong and you'd like to keep building — we either scope a Pro SaaS build or hand over the codebase to your in-house team, your choice. The signal is mixed — you have data to make a real decision and a working product to keep iterating on cheaply. The signal is weak — you walk away with a £15k bill instead of a £150k bill and a clearer view of what to try next.
All three are wins. The MVP exists to surface the signal, not to be the final product.
Real mvp development patterns we’ve shipped
Not adjectives. Specific shapes of build we’ve taken to production for clients like you.
B2B SaaS MVP
Auth, billing, the one feature, a marketing site — ready for your first 5 paying customers in six weeks. Like the foundation under [CloudChat](/work/cloudchat) before the operator dashboard.
Consumer subscription MVP
Signup, payment, the core consumer surface, push or email retention loop. Tight enough to learn whether the retention curve works.
Marketplace MVP
Two-sided marketplace with the supply side onboarded manually, the demand side self-serve, and Stripe Connect wired. Concierge until volume justifies automation.
AI-product MVP
[AI agent](/services/ai-agent-development) wrapped in a real product surface — auth, billing, usage limits — built to learn whether anyone pays for the agent's output.
Internal-tool MVP for a corporate sponsor
Corporate intrapreneurship build — small, fast, ships behind their SSO, lives inside the org, learns whether to fund a full team.
Vertical SaaS MVP
Industry-specific SaaS replacing a horizontal tool in a narrow vertical — built tight enough to acquire the first 10 customers from cold outreach.
Mobile MVP
Single-platform [mobile MVP](/services/mobile-app-development), 5–7 weeks, in TestFlight or Play Console with a real first cohort.
API-first MVP
Developer-facing product with docs, auth, billing-by-usage — built lean enough to learn whether anyone pays for the API itself.
How a MVP Development engagement actually runs
Five concrete steps with deliverables. No retainer fog.
Scope kill (week 0)
One 90-minute working session to cut your feature list ruthlessly. We leave with one core feature, one revenue mechanic, and an explicit list of things we will not build in v1.
Week 1–2: Foundation
Auth, payments, the marketing surface, the deploy pipeline. The boring half of the work. We move fast because we've shipped this floor a dozen times.
Week 3–4: The one feature
The actual differentiated product feature, end-to-end. Weekly demo builds. Every Friday you have a working preview to send to potential users.
Week 5: Polish + paying-customer readiness
Error states, onboarding, billing edge cases, transactional emails, analytics, a 'first run' that doesn't make new users bounce. Not the fun work — the work that decides whether anyone converts.
Week 6: Launch + first 30 days
Public launch, first cohort onboarding, weekly bug-fix releases for 30 days while you find out whether the market wants it.
Real brackets, no surprise invoices
Starting points. Exact quote on the scoping call — written, fixed, no hourly surprises.
MVP Sprint
Fixed-scope, six weeks
- Auth + Stripe checkout
- One core product surface
- Marketing site
- Deploy pipeline + staging
- 30 days bug-fix support
MVP + Mobile
Web + mobile companion, 8 weeks
- Web product as MVP Sprint
- React Native companion (single platform)
- TestFlight / Play internal track
- Shared auth + billing
- 45 days support
MVP → Pro Path
MVP + Pro build commitment
- MVP Sprint included
- Locked-in [Pro SaaS](/services/saas-development) rate after launch
- Same team continues
- Discounted retainer option
Things real buyers ask before paying
If yours isn’t here, ask on the scoping call.
Often shipped alongside this
SaaS Development
Production-ready SaaS platforms with auth, billing, and a real operator dashboard from day one.
Mobile App Development
React Native and Swift / Kotlin apps shipped to the App Store and Play Store, with the offline, push, and release-pipeline work that actually keeps them live.
AI Agent Development
Custom AI agents built on Claude, GPT, and open models — wired to your data, your tools, and your real workflows.
Real builds in production
Ready to scope a MVP Development build?
60-second AI consult and you’ll leave with a written plan. Prefer humans? Drop a custom quote request — we reply within a working day.