Executive Operating Model

$120M → $155M: the whole business on one model

Meridian Cloud is a fictional $120M ARR infrastructure software company with a $155M target. This model connects that target to everything that has to be true for it to happen: the ARR bridge, retention, pipeline requirement, seller capacity, ramp, territories, quota and payback. The output is the operating review a CRO and CFO argue over — not a dashboard.

Headline

Ending ARR

—

Net revenue retention

—

Pipeline required

—

CAC payback

—

Assumptions

Every number on this page moves off these five levers and the retention inputs below.

Gross revenue retention

Expansion rate

Quota-carrying AEs (end of year)

Average quota

Quota attainment

Ramp to full productivity

Win rate (SQL → closed won)

Blended S&M cost per AE

ARR bridge

Beginning ARR to ending ARR, and whether the plan closes the gap to $155M.

Component	$	% of beginning ARR	Note

Segment performance

Where the new business has to come from, and what each segment costs to serve.

Segment	Beginning ARR	New ARR plan	ASP	Deals needed	NRR	Cycle

Capacity, ramp and territories

Attainable capacity vs. plan

Territory and coverage load

Efficiency

Magic number

—

Net new ARR ÷ prior-period S&M

S&M spend

—

ARR per AE

—

Productivity at plan attainment

Rule of 40

—

Growth + assumed margin

Coverage required

—

Pipeline ÷ new ARR plan

Gap to target

—

The operating review

One page. This is what goes in front of the CRO and CFO — the position, the constraint, the decision being asked for.

On the data: Meridian Cloud is fictional and the figures are illustrative. The model structure, the linkages between levers, and the operating review format are the work product.