Fixed scope project
A defined build with an agreed scope, timeline and price. Suited to work where the requirements can be pinned down in discovery.
Approach
How the work actually runs.
Custom software fails more often on process than on technology. This is the process we hold to, and the reasoning behind each stage.
- 01
Discovery
We start with the process, not the software. What happens today, who does it, where it breaks, and what it costs when it breaks. This produces a written scope you can read and challenge before anything is built.
- 02
Architecture
Data model, integrations, hosting and access control are decided and documented up front. You see the plan, including the parts that constrain what comes later, before the first line of production code.
- 03
Build
Delivered in working increments rather than one reveal at the end. You get access to a running environment early and give feedback while it is still cheap to act on.
- 04
Launch
Deployment, data migration, store submission where relevant, and the monitoring needed to know the system is healthy. We do not treat go live as the finish line.
- 05
Support
Handover documentation, source code and full access to the accounts and infrastructure, followed by an ongoing arrangement if you want one and a clean exit if you do not.
Working principles
The commitments that do not change per project.
You talk to the person building it
No account manager relaying requirements to a delivery team you never meet. The person who understands your system is the person who answers you.
You own everything
Source code, accounts, domains and infrastructure are yours and registered in your name from the start. No proprietary platform you cannot leave.
Security is not a later phase
Access control, data protection and backups are designed in at the architecture stage. Retrofitting them after launch costs several times more and rarely gets done.
Scoped in stages
Work is agreed and priced one phase at a time. You are never asked to commit budget to a twelve month plan on the strength of a first conversation.
Written down
Decisions, architecture and handover are documented as the project runs. If we stopped working together tomorrow, another engineer could pick it up.
Direct about fit
If the thing you need is a configured off the shelf product rather than custom software, we say so. A badly matched project helps nobody.
Engagement models
Three ways to work together.
Retained capacity
An ongoing monthly arrangement covering continuous development, maintenance and support. Suited to a live system that keeps evolving.
Advisory
A time boxed review or consultation with a written outcome. Suited to a decision that needs an independent read before budget is committed.