Sales Operations

With three reps, nobody needs this job. Deal records live in one spreadsheet, everyone knows by conversation who covers which company, and the manager gets the quarter's numbers by asking three people.

At twelve reps the arrangement collapses. The spreadsheet has split into five, the same company sits on two people's lists, and both of them reach out. From the customer's side, that company looks disorganized. Pulling the quarter's numbers means the manager collecting twelve files in twelve formats and merging them by hand, which takes two days. Whether the merged figure is correct is something nobody knows, and the two days spent producing it are the two days when the quarter could still have been changed.

Worse is the question of who does that work. With nobody assigned, the strongest seller does it. Fixing tool settings, building templates, and running the aggregation costs five hours a week, so five hours of selling disappear every week — and they disappear from the person whose hours are worth the most.

Sales operations is that work carved out into a dedicated seat. Giving sellers their hours back is the purpose of the role, which is why it's measured not by what this person sold but by what the sellers sold. That inversion is what makes the seat hard to justify early and obvious to justify late.

The work groups into four things: tools, data, rules, and unblocking people.

1. Running the tools. This means managing the sales stack, the combination of tools sales works on. Tidying the fields in the deal record system, and wiring the email sender and the call recorder so they pass the same company record to each other. Unconnected, a rep retypes the same information in four places, and the four copies start disagreeing within a week.
2. Cleaning the data. Merging one company that appears as three rows, finding deals with an empty stage value and going back to the rep about them. Skip this before aggregating and every number downstream is wrong — and wrong in a way that looks fine, since a duplicated company inflates pipeline without leaving any visible trace.
3. Producing the numbers. Stage-by-stage win rates, deal duration, and the sales forecast that estimates next period's revenue from the pipeline. A forecast is the stage win rates multiplied and summed, not the reps' confidence collected.
4. Setting and holding the rules. Calculating the quota assigned to each rep, and keeping territories from overlapping. Arguments like who gets credit for a deal that changed owners get settled at this desk.

A real day tends to run as a morning spent combing last week's records for blanks and duplicates, and an afternoon spent on whatever reps bring in. A screen that won't open in the tool and a company on my list that's assigned to someone else are the two common ones. Neither takes long alone; the point of the seat is that neither one interrupts a rep's afternoon.

The shape changes at quarter boundaries. The last two weeks go to tightening forecast accuracy, which mostly means chasing reps about deals whose stage hasn't been touched in three weeks. The first two weeks of a quarter go to assigning new quotas and territories.

The role deals with the whole sales team, and each counterpart brings a different kind of request.

1. The sales development representatives (SDRs) who create first meetings, and the business development representatives working new markets, arrive with lists and sending tools. How accurate the list is changes their results immediately.
2. The account executive (AE) who owns deals to signature arrives with stage definitions and credit questions — which stage this deal belongs in, and whether this closed number landed against their name.
3. The account manager (AM) holding existing customers needs renewal dates and usage data. Making an alert fire ninety days before renewal is this desk's job, and it's the difference between a renewal conversation and a renewal surprise.
4. The sales engineer answering technical questions wants their involvement recorded per deal. Without that record there's no basis for asking to grow the team.
5. The chief revenue officer (CRO) running the whole revenue organization asks about the gap between forecast and actual. The numbers handed to this person go to the board.

It extends past sales too. With marketing, the criteria for the lists coming across get aligned; with finance, when revenue gets recognized. When the two sides' numbers disagree it's usually because the definitions differ, and reconciling definitions lands here.

"This one's marked proposal but no proposal went out. Can you fix the stage value?"

Correcting a record that has drifted from reality.

"Forecast said $60,000 and actual came in at $38,000. Let's see which stage's win rate is wrong."

Working backward through the calculation that produced the forecast.

"If we redraw territories, the commission rules have to be looked at in the same pass."

A warning that changing one side alone creates disputes.

At Pagedeck, Grace covers this work herself. With three reps, the team isn't large enough to justify a dedicated seat. Grace books an hour every Friday to comb the deal records, finding deals with blank stage values and companies entered twice, and goes back to Sofia about them.

The team has decided to split the work out once reps pass six. The trigger is time: the point where Grace's Friday hour becomes three hours. Left undecided, this work accumulates quietly on whoever is busiest.

A common belief is that sales operations is a tools administrator. A large share of the work is system configuration, so it looks that way. But deciding a configuration is deciding how the team sells. Expand the stages from five to seven and reps see their deals differently; put discount rate into the quota calculation and behavior in the last week of the quarter changes. In organizations that use this seat only as a request queue, those decisions accumulate with nobody accountable for them, and a year later nobody can say why the pipeline is shaped the way it is.

The other belief is that a support function can't be measured. Not selling directly makes revenue an awkward yardstick, which sounds reasonable. But this role has numbers of its own: the gap between forecast and actual, the time reps spend on record-keeping, and list accuracy. An organization whose forecast misses by 20 percent every quarter allocates resources differently from one that lands inside 5 percent. Without those numbers attached, the seat becomes a queue worked in arrival order, with no basis for deciding what matters first.