Engagement 01 of 04
Revenue Diagnostic
A structured read of your revenue engine across five layers, and a ranked order of repair.
The Diagnostic is how most Revops engagements open. Three weeks, a fixed scope, and a written answer to one question: where is the revenue leaking, and what should be repaired first. It is priced because it is real work, and credited against whatever the client decides to do next.
Deliverables
What you get.
A diagnostic that produces only a conversation has failed. These are the documents you keep, whatever you decide afterwards.
- Five-layer assessment across Data, Context, Workflows, Action and Control
- Leakage map showing where signal is lost, delayed or never acted on
- Maturity score per layer, with the evidence behind each score
- Ranked repair plan: what to fix first, what to fix later, what to leave alone
- Effort and expected effect for each item in the plan
- Two-hour restitution session with the people who would run the work
Delivery
How it runs.
Week 1. Access and interviews
Read-only CRM access, stack inventory, 5 to 8 interviews of 45 minutes.
Week 2. Analysis
Data extraction, process reconstruction, layer scoring, leakage quantification.
Week 3. Restitution
Written report, ranked repair plan, two-hour session, arbitration on priorities.
Team
Who is involved.
Revops side
One lead consultant.
Client side
One sponsor, one operational referent, 5 to 8 interviewees for 45 minutes each.
Boundary
What this engagement does not include.
The exclusions matter more on a diagnostic than anywhere else, because the value of the read depends on nothing being touched while it happens.
- No configuration. Nothing is modified in your environment during the Diagnostic.
- No training. No tool selection. No implementation.
- No commitment to continue. The report is yours either way.
Questions
Frequently asked
Why is the Diagnostic paid?
What access do you need?
What if the diagnosis says we are fine?
Next
Where it leads.
Revenue Blueprint if the commercial logic is the problem. Revenue Build if the logic is sound and the system is not.
