Costs
Part of How to work through business acumen as six ordered questions about one purchase
Business acumen examples: counting what you have actually won
Business acumen examples for counting what has been won: backlog against pipeline, order against framework, and where each price reduction lands.
Counting what a business has won is harder than it sounds, because the words that report it are near-twins. A backlog, an order, a contract and a framework all sound like sales already made, and only some of them are.
Operations has its own vocabulary, and it fails in a particular way. The words are not obscure. Each pair is separated by exactly one thing: a denominator, a time horizon, or who is obliged to whom. The examples below apply that to one question, which is what has really been won.
What to take away
- Count obligations and hopes separately. A combined total means nothing, because the two halves are not the same kind of thing.
- A framework agreement sets terms and commits nobody to buy, so it is not a book of business.
- Churn and retention are one minus the other only when the period, the population and the counted event match.
- Discount, rebate, allowance and credit note all reduce what a customer pays, but they land in different places.
Backlog is owed, pipeline is hoped for
Backlog is work already committed and not yet delivered. Pipeline is work that might be committed. The first is an obligation; the second is a hope with a probability attached.
Reporting them together produces a figure that means nothing, because the two halves are not the same kind of thing. Anyone quoting a combined total should be asked for the split. The same pattern appears in the sales vocabulary set out in the business vocabulary mistakes page.
Official statistics draw the same line. The US Census Bureau's manufacturers' survey asks only for orders supported by binding legal documents, such as signed contracts, letters of intent or letters of award.
Forecast, order, contract and framework
These four terms form a ladder of commitment, from nobody bound to both sides bound on stated terms. Reading a report means knowing which rung each figure sits on.
| Term | What exists | What it binds | Where it sits in a report |
|---|---|---|---|
| Forecast | An expectation | Nobody | Pipeline, at most |
| Order | A placed request | Usually both sides, on stated terms | Backlog until delivered |
| Contract | A signed agreement | Both sides, on its own terms | Backlog, on those terms |
| Framework agreement | Agreed terms, no volume | Terms only, until an order is placed | Neither, until an order arrives |
The fourth row is where most disputes start. A framework sets the price and the
What each term binds
Forecast
- What exists
- Expectation
- What it binds
- Nobody
- Volume committed
- None
- Dispute risk
- Low
Order
- What exists
- Placed request
- What it binds
- Usually both sides
- Volume committed
- Stated terms
- Dispute risk
- Medium
Contract
- What exists
- Signed agreement
- What it binds
- Both sides
- Volume committed
- Its own terms
- Dispute risk
- Medium
Framework
- What exists
- Agreed terms
- What it binds
- Terms only
- Volume committed
- None until order
- Dispute risk
- Highest
Keeping what you won: churn, attrition and retention
Churn is the rate at which customers leave over a period. Retention is the share who stay. They are not simply one minus the other unless both are measured over the same period, on the same population, counting the same event as leaving.
Attrition is often used for staff and churn for customers, but the usage is not settled. Neither word tells you whether the count is of accounts, of people, or of revenue. Ask which, as the business vocabulary questions suggest.
A win that leaves again was only borrowed. Quote churn with its period and its counted unit, or the figure cannot be set beside the backlog it is supposed to protect. The business acumen mistakes page treats related confusions as errors rather than as pairs.
Where a price reduction lands
- A discount reduces the price before the invoice.
- A rebate returns money after a condition is met.
- An allowance is a deduction agreed for a defect or a shortfall.
- A credit note cancels part of an invoice already issued.
All four reduce what a customer pays. They land in different places, at different times, with different evidence behind them.
A business that treats them as one thing loses the ability to say why its realized price differs from its list price, a gap the business acumen metrics page tracks.
A routine for counting what has been won
- Split every headline figure into backlog and pipeline before quoting either one.
- Place each item on the ladderforecast, order, contract or framework agreement.
- For churn or retention, state the period, the population and the event counted.
- Record each price reduction as a discount, rebate, allowance or credit note.
Behind every step sits one named axis: committed against hoped for, volume against terms, the direction of the same count.
The business vocabulary metrics page keeps measure, ratio, rate and percentage point apart, and asks what a denominator claims. Once the axis is named, the pair is easy. Naming the axis is the whole exercise,
The single axis behind each pair
Pair
- Capacity, throughput
- Possible against actual
- Backlog, pipeline
- Committed against hoped for
- Order, framework
- Volume against terms
- Churn, retention
- Direction of the same count
- Utilization, efficiency
- Time used against output per input
- Lead time, cycle time
- Customer clock against operator clock
The single axis
- Capacity, throughput
- Backlog, pipeline
- Order, framework
- Churn, retention
- Utilization, efficiency
- Lead time, cycle time
Common questions
Can a framework agreement ever count as backlog?
Not by itself. A framework carries terms and no volume, so it binds nobody to buy. Once an order is placed under it, that order is the thing to count.
Is there a standard definition for any of these?
For a few, within a specific framework or industry standard. For most, no. That is why the working habit is to state the definition you are using in the sentence rather than to look for an authority.
How do I ask about a denominator without sounding difficult?
Ask what the number is out of, and over what period. Two short questions, neither of them a challenge, and they resolve most of it. Public guidance on writing for a reader, such as the federal plain language principles, makes the same point from the writer's side.
What if the other person's definition is different from mine?
Then you have found the disagreement, which is progress. Write both definitions down and decide which one the decision needs. Do not split the difference, because the average of two definitions is not a definition.
