How we work
Evidence first. Then build.
We don’t open with a rebuild proposal. We start by finding the one constraint costing the most, because fixing the wrong thing well is still the wrong thing.
- 01
Diagnose
1–2 weeks
We map how demand reaches you today and follow it all the way to closed revenue — search visibility, conversion paths, intake, follow-up, and what your data can and cannot tell you.
What you receive
- Findings ranked by revenue impact
- A clear statement of the single biggest constraint
- Baseline numbers to measure everything else against
- 02
Map
1 week
The customer journey, the workflows behind it, and the systems holding it together — including the exceptions and workarounds nobody documents, because those are usually load-bearing.
What you receive
- Current-state workflow, exceptions included
- System and data-flow map
- The handoffs where things are being lost
- 03
Prioritise
1 week
A phased plan with the sequence, the trade-offs, and the number each phase is accountable for. Stated explicitly rather than buried in a proposal.
What you receive
- Phased roadmap with scope and sequencing
- The target metric for each phase
- Fixed pricing per phase, not an open retainer
- 04
Build
4–12 weeks typical
We ship in working increments — something usable in production every couple of weeks. You see progress continuously instead of waiting for a reveal at the end.
What you receive
- Working systems in production, not prototypes
- Documentation your team can maintain
- Handover and training as part of the build
- 05
Connect
2–4 weeks
Integrating the stack so data stops being re-keyed between tools, and so one record is true everywhere it appears.
What you receive
- Integrations between marketing, sales and delivery
- A single source of truth per entity
- Monitoring on the connections that matter
- 06
Optimise
Ongoing
Attribution and reporting go live alongside the build, so you can see what the work produced. Then we act on it — the plan changes when the evidence says it should.
What you receive
- Attribution from first touch to closed revenue
- Reporting your leadership team will actually read
- A prioritised backlog for the next increment
What this isn’t
A few things we deliberately don’t do.
No 12-month lock-ins
Phases are priced and committed individually. If phase one does not earn phase two, you walk.
No vanity reporting
Impressions and rankings are diagnostics, not results. We report on qualified leads and revenue.
No black boxes
You own every account, repository and system we touch. Leaving should always be possible.
Questions
What people ask before starting.
Do we have to start with the diagnosis?
Almost always, yes. Skipping it means guessing at the constraint, and the most expensive projects we see are the ones that fixed something that was working. The diagnosis is short and priced separately.
What if the diagnosis says we do not need you?
Then we say so, and you keep the findings. That happens often enough that we plan for it — a diagnosis you can act on yourself is still a good outcome for both sides.
How involved does our team need to be?
Most during Diagnose and Map, where we need people who actually do the work rather than a description of it. Expect a few hours a week for two or three people, then considerably less during Build.
Can you work with the systems we already have?
Usually, and usually that is the right answer. Replacing a working platform is expensive; configuring and connecting it properly is not. We will tell you when replacement is genuinely warranted.
Want to see what the diagnosis would find?
30 minutes, no pitch. If we’re not the right fit, we’ll tell you that too.