A working core
Build the agreed key journey end to end, with the frontend, backend, data storage, and essential behavior your first users need.
Product builder / 02
A focused week of building time, scoped around your idea.
7 days.
A working
MVP.
One senior product builder spends seven focused build days shaping the idea, building its useful core, and getting a first version ready for users.
Discuss your MVPThe point
A real thing changes the conversation.
Skip the long feature list. Build the smallest useful version, put it in real hands, and learn what deserves to come next.
01 / Show it02 / Test it03 / Decide
What you get
Something
you can use.
Ready to learn
Get a deployed first version, a walkthrough, the repository, a prioritized backlog, and a recommended next step.
Fixed price · excl. VAT
EUR. 16.799A working MVP, deployment, a walkthrough, the repository, and a recommended next step. Preparation and handover included.
The route
A clear route
to a working MVP.
- 01 / SCOPE
Scope and choices
Define the user, core problem, must-have journey, and technical constraints. Decide what the MVP will leave out.
- 02 / DESIGN
UX and architecture
Shape the screens, data, and integrations. Agree the smallest path that can work end to end.
- 03 / BUILD
Build the core
Use seven focused build days to deliver the agreed core journey. Share progress, surface risks, and review scope at 75% of the build effort so there is room to finish properly.
- 04 / HANDOVER
Demo and hand over
Walk through the deployed MVP, hand over the repository, and agree a recommended next step. Preparation and handover sit outside the seven build days and are included in the package price.
Seven days of focused effort
Fixed price.
Built to use.
We agree the outcome and scope up front, then schedule seven focused build days around availability, access, and feedback. Preparation and handover are included in the price, and we agree the delivery date before starting.
Focused build effort7 days
7 days
00 / Start75% / Check07 / Finish
The right fit
Built to work.
Ready to learn.
For founders
Get a first useful version into users’ hands and learn whether the problem and solution are worth pursuing.
Keep it focused
Seven build days can deliver a useful MVP, not every feature on the roadmap. We agree the effort, set a clear boundary, and make trade-offs together.
For product teams
Move a promising product idea into a working slice you can put in front of customers and use to guide the next investment.
Questions, answered
The short version.
Will this be ready next week?
Not necessarily. The offer is for seven focused build days of 24 hours. These measure effort, which can be spread over multiple calendar days. Preparation and handover is included in the price. We agree the delivery date before starting, based on availability, access, and feedback.
Will this be production-ready?
The goal is a working MVP you can put in front of users. The level of polish, security, scale, and operational readiness depends on the idea and must be part of the agreed scope.
Do you test it with my customers?
Customer interviews and user testing are included only if we agree them as part of the scope. Otherwise, you can use the MVP to run those conversations yourself.
What if the whole idea does not fit?
It probably will not, and that is okay. We choose the smallest useful version together, review scope during the week, and leave lower priorities for later.
Do I need a detailed specification?
No. The intake helps us find the question worth answering. We agree the priorities and access before the build begins.
Who gets the work afterward?
You get the deployed MVP, a walkthrough, the project repository, a prioritized backlog, and a recommended next step. We can also discuss support for the next iteration.
Start here
What would you
like to make real?
Who is it for, what should they be able to do, and what are you unsure about? A few lines are enough to start.
Discuss your MVP