How a project goes
You see it working before it is finished
Three phases, and what matters is what happens inside them. Every change lands on a preview link you can open the same day, and you deal with the people building it rather than an account manager.
Phase 1 of 3
Idea: We work out what you are actually buying before anyone writes code.
Most projects go wrong here, not in the build. We pin down the goal, the scope and what success looks like, and write it down.
- A conversation about the business problem, not a feature list
- Scope written down, including what is deliberately not in it
- A fixed price where the work fits a package, a costed range where it does not
- A realistic timeline, with the risky parts named as risky
Phase 2 of 3
Build: You see it working while it is being built, not at the end.
Every change goes to a preview link you can open on your phone the same day, so surprises surface in week two rather than week nine.
- A preview link that updates as the work does
- Plain-English updates on what moved and what is next
- You talk to the person building it, not an account manager
- Automated checks run on every change before it reaches you
Phase 3 of 3
Launch: It goes live, then it keeps being looked after.
Launch is a day, not the finish. We put it live, fix what real use reveals, then keep looking after it.
- Deployment, domains, analytics and error monitoring wired up
- The unglamorous parts done: search foundations, accessibility, performance
- A short handover so you can run the parts you should run
- Ongoing hosting, maintenance, security and updates
What has to be true before it goes live
Nothing ships that has not been driven
A passing build is not evidence a feature works. The flow gets used before it is called done.
You never read a technical message
Every error a customer can hit is written in plain language. The detail goes to our monitoring, not their screen.
The unhappy paths are part of the job
Empty states, duplicates, going offline. A working happy path is about half a finished feature.
It is yours once the build is paid for
The build fee buys the software. The monthly fee pays for hosting, maintenance and updates. Two different things.
Start with the problem.
Tell us what is getting in the way. If we are the wrong people for it, we will say so and point you somewhere better.