Services

MVPs Built in Weeks

A first version real people can use, built in weeks rather than quarters.

1 to 3 weeks6 things covered
HomeServices

Overview

The smallest version of the idea that real people can actually use, built well enough that you keep it rather than throw it away. Scope gets cut to what proves the thing, and the rest waits until somebody has asked for it.

  • Build
  • 1 to 3 weeks
  • 5 tools

Covers

06
  • Scoping
  • Core flow
  • Accounts
  • Payments
  • Analytics
  • Launch

Who it suits

03
  1. Founders testing an idea before raising
  2. Anyone quoted three months for a first version
  3. Teams with a spec that keeps growing
01

What you get.

4 included
Included1 to 3 weeks
  1. A scope agreed before anything is built
  2. One core flow working end to end
  3. Accounts, payments and analytics where needed
  4. Something you can put in front of users
Built by Denney
02

How it runs.

1 to 3 weeks

Share of the work, by the weight of each stage.

  1. 17%

    Cut

    Everything not needed to prove the idea comes out of version one.

    Days 1 to 2
  2. 66%

    Build

    One core flow end to end, working properly rather than four half done.

    Weeks 1 to 2
  3. 17%

    Launch

    In front of real users, with enough analytics to tell you what happened.

    Final days
03

Built with.

5 tools
  • Next.jsFramework
  • ReactInterface
  • SupabasePlatform
  • PostgresDatabase
  • StripePayments
04

What to check.

Scope, up front

Version one or everything

Side by side

Version one

  • One flow, working properly
  • In front of users this month
  • Changed once you know something

Everything at once

  • Six flows, all half finished
  • In front of users next quarter
  • Changed after you have paid for it

What this is not

3 excluded
  • Everything on the roadmap, in version one
  • A throwaway prototype you rebuild next year
  • A pitch deck or a fundraising story
05

Seen in the work.

1 project
gosu.ggOpen beta
Case study

GOSU

Permanent PUBG match archive with replays rebuilt from telemetry.

What it proves
A data source that deletes itself after fourteen days, ingested and kept, then rebuilt into watchable replays from the raw telemetry.
Outcome
A record that survives the API deleting it.
Next.jsPostgres
06

Where it is asked for.

1 town

Also build

12 more in all
Web Apps1 to 4 weeks · 5 tools sharedWordPress1 to 3 weeksPlugins3 days to 2 weeksElementor3 days to 2 weeks

Sounds like what you need? Now taking new projects.

Get in Touch