- Home
- How we work
Our software development process, week by week
Most software projects that go wrong do so for the same three reasons: nobody wrote down what was being built, nobody saw working software until it was too late to change, and nobody was accountable for the outcome. Our process is designed around fixing those three things.
- Week 0
First call and estimate
A 30 minute call with the developer who would lead your project, not a salesperson. Within three working days you get a written proposal: the approach, the team, a timeline, and the questions we still need answered.
You get: A written proposal with approach, team and timeline.
- Weeks 1 to 3
Discovery and specification
Workshops with the people who will use the system, a map of the current process, user journeys, a data model, an integration list and a clickable prototype of the key screens. Discovery is where most of the risk in a software project gets removed, so we never skip it on a serious build.
You get: Specification, prototype, architecture plan and an agreed scope and timeline for the build.
- Weeks 3 to 5
Design
Screen designs for every journey in the specification, tested with three to five of your real users before we write production code. Changing a design takes hours. Changing built software takes days.
You get: Signed-off designs and a component library the build follows.
- Weeks 5 to 14
Build in two week sprints
Each sprint starts with an agreed list and ends with a demo of working software on a test link you can click through. You can reorder priorities at the end of every sprint. Code goes to your repository daily, every change is reviewed by a second developer, and automated tests run before anything is merged.
You get: Working software every two weeks and a sprint report.
- Weeks 11 to 15
Testing, data migration and training
User acceptance testing with your team, load and security checks, and a rehearsed migration of your existing data. We run the old and new systems in parallel when getting it wrong is not an option.
You get: A tested release, migrated data and trained users.
- Week 16
Launch and handover
A planned go-live with a rollback plan, then a 30 day warranty period where anything that does not match the specification is fixed by us, no questions asked. You receive the code, documentation, admin credentials and an architecture overview.
You get: Live software, warranty, full handover pack.
- After launch
Support and improvement
Optional support plans cover hosting, monitoring, security patches, bug fixes and a set number of development days each month. You can cancel with 30 days notice and move support to anyone you like.
You get: Response times in writing, monthly report, no lock-in.
The rules we work by
These are in the contract, not just on this page.
Agreed scope before we build
Once discovery is done, the specification is signed off by both sides. If something new comes up, we agree it in writing before we build it, so there are never surprises.
You own everything
Copyright and IP in the code we write for you are assigned to your company. The repository, hosting and third-party accounts are in your name from day one.
One accountable lead
The developer on your first call leads the build. You have their direct line and a shared Slack or Teams channel, not a ticket queue.
Weekly progress, fortnightly demos
A short written update every Friday with what shipped, what is next and any risks. A live demo at the end of every sprint.
Quality you can check
Every change is reviewed by a second developer and covered by automated tests before it is merged, and you can see all of it in your own repository.
UK GDPR from the start
Data protection is designed in, not bolted on: data maps, a DPA where we process personal data, UK or EU hosting, and access only for the people who need it.
How we build
We choose technology for how long it will be supported and how easy it will be for someone else to maintain, not for novelty. Most of our builds use a small set of well established tools:
- Web applications: TypeScript, React or Next.js on the front end, Node.js, .NET or Laravel on the back end.
- Mobile apps: React Native or Flutter for one codebase on iOS and Android, native Swift or Kotlin when the app needs it.
- Data: PostgreSQL by default, SQL Server where your estate already runs on Microsoft.
- Hosting: AWS, Azure or Google Cloud in UK or EU regions, in accounts you own.
- Quality: code review on every change, automated tests, continuous integration, and separate test and live environments.
If your team already has a standard stack, we work in it. See our services and security practices for more detail.
What we need from you
Good software is built with the people who will use it. For a typical project we ask for:
- A product owner on your side who can make decisions, usually two to four hours a week.
- Access to three to five future users for workshops and testing.
- Prompt feedback on each sprint demo, ideally within three working days.
- Access to the systems we are integrating with, and someone who knows them.
That is it. You do not need a technical person on your team, and you do not need to write the specification: that is our job in discovery.
Start with a conversation
Tell us what you want to build and we will come back within one working day with a first view on approach and timeline.
Or call 020 7096 2842.