How a project runs
A project runs in five steps. Each one ends with something in writing or something you can use.
The five steps
Discover
We talk with the people who do the work and follow an order, a quote or an invoice through the company as it moves today.
You get A written scope, a fixed price and a timeline. You decide then whether to go ahead.
Architect
We work out which system owns which data, how the systems connect and what happens when a step fails.
You get A short architecture note in plain language, which you approve before we build.
Build
We build in short rounds. Each round ends with working software you can try.
You get A demo at the end of each round and a test version you can log in to.
Deploy
The new system runs beside the current process on real data first. When the results match, we switch over and train the people who will use it.
You get A dry run, a go-live plan and a way back to the old process.
Support
After launch we monitor the system, fix faults and change it as the business changes.
You get A support plan with agreed response times, the documentation and the code.
You own it
The code, the data and the accounts are in your company's name. If we part ways, everything keeps running and another developer can take it over.
Plain technology
We build with common tools that have been around for years and that other developers know. We pick the stack to fit your systems and the people who will look after it.
Things fail, so we plan for it
An API goes down, a file arrives half empty, someone types a part number that doesn't exist. Everything we build logs what it did, retries what it safely can and alerts a person about the rest.
We say when custom is the wrong answer
Sometimes a setting in your ERP or an off-the-shelf tool solves the problem. When we see that during Discover, we tell you.