Our average ticket went up but revenue didn't move. What does that mean?
Almost always it means completed job count fell by about as much as ticket rose, and both moved for the same underlying reason. Average ticket is a ratio. Revenue is that ratio multiplied by completed jobs. If you tightened dispatch, dropped a cheap job type, or simply lost small-ticket demand, the average climbs mechanically while the total stands still. Never read average ticket without job count beside it.
Decompose the change instead of describing it
Revenue equals completed jobs multiplied by average ticket. So any change in revenue between two periods can be split into three pieces: the change from doing more or fewer jobs, the change from each job being worth more or less, and a small interaction term where both moved at once.
The arithmetic is simple. Change from volume is the change in job count multiplied by the old average ticket. Change from ticket is the change in ticket multiplied by the old job count. The remainder is the interaction. Once you print those three numbers, the conversation stops being about whether the ticket is good and starts being about which lever actually moved.
The mix explanation, which is the usual one
Average ticket is a weighted average across job types, and the weights move constantly. A mild shoulder season kills tune-ups and drain calls first. Those are your low-ticket jobs. Remove them and the surviving population is replacements and installs, so the average rises with nothing having improved.
Check this by computing average ticket within each job type. If every job type is flat and only the blended number moved, it is mix. That test takes five minutes and prevents a quarter of wrong conclusions in home services reporting.
The selection explanation, which is the interesting one
Sometimes the mix moved because you moved it. Raising a diagnostic fee, declining out-of-area work, prioritizing membership customers on the board, or shifting media spend toward replacement intent all filter demand. Each one raises average ticket by removing small jobs.
That can be exactly right. Small jobs consume a full dispatch slot and a full drive. But the decision has to be made knowingly, with the volume loss on the same page. When it happens accidentally — a bid change, a broad match expansion, a new intake script — it looks like a win in the ticket column and a mystery in the revenue column.
Report the three numbers together, always
A revenue line that shows only average ticket is a report designed to be misread. Show completed jobs, average ticket and completed revenue on the same row, for the same period definition, and the decomposition becomes obvious to anyone looking at it.
This is one of the reasons connecting media data to operational data matters more than making either one prettier. See marketing intelligence for how source-level data feeds the same table, and custom dashboards for how the layout gets built.
Topics: average ticket · job count · decomposition · mix · reporting
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.