Plan versus engine: why the number is behind

When a revenue plan is behind, the instinct is to look at the market, the pricing, the competition, or the people. Sometimes that is where the answer is. Usually it is not. Usually the plan was signed off without anyone testing whether the sales engine underneath it could carry the number.

A plan is a set of assumptions wearing a spreadsheet: this many sellers, ramped this fast, converting at this rate, renewing at this rate, expanding by this much. The engine is what actually exists: the team you really have, converting at the rate they really convert, with the churn and the ramp times you really see. The gap between the two is where the miss comes from, and it can be put in pounds.

The four places the money usually is

Most reviews look at one of these. The plan depends on all four.

Capacity. The plan assumes a sales team that does not exist: headcount that has not been hired, ramp times nobody achieves, attrition nobody budgeted. Rebuild the capacity model from how the team actually converts, ramps and churns, and you find out what number the team can really carry.

Pipeline and forecast. Stalled and dead deals sit in the pipeline flattering the coverage number. Strip them out before trusting anything. Then measure the forecast for accuracy and bias, by seller and by manager, so the number stops moving every week.

Retention and the long tail. Renewals run as a service function in most software businesses: churn is explained after the fact, and uplift, term and notice periods are levers nobody pulls. Give renewals the same discipline as new business. The long tail of small customers, which nobody has time for, is usually where the cheapest profit is hiding.

Revenue you are already owed. Users, entities, sites, storage and indexation the customer is consuming but not paying for. This is recovery, not expansion: it is billed now, not sold later.

Twelve weeks, not twelve months

The reason turnarounds drift is that they are run as studies. A finding without an owner, a baseline, a target and a review date is advice, and advice changes nothing.

The alternative is to run it like an operator. Week one: test the plan against the engine. Weeks two to five: assess every part of the revenue engine for whether it works, not whether it exists, and put the gap in pounds. Weeks six to twelve: put the fixes live with named owners, and start the cadences that keep them honest. Every quarter after that: show the board what was created, revenue generated, revenue protected, profit impact, and which interventions failed, by name.

Most turnarounds change the people. Change what the people do first. Most teams get better fast when the process, the cadence and the accountability are right, and the ones who cannot or will not change identify themselves early, with evidence.

One company. Twelve weeks. Judged on what moves.