Start a project

Floor 01 · Build

MVP development company that ships in weeks.

MVP development means shipping the leanest version of your product that strangers will sign up for and pay for. As an MVP development company, yop scopes it with you, builds it in short cycles and puts it live, so you learn from customers instead of from slides.

Scope cutter

What goes in, what waits.

Move features between “In the MVP” and “Later”. Five is a healthy first version.

In the MVP 0

Later 0

    Tap a feature to move it.

    Ready?

    Is your idea ready for an MVP?

    An MVP pays off when there is one clear thing to learn and someone ready to learn it. Check both lists before you book a workshop.

    Ready if

    • you can say in one sentence what users will do in it.
    • you can reach the first twenty users yourself.
    • you know which number would make you continue or stop.
    • you accept that version one will look small on purpose.

    Not yet if

    • the full feature list is fixed and nothing may move to Later.
    • nobody outside the team has heard the idea yet: talk to five buyers first.
    • the launch date matters more than what you will learn from it.

    Cut by question

    Name the question, the cut follows.

    A first version exists to answer one question. Choose the question and watch which features make it into version one.

    Scope by question

    The one question

    Will people sign up?

    The one number

    Share of visitors who sign up

    • Landing pageVersion one
    • Sign-upVersion one
    • The core taskLater
    • CheckoutLater
    • Reminder emailsLater
    • Usage trackingVersion one
    • Admin panelLater
    • Native appLater

    Version one: 3 of 8 features

    A typical cut

    Small on purpose, real from day one.

    Which features usually belong in a first version
    FeatureFeatureIn the MVPLater
    Sign-up and loginYes—
    The one core taskYes—
    PaymentsIf you charge from day onePlans and invoicing
    Admin panelBasicFull roles and reports
    IntegrationsOne that mattersThe rest
    Mobile appResponsive web firstNative apps

    How to build an MVP

    How to build an MVP without the wasted year.

    To build an MVP, name the one thing you need to learn, cut the product down to the task that proves it, and put it in front of paying users as early as you can.

    v0.1
    01

    Name the risk

    Write the single belief that, if false, would kill the product. That belief is what the MVP tests.

    v0.2
    02

    Cut the scope

    Keep sign-up, the core task and payment. Everything else moves to Later, even the features you love.

    v0.3
    03

    Design the flow

    Clickable screens for the core task, tried by five real users before any code is written.

    v0.4
    04

    Build and ship

    Short cycles with a live staging link. The first version goes to real users, not to a demo day.

    v1.0
    05

    Measure and decide

    Watch what users do, not what they say. Then build the next feature, change course or stop.

    After launch

    The first weeks with real users.

    Shipping is the middle of an MVP, not the end. This is how the weeks after launch usually run, and what you and we each do in them.

    Launch day

    Live, not a demo

    Version one goes to real users with tracking switched on and a way to reach you inside the product.

    Week 1

    Watch

    We read the sign-ups, the drop-off points and the first messages with you. No new features yet.

    Week 2–3

    Talk

    Short calls with users who stayed and users who left. Their words decide the next change.

    Week 4

    Decide

    Build the next feature, change course or stop, based on the one number you named at the start.

    What you get

    At the end of the MVP.

    Version one is more than an app on a link. These are the pieces you keep, whatever the numbers say.

    The live product

    Real software on your domain that strangers can sign up for, use and, if it is the question, pay for.

    Code that can grow

    A clean repository in your account, built so the next features land on top of it instead of beside it.

    The number, tracked

    The one measure you chose, counted from the first visitor, with the events behind it.

    Learning notes

    What users did, what they said and what surprised us, written up for your team and investors.

    Next list

    The features that waited, now ranked by what users actually asked for.

    Common traps

    MVP advice we push back on.

    We often hear

    “Make it perfect before anyone sees it.”

    What we see

    Polish costs weeks and teaches nothing. Users forgive a plain screen; they leave when the core task does not work.

    We often hear

    “An MVP is a cheap prototype.”

    What we see

    A prototype shows an idea. An MVP is real software people sign up for and use, built so the code can grow if the answer is yes.

    We often hear

    “More features, more chances.”

    What we see

    Every extra feature blurs the result. With one core task you know exactly what users came for, or why they left.

    Your first version

    Cut the scope, ship the core.

    Bring the idea. We help you decide what goes into version one and what can wait.

    Questions

    Before you write a line of code.

    How long does an MVP take?

    Most first versions we scope fit into a few weeks of build time. The exact number comes out of the discovery workshop, not out of a template.

    No. A prototype shows an idea; an MVP is real software that real users can sign up for and use.

    One team, because it owns the whole path: scope, design, code, launch and the data to decide what comes next. At yop the same small team carries it from sketch to launch, so nothing falls between freelancers.

    It depends on the core task and the integrations it needs. After a discovery workshop we give a fixed price for the first version, so the budget is known before the build starts.

    Sign-up, the one core task and a way to measure whether people use it, plus payment when charging is the question. Everything else waits until users show which feature they need next.

    We read the numbers with you and choose one of three paths: build the next feature, change course or stop before more money goes in. When the idea works, the MVP code usually grows into the full product instead of being thrown away.

    It can, but a responsive web app is usually faster to ship and change, and it needs no store review. We start native when the main task leans on the phone itself: the camera, location or working without a signal.