Process
A delivery process you can hold us to
Custom software fails when scope is vague and nobody agrees what finished means. Our process exists to remove both of those risks before the build starts.
Delivery process
How an engagement runs
The same six phases on every project, whatever the size. Each one ends with something written down, so you always know where the work stands.
- 01
Discovery
We sit with the people who do the work, map the current process, and identify where the cost and risk actually sit.
Output — Requirements and process map
- 02
Scope & proposal
A written scope with deliverables, milestones, acceptance criteria, and a fixed commercial figure before any code is written.
Output — Signed scope of work
- 03
Architecture
Data model, integration points, access control, and hosting decided and documented up front so the build does not stall halfway.
Output — Technical design
- 04
Build
Delivery in reviewable increments on a staging environment, so you see working software throughout rather than at the end.
Output — Staged releases
- 05
Test & sign-off
Functional testing, access-control and security review, and user acceptance against the criteria agreed in the scope.
Output — Sign-off record
- 06
Handover & support
Documentation, staff training, and transfer of code and infrastructure into your ownership, followed by an agreed support arrangement.
Output — Documentation & support
How we work
What you get on every engagement
These are not optional extras or upsells. They are the standard terms of working with us.
Fixed scope, written up front
Every engagement starts with a written scope, deliverables, and acceptance criteria, so there is no ambiguity about what is being built or when it is done.
You own the code
Source code, infrastructure, and accounts are handed over in your name. No lock-in, no hostage licensing, no dependency on us to keep operating.
Tested before it ships
Functional testing, access-control checks, and a staged environment for sign-off before anything reaches the people who rely on it.
Documented handover
Admin walkthroughs, written documentation, and a training session for the staff who will run the system day to day.
Security reviewed in-house
Authentication, permissions, and data handling reviewed by our own cybersecurity specialist rather than left to chance.
Support after go-live
An agreed support arrangement after launch, covering fixes, small changes, and the next phase of work when you are ready.
Have a process that needs a system behind it?
Tell us what the current process looks like. We will tell you honestly whether custom software is the right answer.