The Operator's Guide to the Commercial Operating Model

Most portfolio companies arrive with a commercial function assembled by accretion. The first sales leader built the motion. The first marketing leader built the demand engine. The first CS leader added retention. Each layer was added when the previous one stopped working, and nobody ever redesigned the system.

The commercial operating model is the blueprint for the redesign.

What's at stake

A mid-market portco running on a patched-together commercial model typically loses 10-20% of its revenue potential to structural friction: duplicated work between marketing and sales, handoffs that drop accountability, retention efforts that start after the customer has already disengaged, and pricing that isn't governed against the revenue motion.

At a $50M ARR portco, that structural friction equals $5M-$10M of annual value. Across a portfolio of eight SaaS portcos, the commercial operating model work is often worth more than pricing strategy, sales training, and marketing investment combined. It's foundational work that makes all the other work stick.

The framework

1. Define the revenue engine in one diagram

Why it matters. If you can't draw the commercial operating model on a single page, the team can't operate it. Complexity is where accountability hides.

What to do. Map the full funnel: lead source, qualification, opportunity stages, close, onboarding, expansion, renewal. Name the function that owns each stage. Name the metric that governs each transition.

Common failure mode. Maps that run across four slides with different definitions on each. The map has to fit on one page or it doesn't function as a map.

2. Assign clear ownership for each stage

Why it matters. Every stage needs exactly one owner. When two functions share ownership, neither owns it.

What to do. Build a RACI (responsible, accountable, consulted, informed) for each stage. There is one "accountable" per stage.

Common failure mode. Dual accountability between marketing and sales on mid-funnel stages. Lead conversion suffers because both functions assume the other owns it.

3. Install a single revenue dashboard

Why it matters. If marketing reports pipeline in one tool, sales reports in another, and CS reports retention in a third, cross-functional conversations reconcile data instead of making decisions.

What to do. Pick one dashboard as the source of truth. Decommission the alternatives. Use it in every operating review.

Common failure mode. Building the dashboard without killing the alternatives. Executives keep private spreadsheets because they trust them more than the dashboard.

4. Define the metrics layer around customer lifetime value

Why it matters. Most commercial operating models optimize for acquisition metrics (MQL, SQL, bookings) and ignore the downstream economics. A model that closes fast and churns faster destroys value.

What to do. Track CAC (customer acquisition cost), CAC payback, LTV (lifetime value), and LTV-to-CAC ratio across acquisition channels. Retention metrics belong in the commercial dashboard, not in a separate CS view.

Common failure mode. Reporting bookings and pipeline in a commercial review without retention. The commercial engine looks healthy until the retention cliff arrives two quarters later.

5. Install governance at each handoff

Why it matters. Handoffs are where accountability dies silently. Marketing-to-sales, sales-to-onboarding, onboarding-to-CS, CS-to-renewals. Each handoff is a failure point.

What to do. Define SLAs (service-level agreements) at each handoff. Measure whether SLAs are met. Escalate misses.

Common failure mode. Assuming handoffs work because the team has been doing them for years. They don't. They fail silently, and nobody files a ticket about silent failures.

6. Tie compensation to the operating model

Why it matters. If comp plans reward behavior the operating model is trying to prevent, the plans win.

What to do. Align comp to the stage each function owns. Marketing on accepted pipeline, sales on net ACV, CS on NRR (net revenue retention). Kill activity-based comp.

Common failure mode. Running the operating model with legacy comp. The model says "focus on NRR." The comp plan pays on gross bookings. The team does what the comp plan tells them.

7. Review the operating model quarterly against results

Why it matters. Operating models decay. Team rotations, priority shifts, and political pressure erode the system. Without a quarterly reset, the model returns to its default patchwork state.

What to do. Run a quarterly review: stage conversion rates, handoff SLA performance, CAC payback by channel, NRR by cohort. Compare to targets. Adjust.

Common failure mode. Designing the operating model once and assuming it holds. It doesn't.

Diagnostic questions

• Can your CEO, CMO, CRO, and CS leader each draw the same commercial funnel on a whiteboard?
• Is there exactly one owner for each stage, or are ownership lines fuzzy?
• Do all commercial functions report from the same dashboard?
• Is CAC (customer acquisition cost) payback tracked by acquisition channel?
• Are there defined SLAs (service-level agreements) at each handoff?
• Does your sales comp plan align with the stage sales actually owns, or with legacy quota mechanics?
• When was the last quarterly review of the operating model itself, not just the results it produced?

Immediate next steps

• Map the full funnel on one page with owners and metrics for your largest portco
• Consolidate commercial reporting into one dashboard and decommission alternatives
• Audit handoff SLAs across your portcos and identify the biggest silent failure
• Review comp plans for alignment to operating model ownership, not legacy mechanics

Common mistakes

• Reorganizing the org chart without fixing the system. A $45M ARR portco reshuffled functions four times in two years. Same problems, different titles.
• Running commercial reviews on different data sets. A $30M ARR portco had marketing reporting 3x coverage and sales reporting 1.5x on the same pipeline. Every meeting reconciled instead of decided.
• Ignoring retention until it hit the board deck. A $55M ARR portco ran weekly pipeline reviews and quarterly CS reviews. By the time NRR showed up on the operating partner dashboard, two cohorts had already churned.
• Installing the system without fixing comp. A $35M ARR portco built the operating model but left legacy comp plans in place. The behavior the plans rewarded pulled the team away from the new system within two quarters.

---

Run the free assessment or book a consultation to apply this framework to your specific situation.