Home / How we work
How we work
Predictable projects, from first call to long after launch.
Software projects go wrong in familiar ways: vague scope, invisible progress, a big reveal that misses the point. Our process is designed to make each of those impossible.
The process
Five phases. A sign-off at the end of each.
You approve every phase before the next begins, so the budget and direction are never out of your hands.
Discover
Workshops with the people who do the work. We map current processes, systems and data, and find where time and money are lost.
You receive: findings & prioritiesDesign
Architecture, security approach, user journeys and prototypes, turned into a fixed-scope plan with milestones and costs.
You receive: plan & fixed quoteBuild
Two-week cycles, each ending in a demonstration of working software on a test environment you can use.
You receive: working softwareLaunch
User acceptance testing, security review, data migration, training and a rehearsed go-live with rollback ready.
You receive: a calm launchOperate
Monitoring, support and a roadmap of improvements, reviewed with you every quarter.
You receive: continuous improvement
Ways to work together
Choose the model that fits the work.
Every engagement starts with a free consultation and, for larger projects, a short paid discovery that is credited against the build.
Fixed-scope project
Best for: a defined outcomeAn agreed scope, timeline and price. Ideal for a new website, a specific automation or a set of integrations. Changes are quoted before they are made, so the budget never drifts.
- Fixed priceAgreed after discovery
- Clear milestonesPay as each is delivered
Dedicated team
Best for: ongoing product developmentA consistent team of engineers, working as an extension of yours on a longer roadmap. Ideal when you are building a platform, not a single feature, and need capacity you can rely on.
- Monthly capacityScaled up or down with notice
- Shared roadmapPlanned and reprioritised with you
Support retainer
Best for: keeping systems healthyMonitoring, maintenance, security updates and a monthly allowance of improvements, with agreed response times. Ideal after launch, or for systems we take over from another supplier.
- Agreed response timesPrioritised by impact
- Monthly allowanceFor small enhancements
Principles
What you can hold us to.
These are not values on a wall. They are how we run every project, and you should expect them from us in writing.
Costs agreed first
Nothing is built, and nothing is billed, that you have not approved.
Demo every fortnight
You see working software regularly, not status reports about it.
Honest advice
If an off-the-shelf tool would serve you better than custom work, we will say so.
Full ownership
Code, data, documentation and accounts belong to you from day one.
FAQs
Questions clients ask before starting.
If yours isn't here, ask us directly. We would rather answer it now than after you have signed.
How much does a project cost?
It depends on scope, which is why we quote a fixed price after a short discovery rather than guess. As a guide, a professional website is a smaller engagement, a single automation or integration sits in the middle, and a client platform or multi-system programme is a larger one. We will always give you a range in the first conversation.
How long does it take?
A website typically takes a few weeks; a focused automation or integration a few weeks to a couple of months; a platform several months, delivered in usable stages. You get a timeline with the fixed quote, and working software to use well before the end.
Do you work with regulated firms?
Yes, it is a core part of what we do. We build with audit trails, access control, data protection and explainability designed in, and we work alongside your compliance and risk teams so the systems support your regulatory obligations. We do not provide legal or regulatory advice; your compliance function remains the authority on your obligations.
Is it safe to use AI with our customer data?
It can be, when it is done properly. We select providers and deployment options that match your data-protection requirements, avoid sending data you don't need to send, keep a log of inputs and outputs, and keep a person in charge of any decision affecting a customer. We will explain the trade-offs in plain English before anything is built.
Can you work with our existing systems?
Almost always. Most of our work is making existing systems work better together rather than replacing them. Where a system has no API, we look at secure alternatives, and we tell you honestly when replacing something would be cheaper than connecting it.
Who owns the code and data?
You do, completely. Code lives in repositories in your name, infrastructure runs in accounts you own, and everything is documented so any competent team could maintain it. There is no lock-in.
What happens after launch?
Most clients move onto a support retainer covering monitoring, security updates and ongoing improvements, with agreed response times. It is optional, and you can take everything in-house whenever you choose.
Can you take over a system built by someone else?
Yes. We start with a technical audit covering security, reliability and code quality, give you a plain-English report and a prioritised plan, then stabilise the system before we build anything new on it.
Start with a free consultation.
Thirty minutes, no obligation, and you will leave with a clearer picture whether or not you work with us.