Validating a new product
You have customer conversations and a strong hypothesis, and need a real product in front of users rather than another prototype.
Package
From idea to a launched MVP.
Take one clear product idea to a working release your first users can try. We handle scope, design and engineering, and we keep the build small enough to launch.
Duration8 to 12 weeks
FormatFixed-scope product build
Best forFounders and product teams
OutcomeA launched, supported MVP
Overview
Small enough to launch, real enough to learn from.
An MVP is not a smaller version of the final product. It is the shortest path to finding out whether people want what you plan to build. That means choosing a narrow first audience, one or two core jobs and the few screens needed to do them well. We treat that boundary as a feature, not a limitation.
We work in short iterations with a demo every week or two, so you always know what exists and what does not. Design, engineering and testing move together, and the release includes the operational basics: accounts, payments where needed, analytics and a way to support users from the first day.
Scope cut to what matters
We agree the first audience and the two or three jobs the product must do, then hold that line as the build starts.
Design and build in one team
Product design, front end and back end sit together, so decisions are made in hours rather than handed between vendors.
Weekly working software
You see a running build at every review, not a slide deck, and your feedback shapes the next iteration.
Launch basics included
Accounts, payments where relevant, analytics, error tracking and a support path are part of the first release.
Built to continue
Code, tests and infrastructure are set up so a later team can extend the product without starting again.
A launch plan, not a surprise
We prepare the release, the rollback and the first week of support before anyone invites users in.
Use cases
Where this program fits
Best for a first release with a real audience, a clear problem and a decision still to be tested.
Replacing a manual service
A service runs on spreadsheets and email today, and a focused web app would remove the worst of the busywork.
A second product line
An established team wants to test a new offering without pulling its main engineers away from the core product.
A rebuild before launch
An early build has stalled or grown messy, and the fastest path is a clean, smaller version with a firm scope.
Deliverables
What you receive.
- A defined first audience and release scope
- Product design for the core screens
- A working web application in production
- Accounts and payments where needed
- Analytics, error tracking and monitoring
- A launch plan and first-week support
- Documentation and a clean handover
How we work
How the weeks are arranged.
Weeks 1 to 2: Scope and design
We define the first audience, the core jobs and the release boundary, then design the main screens and the data model.
Weeks 3 to 5: First build
Engineering starts on the core flow while design fills in the remaining screens, with a demo at the end of each week.
Weeks 6 to 9: Complete the flow
We add accounts, payments where needed, notifications and admin tools, then test the whole path with real scenarios.
Final weeks: Launch
We prepare the release, monitoring and support, launch to a small group and fix what the first users find.
FAQ
Common questions.
What if we already have designs?
We can start from them and keep what works. We will still review the scope and the flows, since a launch usually reveals gaps in a static design.
Will the MVP be ready to scale?
It will be ready to continue. We build for a small first audience and avoid shortcuts that would block growth, without over-engineering for users you do not have yet.
Who owns the code and accounts?
You do. The repository, cloud accounts and third-party services are in your name from the start.
What happens after launch?
Some teams continue into a dedicated engineering team, others take the code in house. We plan the handover either way.
Can you work with our existing team?
Yes. We can lead the build, join your team or work alongside an in-house developer, depending on what you need.
Next step
Start the conversation
Have a product idea ready to test?
Send us a short description of the idea and the audience. We'll reply with a view on scope and the right first release.