New product build · MVP launch sprint
Build the proof, not the whole platform.
You bring the problem, domain knowledge, and access to the first users. I cut the idea to its critical journey, build a working product, and put it in users’ hands so you can decide what deserves further investment.
When it fits
The signs this is the work.
- You understand the problem and can reach a small number of people who experience it.
- You have useful domain knowledge but no product team ready to turn the idea into a working release.
- A prototype, specification, or AI-generated demo exists, but users cannot yet rely on it as a product.
- You want evidence from real use before funding, hiring for, or commissioning the full platform.
What changes
A product, evidence, and a decision.
A live first product
One critical user journey working end to end on a real URL, with enough quality for controlled early use.
Evidence, not opinion
Basic analytics, feedback capture, and a defined validation question so early use produces a decision.
A foundation you own
Source code, infrastructure, documentation, and deployment accounts handed over without platform or supplier lock-in.
How the work runs
From idea to first users.
Days 1-5: define the proof
Name the target user, the problem, the riskiest assumption, the critical journey, and everything the first release can leave out.
Weeks 1-4: build the journey
Design and build the smallest coherent product, share working releases as it develops, and deploy it in an environment you control.
Launch: learn and decide
Put it in front of early users, review what they do, and decide whether to stop, change direction, iterate, or build the broader platform.
What ships
Enough product to produce a real answer.
- A written validation brief and explicit feature cut list.
- The critical user journey in a clean, responsive web product.
- The back end, data model, and only the authentication, payments, or integrations the test requires.
- Founder administration, basic analytics, and a route for early-user feedback.
- Deployment in accounts you control, with source code, documentation, and handover.
What waits
The first release is deliberately incomplete.
- Every feature imagined for the eventual platform.
- Native mobile applications unless the validation genuinely depends on them.
- Complex permissions, integrations, or automation that can be handled manually during the test.
- Enterprise-scale architecture or compliance work before the market evidence requires it.
Example scopes
Small enough to launch. Complete enough to test.
These are examples of the shape of a focused first release, not claims about previous client projects.
B2B workflow product
A customer submits work, the business manages it through one defined process, and both sides can see the result without email and spreadsheets.
AI-assisted expert service
Structured intake, controlled AI processing, expert review, a usable customer output, and the measurements needed to test quality and willingness to pay.
Focused marketplace test
One side creates demand, the founder fulfils or matches supply manually, and the product tests whether the transaction and repeat behaviour exist.
Relevant evidence
From product idea to an enterprise AI platform.
As founder and CEO of Eclipse, I built the CASi multi-agent engine, dashboard, data model, and production pipelines as well as defining the commercial product and operating the business.
See my experienceInvestment
Fixed scope. Predictable investment.
The definition sprint is £1,250 and is credited against the build. A focused MVP typically takes three to six weeks and falls between £6,000 and £15,000, quoted at a fixed price once the scope is explicit.
After launch
The next decision follows the evidence.
If the signal is weak, stop or change direction. If it is strong, I can continue into iteration, the full platform build, or the operating structure needed as customers, delivery, and the team begin to grow.
Questions
What buyers usually need to know.
- What kinds of MVP do you build?
- The strongest fit is a focused web product: B2B SaaS, AI-assisted services, workflow products, expert tools, and tightly scoped marketplaces. The first release needs one identifiable user and one critical journey that can be tested end to end.
- How quickly can an MVP be launched?
- A focused build will typically take three to six weeks after the scope is agreed. The timeline depends on the number of user roles, integrations, data requirements, and whether payments or regulated information are involved.
- How much does an MVP build cost?
- The definition sprint is £1,250 and is credited against a subsequent build. Most focused MVP builds fall between £6,000 and £15,000 at a fixed price once the validation question and scope are agreed.
- Do I own the source code and infrastructure?
- Yes. The repository, deployment, data, and relevant service accounts sit in environments you control. The engagement includes documentation and a handover suitable for continued development by me, an internal hire, or another engineering partner.
- Can the MVP become the full platform?
- Often, but that is not assumed. The first build is structured cleanly enough to continue when the evidence supports it. If the evidence changes the product direction, the right decision may be to revise or replace parts rather than preserve the first scope at any cost.
Next step
What does the first release need to prove?
I will reply personally and tell you whether this is the right engagement.
Tell me what you want to prove