Discover
Understand the context, people, constraints, and outcome that matters.
Output: A shared problem statement and evidence map.
Client decision: Confirm the outcome and the right problem to solve.
What working together feels like
From a hard problem to working software.
We understand the problem, shape a useful first move, build it in visible steps, and learn from what works.
The product loop
Six connected stages.
Every stage creates a clear output and a decision you can review.
Plan
Set the scope, architecture, responsibilities, and release plan.
Output: A practical delivery plan with assumptions and risks.
Client decision: Agree the first release, responsibilities, and boundaries.
Design
Make critical journeys, states, and product decisions reviewable.
Output: Reviewed journeys and a clear interface direction.
Client decision: Approve the experience before engineering deepens.
Build
Deliver working increments with engineering, quality, and visible trade-offs.
Output: Working software and a visible decision record.
Client decision: Review the increment and choose the next priority.
Launch
Prepare production readiness, ownership, monitoring, and support.
Output: A release-ready product with known operating boundaries.
Client decision: Approve launch when the product and owners are ready.
Improve
Use evidence to prioritise the next useful investment.
Output: A learning review and prioritised improvement path.
Client decision: Choose what to improve, extend, or stop next.
Commercial models
Choose the working model that fits the work.
We agree the practical model before delivery starts, then make scope, ownership, and review points visible.
Focused project
For a bounded outcome. The proposal defines deliverables, assumptions, milestones, timing, and fees.
Continuing product team
For evolving priorities. The proposal defines the initial team, cadence, responsibilities, review points, and billing basis.
Representative milestones
Know the moments you will review together.
A useful engagement has visible points to check direction, working software, and readiness.
Kickoff
Confirm the outcome, people, constraints, and working rhythm.
Scope and design approval
Agree the focused release and critical journeys before deeper build work.
Working release
Review usable software, evidence, and the next delivery decision.
Launch
Confirm readiness, ownership, monitoring, and support preparation.
Handover
Make code, documentation, access, and remaining risks clear.
The signed proposal controls the actual milestones and payment terms.
What collaboration feels like
Close to the work. Clear about decisions.
Meet the people doing the work, review working software, and keep important tradeoffs visible.
A shared product brief
The outcome, user, scope, evidence, and open risks stay visible.
Frequent working software
Progress is reviewed through the product, not a percentage-complete report.
Decision records
Important tradeoffs are documented so future teams understand the why.
Operable handoff
Code, environments, documentation, and remaining risks are made clear.
Start honestly
A rough problem is enough for the first conversation.
Share the desired outcome, current state, and what makes the work difficult. We will help structure the next step.
Frequently asked
Questions worth answering before the work begins.
Do you require a complete product specification before starting?
No. We can begin with the problem, user, constraints, and desired outcome. Product shaping is part of the work when the right release or technical path is not yet clear.
How will we see progress during the engagement?
Through working product increments, focused reviews, concise written updates, and visible decisions. The exact cadence is agreed for the project, but progress is demonstrated rather than asserted.