Process
How a project actually runs
The same shape applies to a small bot and to a system built over six months. The length of each stage changes, not the order.
- 01
Conversation
We ask what is not working today and what it costs you. At this point we talk people out of builds more often than into them — if configuring an existing tool solves it, we say so.
30–60 minutes
An initial scope and a cost range
- 02
Scope and quote
We write down what gets built, in what order, and how we will know it works. The quote is fixed for the agreed scope — no surprises mid-build.
3–5 days
A scope document and a fixed quote
- 03
Design
For sites and apps we show the design on real content. For integrations we draw the data flow and agree what happens when one of the systems does not respond.
1–2 weeks
Mock-ups or a data flow map
- 04
Build
We work in two-week blocks. Each one ends with a version you can click through and check — not a progress presentation.
2–8 weeks
A working version every two weeks
- 05
Launch
We move to production, wire up monitoring and alerts, hand over access and train your team. We stay on standby through the first days after launch.
2–5 days
A live system and all the access
- 06
Care
We monitor uptime, update dependencies and respond within the agreed time. Once a month you get a short report and a list of what is worth improving.
ongoing
A monthly report and an agreed response time
Tell us what you want to build
Write a few sentences about the project. We reply within one business day, and if we are not the right people for it we will say so and point you somewhere better.