Consumption Revenue

Hassan's description of RevOps at an early-stage hypergrowth company: building processes and systems while the foundations underneath keep shifting.

A smaller company is a small boat that is easy to steer, while a larger organization is a cruise ship that takes hours or days to change direction, so RevOps design has to match the vessel.

RevOps that agrees with everything a CRO says and executes is a ticketing center. Strategic RevOps asks why, explains the risks of a bad decision and offers alternatives that still reach the goal.

A compensation model for a business with no contracts, in which sales, post-sale and solutions engineers all take a percentage of each customer's monthly revenue for a year.

A prediction model that estimates a new customer's annual revenue from roughly their first 60 days of usage, trained on historical customer usage and adjusted for known seasonal patterns.

Reconciling the top-down target investors set with a bottoms-up model of how many reps, and how much marketing coverage, are needed to hit it.

Hassan's build order for the function: a generalist at Series A, a strategic leader with technical and analyst layers from Series B to D, and a specialized team after IPO.

The early-stage goal for RevOps: not to stop the chaos of a startup but to give it a method, so the environment is still chaotic but makes sense.

At Series B to D, the head of RevOps adds a technical persona and an analyst persona beneath them to absorb tactical work.

Sales is the driver everyone watches. RevOps is the pit crew doing unseen tire changes in seconds, and truly world-class RevOps also designs the car.

AI agents should be evaluated against the same north-star metrics as any other investment, not by asking for the ROI of the agent itself.

The knowledge of how the go-to-market systems actually work and how metrics are defined, which Hassan calls the most important piece of any AI deployment, and which sits with RevOps.

AI deployed without RevOps governance makes disinformation faster: it returns a wrong answer with confidence, and that answer spreads.

When a CRO asks what the ROI of RevOps is, reverse the question and ask what it costs to run a scaling go-to-market machine with nobody strategically designing, overseeing or managing it.

A split between back-office RevOps (systems, process, tickets, quota fixes — never touches the field) and field-operator RevOps (lives between the sales team and the machine, injecting value into forecast calls, campaigns, and programs).

Build your internal operating rhythm around the four phases of how a customer consumes you — awareness, consideration & decision, implementation, and value realization — rather than around your org chart.

Staff sales enablement by treating every non-quota role (managers, RevOps, SEs, enablement) as overhead wrapped around a $1–2M-quota AE, and asking what each role gives back. Budget it zero-based and build it as a living sales academy, not a content factory.

Stand up formal enablement once a frontline manager's span of control passes five or six reps — earlier if you sell complex, enterprise, high-consideration products.

Split the field into hunters who acquire new logos (traditional sales path) and farmers who grow the install base aggressively, then engineer the bridge so neither feels the other is interloping.

In consumption revenue, the signed PO is where the work starts. Because revenue recognizes on usage, the entire post-signature job is driving adoption and demonstrated value.

Land small as a paid pilot, prove value fast, run a ~6-month 'double-tap' true-up, then bridge to the 12-month renewal — which is really the first real deal.

Acquisition and install reps carry different numbers; acquisition sellers ideally carry no consumption quota. Build a bookings plan for hunters and a consumption plan for farmers, layered with spiffs and target-incentive mixes.

Go-to-market gathers raw materials (account plans, commercial events, product releases, macro signals); a centralized data-science function owned by finance turns them into a forecast. Sellers cannot predict consumption.

Leverage is forcing your way into the room by making leaders unprepared without you. Trust is being invited in because sales leaders want you there. Only trust builds durable influence.

RevOps sits in a strange seat: reporting to the CRO but excluded from the CRO's peer conversations, while simultaneously knowing more than most of its peers and hearing things in rooms sales never enters.

AI is a productivity multiplier that requires clean data and human oversight. A productivity gain should be reinvested in more capacity to go faster, not banked as headcount reduction.

Design monetization in sequence: packaging first, then pricing structure, then the pricing metric (what you charge on, and whether forward- or backward-looking), and the price point dead last.

Bundle features around the outcomes a customer is trying to achieve, not around a product-team ranking of which features get used most.

The amount of pricing/packaging complexity a business can carry is capped by its ACV and the type of customer it sells to — high ACV can absorb complex enterprise pricing; low-ACV startup sales demand simplicity.

Classic SaaS had near-zero marginal cost and 80–95% margins; AI reintroduces a real, usage-driven cost to serve that most SaaS-native companies can't even measure, so pricing that doesn't follow cost loses money.

Outcome-based is what you price on; usage-based is how you meter it — and they can combine. Outcome pricing fits vertical products with a uniform outcome and is a trap for horizontal products where the same usage means different things to different users.

You're a candidate for outcome-based pricing only if: (1) you can clearly define one outcome across your customer base; (2) customers agree to and accept that exact definition; and (3) the value of that outcome is similar across all customers.

Make usage-based pricing palatable by combining a recurring base fee with usage on top, wrapped in real-time visibility, per-team spend controls, caps/notifications, and token-level billing traceability.

De-risk migrating your most important customer by working backward: test new pricing on the least-important segment or market, then new business, then run validation interviews with your 2nd–5th customers, plus internal validation with the sales team, before migrating the anchor account.

Treat pricing and packaging as a living product surface, revisited every product-release cycle or sales cycle (whichever is longer) — not set once and left for five to seven years.

Spend the opening months of a new role absorbing information from two sources — the people on the ground doing the selling and implementing, and the available data — then marry those perspectives into a working theory of what's actually happening before setting priorities.

When you miss a quarter, an intellectually honest post-mortem usually ties the miss to a planning or strategy assumption you weren't honest about — not to near-term deal execution.

Charge only when the AI agent completes the entire job correctly (e.g., reads and infers every field on a document 100% right), so price tracks roughly one-to-one with the value delivered.

Report usage-based revenue to the board by stacking two clearly labeled layers: contracted ARR ('take it to the bank') plus a conservative fraction of the forecasted amount booked as 'estimated ACV' (EACV).

Start with a small, high-confidence use case you know you can nail, prove value fast, and use that win to earn the right to the next project — becoming the customer's primary consideration for what's next.

Qualify and sell the deal first, then run the POC only to confirm the solution works and the teams click — never as a desperate Hail Mary to generate intent that isn't there.

Before offering a POC, square away the MSA, legal and security, and budget, and get both IT and operations (the business side) at the table and excited. The POC then only validates the solution and the working relationship.

Have the implementation / agent-PM team scope the work during the sales cycle, so the buyer meets who they'll work with, gains confidence, and sellers can't over-promise.

Build the revenue plan so every channel has its own win rate and ASP and new-logo ('NUCO') plugs the gap to the number — robust enough that a missed quarter can be traced to a specific assumption that broke, with leading indicators warning you a quarter or two out.

Leadership sets a non-negotiable number; what's up for debate is only the resources required to deliver it. The exercise is iterative and cross-functional, and pairs with a proactive 'what would it take to 10x my org' model run before the CEO asks.

A go-to-market model with no contracts and no renewals — pure pay-as-you-go, even on multi-million-dollar enterprise deals — so the customer can leave at any time and the company effectively re-earns the business every single day.

Anthony's framing for the startup-vs-scale-up choice: a big ship already has a direction and goes far; a jet ski is nimble and yours to steer. Oliver's corollary: at early stage you work ON the company (creating its DNA), and at scale you work IN it (executing).

Define ARR by taking collected revenue and extrapolating it forward twelve months, then stacking disciplined, repeatable consumption projections — derived from a customer's telemetry data or their prior-vendor usage — on top of the extrapolated actuals.

Pay commissions up front on a projected ACV — the customer's estimated one-to-three-year spend — protected by security-margin haircuts, a two-person review of the estimate, a rep-adjustable projection, and a consume-to-earn provision that only fully vests the commission once the customer actually consumes.

A comp plan surfaces problems but rarely causes them. If deals collapse at scale, the root cause is bad hires or a product that isn't doing its job — not the incentive structure, which only mitigates or escalates the underlying issue.

Staff a company in waves: SEALs first (operate confidently without supervision in uncharted terrain, mission evolves as they gather intel in the field), then Marines (build the foundation), then infantry (scale once the foundation exists).

Motivation is why someone joined your cause — intrinsic, and not the leader's job to install. Morale is how someone feels in a given moment — situational, and squarely the leader's job to manage by supporting people through hardship without removing it.

The real leverage from AI isn't the model — it's the discipline of organizing and maintaining company knowledge so an agent has clean, current context to draw from, turning a one-hour subject-matter meeting into a five-minute prompt that's 95% right (plus a ten-minute human review of the output).

Data silos are structural, not attitudinal: product and billing data sit with engineering or a data team, RevOps sits under go-to-market, and as long as they're distinct teams the data stays separated from the people who need it.

The data-team gatekeeper who deprioritizes RevOps requests as mundane while, in reality, those requests are the highest bottom-line-impact work at the company.

A 'data model' is a curated, reusable catalog of source fields you green-light (authorize) for syncing — built from a database table, a custom SQL query, or a spreadsheet — that anyone can then grab from to sync anywhere.

The single simplest usage field — the date a customer last logged in — predicts churn better than most sophisticated composite product signals.

Segment accounts by product engagement in the CRM and route the play accordingly: heavy users get an immediate upsell script, light users get an education pitch rather than a sales pitch.

A reframe that evaluates every data request by its revenue dimension — collections, overage monitoring, churn avoidance, or upsell — instead of by the data itself.

The practice of breaking cross-team silos by leading with curiosity about the other side's priorities — RevOps asking to be educated on the data team's world, and technical teams asking who's affected and why a request matters — in both directions.

Because every public SaaS company answers to the same SEC rules, quote-to-cash should be a standardized, out-of-the-box process — not a uniquely engineered snowflake per company. A 'unique' process is a problem to fix, not a competitive advantage.

Instead of a separate CPQ, billing system, and revenue-recognition system integrated between CRM and ERP, run a single platform that handles CPQ, AR/billing, and ASC 606 rev rec — sitting between the CRM and the GL with no reconciliation and one product catalog.

An AI agent that lets any seller generate a compliant quote by typing a plain-English request into Slack (or mobile, email, or the CRM). The agent parses the request, asks for any missing policy-required inputs, applies product rules, and returns a quote PDF.

A business-focused Q&A layer that asks a seller simple questions (where is the customer located, what segment) and converts the answers into the right products, compliance, and discounting — instead of making the rep understand how the CPQ is configured.

Usage/consumption billing comes in distinct models: pure pay-as-you-go (no commitment, invoice on actual use), pre-committed plus overage (commit to a volume like 200,000 API calls/month, pay extra above it), and credit pools (buy a $100k pool and draw down across products, AWS/GCP-style).

A policy-driven method for turning variable consumption into a defensible ARR: for pay-as-you-go, take average consumption over a trailing 3-6 months and recognize a set percentage (e.g., 80%); for committed-plus-overage, the commitment is fixed ARR and overage recognition depends on how straight-line it is and what the auditor will accept (from ~95% down to ~20%).

When a customer adds licenses and renews early, you cancel the current term (crediting the unused period, like dropping a car lease) and restructure into a new term. Done right it's one opportunity, one order form, with credits and proration auto-calculated and reporting that shows it as upsell — not churn plus a new deal.

The design principle that the primary consumer of a CPQ should be the seller, not deal desk or RevOps. Reps should be able to run even complex deals (multi-year ramps, partner margins, special payment clauses) and the entire post-signature lifecycle themselves.

The seller creates an 'order' (draft during the sale cycle, confirmed once closed) and that same object generates the invoice and feeds finance. There's no separate quote-to-invoice re-keying, so numbers can't diverge between what sales sold and what finance bills.

Treat gross revenue retention and net revenue retention as a single paired metric. NRR sums churn, contraction, and expansion; GRR strips out expansion to isolate how much of the starting book remains. Reading only one lets expansion mask underlying churn.

Pick your health-scoring method based on your motion. High-touch, low-account-count books use sentiment-based human judgment (green/yellow/red from the CSM who lives the account). Low-touch, high-volume books use systematic signals (utilization, penetration, login/usage drops).

Capture customer sentiment through two surveys. NPS measures likelihood to refer — a directional proxy for renewal. CSAT measures satisfaction, read through specific engagements, journey milestones, or the overall relationship. Survey on the right cadence, across a representative cross-section, without pestering.

An informed estimate of what a usage-based deal will be worth over its first 12 months (or a chosen period), assigned even when zero dollars are contractually committed, so the deal can be reported, forecast, and managed.

A closed-loop discipline of tracking each deal's real consumption against its assigned expected value — daily, monthly, or otherwise, but at least through the first year — to see where estimates over- or under-called.

A method for estimating expected value that starts from a data baseline — usage trends of similar companies and of a customer's first three, six, and nine months — then layers in rep discovery, safeguards, and discounts to land a defensible number.

The anti-pattern of forcing usage into a committed contract by discounting the per-unit price — e.g., committing 25% of expected volume for a 10% price cut — to buy reporting predictability.