How we work · Discovery first
Understand the work. Then engineer the system.
Good technical decisions start with the people, information and constraints behind a business. We make the work and its approval points clear before moving forward.

Six stages, with clear decisions.
A small website may combine discovery, mapping and architecture into a short scoping exercise. A complex platform needs deeper workflow analysis and staged delivery. The proposal sets the level of detail.
- 01
Discover
Understand the operation and the problem before choosing technology.
- You provide
- Your goals, current tools and examples of where work slows down.
- We produce
- A shared problem statement and constraints.
- Decision & next step
- Agree what is worth investigating next.
- 02
Map
Trace the people, data and handoffs that make the work happen.
- You provide
- A walkthrough of key tasks and the people responsible for them.
- We produce
- A workflow map and prioritised requirements.
- Decision & next step
- Confirm the essential journeys and scope boundaries.
- 03
Architect
Choose a proportionate structure, integration plan and security approach.
- You provide
- Feedback on priorities, budget and operational constraints.
- We produce
- A technical approach, written scope and proposed milestones.
- Decision & next step
- Approve the scope, responsibilities and commercial terms before build.
- 04
Build
Develop in stages so you can review the work while decisions are still easy to change.
- You provide
- Content, necessary access and feedback at agreed checkpoints.
- We produce
- Reviewable increments with progress against the agreed scope.
- Decision & next step
- Approve milestones; agree changes and their cost before adding work.
- 05
Validate
Check the important journeys, permissions and responsive behaviour before release.
- You provide
- Realistic scenarios and a named person to review acceptance criteria.
- We produce
- Test findings, resolved release issues and a handover plan.
- Decision & next step
- Sign off the release and agree deployment responsibilities.
- 06
Support & optimise
Hand over clearly and agree how the system will be maintained after launch.
- You provide
- An operational owner and feedback from day-to-day use.
- We produce
- Access and documentation, plus a support scope where agreed.
- Decision & next step
- Prioritise improvements and confirm any ongoing maintenance agreement.
Keep the agreement as clear as the engineering.
The written proposal defines scope, milestones, review responsibilities, acceptance criteria and payment terms. Changes are discussed with their effect on cost and timing before work is added.
Handover covers agreed access, documentation and operating responsibilities. Third-party licences and subscriptions retain their own terms. Post-launch fixes and ongoing support are defined in the engagement agreement.
What does your project need?
Tell us about the operation and the problem. We’ll discuss the right depth of discovery and a sensible next step.
