How a project runs
Discovery first, then fixed-price phases with a demo every week, then handover with the code and the data in your name. This is the whole method. The detail lives on the Workflow Audit page.
We do not pick the technology before we know where the time goes.
So most projects open with the Workflow Audit: every member of staff documents their own repeating work, and the result comes back priced in pounds. From that document we scope the first phase, quote it as a fixed price, and start building. You see working software every week from week two.
Discovery, price, build, hand over
Each step ends with something you can hold: a report, a number, working software, the keys.
Discovery
The Workflow Audit for most builds: every member of staff documents their own repeating work and the result comes back priced in pounds. For a single site or system, a shorter scoping engagement: we sit with the people who do the work and write down what the software has to do.
Scope and fixed price
A written scope for the first phase and one number. If the number is wrong, we absorb it. Larger systems are split into phases, and every phase ships something you can use on its own. If one part is a real unknown, such as data locked in an old program, we test it first in a short discovery spike.
Build in phases, demo weekly
Working software on a staging address from the second week. You use it, and what you say steers the next week. Nothing waits for a big launch.
Handover and support
Repository, cloud account, database, documentation and training, all in your name. Support afterwards is optional, monthly, and yours to stop.
Three things we turn down
A build the audit does not justify
- If the return is not there, we say so and the report is still yours
- If a package fits, we tell you which one and help you set it up
A rebuild when a refresh will do
- A dated design on a sound platform is a refresh, not a rebuild
- We look at the site, the analytics and the console before quoting anything
A feature nobody in the audit asked for
- Scope comes from what your people do all week, not from a wish list
- Anything added mid-phase is quoted before it is built
Start with the audit, or send us the problem
The sample audit report is on the Workflow Audit page, every number shown. The first call is free and its job is to work out whether we are the right fit.