Skip to content

MVP sprint

A focused first version of a new product

An MVP sprint builds the smallest useful version of a new product, so you can put it in front of real users and learn what to build next.

Introductory MVP sprints are available for suitable projects. Eligibility, features, price, start date and timeline are confirmed after we review your idea.

Usually a good fit

  • One core user journey that you want to test with real users
  • A web application or a React Native mobile app
  • A simple backend: accounts, data storage and an admin view
  • A founder or business owner available to make decisions quickly

Usually better as a regular project

  • Several user roles or complex permissions
  • Many third-party integrations, or integrations without good documentation
  • Payments, health, financial or other regulated data
  • Rebuilding or extending an existing product

How a sprint works

  1. Step 1: Share your idea

    Describe the problem, the users and the one thing the first version must do.

  2. Step 2: Review and scoping call

    We ask questions, suggest what to leave out, and tell you if the idea is better suited to a regular project.

  3. Step 3: Written scope and quote

    You receive the features, exclusions, price and timeline in writing. Nothing starts until you agree.

  4. Step 4: Build, hand over and decide

    We build and hand over the agreed scope. You then decide whether to continue to a next phase.

Agreed in writing before we start

So that both sides know exactly what the sprint covers:

  • The features included, and the features that are not
  • The price and payment terms
  • The start date and the delivery timeline
  • Who pays third-party costs such as hosting, app store accounts and paid APIs
  • How feedback rounds work and how many are included
  • What support, if any, is included after delivery