What is the difference between sales operations and revenue operations?

Sales operations focuses on the sales team specifically: CRM hygiene, pipeline stages, forecasting and territory rules. Revenue operations covers the same discipline across marketing, sales and customer success together, on one shared data model and one forecast. A growing team usually starts with sales ops and folds it into revenue operations once marketing and success need the same rigour.

How many people do you need before sales ops becomes a dedicated role?

Most founder-led teams manage informally up to around eight to ten sales staff, with the founder or a sales lead handling it alongside other work. Past that, a dedicated owner, even part time or fractional, usually pays for itself quickly, because the cost of unclear definitions and missed handoffs grows faster than headcount does.

What should a sales ops function fix first?

Definitions before tools, every time. Agree what each pipeline stage actually means, write it down, and get every rep re-tagging their pipeline against it. A new CRM or forecasting tool built on top of five different private definitions of "qualified" just displays the same confusion with a nicer interface.

How often should a sales team review its forecast?

Weekly, on a fixed day, using the same format every time. A monthly or quarterly cadence catches a slipping deal only after it has already been reported upward, whereas a weekly review flags the problem while there is still time to do something about it.

Do these practices apply to a small founder-led team, or only larger ones?

They apply earliest to small teams, not latest. A five-person team can agree a stage definition and a forecast cadence in one meeting. Waiting until the team is fifteen people means untangling habits and private spreadsheets that have already hardened, which is a much slower fix than starting clean.

Sales operations best practices

Why this matters. Sales ops is what makes growth survive headcount.

Sales operations best practices matter because a sales process that works at five people rarely survives at fifteen without them. Below a certain headcount, a founder can hold the whole pipeline in their head: who's talking to whom, what stage a deal is really at, which forecast number to trust. Past that point, the same job needs a shared system, not one person's memory, and the businesses that get this transition wrong lose deals to confusion rather than to competitors.

Salesforce's State of Sales research has found that the average seller spends less than 30 percent of their time actually selling, the rest going to admin, internal meetings and chasing data that should already be sitting in the CRM. That gap is not a productivity problem to fix with more hustle. It's an operations problem: too many manual handoffs, too little shared agreement on what a stage or a status actually means. Revenue operations closes that gap across the whole revenue function; sales operations does the same job specifically inside the sales team.

The list, with how to apply each. Eight practices that hold as the team grows.

1. One CRM, one definition of a stage

Every rep works from the CRM, not a personal spreadsheet that shadows it. That sounds obvious until you check: a spreadsheet that started as one rep's "better view" of their pipeline usually means the CRM is quietly wrong, because updates go to the spreadsheet first and the CRM second, if at all. Retire the shadow system. If the CRM is too clunky to use as the primary tool, that's the actual problem to fix.

2. Written exit criteria for every stage

A stage should have a specific, checkable condition attached to it, not a feeling. "Qualified" should mean a defined budget, authority, need and timeline have been confirmed, not "the call went well." Write the criteria down, one line per stage, and put it somewhere every rep can see it while they're updating a deal.

3. A fixed weekly forecast cadence

Same day, same format, every week, not just a scramble in the final week of the quarter. A weekly rhythm catches a slipping deal while there's still time to do something about it; a monthly or quarterly one catches it after the number has already been reported upward.

4. A named owner for every handoff

Marketing to SDR, SDR to AE, AE to customer success: each handoff needs a named owner and a defined service-level agreement, typically a maximum response time. Unowned handoffs are where leads and momentum quietly die, not because anyone dropped the ball deliberately, but because everyone assumed someone else had it.

5. A marketing-to-sales lead response SLA

Agree, in writing, how fast a marketing-qualified lead gets a first sales touch, and track it. Without a number, "we follow up quickly" means something different to every person on the team, and the gap between what marketing believes and what sales actually does is where trust between the two functions breaks down.

6. A deal desk for anything non-standard

Discounts, custom terms and non-standard contract clauses go through a lightweight approval step, even if that step is just a Slack message to one named approver. Without it, margin erodes one quiet exception at a time, and nobody notices until the pattern shows up in a quarterly review.

7. Written territory and account assignment rules

Decide the rule before the dispute, not during it. Geography, account size, industry vertical, whatever the logic is, write it down so a new rep can be assigned correctly on day one, and so two reps never end up quietly working the same account.

8. One dashboard leadership actually trusts

Pick one reporting view as the source of truth and retire the rest. When sales, marketing and finance each keep their own version of "how many deals closed this month," with slightly different definitions of what counts, meetings turn into arguments about whose number is right instead of decisions about what to do next. Our own take on which numbers earn a place on that dashboard is in the RevOps metrics that actually matter, which is a shorter list than most teams start with.

A twenty-person SaaS sales team I've worked with had four different working definitions of "qualified" spread across three regional pods, each rep tagging the same CRM stage against their own private sense of what it meant. The pipeline number the VP reported to the board bore only a loose relationship to what reps privately expected to close. The fix wasn't a new tool. It was one page of exit criteria per stage, agreed in a single meeting, followed by an afternoon where every rep re-tagged their open pipeline against it. Reported pipeline dropped by close to a third that week. It felt like a step backwards. It was actually the first honest number the board had seen in two quarters.

Where teams go wrong. Buying tools before fixing definitions.

The most common mistake is sequencing: buying a better CRM, a forecasting tool or a CPQ system before agreeing what "qualified," "committed" and "closed-won" actually mean. A new tool built on top of five different private definitions doesn't fix the confusion, it just displays it faster and with a nicer interface.

The second is leaving the CRM itself unowned. Someone, whether that's a dedicated ops hire or a rotating responsibility in a smaller team, needs to own data quality, field definitions and process changes; see RevOps roles explained for how that ownership tends to grow with headcount. Without an owner, the CRM decays gradually: fields get repurposed informally, workarounds accumulate, and eighteen months later nobody fully trusts what's in it.

The third is reviewing the forecast too rarely to catch problems while they're still fixable. A monthly review means a deal that started slipping in week one isn't flagged until week four, by which point the quarter is already at risk. A weekly cadence costs thirty minutes and buys three extra weeks of runway to react.

My rule when a founder is building out a sales ops backlog: fix definitions before you fix tools. Every time. A dashboard, a new CRM field, or a smarter routing rule sitting on top of an unclear definition of a stage just makes the underlying disagreement more expensive to unwind later, because now it's baked into a report leadership has already started relying on. This is the first piece of work in most RevOps consulting engagements, before a single new tool gets discussed.

Sales operations best practices. The ones that still hold once headcount doubles.