The Lights Always Turn On

Staff roles are the people whose names rarely appear in a launch email. Finance, Legal, RevOps, Recruiting, Strategy, IT. They don't own a product line or a sales quota. What they own is the wiring: budgets, contracts, forecasts, compliance, the systems that let builders build and sellers sell. When they're doing their jobs, the company runs. When they're not, the same company can stall without warning.

Several years ago, two sales reps stumbled into the same account. One had a sequence running; the other had already met the buyer. Both screenshots hit chat within minutes. Their manager's face went flat because comp plans, forecast commits, and three weeks of pipeline choreography now hinged on who technically owned the territory. RevOps pulled up the map, found the overlap, redrew the line, and moved the account before tempers calcified. Ten minutes later everyone was back to work. No one treated it as a save. The fire never had time to start.

Elsewhere, a duplicate invoice gets flagged before it overstates revenue by hundreds of thousands. A contract clause gets tightened and what could have been a lawsuit dissolves into routine. Headcount projections get corrected before they turn into twenty unbudgeted hires. None of it shows up in the demo environment. The only proof is that nothing blows up.

I benefited from this kind of work for years and rarely thought about it. Someone kept the territory maps clean so my deals didn't collide. Someone reconciled the numbers before they reached my slide deck. Someone made sure the contracts I sent out didn't contain language that would come back around in twelve months. I knew these people existed the way I knew the building had plumbing. I used what they built every day and never once walked over to say so.

In a software company, if you aren't closing deals or shipping code, the accounting system labels you overhead. Helpful, maybe, but optional. A line item that could be trimmed during the next efficiency drive. In meetings where people talked about "right-sizing" support functions, the logic always sounded clean. The forecasts I relied on appeared to just happen and the processes I depended on felt permanent, as if they required no maintenance at all. It was easy to agree with the numbers when the numbers made the case for you.

I once sat through a quarterly review where Finance showed one revenue number, Sales showed another, and Customer Success insisted both were wrong. The next two hours weren't about strategy. They were about who owned the definition of "renewal." Bright people stuck trying to reconcile numbers instead of deciding what to do next. The person who used to maintain that definition had left two months earlier. Her role was absorbed, which is the corporate word for eliminated without admitting the work still needs doing.

That meeting was the first time I understood what had been holding the room together before. I'd never thought about why the numbers usually matched. I just expected them to, the way you expect the lights to turn on when you flip the switch. The absence of staff work doesn't create a vacuum. It creates noise, people spending Fridays reconciling things that should have matched hours ago, piecing together context that used to live in a system built to remember for them.

Systems don't maintain themselves. They corrode in ways that aren't dramatic enough to notice in real time. Definitions drift over quarters. Forecasts slowly splinter. Meetings multiply to compensate for uncertainty. Every unanswered ambiguity settles on someone's desk, even if no one can name whose. The drag shows up as a slow grind, the kind that wears people down long before anyone calls it a problem. Eventually people stop asking why it feels harder to work than it used to. They just decide they'd rather be somewhere that feels lighter.

I think about the RevOps analyst who redrew that territory line in ten minutes. She'd been maintaining the maps for months, updating them as reps moved and accounts shifted. A few weeks after the incident, someone in leadership described her team as "back office." The label landed without resistance. That's how these things work: not through malice, but through a vocabulary that narrows what counts as building.

The RevOps analyst who kept the territory maps current was building something. Not a feature, but the system that let the deal close without politics. The person who maintained the definition of "renewal" was building shared language. The finance team flagging the duplicate invoice was protecting the number the whole company reports to the board.

Some people build the product. Some build the conditions that let the product move. Keep the lights on long enough and everyone forgets someone had to.