1. 1Page 1Cover: the outcome title, three app screens (home, book a make-up, progress) standing on a pool, and the front matter: prepared for and by, investment, valid until
2. 2Page 2Summary: the calls problem and its cost, three objectives from baseline to target with their worth, the release map of MVP against Release 2 against later in five lanes, then the recommendation, price, timeframe and next step
3. 3Page 3What’s happening now: front-desk calls by reason with the share the MVP removes, calls by hour, what 1,140 parents said, re-enrolment by term, why families left and what a point of re-enrolment is worth
4. 4Page 4Who it’s for: parents, centre managers and front desks with their jobs, how they work today and success at launch, the absence-to-make-up journey today and with the app, and the assumptions discovery will test
5. 5Page 5MVP scope: the ten launch features, each with its user story, acceptance criteria, sprint and size in points, the platform work under them, and what is not in the MVP
6. 6Page 6Release 2 and later: each Release 2 feature with why it waits and what will decide it, the May review’s four gates and three paths, the priced Release 2 option and the later list
7. 7Page 7Technical approach: an architecture diagram (the app, the notice console, the API layer in AWS Sydney, the enrolment system, push and SMS), the main decisions, security and children’s privacy, and the component register with licences
8. 8Page 8Delivery plan: discovery, design, five two-week sprints, staff and family betas, store review and the warranty as a Gantt with the payment milestones, what each sprint demo shows, how a sprint runs and the risks we’re watching
9. 9Page 9Team and working together: five people with their roles and days a week by phase, how the two teams keep in touch, the tools Bluewren can see, and what Bluewren provides by when and what it holds up
10. 10Page 10Quality, launch and support: the device list, accessibility to WCAG 2.2 AA, the three-pool family beta, store submission and launch week, the 60-day warranty and the care plan’s response times
11. 11Page 11Investment: the fixed price of each phase over the sprint timeline, five payment milestones with their acceptance tests, the Release 2 option, the care plan and the running costs Bluewren pays directly
12. 12Page 12Terms and acceptance: eleven terms in plain words, the dated steps from signature to sprint 1, the acceptance statement and both signing blocks, the studio’s pre-signed

1. Step 1

   Put your studio, the client and the dates on the cover, and redraw the three phone screens around their app.

2. Step 2

   Rewrite the problem page and the MVP stories from your discovery, keeping each acceptance test specific.

3. Step 3

   Adjust the sprints, team and timeline, then check the plan, the investment timeline and the payment milestones still agree.

4. Step 4

   Set your phase prices and terms, then send it as a link or PDF for signature.

Start from the Mobile App Development Proposal now.

Customise with Docsiv AIOpen in the editor

• 

  Executive Search Proposal

  Proposals·13 pagesPreview
• 

  Design Proposal

  Proposals·14 pagesPreview
• 

  Brand Identity Proposal

  Proposals·15 pagesPreview
• 

  Website Proposal

  Proposals·16 pagesPreview
• 

  Consulting Proposal

  Proposals·16 pagesPreview
• 

  SEO Proposal

  Proposals·16 pagesPreview

Starting from a description instead? Try the Proposal maker.