How we work
A clear path from idea to implementation.
Seven stages give every project a shared map—from understanding your goals to supporting the solution after launch. Feedback and testing continue throughout, and the approach adapts to the scope of each engagement.
Seven stages
What happens at each stage
Typical outputs are examples. The actual outputs for your project are confirmed in the agreed scope.
-
Stage 1: Understand Your Goals
Clarify the business problem, users, desired outcomes, and constraints.
We start with conversations about what you want to achieve and why. Who are the users? What does success look like? What budget, time, or technical constraints apply? The answers become a shared brief that keeps decisions anchored to business outcomes.
Typical output Shared project brief
-
Stage 2: Discover & Analyse
Examine workflows, requirements, existing systems, and risks.
We look closely at how work happens today: the processes, the people involved, the systems and data already in place, and the risks that could affect delivery. This produces documented requirements and an initial view of scope.
Typical output Requirements and initial scope
-
Stage 3: Explore Solutions
Compare approaches and identify a practical direction.
Strategy, design, and engineering perspectives come together to compare options—build, extend, integrate, or buy—and their trade-offs. We recommend a practical direction and explain why.
Typical output Options and recommended approach
-
Stage 4: Design & Prototype
Develop user journeys, interfaces, and prototypes for review.
We design user journeys and interfaces, then build prototypes so you and your users can review the direction before development effort is committed. Feedback refines the concept.
Typical output Designs and validated direction
-
Stage 5: Build & Integrate
Implement the solution iteratively and connect relevant systems.
Development proceeds in increments you can review. Tasks are tracked, changes are managed in version control, and the solution is connected to the systems it depends on. Testing runs alongside development rather than waiting until the end.
Typical output Working software and integrations
-
Stage 6: Validate & Launch
Check functionality, usability, and readiness; resolve issues and prepare release.
A final validation stage confirms functionality, usability, and operational readiness. Issues are resolved, release steps are prepared, and documentation is handed over.
Typical output Tested release and handover
-
Stage 7: Support & Improve
Maintain the solution and plan improvements as needs evolve.
After launch we maintain the solution, respond to issues under the agreed arrangement, and plan improvements as your business and users change.
Typical output Agreed support and improvement plan
Not a rigid sequence
Feedback and testing run throughout.
PlanBuildTestReview
The seven stages are an overview that helps everyone understand where a project stands. In practice, stages overlap and repeat: prototypes are revised after feedback, development happens in reviewable increments, and testing starts early rather than waiting for the end.
We use Agile delivery adapted to each engagement. Some projects benefit from short iterations and frequent releases; others need more upfront analysis and a planned release. We agree the approach that suits your goals, risks, and ways of working, and draw on traditional methods where they help.
Testing is continuous throughout delivery, followed by a final validation stage before launch to confirm functionality, usability, and readiness.
Working practices
How we keep delivery visible and quality high.
Task accountability
Every task is tracked to its conclusion, so progress and ownership stay visible.
Defect tracking
Issues are logged against the functionality they affect and followed through to resolution.
Version control
All changes are recorded, reviewable, and reversible.
Quality assurance
Testing runs throughout delivery, with a final validation before launch.
Test-driven development
Automated tests are written first where they protect important behaviour and document how the system should work.
Maintainable code
Clean, consistent code and logging make the solution easier to support in production.
Questions
About our process
Most projects touch every stage, but the time spent on each varies. An advisory engagement may focus on the first four stages, while a support arrangement concentrates on the seventh.
You will be involved at key points: sharing goals, reviewing designs and prototypes, giving feedback on working software, and approving the release. We agree how often we review progress at the start.
They are agreed after discovery, when we understand your goals, requirements, and constraints well enough to propose a realistic approach.
Ready to take the first step?
Stage one starts with a conversation about what you want to achieve.