One hypothesis
Together we name the user behavior that would prove or disprove the idea. Anything that does not affect that stays out of the first version.
An MVP is the shortest working version of a product that tests the main hypothesis on real users. It is not a cut-down mockup or a pitch deck: a person can sign up, complete the core flow and pay, when payment is what the test is about.
We help name exactly what is being tested, cut everything that does not change the answer, and ship the first version in weeks. The estimate is fixed for the agreed scope: if we underestimate it, that cost is ours.
Together we name the user behavior that would prove or disprove the idea. Anything that does not affect that stays out of the first version.
We design the screens and states a user needs to reach the target action. We do not draw the rest.
We write down what is in the first version and what is deliberately postponed. That list becomes the estimate.
A web or mobile app with the core flow, sign-up and data that is actually stored.
If the hypothesis is about money, we connect payments. Events in the core flow show up in analytics.
Production environment, deployment and monitoring. After release you can invite users immediately.
Before launch we agree which events answer the hypothesis. The next stage is decided from those.
If the hypothesis holds, we extend the product on the same codebase. If it does not, we do not build what turned out to be unnecessary.
After launch we either keep running the product or transfer the code, designs and documentation to your team.
We dig into the business goal, users and constraints — free of charge.
The team estimates every task with planning poker. The price is fixed for the agreed scope: if we underestimate, that’s on us. New requests are estimated separately.
A shared Slack channel, regular demos and progress you can see — no black box.
We ship to production and stay on call 24/7 — or hand over cleanly to your team.