How it works
Four stages. Nothing hidden.
You'll know what's happening at every point, and you'll be using working software long before the end.
A conversation
Day one
Tell us what's slow, manual or unreliable. We ask questions, we don't pitch. If software isn't the answer, we'll tell you.
What we need from youHalf an hour, and whoever knows the problem best.
On the ground
Before anything is designed
We spend time where the work happens, with the people who do it. The software has to fit the job on a bad day, not the job as described in a meeting.
What we need from youAccess to your site and a few of your people's time.
Build, in the open
In stages
You see working software early and often. Each stage is agreed before it starts, so there's no surprise at the end and no long wait for something you can't react to.
What we need from youHonest feedback as you go.
Live, with your team
Switch-on and after
We're there for the switch-on, we train the people using it, and we stay on for support. Software that nobody uses is a failure, so adoption is part of the job.
What we need from youA named person on your side for the switch-on.
Three rules we keep
Fit the work
The software bends to the job, not the other way round.
Build for the worst day
Night shift, cracked screen, no signal. If it works then, it works.
Plain language
No jargon in the room, no jargon on the screen.