01 / THE BRIEF

From idea
to interaction.

ONE FOCUSED FIRST RELEASE

Deliver an Android MVP for [primary audience] with account access, a core workflow and notifications. Confirm the supported Android versions, devices and integrations during discovery.

DEFINE.
BUILD.
RELEASE.

02 / SCOPE OF WORK

One product.
Four workstreams.

01

Product and UX

Document user journeys, acceptance criteria and a prioritised release backlog. Produce clickable prototypes for the agreed core screens and include two review rounds.

02

Android application

Build sign-in, profile management, [core workflow], status views and push notifications. Use an agreed architecture and connect to the documented client-provided API.

03

Quality and release

Test the agreed journeys on the approved device matrix, resolve release-blocking defects and prepare the store listing package. Store review outcomes remain outside the delivery team's control.

04

Handover and support

Provide source code, build instructions, release notes and one knowledge-transfer session. Include a 30-day defect correction period against the signed acceptance criteria.

03 / DELIVERY PLAN

A build you can follow.

01

Define

[Dates] / backlog and UX approval.

02

Build

[Dates] / regular demonstrations.

03

Release

[Dates] / acceptance and handover.

04 / COMMERCIAL SCHEDULE

Your product.
Your investment.

Invoice at the agreed milestones: kickoff, feature-complete review and final acceptance. Hosting, messaging and store-account charges are agreed separately.

PAYMENT & SCOPE CHANGES

Payment schedule: [approved schedule]. Confirm any deposit, due dates, applicable tax and exclusions. Additional work or changed terms require written agreement.

FINAL / REVIEW & APPROVAL

Agree the next move.

01

Acceptance criteria

Agree testable acceptance criteria before implementation. The client has [review days] business days after each milestone to report issues against those criteria. Record approval explicitly.

02

Client dependencies

Supply brand assets, approved content, test accounts, API documentation and timely decisions. The client owns the store and production service accounts and grants access to the delivery team.

03

Changes and exclusions

New features, additional integrations, backend development, data migration and iOS delivery are excluded unless listed. Changes require written scope, cost and schedule approval.

04

Security and handover

Agree data handling, access controls and security requirements during discovery. IP transfer, third-party licences, support boundaries and liability follow the approved development agreement.

Approve the MVP scope, milestone fees, acceptance criteria and attached development agreement before kickoff.