Free template · MVP proposal

MVP development proposal template

A proposal for a first version that exists to answer one question. It names the test, lists what's deliberately left out, and stops at a checkpoint where the founders decide what's next. Written out in full for a fictional delivery-route startup.

Sections
10
Estimate
8 lines, 108 hours
Example total
$13,068.00
Payments
30% / 40% / 30%
Proposal

Tallyroute: MVP for bakery delivery routes

Prepared for Tallyroute

Investment
From $13,068
Payments
3 stages

What the MVP has to prove

You believe small bakeries lose an hour every morning planning delivery routes on paper. The MVP has one job: show that ten pilot bakeries will plan their routes in Tallyroute every day for a month.

Everything below serves that test, and anything that doesn't is on the "not in v1" list.

In v1, and not in v1

In v1

  • Add the day's orders by hand or from a CSV
  • One-tap route for one or two drivers, on a map
  • A driver view on the phone: next stop, directions, mark delivered
  • Sign-in for the bakery owner and their drivers

Not in v1 (and why)

  • Payments and invoicing: the pilot is free
  • Native apps: the driver view is a web app added to the home screen
  • Integrations with order systems: CSV covers the pilot
  • Offline mode: worth it only if pilots ask

Scope of work

Shape

  • A one-week sprint to agree screens with you and two pilot bakeriesS-1
  • Clickable prototype tested with the pilots before we buildS-2

Build

  • Orders, routes and the driver view, as listed aboveS-3
  • Route planning with Mapbox (up to two drivers, 40 stops)S-4
  • Sign-in and roles for owners and driversS-5

Pilot

  • Set-up for ten pilot bakeriesS-6
  • Usage you can see: who planned routes, how oftenS-7
  • Fixes for what the pilots find, for four weeksS-8

Estimate

Fixed price for Shape and Build; the pilot support is capped at the hours below. The native-app wrapper and the analytics dashboard are optional.

TaskHoursRateAmount
Shape · 22 h$2,420.00
Shaping sprint and clickable prototype18$110.00$1,980.00
Testing the prototype with two pilots4$110.00$440.00
Build · 62 h$6,820.00
Orders: manual entry and CSV import14$110.00$1,540.00
Route planning with Mapbox22$110.00$2,420.00
Driver view on the phone16$110.00$1,760.00
Sign-in, roles and set-up10$110.00$1,100.00
Pilot · 24 h$2,640.00
Pilot set-up and usage tracking8$110.00$880.00
Pilot fixes (capped)16$110.00$1,760.00
Optional extras
Native app wrapper (iOS and Android)24$110.00+$2,640.00
Founder analytics dashboard10$110.00+$1,100.00
Subtotal$11,880.00
Contingency (10%)$1,188.00
Total$13,068.00

The learning checkpoint

Four weeks into the pilot we meet with the numbers: how many bakeries planned routes on how many days. Then you decide: build on it, change direction, or stop. Nothing after the checkpoint is committed in this proposal.

Timeline

Ten weeks: shape in week 1, build in weeks 2–6, pilot in weeks 7–10.

Payment schedule

  1. To startOn approval$3,920.4030%
  2. Ready for the pilotWeek 6$5,227.2040%
  3. Learning checkpointWeek 10$3,920.4030%

Assumptions and running costs

  • One founder joins a 30-minute check-in each week and answers questions within a working day
  • Running costs are yours and small at this size: hosting about $25 a month, Mapbox free up to its monthly allowance
  • You recruit the ten pilot bakeries; we help with the set-up
  • The code is written to be built on, not thrown away, but v1 is not built for thousands of bakeries

Terms

Invoices are due within 14 days. You own the code and the accounts from the first day. Anything added to v1 is quoted in writing and usually swaps with something on the list.

Next step

Approve below and we'll book the shaping week with you and your two first pilots.

A worked example for a fictional client. Every word and number is yours to change.

How to write each part

  1. Name the one thing v1 must prove

    An MVP isn't a small product, it's a test. Write the test as a sentence the founders agree with (“ten bakeries plan their routes in it every day for a month”), and use it to judge every feature request.

  2. Write the “not in v1” list

    The list of what's left out, with a reason for each, is the most useful part of an MVP proposal. It stops scope creep before it starts and shows the founders you've thought about later.

  3. Prototype before you build

    A clickable prototype tested with two real users in week one costs a few hours and saves weeks of building the wrong screens. Put it in the scope.

  4. Stop at a learning checkpoint

    End the proposal at the moment the founders have the numbers. Committing to version two before the pilot runs is guessing; the checkpoint makes the next proposal easy to write.

  5. Show the running costs

    Founders worry about the monthly bill. Give rough hosting and API costs at pilot size, and say they pay the providers directly.

Questions people ask

What should an MVP proposal include?

The question the MVP must answer, what's in version one and what's left out (with reasons), a prototype step, the build scope, a pilot with real users, a learning checkpoint, running costs, the timeline and the price. The template above has each part written out.

How much does an MVP cost to build?

It depends on the test, not the idea. A focused web MVP with three or four screens is often 100 to 200 hours; the example above is about 110 hours before its optional extras. Price it fixed, with a cap on the pilot fixes.

How long should an MVP take?

Long enough to run a real pilot: around six weeks to build and four to pilot is common. If it takes six months, it's not an MVP any more.

Should an MVP be fixed price?

Usually, yes, for the build: a short “not in v1” list makes the scope clear enough. Keep pilot support capped in hours so changes found by real users don't become open-ended.

Can I download this MVP proposal template?

Yes: download it as Markdown for Google Docs, Notion or Word, or open it in Devposal and send it as a link your client approves online.

Related