The process
How we work
Seven stages, from the first conversation to looking after your software for years. Here's what happens at each one, what you get, and what we need from you.
- 01
Discover
We learn how you really work.
We ask questions, watch a normal day, and listen to the people who'll use the software every day.
- You get
- A short write-up of what we heard
- We need from you
- An hour or two of your time, and access to the people who do the work every day.
- 02
Requirements
We write down what it must do.
Every feature, every rule and every awkward case, in plain language, agreed with you before anyone builds.
- You get
- A clear list of requirements
- We need from you
- Your answers to our questions, and a careful read of the list before you agree it.
- 03
Architecture
We plan how the parts fit.
Which pieces we'll build, how they talk to each other, and the reason behind each choice.
- You get
- A plan of the parts, with reasons
- We need from you
- Details of any systems we need to connect to, and who looks after them.
- 04
Build
We build it in small pieces.
You see working software early and often, so there's never one big reveal at the end.
- You get
- Working pieces you can try
- We need from you
- A few minutes every week or two to try what we have built and tell us what you think.
- 05
Test
We test it where it'll be used.
On real Android phones and slow networks, not just on our own laptops.
- You get
- The test results
- We need from you
- A couple of people to try it as real users before launch.
- 06
Launch
We go live carefully.
Step by step, with a plan for rolling back if anything misbehaves.
- You get
- A launch plan with a way back
- We need from you
- A go-ahead for the launch date, and someone on hand that day.
- 07
Maintain
We stay and look after it.
Updates, monitoring and fixes, with a short note each month on what we did.
- You get
- A short note every month
- We need from you
- A way to reach you when something needs a decision.