Choose a starting point. Know what it includes.

App blueprint

One founder working session, an existing-material review, core screen map, feature priorities, technical risks and a delivery recommendation. One consolidated findings review is included.

Participant recruitment, a large research program, brand design and production code are separate.

Design & brand

The agreed core screens, visual identity essentials, reusable components and a clickable prototype. The scope identifies the number of flows, review rounds and launch assets.

Naming clearance, purchased assets, extensive illustration and additional flows are separate.

App build

A scoped version one for iPhone and Android, client-owned code and accounts, test builds, agreed integrations, validation and submission support.

The range starts after scope, design, access and dependencies are ready. Complex migrations, new requirements, store review delays and third-party fees are separate.

Care & insights

A prioritized maintenance and improvement allocation, a work log and a monthly review. Dashboard maintenance and feedback analysis are included only where specified.

Unused time, overages, coverage and cancellation terms are agreed in writing. This is not round-the-clock incident response.

What the agreement needs to settle

Before work begins, both sides agree the finish line and how changes are handled.

• Named contracting parties, scope, exclusions and acceptance evidence.
• Payment schedule, applicable taxes, third-party costs and account owners.
• Review windows, start date, access dependencies and support coverage.
• Ownership of project work and licenses for pre-existing or third-party materials.
• A proposed 30-calendar-day correction period for reproducible defects against accepted scope.

Not ready to commission a build?

Book a conversation to describe the problem and decide whether a blueprint is useful. A call does not commit you to a paid engagement or promise a start date.