A first version.
A complete experience.
A project that takes a defined mobile or web application from scope and interface design to a tested first release.
A useful fit
A business ready to build a focused first product with a clear user task, an owner and a path to real users.
The shape of the scope
What we would
work through.
- A prioritised scope and acceptance criteria
- UX/UI design and application development
- Backend services and agreed integrations
- Testing, release preparation and source-code handover
Build around a complete journey.
We agree the smallest release that lets a real user achieve the intended outcome. Supporting steps such as access, validation and a meaningful confirmation belong in that scope.
Milestones make progress reviewable in working software. The backlog records what is included now, what comes later and which new requests would change the plan.
Release with ownership in place.
Testing and launch preparation are part of delivery. We confirm environments, account access, release responsibilities and the requirements of any app-store submission.
The first release provides a basis for learning from use. Further features and support can continue under an agreed arrangement, with the handover complete regardless of that choice.
What to bring.
- A product owner who can prioritise and approve
- A core user journey and intended audience
- Access to integrations, content and required accounts
- An agreed scope, budget and review rhythm
At handover
The agreed application release, source code, design files, configuration guidance and a record of known issues and next priorities.
Begin with the situation.
Describe the app, the people who will use it and the task it should make easier.
Prepare a project outline