From brief to go-live, every step in writing.
There are no calls. One written thread carries every question, every decision and every approval, from your first message to the day the work goes live, and you can search it afterwards. The brief reaches the person who would do the work, and when the answer is that you do not need us, the reply says so in writing.
One engagement, start to finish.
Each step leaves something in writing behind it, and the next step starts from that document.
Brief
What the work is, where it happens today, who does it now and which systems it touches. Your own words are enough.
Written proposal
Scope, a fixed price, dates, what goes to staging and which points need your approval. You decide in your own time, in writing.
Staging
We build and test the work away from your live systems, then record a walkthrough of it running and post it in the thread.
Your approval
You watch it working on staging and approve it in the thread. The approval carries the name of the person who gave it.
Live
The work is switched on, with access limited to what it needs and to the people you named.
Audit trail
Every action and approval stays on record, and the documentation comes to you with the finished system. The system is yours.
Four things that do not change.
The size of the work changes the scope and the dates. These four stay the same.
No calls
Every message gets a written reply within one business day, in the same thread as everything before it.
A fixed price
Set in the proposal before work starts. It changes only through a written change of scope that you accept.
Nothing live without your approval
The work stays on staging until a named person on your side approves it in the thread.
Access you grant
You decide who gets access, what it covers and until when. It is scoped to the work and ends when the work ends.
One thread from the first line to the handover.
Your brief becomes a written proposal, the proposal becomes a build on staging, and nothing moves to live until you approve it. The thread runs above every step; the audit trail keeps every decision below it.
Four things you always get.
Whatever the size of the work, these come with it.
A written brief
What we agreed to build, in one document.
A fixed price
Set in the proposal, before work starts.
Staging + approval
You see it and approve it before it goes live.
Documentation
How it works and how to change it, handed over.
Before you send the brief.
Send any other question in writing; a written answer follows within one business day.
Why no calls?
A written thread keeps the brief, the proposal and every approval in one place that both sides can search later, so what was agreed is never a matter of memory. Your message goes to the person who would do the work, not to a sales desk, and if the answer is that you do not need us, the reply tells you that.
What if the scope changes halfway?
The fixed price holds for the scope in the proposal. When the work needs to change, we write down what changes, what it does to the price and the dates, and nothing moves until you accept it in the thread.
Who approves on our side?
The person you name in the proposal. Their approval is recorded in the thread with their name, and the work does not go live without it. You can name more than one person.
What happens after go-live?
The documentation is handed over: what runs, how it works and how to change it. The accounts and the system stay yours. If you want it looked after month by month, that is a separate operations engagement.
Not sure what you need? Ask in writing.
Write down what takes up your team’s day and which systems you run. The reply comes in writing within one business day, with what we would build, how and when, or a note that you do not need us.