A defined first phase.
Discovery identifies the users, priorities, dependencies and acceptance criteria. We distinguish an initial release from later improvements before proposing delivery milestones.
Keep improving after launch with planned updates, technical care and a clear support arrangement.

A conversation that moves things forward.
Illustrative stock photographyLaunch begins a new phase of the product. We agree ownership, support channels, maintenance priorities and escalation arrangements to match the product’s needs.
We agree the exact deliverables during discovery. A considered engagement makes both progress and responsibilities visible.
A shared problem statement, prioritised requirements, integration assumptions and acceptance criteria.
Working increments, review notes, test evidence and decisions recorded against the agreed scope.
Agreed source access, environment documentation, release notes and a clear maintenance arrangement.
Understand the people, the problem and what success should look like.
Make the important decisions tangible through journeys and prototypes.
Develop in clear milestones, with regular reviews and testing.
Launch with a handover plan and keep improving with evidence.
Support hours and response targets are agreed in the service contract after reviewing the system and operational requirements.
Pricing depends on scope, integrations, design, data and delivery constraints. Use the project planner to organise your requirements, then request a proposal. We do not publish unapproved indicative prices.
We agree a handover and maintenance plan, including ownership of hosting, monitoring, updates and support. Service levels are defined in the contract.
From a first tap to a daily habit. We design and build iOS, Android and cross-platform apps around the people who use them.
Customer-facing websites, ambitious SaaS platforms and internal tools. Built to work beautifully on every screen.
Put AI to work on a real business problem. Useful assistants, connected workflows and knowledge tools, with people in control.
Bring the idea. We’ll help you find the right way forward.
Select a perspective to explore the approach, decisions and deliverables for your project.
01 / Understand the productReview architecture, dependencies, access, documentation and known issues before agreeing maintenance responsibilities.
An effective support plan starts with a shared understanding of the product and its operating environment.
02 / Maintain and improvePrioritise dependency updates, fixes and small improvements through an agreed review and release process.
Group changes into an agreed workflow so fixes and improvements remain visible and manageable.
03 / Respond and recoverAgree incident contacts, escalation, monitoring and recovery procedures. Response windows depend on your written service agreement.
Agree response windows and responsibilities in writing, and prepare the information needed to investigate an issue.