Process
From brief to launch,
one clear process.
Five phases. Each one answers a different question: what matters, what is in scope, what it should look like, whether it works, and whether it is ready to use.
Understand
Understand the business context before deciding what the system should be.
What we need from you
- Current workflow
- Users and owners
- Data and documents
- Existing tools and integrations
- Expected outcome, constraints, budget and timeline
What you receive
- Shared problem definition
- Known constraints and dependencies
- Open questions for solution definition
Decision made
Is this the right problem to solve?
Define
Turn the problem into a focused scope with visible assumptions and exclusions.
What we need from you
- Discovery findings
- Technical access information
- Business priorities
What you receive
- Scope and feature priorities
- Architecture direction
- Delivery phases
- Assumptions, exclusions and milestone plan
Decision made
What belongs in the first release?
Design
Design the product, the flows and the interface before anything is built.
What we need from you
- Agreed scope
- User and operator context
- Brand and content
What you receive
- User flows and information architecture
- Interface design for every core screen
- Interaction and state behaviour
- A component direction the build can follow
Decision made
Is this the right thing to build?
Build
Develop the agreed system in reviewable milestones with decisions recorded.
What we need from you
- Approved scope and design
- Required access
- Milestone priorities
What you receive
- Visible progress in a review environment
- Regular checkpoints
- Documented decisions
- Source-controlled implementation and secure configuration
Decision made
Does the system work as agreed?
Launch
Test, deploy and hand over, then improve the system with real usage behind it.
What we need from you
- Completed milestone scope
- Review feedback
- Launch plan
What you receive
- Functional, accessibility and performance testing
- Agreed deployment and structured handover
- Analytics and workflow review
- Optional maintenance and feature iteration
Decision made
Is it ready to operate and hand over?
Commercial clarity
Payment and project control
The project agreement defines the commercial terms for the specific engagement.
- 01
Milestone-based payments
- 02
Scope changes documented and agreed separately before implementation
- 03
No hidden work added outside the approved scope
- 04
Handover after the agreed payment milestones
- 05
NDA available when appropriate
A useful first conversation starts with the real workflow.
Tell us what happens today, where it breaks and what should be different.