Mobile Build / Cutaway

A fixed-price mobile app proposal: the client’s situation, a recommended iOS and Android build of the core customer journey, a four-stage build process, the team, client results, supported devices and exclusions, a 16-week timeline, common questions and milestone pricing.

Mobile App Development Proposal

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Introduction</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Hello {{CLIENT_NAME}},</p>
<p>Thank you for taking us through your product and your plans for mobile. Your customers already reach {{CLIENT_COMPANY}} on their phones, but today they do it through a mobile website that was not designed for the way they use your service.</p>
<p>This proposal sets out the app you get on iOS and Android, the devices it supports, the 16-week schedule, the fixed price and what your team needs to provide. The decision we are asking you to make is to approve the fixed-price build.</p>

<p style="font-family:var(--proposal-font-accent);font-size:clamp(20px,2.1cqw,23px);line-height:1.4">{{SELLER_NAME}}</p><p>Product lead, {{SELLER_COMPANY}}<br>{{SELLER_EMAIL}}</p>

Introduction

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Our recommendation</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">We recommend one app for iPhone and Android, built from a single codebase around booking and payments. You also get saved sign-in, push notifications and offline handling, designed for your customers and tested on the devices they use.</p>

<p><strong>What the build includes</strong></p>

24 Designed screens

2 Store releases

16 Weeks to submission

Planned scope

Our recommendation

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Your situation</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Here is your situation as you described it to us. If anything has changed since your call, tell us and your proposal will be updated.</p>

<p>Most of your traffic is mobile, and the steps your customers repeat every week take longer on your mobile site than they should.</p>

Your customers are mostly on phones

<p>Your customers have to sign in again, retype details and wait for pages to load, and many leave before they finish.</p>

Customers drop out mid-journey

<p>Without an app you have no push notifications, so your reminders and updates depend on email that your customers often miss.</p>

You cannot reach customers directly

Bookings by channel, last 90 days, % of all bookings

Your situation

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">How we build</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">The project has four parts. You review and approve each one before the next begins.</p>

<p>Two workshops turn your core customer journey into user flows, a feature list and acceptance criteria you sign off.</p><ul><li>User flows for each step</li><li>Acceptance criteria</li><li>API gap list</li></ul>

Specification

<p>A clickable prototype tested with five of your customers, then final designs for all 24 screens.</p><ul><li>Native iOS and Android patterns</li><li>Two rounds of changes</li><li>Empty, error and offline states</li></ul>

Design

<p>One React Native codebase connected to your existing API, with a working build on your phone every two weeks.</p><ul><li>Sign-in and saved sessions</li><li>Apple Pay, Google Pay, cards</li><li>Push notifications and offline</li></ul>

iOS and Android build

<p>Every key journey is tested on 12 physical devices, then your team tests the beta before we submit both apps.</p><ul><li>Permissions and offline checks</li><li>TestFlight and Play beta</li><li>Store listings and submission</li></ul>

Testing and release

How we build

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">What is included</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Everything the fixed price covers, the devices the app supports, and what it does not cover.</p>

Specification, user flows and acceptance criteria

Clickable prototype and 24 screen designs

iOS and Android app from one React Native codebase

Integration with your existing API and payments

iPhone on iOS 16 and later

Android phones on Android 10 and later

Testing on 12 physical devices

Store listings and submission to both stores

60 days of fixes after release

Guaranteed approval by Apple or Google

Tablet layouts, wearables and older OS versions

New backend features or API changes

What is included

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Timeline</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Work starts on {{KICKOFF_DATE}}. Each stage ends with a review, so you approve the work before the next stage begins.</p>

<p>Workshops, user flows, feature list, acceptance criteria and a review of your API.</p>

Discovery and specification

<p>Clickable prototype, tests with five customers, then final designs for all 24 screens.</p>

<p>Four two-week sprints. You see a working build on your own phone at the end of each one.</p>

Build

<p>Device testing, your acceptance testing, fixes, store listings and submission to both stores.</p>

Testing and submission

Timeline

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">{{SELLER_NAME}} is your main contact. The same core team works on your app from the first workshop to submission.</p>

<p>Runs the workshops and reviews, owns the specification and schedule, and is your day-to-day contact.</p>

Product lead

<p>Designs the prototype and every screen, and runs the tests with your customers.</p>

Product designer

<p>Leads the React Native build, the API integration, device testing and both store submissions.</p>

Lead mobile engineer

Your team

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Client results</span></h2>

<p>A similar customer journey, the scoped mobile experience and the evidence reviewed at release.</p>

Client results

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Questions</span></h2>

Questions

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Pricing</span></h2>

<p>Three options. We recommend Full app. Choose an option and any extras on this page.</p>

<p>Prices are in USD and exclude tax. 30% is due on approval, 20% when the designs are approved, 30% when the beta builds are delivered and 20% on store submission.</p>

Sign-in, booking and payments on iOS and Android, without push or offline.

Core app

Full app

Plus three months of fixes, small changes and a monthly review after release.

Full app and launch support

<p>Apple and Google developer account fees are paid by you directly. This proposal is valid until {{VALID_UNTIL}}.</p>

Pricing

<h2 style="font-weight:600;line-height:1.1"><span style="font-size:clamp(28px,4.2cqw,44px)">Next steps</span></h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">How we get started once you approve the fixed-price build.</p>

<p>Accept on this page, or reply to this email. We send the first invoice for 30%.</p>

Approve the proposal

<p>Within five working days we hold the first workshop and collect API documentation and store account access.</p>

Kickoff and access

<p>By the end of week two you review the user flows, feature list and API gap list.</p>

Specification review

<p>Questions? Contact <strong>{{SELLER_NAME}}</strong> at {{SELLER_COMPANY}}<br>{{SELLER_EMAIL}}</p>

Mobile App Development Proposal - Preview