How to Build a Growth Operating System
Your commercial team is running four improvement projects at once. Pricing is under review. Sales has a new methodology. Marketing rebuilt the funnel. Product is reworking the tiers. None of them compound, because each was designed as if the other three did not exist. A growth operating system connects pricing, sales, marketing, and product into one system where every decision references the same customer, the same price logic, and the same scorecard. This guide covers the four modules, the commercial operating model underneath them, the go-to-market alignment tests, the 90-day install, where it breaks, and how to measure it.
Your P&L Is Paying for Disconnected Fixes
The standard approach to commercial improvement is to find the loudest pain and fix it. Win rate drops, so you hire a sales consultant. NRR slides, so customer success gets a playbook. Pricing feels arbitrary, so you run a repricing exercise. Each project produces a brief improvement, then stalls, because commercial performance is a system and you fixed one part of it.
Somewhere in your pipeline a rep is discounting 18% because a deal feels like it might slip. Somewhere in marketing a campaign is live because it worked two years ago. Neither is a bad decision. Each is a habit that was never written down as a belief, so it was never tested.
Left without a governing system, commercial behavior drifts toward whatever reduces friction this quarter. Discounts rise because they close deals faster. ICP boundaries blur because a logo feels like growth even when the customer will not stay. Tiers lose coherence because every enterprise negotiation adds an exception. The cost is not dramatic. It is a 2-point rise in average discount per year, a 3-point NRR decline per cohort, a 10% longer sales cycle. None of those triggers a board call. Over 36 months they compound into a structural problem that costs real money to unwind; across our engagements the revenue left uncaptured typically runs 10-20% of the top line.
Strip away the frameworks and a growth operating system has three components. A precise model of who creates durable value for you: not who buys, but who buys, stays, expands, and refers. A pricing and packaging structure that captures a fair share of that value, because pricing is a signal before it is a number. And a commercial cadence that keeps both calibrated and produces at least one structural decision a month. Everything else on this page is mechanics for installing those three.
Fixing pricing without fixing sales creates pricing shelfware
A new price architecture needs a new sales motion. If your reps lack the qualification criteria, the negotiation skill, and the objection playbook to defend it, they discount their way back to the old effective price within two quarters. The new list becomes the starting point for the same negotiation.
Fixing GTM without fixing packaging creates demand without conversion
New positioning and a better channel mix bring more qualified buyers into the funnel. If the packaging does not communicate the value the positioning claims, they will not convert at the price it implies. Marketing generates interest the product architecture cannot close.
Fixing sales without fixing qualification fills the pipeline with the wrong deals
A better-coached team closes more deals. If the ICP is loose and the qualification gate does not enforce it, the team closes more of the wrong deals: lower ACV, higher churn, higher cost to serve. Win rate improves this quarter. NRR and CAC payback deteriorate over the next four.
The Four Modules of the Growth Operating System
Each module is a complete commercial subsystem with its own diagnostic, architecture, and cadence. The output of each is an input to the next: pricing informs packaging, packaging informs positioning, positioning informs the sales playbook, and sales data feeds back into pricing.
Pricing Engine
Architecture (what you charge and how it is denominated), governance (who can discount, under what condition, up to what amount), and analytics (pocket price by segment and rep). A functioning Pricing Engine keeps the gap between list and pocket steady and intentional, and shows customers moving up tiers on their own.
- + Value metric selection and validation
- + Packaging architecture and tier design
- + Discount authority matrix and deal desk
- + Pocket price analytics and cohort reporting
Sales Operating System
Qualification (finding the right buyers before you spend expensive time on them), negotiation (defending price through value), and pipeline velocity (removing friction stage by stage). A functioning Sales Operating System produces consistent win rates by segment, a declining average discount, and shorter cycles for qualified deals. Sales capability assessment tells you whether the reps can run it.
- + ICP definition and qualification gates
- + Value-based negotiation playbooks
- + Stage exit criteria written as observable behaviors
- + Rep-level coaching and comp alignment
GTM Architecture
Positioning (the specific claim you make in your market), channel strategy (which channels reach your ICP and retain them), and conversion (first touch to close). A functioning GTM architecture funds channels by retention rather than lead volume, and gives reps positioning they use in the first minute of discovery.
- + Segment-specific positioning and messaging
- + Channel mix funded by cohort NRR
- + Handoff criteria based on commercial fit
- + Category design and competitive framing
Product-Revenue Alignment
Packaging (which features sit in which tier and why), monetization (whether a new feature is packaged for expansion or absorbed at no incremental price), and roadmap prioritization (how commercial data shapes what gets built). A functioning module produces expansion without a CS upsell call, because the value metric grows with the customer.
- + Feature-to-tier mapping by buyer outcome
- + Expansion trigger design and CS playbooks
- + New feature monetization framework
- + Roadmap-to-revenue impact modeling
The Commercial Operating Model: Three Structural Decisions Before the First Hire
The commercial operating model is the mechanism layer of the Growth Operating System on the revenue side: the value metric, the pricing architecture, the compensation design, the deal desk, and the metrics that hold them together. It is not a strategy document. Build it well and it runs mostly without you. Build it badly and every commercial decision becomes a negotiation between the model and whoever has the most urgency that afternoon. Urgency usually wins. That is how good strategies produce bad results.
Every model is built on a belief about the buyer, and the belief is rarely written down. Brennock Infrastructure Software, $31M ARR, rebuilt its commercial model three times in four years. Each redesign assumed the buyer was an IT director who had to justify the purchase to a CFO. The win data, when someone finally read it, showed 68% of the best accounts were initiated by a VP of Engineering who already had budget. The IT director was a gatekeeper. Rebuilt around the real buyer, median cycle fell from 94 to 51 days and ACV rose 28%. Write the belief down before you build on it.
Design the pricing architecture around a value metric
Your value metric is what grows as the customer gets more value: seats, records processed, locations, revenue through the platform. When price scales with it, expansion happens without a sales call. When price is flat regardless of usage, your top decile gets several times the value of your median customer at the same price, and NRR stalls just above 100%. Would your top 20 accounts accept pricing tied to that metric? If yes, rebuild the packaging around it before you add a rep.
Write a compensation plan that rewards what the model needs
List the three behaviors the model needs from a rep. Usually: qualify hard, hold price, close customers who expand. Now read your comp plan. Most plans pay on new ARR closed, which pressures reps to do the opposite of all three. Deal governance protects margin; sales comp alignment keeps it. Weight expansion, set a minimum ACV, and pay on pocket price rather than list wherever you can. Sales compensation alignment covers the mechanics, clawbacks and discount floors included.
Install the deal desk before you need it
A deal desk is governance, not bureaucracy: the process that triggers above a discount threshold, on non-standard terms, or on a restructured payment schedule. At eight reps a founder holds the line personally. At 25, nobody can, and nobody else was given the authority. Set the bands, name the approvers, put a 48-hour service level on escalations, and run 15 deals through it before you scale. An exception approval rate above 60% is a suggestion box, not governance. The AI commercial operating model diagnostic shows a routed deal desk with human gates once volume outgrows email.
Larkin Legal Software, $23M ARR, missed bookings plan two quarters running by more than 20% and blamed demand gen volume. The comp plan paid a flat 8% on all new ARR, so a $6K deal with a 90-day cycle earned the same rate as a $60K deal with a six-month cycle, and reps rationally filled the pipeline with $4K to $8K deals. Those deals were on-ICP by industry and size and churned at 67% in year one, because companies that small never reached value. A minimum ACV threshold and an ACV-weighted rate took three weeks to write. Two quarters later average ACV had moved from $9K to $17K and first-year churn from 67% to 38%. The model was selecting the customers. The reps were following it.
Then make the model survive the people. Document the GTM motion with exit criteria at every stage. Put four commercial quality metrics in the board pack next to revenue and EBITDA: pocket price as a percentage of list, NRR by cohort, CAC payback by channel, and deal desk cycle time. And break the dependency on one leader: a VP of Revenue who carries the discount policy in their head tends to leave within 12 to 24 months of a transaction, and the model leaves with them. The operator's guide to the commercial operating model covers the same three decisions in the language of a value creation plan.
Go-to-Market Alignment: The One-Sentence ICP Test and the 40-Deal Diagnostic
Go-to-market alignment is not a communication problem. You can run a weekly sales and marketing sync for two years and watch both functions pull in opposite directions, because they are working from different theories of who the customer is. Sales and marketing alignment in B2B is an agreement about the buyer, enforced through shared metrics. Everything else is meetings.
Halden HR Software spent 14 months and $1.2M building a self-serve product-led motion on the belief that individual contributors would adopt and expand. Every deal above $30K ACV told a different story: a VP of HR responding to a compliance event. The self-serve users churned at 63% in year one because they had no budget authority. The VP-initiated deals renewed at 91%. Restructuring around the VP took six weeks: ACV rose 34% and the cycle shortened by 22 days. Fourteen months on the wrong buyer, because nobody wrote the assumption down.
The one-sentence test
Ask your VP of Sales and VP of Marketing to write your ideal customer in one sentence, independently, with a title, a company profile, a trigger event, and a timeline. Something like: “VP-level buyers at manufacturers with 200 to 500 employees who manage compliance manually and are 90 days from an audit.” Compare them. They rarely match. Where they differ is where your GTM spend is going to waste.
The 40-deal diagnostic
Pull your last 40 closed-won deals and your last 20 churned accounts. For each, answer three questions: who was the buyer by title and seniority, what triggered the purchase, and what value driver did they cite. Score every deal against both sentences. Two patterns show up almost every time: a third or more of won revenue came from a profile marketing was not targeting, and the churned accounts fit the marketing sentence better than the won ones. The pattern across won and churned is your real ICP. Build the motion backward from it: rewrite the definition, adjust the channel mix, and rewrite the qualification gates to match.
Root the ICP in retention data, not acquisition data. Most companies define the ideal customer as whoever is easiest to close, which produces efficient pipelines and poor retention. Define it from your top retention quartile instead, then ask whether marketing is generating those customers and sales is qualifying for them. Rebuild the handoff around commercial fit, not activity: segment, size, role, budget, and a qualification conversation, not four whitepaper downloads. The GTM misalignment tax shows this at an analytics platform where three verticals were 22% of customers and 41% of revenue.
The operator's guide to go-to-market alignment runs the same tests with a hold period on the clock.
Channel-Level NRR: Fund the Channel That Retains
Most teams know pipeline volume by channel. Few track conversion, discount, and NRR by channel, which is the analysis that tells you whether a channel is funding growth or funding misalignment at scale. A channel with high volume, low conversion, deep discounts, and low retention looks productive on a volume dashboard and destructive on a quality dashboard. Marketing usually only has the first one.
Corvane Compliance, $48M ARR, ran two primary channels: partner referrals and direct outbound. Both looked productive on lead volume. Followed through to retention, partner referrals were 45% of pipeline at a 19% close rate and 91% NRR at twelve months. Outbound was 30% of pipeline at a 34% close rate and 107% NRR. Forty percent of the marketing budget was feeding the weaker channel. Moving a quarter of it to outbound and narrowing the partner program to the one vertical where referred NRR ran above 100% took blended NRR from 98% to 104% in four quarters.
Three measurement streams, run continuously:
- •Conversion by acquisition channel, measured from lead to closed-won, not from MQL to SQL
- •Pocket price discount by channel and by rep: a channel that discounts is attracting buyers who do not fit, and a rep who discounts alone has a skills or comp problem
- •NRR at twelve months by original channel and by first product sold, the long-lag indicator that is always already in your system
The install base is where the money is. The High Alpha and OpenView SaaS Benchmarks Report puts roughly 60% of new ARR at companies above $50M ARR as coming from existing customers, which means the channel that retains is your growth engine and the channel that merely converts is a cost. The operator's guide to net revenue retention covers the cohort mechanics.
The Revenue Triangle: Pricing, Marketing, and Product Tell One Story
Ask your marketing lead, product lead, and pricing lead to describe your value proposition in one sentence. Three different answers is not a messaging problem. It is a structural one. The three functions that decide how a customer perceives, experiences, and pays for your product have stopped coordinating, and the buyer experiences all three in sequence. Confusion is the enemy of willingness to pay.
Marlowe Analytics ran a premium positioning campaign, saw inbound rise 40%, and watched close rate fall from 28% to 19%. Pricing had added a $29 a month entry tier in the same quarter. Prospects who saw the premium messaging landed on the pricing page and asked sales “what's the catch?” before the first demo. Two quarters, $1.4M of stalled or lost deal value, and nobody had made a bad decision inside their own function.
The four-function test, scored
Extend the test to sales and run it casually, in separate conversations, without announcing it. Four aligned answers: optimize. Three and an outlier: investigate the outlier. Two and two: two competing narratives, and it is urgent. Four different answers: your commercial system is fighting itself. Twenty minutes, and it tells you more than a two-day audit.
The Value Proposition Alignment Map
One page, three columns: what marketing promises, what product delivers, what pricing quantifies, for your top three segments. Where the columns do not line up is your disconnection point. Fix the most visible conflict first, which is almost always the pricing page: tier names that use different language than the website, an entry price that contradicts the segment messaging, feature descriptions that do not match the demo. Then walk the first 30 days from ad impression to first login and note every signal at every transition. Premium homepage, mid-market pricing page, self-serve onboarding: three signals, three stories.
Then change the review cadence, not the org chart. A monthly 30-minute pricing-product sync with a fixed agenda (what shipped, how it changes pricing assumptions, what willingness-to-pay data exists) and a shared decision log. A one-page tier rationale for sales: why each tier exists, what it delivers, when to recommend it, and what to say instead of a discount. Reps do not need permission to hold price. They need the language. Commercial connective tissue follows a feature that 34 of 41 enterprise deals bundled for free because the three functions never agreed what it was worth.
Installation: The 90-Day Sprint Model
The system is not installed all at once, and it is not installed by a strategy deck. Sequencing comes from the diagnostic: which module has the largest gap and the fastest path to a measurable result. Why a $200K strategy deck loses to a 90-day sprint makes the case. This is the sequence.
Days 1-30: Diagnostic
Pull the four baseline numbers, score each module, and rank the gaps. The deliverable is a scored assessment, a ranked opportunity map, and one 90-day plan for the module where improvement produces the fastest, largest result. Not four plans. One.
Days 31-90: Install the first module
For most companies this is the Pricing Engine, if discount leakage is large and governance is absent, or the Sales Operating System, if win rates are falling and qualification is weak. The module lands with documentation, training, and CRM integration so your team owns it from week eight. A measurable result, usually a lower discount rate or a higher qualified pipeline rate, gates the next sprint.
Days 91-180: Install the adjacent modules
GTM Architecture is usually second after pricing, because new pricing needs updated positioning to be credible in market. Product-Revenue Alignment is usually third, because packaging cannot be redesigned until pricing and positioning are stable.
Days 181-270: Connect the system and transfer ownership
The modules are connected into one operating rhythm: a weekly commercial review, a quarterly packaging review, an annual repricing framework, and a hiring profile for the internal leader who will own it. At the end of this phase the growth operating system runs entirely inside your organization.
The 30-day loop inside every sprint
State the belief in one sentence: we believe this action will produce this outcome because of this evidence. If you cannot write it, you have a habit, not a hypothesis. Run the smallest test that produces signal: twelve deals, forty sequences, one segment. Then turn the result into a rule: a pricing floor, a qualification gate, a segmentation criterion, a comp threshold. Learning that does not become infrastructure gets overwritten by next quarter's pressure.
Build to Disappear
Every playbook, governance structure, and report is written for your team to run without us from the end of the second sprint. Governance is anchored in your existing management cadence. Analytics run on your existing data. We measure success by how quickly we make ourselves unnecessary.
The 18-Month Cliff in a PE Hold
The standard operating partner situation is not a failing company. It is a company that grew past the point where informal commercial execution scales, with a thesis that depends on roughly doubling ARR inside 36 months and no infrastructure to get there. The first year post-close looks fine. Pipeline is healthy, the team is energized, the targets create focus. Then the cracks show at month 18.
Sales headcount has doubled. Growth is 22% against 40% in the model. NRR has slipped from 109% to 103%. The VP of Sales hired at month six has spent a year managing a team instead of running a system. CAC payback has moved from 18 to 26 months. Do the math for your own portfolio company: 40% versus 22% growth over 18 months on a $25M base is roughly $11M of ARR, and at a 6x multiple that is $66M of enterprise value gone quietly.
Confusing motion for system
Headcount, marketing spend, and a channel program are activities, not a system. Activity added before governance generates pipeline the system cannot reliably convert or retain.
Transformation before triage
A portco with a 24% average discount and falling NRR does not need a new go-to-market strategy. It needs a pricing floor enforced and an ICP validated. Transformation before triage produces change without stability.
Designing for the board slide
If the CRO and the VP of customer success cannot describe the system, operate it, and adapt it without an external call, it is a reporting layer, not an operating system.
Days 1 to 90 are for baseline and structural triage, not transformation: pull the pocket price waterfall, cohort NRR, and the discount trend, identify which of the four failure patterns below is active, and fix that before adding any growth resource. The most common mistake is hiring ahead of the fix: a VP of Sales hired into an undefined ICP with no pricing governance fails within 18 months regardless of track record, because they build a team on the broken foundation. Days 91 to 270 build the three components with named owners inside the portco, and the operating partner shifts from builder to reviewer. The operator's guide to the Growth Operating System in PE-backed companies runs the full hold. If the baseline is being built before close rather than after, the PE pricing diligence guide is the diligence version.
The 90-minute review
Five questions for the CRO or VP of Sales. Three or more uncertain answers and the infrastructure gap is worth closing before the next growth investment.
- •What is the average effective discount rate, and which way is it trending
- •What is NRR by cohort for the last four acquisition quarters
- •What share of deals enter the formal pipeline without meeting the stated ICP
- •What structural decision came out of last week’s commercial review
- •When was the pricing floor last validated against willingness-to-pay data
Four Failure Patterns of a Growth Operating System
A Growth Operating System rarely breaks on a bad decision. It breaks on a successful quarter that nobody examined, and it accumulates. Four patterns account for most of it, each with a signature in data you already hold and a different fix.
ICP drift
Signature: churn rising in newer cohorts while older cohorts hold. The definition blurred under growth pressure and the team acquired lookalikes. Fix: compare NRR by acquisition cohort, revert the definition to the behavioral one, and quarantine any new segment into its own motion with its own economics.
Pricing governance collapse
Signature: average discount rising for four or more consecutive quarters with no structural cause. Fix: a discount audit by rep and by segment, then a written floor with named approvers for exceptions. The floor matters less than the consistency of enforcement.
Cadence decay
Signature: the meeting still happens and no decision is made. Within six months it is monthly; within a year, quarterly. Fix: redesign it around decisions. Each weekly review produces one documented structural change, a deal deprioritized, an exception denied with reasons, a stage criterion tightened, or the cadence has not been restored.
Data disconnection
Signature: a clean dashboard and worsening numbers. Fenwick Systems, 60 people, had clean CRM data, a RevOps dashboard reviewed every Monday, and a discount rate that rose from 11% to 19% over 18 months, because nobody in the room had the mandate to say this deal does not proceed at that discount. Data without decision rights is intelligence without action. Fix: build the decision rights with the data.
Measuring the Growth Operating System: Pocket Price Realization and Revenue Quality
The investment conversation stalls at the same point every time. Someone asks what the return is, and the answer comes back qualitative: better alignment, faster decisions. Unmeasurable investments do not get approved. Measure the Growth Operating System in three places, and baseline all three first.
Pocket price realization
Pull every deal closed in the last 12 months. Contract value divided by units, divided by list for that configuration, averaged across the book. That is your realization rate. A 1% improvement in realized price is worth roughly 11% of operating profit (McKinsey, The Power of Pricing). On $50M of revenue every point of realization is $500K of top line and a much larger share of EBITDA. Marn and Rosiello's pocket price waterfall (“Managing Price, Gaining Profit,” Harvard Business Review) is still the cleanest way to see where each point went.
NRR by cohort
Model two trajectories: current drift, and the improvement from better qualification at entry, earlier expansion identification, and proactive churn intervention. Weight each conservatively. Then track cohort NRR, not blended, because blended NRR hides cohort deterioration for 12 to 18 months.
CAC payback and qualified pipeline rate
Measure the share of opportunities entering the formal pipeline that meet the ICP, then model a 20-point improvement. Reps who stop working unqualified deals close more of the right ones in fewer days, which moves CAC payback without adding headcount.
Revenue growth is not revenue quality
Two measurement failures recur. The first is measuring growth instead of quality. A company that grows from $40M to $52M while NRR falls from 108% to 96% has not improved its system. It acquired enough logos to mask the deterioration, and a buyer's diligence team will price the NRR, not the bookings. The second is attribution bias: crediting the Growth Operating System for every improvement and the market for every decline. Isolate the levers the system touched and measure only those.
Five numbers belong in the monthly review: pocket price realization, NRR by cohort, pipeline conversion by stage, discount rate by segment, and forecast accuracy against the prior quarter's call. Gartner finds only 7% of sales teams reach 90% forecast accuracy and the median sits at 70 to 79%. If yours sits in the median, the cadence is producing status, not calibration.
Four Financial Signals That Precede the Board Question
A broken commercial model looks like a people problem, a market problem, or a product problem until you inspect the mechanism. It shows up in four financial lines before it shows up anywhere else, usually 12 to 18 months before the quarterly miss. Set a tripwire on each.
Average selling price drifting down
Quarter over quarter, with no change in mix. Reps are optimizing for closed revenue over profitable revenue and nothing in the system corrects them. At $35M ARR, ten points of ASP is $3.5M at the same volume.
CAC payback extending
The ICP is too broad, pricing is under-anchored, or both. When payback moves past two years at a sub-$50K ACV, treat it as a model signal rather than a marketing one.
Gross retention eroding in newer cohorts
Most of the loss below your own floor is selling to the wrong customer, not product failure. Most churn is misunderstanding, not dissatisfaction, and the misunderstanding started in the deal.
Rep attrition rising
The good ones leave first. They can see the dysfunction and do not want to work against the model for another year, and their departure removes the knowledge that was compensating for its gaps.
The earliest signal of all sits in deal velocity by stage. Slowing at qualification is an ICP problem. Slowing at proposal is packaging or price clarity. Slowing at negotiation is the deal desk. Weston HR Software, $58M ARR, watched NRR drop from 102% to 91% in one quarter with no warning. Negotiation-stage velocity had been slowing for three quarters and the response had been bigger discounts to keep deal pace. The cohort bought at those discounts never reached the value behind its ACV and contracted at renewal. Time-in-stage tracking costs reps nothing and would have surfaced it five months early.
Three Ways a Growth Operating System Fails
Across 80+ engagements I have seen each of these more than once and have made at least one of them myself. The names are invented. The patterns are not.
1. Scale first, architecture later
The approach. Tessmark Analytics, $18M ARR, raised growth capital and took the sales team from 5 to 14 reps in six months. The commercial model existed on paper: tiered pricing, a standard ACV target, an ICP paragraph on the wiki. Pipeline coverage looked healthy at 3.2x, so the board approved.
Where it broke. None of it had been tested. The tiers were the founder's intuition. The ICP had not been reviewed in 14 months. Discount authority was informal: reps asked their manager, who usually said yes. Six of the 14 reps were qualifying a segment with a 58% first-year churn rate, because nothing in the definition excluded it.
Consequences. By month nine, average ACV was 22% below plan, three of the eight most expensive reps had left, and gross retention was 74%. The board called for a commercial review it could have run before the first requisition.
The corrected approach. The three structural decisions first: value metric, comp plan, deal desk. Then run ten deals through the stated architecture and count how many closed at list, at what discount, and why. More than three below target margin means the architecture has a problem that scale will only make more expensive.
2. The ICP broadened by a winning quarter
The approach. Holloway HR Software, Series C, had a Growth Operating System that was working: quota attainment above 70%, NRR at 108%. Three years earlier the team had won a cluster of enterprise accounts on aggressive multi-year pricing. Those accounts retained well, so leadership concluded enterprise was a natural expansion and broadened the ICP. Twice.
Where it broke. Within 18 months, 40% of new pipeline was enterprise, closing at 9%, and the discount required to close it was eroding margin on the core segment. Nobody made a bad decision. The definition had drifted on the back of a success.
Consequences. Quota attainment fell to 58%. NRR slid three points a quarter to 97%. The average discount reached 26% and was rising. The forecast missed by more than 25% for three consecutive quarters.
The corrected approach. Revert the ICP to the original behavioral definition, quarantine enterprise into a dedicated motion with its own economics, reinstate the pricing floor with a written exception process, and rebuild the weekly review around discount rate and NRR. Three quarters later NRR was 107% and forecast accuracy had moved from 68% to 88%. A segment that wins is not the same as a segment that belongs in the definition.
3. The Growth Operating System that lived in one head
The approach. Halberd Property Software, $31M ARR, acquired with a value creation plan covering international expansion, a platform upgrade, and a sales build from 12 to 22 reps, all funded within 90 days. The commercial system ran through a strong VP of Revenue who carried the playbook, the training, and the discount policy personally.
Where it broke. The VP left at month 14. Nothing was written down. The three reps hired in the previous quarter had never been trained, and nobody could say what the discount rules had been.
Consequences. Deal cycle length rose 35% in the following quarter. Win rate dropped 12 points. Rep ramp extended by 60 days. Two quarters of commercial disruption in the middle of a hold, on a plan that was otherwise right.
The corrected approach. Shadow the revenue leader through a deal review and a pipeline call in the first 90 days and write down every decision and every piece of knowledge they apply. That document starts the GTM playbook. Put the commercial quality metrics in the board pack, formalize training, and hire the next VP into a functioning system rather than an empty chair.
The 90-Day Diagnostic Checklist
Ninety days is enough to know whether your commercial system has structural problems. It is not enough to fix them all. It is enough to stop pretending they are noise. Days 1 to 30 baseline. Days 31 to 60 audit the ICP and the story. Days 61 to 90 test governance and cadence, then pick the first module.
- 1.Pull discount rate by segment and by rep for the last 12 months
- 2.Pull NRR by acquisition cohort for the last six quarters
- 3.Pull forecast accuracy for four quarters: what you called 90 days out against what closed
- 4.Pull sales cycle for deals above and below your median size, plus churn reason codes for the last 20 lost accounts
- 5.Run the one-sentence test across sales, marketing, product, and pricing
- 6.Score the last 40 won and 20 churned deals against both ICP sentences
- 7.Compare firmographics, trigger events, stakeholder patterns, and time-to-value for the top and bottom 20% of accounts by NRR
- 8.Build the Value Proposition Alignment Map for your top segment and read the pricing page against the current campaign
- 9.Count the deals that closed above the stated discount floor last quarter and record who approved each one
- 10.Check whether pipeline stage exit criteria are applied the same way by every manager
- 11.Confirm the weekly commercial review produced at least one structural decision in each of the last four weeks
- 12.Confirm NRR is reviewed monthly at leadership level with explicit expansion and churn targets, then pick the first module
Two findings recur. Teams overestimate ICP precision: they can describe the customer they want and go quiet when asked which conditions predict churn inside 18 months. And discount data does not exist in usable form: tracked per deal, never aggregated by rep or trended over time. Both are findings, not failures. Start there.
Company names and figures in worked examples are illustrative.
Who the Growth Operating System Is For
The growth operating system is designed for companies that have outgrown their original commercial infrastructure and need to rebuild it at the next level of complexity. Three types of organizations fit this profile.
PE-backed companies post-close
Private equity firms acquire businesses with commercial improvement potential built into the investment thesis. A growth operating system provides a structured, sequenced plan for realizing that potential. For PE-backed companies, the 6-9 month installation timeline maps directly to a 90-day sprint and a year-one value creation agenda. The diagnostic deliverable is designed to plug directly into the board-level value creation plan.
High-growth SaaS companies scaling from $10M to $100M ARR
The commercial motion that gets a SaaS company to $10M ARR is almost never the motion that gets it to $100M. At $10M, your founding team sells on relationships and vision. At $30M, that stops working for new segments. At $50M, the packaging is outdated, pricing hasn't been reviewed in three years, and your GTM is running campaigns for a buyer profile that no longer exists. A growth operating system rebuilds the commercial infrastructure for the next stage.
Enterprise organizations replatforming commercial infrastructure
Large enterprises that have acquired companies, expanded into new markets, or shifted their go-to-market from a direct sales model to a product-led or partner-led model often need to rebuild their commercial infrastructure from the ground up. The growth operating system provides the architecture, the governance, and the operating rhythm to run a more complex commercial operation without adding proportional headcount.
Growth Operating System: Common Questions
What is a growth operating system?
How is a growth operating system different from a commercial operating model?
Where do you start?
How long does it take to install a growth operating system?
How do you know whether sales and marketing are aligned?
Do you need to reorganize or hire a CRO to fix it?
How do you measure the ROI of a growth operating system?
Which buyers benefit most: PE-backed post-close, $10M-$100M ARR scale-ups, or replatforming enterprise?
Find out which module to fix first
The FintastIQ Commercial Maturity Assessment scores your pricing, sales, GTM, and product-revenue alignment and returns a module-by-module diagnostic with a recommended sequence. If you would rather talk it through, bring your four baseline numbers to the call and leave with the first sprint.