Revenue Diagnostic
Where the engine leaks, and what to fix first.
- Duration
- 3 weeks
- Prerequisite
- None. This is the entry point.
Each one is scoped, dated and bounded.
An engagement has a duration, a defined scope, a named set of deliverables and a written boundary stating what it does not include. We work this way because open-ended consulting is how both sides end up disappointed. The map of the discipline itself, four domains and twenty-one capabilities, lives under RevOps. Read it to locate the problem. The work itself is scoped here.
The sequence
Diagnostic, Blueprint, Build, Operate.
Each engagement takes the previous one as its input. That is why the sequence matters more than the individual scopes: a Build quoted without a Blueprint is a guess, and a Blueprint written without a Diagnostic solves the wrong layer.
Revenue Blueprint
The commercial logic, written to be built from.
- Duration
- 4 to 8 weeks
- Prerequisite
- A Revenue Diagnostic, or an equivalent documented assessment we can audit.
Revenue Build
The logic, running in your existing stack.
- Duration
- 6 to 12 weeks
- Prerequisite
- A Revenue Blueprint, or an existing written specification we can audit.
Revenue Operate
Motions operated to a standard, then transferred.
- Duration
- Recurring
- Prerequisite
- A Revenue Build, or an existing system we have audited and can operate inside.
Where it starts
The Diagnostic decides the rest.
Three weeks, fixed scope, fixed price, creditable against whatever follows within ninety days. It exists because scoping a build without reading the engine produces a proposal that is wrong in ways nobody can see yet, including us. A company arriving with a documented assessment we can audit starts further down the sequence.
What comes after it is not a choice between products. It is whatever the read finds, and the four situations below account for almost all of them.
- A
The commercial logic is unclear or contested
The teams are not operating the same process, and configuration cannot settle a disagreement about definitions. The logic has to be written down before anything is built. That work is a Blueprint.
- B
The logic is sound, the system does not carry it
The rules exist on paper and break in practice. Nothing needs rethinking, so the remaining work is implementation. That work is a Build.
- C
The system holds, execution is the constraint
The engine is fine. The motion is simply not being run to a standard, day after day. That work is an Operate engagement.
- D
Nothing is broken enough to justify the work
We say so, and it ends at the Diagnostic. It is a better outcome than a project nobody needed.
What sits underneath
The discipline behind the engagements.
Every engagement draws on the same four domains and twenty-one capabilities. They are documented in full under RevOps, with the boundary between each one stated explicitly.
Designs the commercial logic
Revenue Design
Build the operating logic that turns demand into revenue.
Explore Revenue Design- Acquisition & DemandDesign the acquisition model and the entry points into the revenue journey.
- Lead ManagementDefine lifecycle, ownership, prioritization, nurture and recycling rules.
- Sales PipelineDesign stages, evidence, progression rules and management cadence.
- Customer RevenueStructure onboarding, retention, renewal, expansion and reactivation.
- Revenue IntelligenceTurn commercial signals into diagnostic and management decisions.
Makes the logic executable
Revenue Systems
Make your revenue infrastructure operate as one system.
Explore Revenue Systems- CRM & Revenue DataLifecycle, objects, fields, ownership and data governance.
- Workflow AutomationTriggers, rules, actions, exceptions and escalation.
- Lead RoutingAssignment logic based on fit, intent, territory, language, offer or capacity.
- Opportunity ManagementSystem controls that operationalize the sales pipeline.
- Reporting & ForecastingGoverned definitions, dashboards and forecast logic.
- Integrations & ArchitectureConnect the required stack without creating technical debt.
Operates the motions
Revenue Execution
Add execution capacity without losing control of the revenue process.
Explore Revenue Execution- SDR & ProspectingStructured outbound targeting, calling and follow-up.
- QualificationConsistent decisions on fit, intent, need, timing and next action.
- ReactivationRecover value from dormant leads, lost opportunities and inactive customers.
- Customer EngagementOperate customer conversations while preserving context and ownership.
- Revenue CampaignsCoordinate growth, systems and sales follow-up as one motion.
Creates the signals
Growth & Content
Create attention that the revenue system can recognize and act on.
Explore Growth & Content- Demand GenerationCampaign programs that create and capture buying signals.
- Performance MarketingPaid acquisition optimized beyond platform-level metrics.
- Content & CreativeMessaging and assets with a defined commercial role.
- Social MediaStructured narratives, publishing and conversion paths.
- Video & MediaReusable video assets designed for attention, proof and response.
How they work together
Signals in, revenue out.
Growth creates the signals, the engine designs how they are treated, systems make that executable and execution operates it. What execution learns flows back into the design.
Clear boundaries
Where one solution ends and the next begins.
Some solutions sit close together. Each one owns a different part of the problem, so you can start with the one that matches yours.
Acquisition & Demand designs the acquisition architecture: ICP, channel roles, conversion model, economics, lifecycle entry points and handoffs. Demand Generation operates market programs that create buying signals through campaigns, content, offers and distribution.
Sales Pipeline designs the business process: stages, qualification gates, exit criteria, buying progress and sales governance. Opportunity Management implements that logic in systems: CRM fields, tasks, approvals, alerts, controls and deal hygiene.
Reporting & Forecasting establishes operational truth: definitions, dashboards, actuals, pipeline views and forecasts. Revenue Intelligence turns that truth into decisions: patterns, anomalies, risk signals, diagnostic questions, recommendations and management action.
Lead Management owns lifecycle logic and the rules for handling a lead. Lead Routing implements assignment. Qualification is the human or assisted execution of the decision.
Demand Generation creates and distributes demand programs. Revenue Campaigns orchestrates the full cross-functional motion from audience and creative through CRM, routing, sales follow-up and revenue measurement.
Explore by problem
Or start from the symptom you can already see.
Each symptom names the layer that usually causes it, and the solution that owns the fix.
Unprocessed leads
Signals arrive and nothing happens to them.
Workflows layerLead ManagementLeads that do not convert
Volume is fine. The standard applied to it is not.
Context layerQualificationPoorly used CRM
The system of record records almost nothing.
Data layerCRM & Revenue DataSales and marketing silos
Two teams, two definitions, one lost handover.
Workflows layerAcquisition & DemandLimited pipeline visibility
You find out the quarter is missed inside the quarter.
Control layerReporting & ForecastingLost opportunities
Deals stall quietly and nobody is alerted.
Action layerOpportunity ManagementScattered data
Six tools, six truths, no shared model.
Data layerIntegrations & ArchitectureManual tasks
People are the integration layer.
Workflows layerWorkflow Automation
Questions
Frequently asked
Can we start with a Build instead of a Diagnostic?
Yes, when you already hold a documented assessment we can audit. Without one, we would be pricing a build from assumptions, and the rework costs more than the read would have.
How is pricing structured?
Fixed price per engagement for Diagnostic, Blueprint and Build, scoped after the previous step. Operate is a monthly fee based on the motions and capacity involved.
What does the engagement require from our side?
One sponsor, one operational referent, and a few hours per week from the teams in scope. The offer pages state the commitment for each engagement.
Start where the sequence opens.
Five fields. We reply within one working day.