20-Day MVP

A first version your customers can use, live in 20 working days.

$20,000 to $35,000 fixed. 20 working days. Starts with a $3,500 discovery sprint.

One core workflow, designed, built and launched on web or mobile in four weeks. Not a clickable mockup and not a demo. Something real people can sign up for and use, so you can learn whether the idea holds before you spend more.

Book a free 30-minute call

This is for you if

You have a clear idea and a deadline: a pilot customer, an investor meeting, a trade show, a board date.
You need to test one thing with real users before committing to a full build.
You want a price and a date before you start, not an estimate that grows.
Your in-house team is busy with the main product and this would sit in the queue for months.

What ships on day 20

One core workflow, end to end. The thing your product exists to do, working from sign-up to result.
Design. Clean, usable screens built on a standard component library, so the budget goes into the product, not pixels.
Sign-in and accounts. Secure authentication from day one.
A production environment. Deployed, monitored and backed up. Live on the web, or submitted to the app stores where mobile is the right call.
The basics done properly. Error tracking, logging, a tested restore, and automated tests on the main path.
Handover. Your repository, your accounts, documented so anyone can pick it up.

Not included: every feature on your wish list. The discovery sprint decides the one workflow that matters. Everything else goes on a list for later, with a price next to it.

It starts with a discovery sprint

$3,500 fixed. 2 to 5 days.

We work with you to define the one workflow, the users, the screens and the technical approach. You get:

A written scope: what is in, what is out, and why.
Wireframes of the main screens.
A fixed price and a start date.

The scope is yours to keep. If you go ahead with us, the $3,500 comes off the build price.

What happens each week

Week 1.
Foundation: accounts, data, deployment pipeline, first screens.
Week 2.
The core workflow takes shape. You use it in staging.
Week 3.
The workflow is complete. We fix what you found and polish.
Week 4.
Testing, production release, handover.

Every week: a release you can use, a written update, and a 30-minute call.

What you own at the end

All code, in your repository.
All infrastructure and accounts, in your name.
Full intellectual property rights.
30 days of support for questions after launch.

Work we have shipped

See the portfolio

Questions

Is 20 days really enough?

For one workflow, yes. The constraint is the point: it forces the decision about what matters most, which is the decision most early products get wrong.

What if we need more than one workflow?

Then it is a Product Build, and we will tell you that in the discovery sprint rather than squeezing it into 20 days.

What happens after launch?

You can take it anywhere. Many clients keep going with us on a second fixed-price phase, or on monthly ongoing support. There is no obligation either way.

Do you use AI to build it?

Yes, for the mechanical parts: scaffolding, tests, documentation. Senior engineers make every design and architecture decision and review every line that ships.

Tell us what the first version has to do.

Thirty minutes is enough to tell you whether it fits in 20 days.