Four stages from first conversation to running software
Our delivery framework has four stages: understand the work, make the solution concrete, build in short cycles and launch with a clear handover. The scope of each stage depends on what you need and what already exists. Discovery or review can also be a standalone engagement. Ongoing support is agreed separately.
Designed to remove the usual surprises
AI where it pays off, not everywhere
We add AI to the steps where it saves real time, and keep a person responsible for the result.
Built around how your business actually runs
We start from your operations, not from a feature list, so the software fits the work instead of the other way round.
One team from first sketch to launch
Design, engineering and delivery sit with the same people, so nothing is lost in a handoff.
You own the bespoke code we build
You own the bespoke code. Project accounts are set up in your name, and documentation supports a handover to your team or another provider.
How long could your first release take?
What you build, how much belongs in the first release and the design approach all shape the schedule. Use these examples to start planning; we confirm the scope, inputs and dependencies before agreeing your timeline.
What are we building?
Explore the service that fits your project. Websites, applications and AI solutions have different delivery needs.
How much belongs in the first release?
Planning guides for web applications and internal tools, from kickoff to initial handover. These examples assume established interface components, available inputs and bounded integration work. We confirm your scope and schedule during planning; later phases and ongoing support are agreed separately.
- Focused MVP
- 5–10 weeks
- One core workflow, essential user roles and a small number of straightforward integrations. Enough to put the main idea into use.
- Fuller first release
- 10–16 weeks
- Several connected workflows, customer and admin journeys, and the integrations needed to operate the initial product.
- Complex product
- 16–24 weeks
- Multiple roles, interconnected workflows and substantial integration or data work, delivered against a clearly defined initial scope.
- Larger scopes can take longer. Later phases are planned separately.
What design approach does it need?
Design can extend the work in the examples above. We estimate the screens, components and interactions involved; there is no fixed percentage added to every project.
Established components
Familiar layouts and proven interface components, adapted to your brand.
The baseline for the web application and internal tool examples above.
Custom design system
Bespoke screen designs, reusable components and documented visual rules for your product.
Needs more time for design, implementation and review. An existing design system can reduce that work.
Advanced motion & interactions
Bespoke transitions, animated storytelling or complex interactive experiences.
An optional addition to either approach, with extra design, development, performance and accessibility testing scoped around the interactions.
Inside a focused first release
The stage ranges below illustrate a focused first portal, internal workflow or AI automation: 5–10 weeks from kickoff to initial handover. The scope, inputs and dependencies determine the agreed schedule. Ongoing support is scoped separately.
01. Discover
Understand the problem and define a useful first release.
- Map how the work runs today: who does what, in which tools, where time is lost.
- Agree the outcome the project must produce and how we will measure it.
- Review existing plans, systems and constraints, and identify the assumptions that could change the scope or estimate.
Review the scope and estimate before deciding whether to continue.
- Written scope with boundaries
- Prioritised feature list
- Estimate and plan for the next stage
02. Plan & design
Make the solution concrete before building it.
- User flows and wireframes for the screens that matter most.
- Data model, integrations and architecture written down in plain language.
- Review wireframes or a prototype together, then agree the scope, milestone schedule and checks required before launch.
Agree the proposed solution, milestone schedule and launch checks before the build.
- Prototype or wireframes
- Technical plan
- Milestone schedule
03. Build & integrate
Ship working software in short cycles, connected to your systems.
- Build the agreed workflows in reviewable increments and use your feedback to guide the next cycle.
- Review working software at the end of each agreed delivery cycle, with a written summary of progress and next steps.
- Integrations with your existing systems, automated tests and code review on every change.
Review each delivery cycle; approve changes to scope, cost or timing before additional work starts.
- Working increments
- Demo and written progress summary
- Test coverage for critical paths
04. Launch, support & improve
Initial rollout and handover. Ongoing support is agreed separately.
Launch with agreed checks, clear ownership and a practical handover.
- Review the agreed launch checks with your team and confirm the rollout and recovery plan.
- Complete any agreed data migration, hand over code and account access, and walk your team through running the system.
- Document who handles monitoring, backups and maintenance, with ongoing support agreed separately.
Review the launch checks and handover, and confirm who handles ongoing operation and support.
- Initial release
- Code and account access
- Operating guide and handover
- Support responsibilities
What we need from you
Access to the right people
The people who do the work today, and someone who can make decisions.
Feedback on working software
A short review after every demo so the next cycle starts from what you saw.
Decisions on time
Approvals for scope changes and milestones, in writing, so the schedule stays honest.
Questions about working together
An existing plan gives us a useful starting point. We review the requirements, designs and any existing code, then identify what still needs checking before we build. Discovery focuses on those gaps: the workflow, integrations, risks and assumptions that could change the scope or estimate.
Ready to start with discovery?
A free 30-minute strategy call helps us decide whether there is a fit. If discovery would be useful, we send a proposal with its scope, outputs and price for you to approve. You can take the resulting written scope and estimate to another team.