Home / Approach
The playbook, published in full.
This is how an engagement actually runs, written down in enough detail that you can hold us to it — what happens in week one, how we scope, what we refuse to build, and exactly how a contract ends. Read it before you talk to us.
Principles
Name the real problem
The symptom you noticed often lives one layer below where you are looking — broken tracking under a marketing problem, a broken process under an automation request. We will say so before quoting for the visible fix, even when that makes the engagement smaller.
Boring beats clever
We choose the least sophisticated tool that solves the problem. Every additional moving part is something your team maintains after we leave.
Write the decision down
Significant choices go into decision records you keep — what we chose, what we rejected, and what would make us change our minds.
Build for the handover
Success is your team running it confidently without us. We optimise for that from the first day, not from the last week.
The engagement, week by week
Conversation
A call, free, about an hour. We are trying to work out whether we are the right people for this. Sometimes the answer is no, and we will say so and suggest what kind of help would fit better.
Audit
Paid, fixed fee, credited against the build. We read the systems, the funnel, the pipeline or the process — whichever applies — and interview the people who run it. Output is a written map, a ranked build list and a recommendation.
Scope
A written proposal with fixed deliverables, acceptance criteria, a price and a timeline. If you stop here, you keep everything from the audit.
Delivery
Work happens in your accounts and repositories, visible as it lands. Weekly written progress note: what shipped, what is blocked, what changed in the estimate. No status theatre.
Handover
Runbooks, a recorded walkthrough, and a working session with your team. Thirty days of support included for questions and defects.
Working agreement
The terms we hold ourselves to.
- Your accounts, from day one. Code in your repository, campaigns in your ad accounts, CRM in your tenant. We do not develop in private and deliver a zip file.
- You own the output. Full IP assignment on delivery. Nothing we build depends on a licence from us.
- Fixed scope, fixed price. If we underestimate, that is our cost to absorb, not a change request.
- One weekly written update. Sent whether or not the news is good.
- An exit clause in every contract. How it ends, what you keep, what you owe — agreed before it starts.
- We will tell you when to stop. Including when the honest recommendation is that you do not need us.
If we underestimate, that is our cost to absorb — not a change request.
— fixed scope, fixed price, in the contract
Hold us to any of it.
If something here does not match your experience of working with us, say so and we will fix it or refund the sprint. That commitment is in the contract, not just on this page.