APPROACH
How we actually run this
A short version of our operating manual. If any of it sounds like something you would fight us on, better to know now.
PRINCIPLES
Four rules we work by
One thing at a time
Parallel changes mean you never learn which one worked. We change one variable, let it run long enough to read, then move on. It feels slower for a month and it is faster for a year.
Numbers agreed before the work
Including the ones we will ignore. If a metric is not going to change a decision, it does not go in the report. We write down what counts as a qualified lead before anything is built.
Written handover rules
Anything that lives in someone's head breaks when they are on holiday. Routing, qualification and escalation are documented, in your systems, in plain language.
We say when something is not working
Early, including when it is our fault. If a channel is not going to pay back, you hear it from us before you hear it from your finance team.
RHYTHM
The working rhythm
Weekly, monthly, quarterly and always. The cadence is the product as much as the work is.
Weekly
01What we look at and what we ignore
A short pass over the things that can actually move in a week, and a deliberate refusal to react to the things that cannot.
- Enquiries by stage, and what was asked
- Anything broken: tracking, routing, pages
- No rank checking, no traffic noise, no daily dashboards
Monthly
02The review and what can change
The same numbers in the same format, followed by a decision. Changes are agreed here rather than drifting in between.
- What moved and what did not
- One change proposed, with the reason
- Anything we want to stop doing
Quarterly
03What gets stopped
A quarter is long enough to tell signal from noise. This is where work is retired rather than quietly kept alive.
- Channels or pages that did not pay back
- Assistant flows nobody used
- Reporting that never changed a decision
Always
04How to reach us and how fast we answer
One person, one channel, no ticket queue. Urgent means something is broken in production, not that a report is late.
- Reply within within two working days on working days
- Same person across all three stages
- Escalation path written down at kickoff
ACCESS
Tooling and access
You own every account and every record. We work inside your systems, never a copy we control.
What we need
- Analytics and search console, read or admin as you prefer
- The CMS or repository for the pages we change
- The CRM or inbox where enquiries land
- One person who can answer product questions within a day
What we never ask for
- Bank, payment or finance systems
- Customer data beyond what an enquiry contains
- Personal logins shared between people
At the end of an engagement the accounts, the data, the documentation and the assistant configuration stay with you. Nothing needs to be handed back, because none of it was ever ours.
- AI assistant platform
- Language model provider
- First-party reporting
- Search Console
- Client-owned CRM
LIMITS
What we will not do
Next step
If this is how youwant to work, say so
Thirty minutes to check the working method against how your team actually operates.
No deck, no pitch, you leave with a plan.