Process
From first conversation to launch.
Most projects follow the same basic path: understand the work, agree what needs to be built, build it, test it and launch it properly.
- 01Understand
- 02Define
- 03Build
- 04Test
- 05Launch
- 01
Understand the work
We look at how the work is handled now, who is involved, where problems occur and what the new system actually needs to do.
What you receive
- A clear project brief
- Main priorities
- An initial price and timing range
- 02
Define the solution
We turn the brief into clear screens, workflows, features and boundaries before the full build begins.
What you receive
- Agreed project scope
- Key screens or flow direction
- Final project plan
- Confirmed quote
- 03
Build in stages
The system is built in agreed stages. You review working versions as the project moves forward.
What you receive
- Working builds
- Regular review points
- A clear view of progress
- 04
Test with real use
We test the important flows, edge cases, access rules and supported devices. You also review the system before launch.
What you receive
- A tested release candidate
- Fixes from review
- Final launch approval
- 05
Launch and hand over
We deploy the finished project, confirm access, hand over the agreed source code and documentation, and support the initial go-live period.
What you receive
- Live system
- Required access
- Agreed source-code handover
- Project documentation
- Agreed launch support
What keeps a project moving
The fastest projects usually have clear decisions and timely feedback.
One main contact
Someone who can answer questions and make or coordinate decisions.
Quick feedback
Review screens and working versions while the context is still fresh.
Access when needed
Provide access to the tools, files or data the project needs to connect.
Clear changes
If priorities change, agree what moves in or out of the current scope.
Have a project in mind?
Tell us what you are trying to build and we can work out the next step.
Discuss a project