How we work
How a project runs.
A project moves from understanding the need and agreeing the scope, through building and review, to preparing for launch and continuing support. At each point you know which step you are in and what happens next.
The five steps
One project, five steps.
Understand the need
We learn how the work runs today: who does what, which systems and paper are involved, and what has to change.
Agree the scope
We agree in writing what will be built, what it connects to, and how support works after launch.
Build and connect
We build in stages and show working parts early, so your team can check them against real work.
Review and prepare for launch
Your team tests with real cases while we prepare training, data and the move from the old way of working.
Operate and support
After launch we stay responsible for monitoring, maintenance, backups, updates and further development.
In detail
What happens, and what we ask of your team.
Understand the need
We spend time with the people who currently do this work, and look at the systems, forms and paper already in use to see where the process creates problems.
What we ask of your team: Time from the people who do this work today, and access to the systems, forms and records they use.
Agree the scope
We put in writing what will be built, what it needs to connect to, and how support will work once the system is in use.
What we ask of your team: Time to review the written scope and confirm it matches how your organisation needs to work.
Build and connect
We build in stages, connect the new work to the systems it depends on, and show working parts as they are ready.
What we ask of your team: Real examples from everyday work, so what we build can be checked against how the work actually happens.
Review and prepare for launch
Your team works through real cases while we prepare training, prepare the data, and plan the move away from the old way of working.
What we ask of your team: Time for your team to test with real cases and take part in training before launch.
Operate and support
After launch we stay responsible for monitoring, maintenance, backups, updates and further development, as agreed with you.
What we ask of your team: Agreement, from the start, on how support and responsibility will work once the system is live.
After launch
The relationship continues after launch.
Launch is not the end of the relationship. An organisation needs confidence that its software will keep being looked after once people rely on it — resolving problems, maintaining the system, managing updates and adapting it as needs change. What this covers depends on the system and on what you agree together.
What we ask of your team: A shared understanding of what your support arrangement will include — for example monitoring, backups, recovery, staff assistance, maintenance and future development.
Ask us for a written scope.
Tell us what you need built and what it has to connect to. Step two is where that becomes a written scope. The contact page opens your own email app with the message ready to send.