How a project runs, start to finish
Five steps from the first call to measuring what the launch did.
(chalk version)
From first call to launch
The same stages for a new app or a search programme.
A first call
We listen, ask about your customers and goals, and say plainly whether we are the right fit.
A written scope
You get a short document with what we will build, what we will not, and how we will check it.
Sprints you can watch
We build in short cycles with a shared board, so you see working software and can change direction.
Launch
We test, move the work to production, check redirects and structured data, and hand over what you need.
Measure and adjust
We look at speed, search and AI answers after launch and fix what the numbers show.
Questions we get
How long does a project take?
It depends on scope, which is why we write it down first. Small builds often take a few weeks and larger ones a few months, and the written scope gives you our estimate before you commit.
Will I see the work before it launches?
Yes. We work in short sprints and show working software at the end of each one. You can give feedback while it is still cheap to change.
What happens after launch?
We hand over the code, access and notes, and check how the site performs in search and in AI answers. If you want ongoing help, we can agree on a monthly programme or a sprint retainer.
Tell us what you’re building.
- A call about the goalThe budget, the deadline and what success looks like.
- A written scopeWhat we build, in what order, and the quote.
- Work in sprintsA demo at the end of each one.