Sales Compensation

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.

A CRO knows what to fix and even knows candidate strategies, then freezes — either because execution looks like an overwhelming amount of work, or from fear of taking a step back and breaking what already works. RevOps is where that freeze thaws.

RevOps shows up with a point of view on what the business should do rather than waiting for direction — enabled by an information edge, because the field shares candid feedback with the head of RevOps that it won't share directly with the CRO.

Keep an annual anchor tied to strategic and fundraising commitments, but plan continuously: evaluate performance to plan monthly, decide on adjustments quarterly, and run a second-half replan as conditions change.

A one-hour, bi-weekly meeting between RevOps and sales leadership, anchored on a fixed dashboard of five to eight initiatives, that serves as the catch-all forum for the business.

Beyond standing metrics, instrument each strategic bet on its own — a spiff's multi-attach rate, deal progression past a stuck stage, or pipe from moved vs. unmoved accounts — so you can prove whether it's working.

Data-driven modeling of territories across three lenses — firmographic (segment thresholds), 'smart plan' (balance by priorities like ARR or tier-A account count while minimizing disruption), and geography — layered with coverage, quota, and policy modeling.

Run territory planning like a gold-mining company: first know where the gold is, then decide which miners to send where, and keep the operation flowing when a miner goes down.

Survey your total addressable market and assign a potential revenue valuation to every account, then use that field to carve and balance territories so each seller has an equal amount of gold to mine.

The most consistent RevOps career path leads to COO; the way to grow toward it is to run RevOps today as if you already held the COO role — operationally minded, program-driven, and confident enough to lead the CRO.

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).

A maturity path for tying customer success to revenue: crawl (run a value cycle, lead with hard value, and book CSMs under S&M not COGS), walk (give CSMs CSQL goals and track the funnel), run (train CSMs to close simple upsells, or add an account-management layer inside the CS org for complex ones).

A way to tie business outcomes at the customer back to your product. Soft value is sentiment-based (how the customer feels); hard value is measurable — hours saved, dollars saved, headcount saved — that you can attach real numbers to.

When CSMs don't own the upsell directly, they're accountable for surfacing a set number of customer success qualified leads through normal customer work and handing them to sales; the leader tracks close rate, cycle time, revenue, and funnel shape.

Call it a bonus, not a commission, to shift the mindset. Pay 80% base / 20% bonus, split into two or three parts. The three-part version weights NPS, gross retention (an individual number), and net retention (a company/team goal) a third each; the two-part version drops NPS for individual gross plus company net, with an upside kicker above 115% NRR.

Give everyone in the company — not just customer-facing roles — a small bonus tied to NPS and NRR, so office managers and engineers alike have a stake in customer sentiment and retention.

Picture a bucket with capacity 100 (100% retention). The hose pouring in is revenue; you want to fill and overflow the bucket (>100% NRR). Every hole punched in the bucket is churn.

A CS-plus-sales/AM pod structure is justified only when the average contract value and the available 'green space' to expand support the coverage cost; otherwise a single AM covers the whole portfolio.

Have each team member list what they do daily, weekly, and monthly. Anything that doesn't require critical thinking is a candidate to hand to AI — via custom GPTs or purpose-built tools — freeing CSMs for critical thinking and human relationship-building.

Model your target as current ARR + new ARR + expansion − churn/contraction. New ARR is new logos (and new contracts with existing customers); expansion and churn both come from the existing base.

Take the macro ARR goal and reverse-engineer it top-down through funnel metrics (net retention, SQL-to-close, sales cycle, MQL-to-SQL, average ACV) and bottom-up through the resources and team (CS capacity, quota/performance, ramp time, cost per SQL, salaries) required to hit it.

When executives challenge the outputs (reps, budget, pipeline required), don't defend the outputs — send them back to the inputs and ask which specific assumption they'd change: conversion rate, sales cycle, MQL-to-SQL, expected performance.

Because deals don't close the month a lead arrives, the length of the sales cycle dictates when pipeline must exist. A two-quarter cycle means the pipeline for Q3 bookings has to be built in Q1.

A rep is 'ramped' only when building pipeline and closing at full productivity — not when training ends. Ramp time should never be shorter than the sales cycle, which forces you to hire ahead of the number.

The board evaluates the plan not as a sum of initiatives but as unit economics balanced against growth, judging whether the company can graduate to the next funding stage. If it fails that test, the CEO and CFO reject it back to you.

Because you invest in SaaS before results arrive, unit economics degrade when you invest and improve as ROI lands. Plan a trend that grows into the economics the board wants — not a perfect green line every quarter.

Anchor and stress-test assumptions against VC/PE-published benchmarks (win rate by ARR band and deal size, quota-to-OTE ratios, funnel conversion rates) so the conversation becomes 'you vs. the market' instead of 'you vs. the person.'

Replace the static spreadsheet with scenario modeling for sensitivity analysis, live progress-to-target reporting, a core-vs-new-bets split, and a daily sales-tracker email that becomes the company's single source of truth.

There are no silver bullets. Compounding small, daily improvements — messaging, coverage, demos — is what drives real growth: 1% better every day is roughly 37x over a year, while 1% worse is a ~97% loss.

Sum, across all possible outcomes, of each outcome's probability times its value: EV = P(outcome1) x V(outcome1) + P(outcome2) x V(outcome2) + ... . A positive EV is a good bet; a negative EV is a bad one.

From Annie Duke's book: judge choices by the quality of the bet given what you knew, not by whether the single outcome was good or bad. A good decision can lose and a bad decision can win.

A core value of Spencer's company: constant, incremental self-improvement — applied here to decision-making, by reviewing whether a choice had positive expected value regardless of how it turned out.

The ratio of the amount you must call to the total pot you stand to win, expressed as the minimum win probability that justifies calling. Call $100 into a pot that becomes $400 and you have 25% pot odds.

Model each go-to-market segment as a bet: win rate (probability) times ACV (value) gives per-deal EV; then layer in deal volume, fully-loaded rep cost, and marketing cost to get the true expected value of investing in that segment.

A calculated field in Salesforce or HubSpot — built from custom properties and workflows — that outputs how much a given account or open deal is 'worth' by expected value, so reps can filter to the highest-EV deals.

Build territories and quotas from expected value — TAM and account valuation weighted by expected conversion rate — rather than gross dollar value.

A five-part checklist for a trustworthy CRM: (1) enable field history tracking, (2) timestamp critical stage and status changes with custom fields, (3) freeze closed-won data, (4) flow lead data into every object on conversion, and (5) put validation rules in place.

Turning on Salesforce field history tracking to record how data evolves over time, providing an audit trail for diagnosing issues and a historical snapshot for admins, users, and downstream tools.

Dedicated custom fields that capture the date each important status or stage changed — lead status, lead lifecycle stage, opportunity stage, customer stage, or proof-of-concept stage — so change data is directly reportable.

Locking closed opportunity data so it can't be edited after the deal closes — restricting changes to a super admin and reinforcing it with validation rules, automation, and weekly backups.

Ensuring that when a lead converts, its important fields — lead source, lead source detail, owner/SDR, and lifecycle timestamps — carry across to the account, contact, and opportunity records.

Rules that block records from saving unless they meet your business process — from simple checks (required amount, no past close dates) to methodology-driven requirements that ask for the right data at each stage.

Partnerships require giving value — and making concessions — before you get anything back, in contrast to the common approach of building a channel purely to sell more of your own product.

A partnership program must be sponsored from the board and executive leadership down, because early concessions and delayed ROI can't survive quarter-to-quarter decision-making.

Treat your strategic partners as potential acquirers, using a multi-year partnership to build relationships, test integration and cultural fit, and position for a strategic exit.

Concentrate limited bandwidth on a select few high-conviction partnerships where the combination is disproportionately valuable, rather than spreading thin across many low-producing relationships.

Build trust so high that a partner would call your personal phone at 3am on a Sunday and know you'll pick up and problem-solve as eagerly as they need.

Deliberately weight travel and face-to-face time above other activities to win partners' hearts and minds and to harvest the off-the-record intelligence that never surfaces on a recorded call.

Give every partner equal access to support, technology teams, and roadmap, and hold commercial terms you'd be comfortable exposing to a partner's competitor — the foundation for managing channel conflict.

Tie the partnership team's KPIs to overall company revenue rather than channel-only revenue, so channel and direct teams succeed together.

Make an honest assessment of whether a partner motion fits your GTM, then either fully commit the resources or don't start — no one-foot-in, one-foot-out programs.

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.