An MVP in six weeks – how we do it

When we say there’ll be a usable first version after six weeks, people often ask: so what gets dropped along the way? The honest answer: quite a lot – and on purpose.

The core comes first

Every product has a core that shows whether the idea holds up. For a booking tool, that’s the booking, not the reporting. For a portal, it’s the one workflow users need every day. Everything else waits.

What happens in those six weeks

1. Week 1 – scoping it together: what goes into the first version, and what doesn’t?
2. Weeks 2–5 – building in short cycles, with something you can see every week.
3. Week 6 – polishing, real data, first users on board.

Why this isn’t throwaway code

A narrow scope doesn’t mean poor quality. What we ship is tested and maintainable – it’s the foundation for everything that follows. What we leave out is features, not care.

And after that?

Once the first version is live, feedback decides what comes next. After six weeks, the roadmap often looks quite different from the original plan – and that’s the whole point.