Launch My MVP
Menu

Process

How a 48 hours MVP build actually works

Six steps, two of which happen before any code is written. That front-loading is the whole reason a weekend build is possible.

Short answer

A 30-minute discovery call decides whether your idea fits a 48 hours build and which three features make the cut. You approve a one-page written scope with a fixed $3,500 AUD price, pay a $1,750 AUD deposit to hold a build slot, and the build runs Friday to Sunday as one uninterrupted sprint. It ends with a demo, the repository transferred to you, and seven days of free bug fixes.

  1. Book a 30-minute discovery call

    30 minutes

    Book a 30-minute call. You explain the problem, who has it, and what the first version needs to do. The call ends with a blunt yes or no on whether the idea fits a 48-hour build, and if it does, which three features make the cut.

    What you get
    A go or no-go answer, and a shortlist of the three features worth building first.
    Your part
    Turn up with the problem you are solving. You do not need a spec, wireframes or a tech opinion.

  2. Approve a fixed scope in writing

    Same day

    You get a one-page scope document in plain English: the three features, what each one does, what is explicitly out, and the delivery date. Nothing is built until you approve it. Once approved, the scope does not move and neither does the price.

    What you get
    A one-page written scope with a fixed $3,500 AUD price and a fixed delivery date.
    Your part
    Read it and push back on anything that is wrong. This is the cheapest moment to change your mind.

  3. Pay the deposit to hold a build slot

    2 minutes

    A $1,750 AUD deposit holds your build slot in the calendar. Payment runs through Stripe, and the balance is not charged until after the demo and handover.

    What you get
    A reserved build weekend with a confirmed start time.
    Your part
    Pay the deposit and send over any accounts the build needs, such as a domain or an API key.

  4. The 48-hour build sprint

    48 hours

    The build runs Friday morning to Sunday evening as one uninterrupted sprint: interface, database, authentication, integrations, payments and deployment. You get a progress update at the end of each day with a link to the live site as it stands, so nothing is a surprise on Sunday.

    What you get
    A deployed, working web application on a real URL, updated as the build progresses.
    Your part
    Answer a question or two if something needs a decision. Otherwise, nothing.

  5. Demo, handover and code transfer

    30 minutes

    A 30-minute call walks you through the product, how to run it, how to change the content, and where everything lives. The GitHub repository transfers to your account with full history, and the deployment moves to your own hosting account.

    What you get
    Full code ownership, admin access to hosting, and a recording of the walkthrough.
    Your part
    Pay the balance once you have seen it working, and create a free GitHub and Vercel account if you do not have one.

  6. Seven days of bug fixes

    7 days

    Real users find things a build never will. For 7 day bug fix window after handover, anything broken gets fixed at no extra cost. New features are quoted separately, or you can take the code to any developer.

    What you get
    A week of free fixes while the first real users hit the product.
    Your part
    Send bugs as you find them. Screenshots help.

Why the preparation matters more than the sprint

The part of this process that does the work is steps one and two. By the time the build starts there are no open questions: the scope is written down, the architecture decisions are already made because the same stack is used every time, and every account and API key the build needs has been collected.

A build that begins with open questions is not a 48 hours build. If you are comparing anyone offering a rapid build, the question worth asking is whether the scope is fixed in writing beforehand — the answer tells you whether the timeline is a plan or a hope.

There is a full hour-by-hour account of what happens during the sprint in the 48-hour MVP playbook, including the five things that are deliberately left out.

Before you book

Two things make the discovery call much more useful. First, one sentence describing what a happy user would have achieved. Second, an honest note on your deadline and budget — hiding either just wastes the call.

Ready to find out if your idea works?

A 30-minute call ends with a straight answer on whether your idea fits a 48 hours build, and which three features make the cut. No obligation, no pitch deck.

Fixed $3,500 AUD. Scope agreed in writing before anything is built.