Churn rate: measuring it in a way that tells you what to fix
Churn rate is one number hiding several questions. Measured as customers it flatters you; measured as revenue it usually does not.
A sales plan template is not a forecast. The forecast says what you expect to close; the plan says who will do what, to whom, how often, to make that number arrive rather than merely be predicted.
A sales plan template is a structure for turning a revenue target into weekly behaviour. It answers four questions in order: what number, from which customers, through what activity, owned by whom. Most documents called sales plans answer only the first, which is why they are read in January and never again — a number without an activity model attached is a wish with a deadline.
It is worth separating three documents that constantly get merged. A sales forecast estimates what will close and when. A go-to-market strategy decides how a product reaches a new buyer. A sales plan sits between them: given the target and the market, what does the team do on Tuesdays.
The step teams skip is the last one. A plan that requires each rep to hold forty qualified conversations a week when they currently hold twelve is not ambitious, it is arithmetic that has already failed. Catching that in the planning hour costs nothing; catching it at the half-year review costs two quarters.
A sales plan has two review rhythms and confusing them is the common failure. The weekly review is about the pipeline — which deals moved, which stalled, what activity happened — and it never reopens the plan. The monthly or quarterly review is about the assumptions: is the win rate what we said, is the deal size holding, is the mix between new and existing drifting. Assumptions get revised there, in writing, with the date, so that a missed number can be traced to which assumption broke.
The accounts, the conversations and the pipeline stages belong in Ettex CRM, since the activity numbers in the plan are only as good as the record of what actually happened. The plan document itself — targets, territories, assumptions, discount authority — sits in Ettex Docs where it can be revised and commented, and the quarterly arithmetic is easier to keep in Ettex Sheets next to the forecast.
The limits are worth naming. There is no territory optimisation engine, no quota management module, no commission calculation and no sales forecasting model that predicts on your behalf. The pipeline is what your team records; the arithmetic above is arithmetic you do. Anyone selling a system that removes the judgement from those steps is selling a confident number rather than a plan.
The forecast estimates what will close and when. The plan sets out the targets, territories and weekly activity intended to make it happen. One is a prediction, the other is a commitment.
Two to four pages. The useful content is the target split, the territory map, the conversion assumptions and the weekly activity that follows from them; everything else is context that ages badly.
Pipeline weekly, assumptions monthly or quarterly. Keeping those separate stops every weekly meeting from reopening the strategy, which is how review meetings become unbearable.
Then the plan is wrong now rather than in six months. The three honest responses are more people, a demonstrable improvement in conversion, or a smaller target — and picking one in the planning session is the entire value of doing the arithmetic.
Churn rate is one number hiding several questions. Measured as customers it flatters you; measured as revenue it usually does not.
A recruitment process is a series of decisions about evidence. Decide what evidence you need before you meet anyone, and most of the usual problems disappear.
A CRM for real estate has to hold two sides of every deal — people and property — without becoming a system nobody updates on a viewing day.