About
We scope before we engage. Nothing is signed until the problem is sized, the work is bounded, and a named lead is accountable for the outcome.
Most advisory engagements are sold before the problem is understood. A proposal is written from a discovery call, a retainer starts, and the first month is spent finding out what the work actually is. The client pays for that month either way.
We work the other way round. We diagnose first, in a bounded piece of work with its own deliverable, and only then do we scope the engagement. You see the problem sized before you commit to fixing it, and if the answer is that you do not need us, that is a legitimate outcome of the diagnostic rather than a failed sale.
A scoping period of up to ninety days can precede a full engagement, depending on how tangled the operation is. Everything is defined before the build starts: what is in scope, what is explicitly not, who the named lead is, how long it takes, and what the outcome looks like in your numbers.
Two things follow from that discipline. The scope does not grow on its own, because it was written down. And there is no ambiguity about who is accountable, because one person's name is on it.
We do not consider the work done until the numbers have moved.
What you get
of the annual cost of a senior revenue or GTM hire, which runs $160K–$200K per year. Scoped to a defined outcome, with no long-term overhead.
The Engagement Arc
A structured first phase: CRM data, team interviews, pipeline review, reporting audit. We find every layer of the problem rather than the first one that presents. You get the findings whether or not you go further.
A written brief: what we found, what we will fix, what we will not, how long it takes, and what the outcome looks like. This is the document the engagement is judged against, and it is agreed before anything is signed.
We embed and execute. Process, CRM rebuild, outbound infrastructure, reporting, AI workflows, whatever the brief specifies. A named Grand Oak lead is accountable throughout and is the person you call when something is wrong.
Documented, trained, and owned by your team. Systems your people can operate and change without us. The engagement is designed to end, and a dependency on us would be a failure of the design.
What This Rules Out
Scope that grows on its own
The brief states what is out of scope as clearly as what is in it. Work outside that is a new conversation with its own scope, not an invoice that quietly gets larger each month.
Senior pitch, junior delivery
The people who scope the work are the people who do it. You are not sold on an experienced operator and then handed to someone learning on your account.
A strategy document and an invoice
We build and run the thing. A deck describing what you should do is not a deliverable we would charge for, because it does not move the number on its own.
Permanent dependency
Handover is a phase of the engagement, not a favour at the end. If your team cannot run the system after we leave, the work is not finished.
Tell us where the revenue operation is breaking down. We will scope the diagnostic and come back with what it covers, what it costs, and what you will have at the end of it.
Get in Touch