Work · Growth architecture

Building a growth model that started with revenue, not leads.

We already knew how many leads were coming in. That was not the hard part. The harder question was whether the rest of the business could turn that demand into revenue—and, if not, where the system was breaking first.

FocusDemand · qualification · capacity · conversion · economics
ShiftFrom channel and lead metrics to one connected operating model
UsePlanning, investment decisions, forecasting and constraint diagnosis
My roleExecutive design of the measurement, planning and decision framework

The lead number was visible. The constraint was not.

A revenue gap can be caused by weak demand. It can also be caused by poor qualification, missed appointments, limited sales capacity, weak conversion, bad economics or simply the time it takes to move through the cycle.

If every gap gets translated into “we need more leads,” the business can spend more money and make the actual constraint worse. I wanted a model that showed the whole path clearly enough that we could see what was really limiting growth.

We stopped treating the funnel as a marketing report.

The useful view was the complete path from demand to revenue. Every stage had its own metric, but no stage made much sense without the stages around it.

Demand
Qualified
Conversation
Capacity
Conversion
Revenue
Economics
Acquisition cost and value
Measurement
Source, quality and outcome
Timing
Lag between demand and revenue
The model is intentionally simple. The point is to make the weak link visible before deciding which team or budget should change.

Start with the revenue gap and work backward.

I prefer models that a room full of people can challenge. The math does not need to be impressive. The assumptions need to be visible.

RevenueHow much incremental revenue is actually required?

Start with the business target, not the marketing budget.

CustomersHow many new customers does that imply?

Translate the gap into a concrete customer requirement.

OpportunitiesHow many real sales opportunities are needed?

Expose the close-rate assumption rather than burying it.

DemandHow much qualified demand must be created?

Work backward through qualification instead of treating every lead the same.

CapacityCan the team actually process that volume?

A mathematically sufficient funnel can still fail operationally.

EconomicsWhat does that demand cost, and is the value worth it?

Connect acquisition spending to contribution, not just activity.

What this looked like once it became an operating system.

These are sanitized reconstructions of the forecast, scorecard, routing and weekly dashboard logic behind the work. They are here to show how the decisions were structured, not to publish internal company reporting.

Forecast fragmentWeekly outcome plan: baseline → milestone → stretch
Sanitized planning example
Baseline14completed conversations / week
Milestone30minimum operating target
Stretch46requires added demand + capacity
Show-rate assumption68%
Target cost / completed outcome$750
Planned capacity near milestone~3.5 FTE
The forecast ties every target to the operating conditions required to support it. Volume, show behavior, acquisition economics and capacity stay connected.
KPI architectureLeading → operating → business outcome
Scorecard logic
LeadingIs enough useful demand entering?
  • Source and volume
  • Qualified demand
  • Booked conversations
OperatingCan the system process it well?
  • Show behavior
  • Capacity utilization
  • Cycle and routing
OutcomeIs it creating economic value?
  • Completed outcome
  • Cost per outcome
  • Close / revenue outcome
An upstream metric only matters if it helps explain what happens downstream.
Workflow fragmentKeep fit and readiness as separate decisions
CRM / automation
Stage
Signal
Fit
Readiness
Route
Schedule
Outcome
System
Capture
Score
Classify
Assign
Confirm
Record
Human
Context
Exception
Judgment
Ownership
Conversation
Decision
Automation handles repeatable structureHumans keep judgment and exceptions
The system creates consistency without forcing nuanced eligibility or readiness decisions into one score.
Executive dashboard fragmentA weekly view built for decisions, not reporting volume
Sanitized scorecard
Weekly completed outcome14
Baseline · needs growth
Milestone target30 / week
Gap visible by source
Target acquisition cost$750
Manage to completed outcome
Show-rate assumption68%
Operating conversion
Capacity3.5 FTE
Near milestone requirement
DecisionWhere is the gap?
Demand · quality · capacity · conversion · economics
Weekly view: actual / target / trailing context / gapOnly surface metrics that can change a decision.
The scorecard keeps current performance, target, trailing context and the size of the gap in one place—then adds just enough detail to decide what to do next.

Before spending more, find the first place the system breaks.

DemandNot enough qualified demand is entering.

The answer may be acquisition, distribution, positioning or better audience quality.

QualificationThere is volume, but too little of it is useful.

Fix fit, targeting, scoring or the definition of a qualified opportunity first.

CapacityThe team cannot process the available demand well.

More volume can create slower follow-up, lower conversion and worse economics.

ConversionEnough opportunities exist, but too few become customers.

The problem may sit in sales execution, offer, pricing, proof or customer fit.

EconomicsThe system can grow, but not at acceptable cost.

Growth that destroys contribution is not fixed by increasing its volume.

TimingThe plan ignores the lag between activity and revenue.

Forecasts need to respect the time required for qualification, scheduling and closing.

The KPI stack had one job: show what decision to make next.

I organized metrics around the questions they answer, not the system where they happen to live.

DemandSource · volume · acquisition costAre we creating enough demand efficiently?
QualityQualification · fit · routingIs the demand useful?
ConversationScheduled · completed · show behaviorDoes qualified demand reach a real sales interaction?
CapacityAvailable selling capacity · utilizationCan the organization absorb more?
ConversionClose rate · cycle · downstream outcomeDoes opportunity become business?
EconomicsCost per outcome · revenue · contributionShould we scale it?
One model

The practical result was a shared way to pressure-test growth plans, separate a demand problem from an operating problem, and decide which constraint deserved attention first.

A revenue target becomes useful when everyone can see what it requires.

01
A revenue target is not a marketing target.

Revenue depends on the whole chain. Marketing can create demand; it cannot independently create sales capacity or close rate.

02
Capacity belongs in acquisition economics.

If demand cannot be processed well, the effective cost of acquiring a customer rises even if channel metrics look stable.

03
Simple models are often easier to operate.

If leaders can see and challenge the assumptions, the model improves the decision instead of becoming another black box.

04
Do not optimize one stage at the expense of the whole system.

The best local metric can still produce a worse business outcome if it pushes pressure somewhere else in the chain.

This case describes the operating architecture rather than company-specific commercial volumes. The visual fragments are sanitized recreations of real planning and operating structures.
← All selected work