A8gent
GlossaryBusiness and buying

What is cost per booked job?

Also called: cost per booking, cost per acquisition

Cost per booked job is everything you spent to win a job divided by the number of jobs booked, and it is the metric that tells you whether an automation is paying for itself.

Written by A8gent
Contents
  1. At a glance
  2. What cost per booked job measures
  3. What to include
  4. Where automation changes it
  5. Segmenting it
  6. What you should know
  7. FAQ
  8. Related terms

At a glance

Category
Business and buying
Formula
Total acquisition spend divided by jobs booked in the same period
Include
Ads, referrals, listings, enquiry-handling labour, tools, amortised build cost
Most common distortion
Leaving labour out, which makes automation look worse than it is
Three automation levers
More bookings per spend, less labour per booking, fewer wasted slots
Better than
Cost per lead, which flatters channels producing leads that never book

What cost per booked job measures

Cost per booked job is total acquisition spend divided by jobs actually booked in the same period. It is the service-business version of cost per acquisition, and it is more useful than cost per lead for one reason: leads are not revenue. A channel producing cheap leads that never book is expensive, and cost per lead flatters it.

For an automation project this is usually the number that decides whether it continues. An automation that costs a fixed monthly amount and increases booked jobs moves this metric directly and unambiguously, which makes it a better argument than any productivity estimate.

What to include

Be generous with the numerator or the number lies. Include advertising spend, referral fees and directory listings; the labour cost of the people handling enquiries, at least in proportion; the tools - CRM, phone system, automation platform, model API; and the amortised cost of building the automation itself.

Leaving out labour is the most common distortion, and it is the one that makes automation look worse than it is. If an automation removes ten hours a week of enquiry handling, that saving only appears if the labour was in the calculation to begin with. Choose a period long enough to be stable - a month for a busy business, a quarter for a lumpy one.

Where automation changes it

Three routes, and they behave differently. More bookings from the same spend: faster response converts enquiries that previously went cold, which reduces cost per job with no change to the numerator. This is where speed to lead and missed-call text-back pay.

Less labour per booking: automation handles the qualifying, the data entry and the follow-up, so the same team handles more volume. Fewer wasted slots: reducing your no-show rate means more of what you booked actually happens. The third one is often the largest and is the most frequently forgotten.

Segmenting it

An aggregate figure hides the decision you actually need to make. Segment by source - which channel produces jobs rather than enquiries - by job type, since a large installation and a small repair are not comparable, and by time period, so you can see the effect of a change.

Cost per booked job is also only half a picture on its own. A channel with a high cost per job that produces customers who return for years may be your best channel; one with a low cost per job that produces one-off price-shoppers may not be. Where you can, look at it alongside the value of the customer over time, not just the first job.

What you should know

Measure it before the automation exists. A baseline nobody disputes is what makes the after number credible, and it takes one afternoon with your accounts and your CRM. Without it, every claim about the automation's effect is an argument rather than a fact.

Then use it honestly. If cost per booked job did not move, say so and find out why - usually the automation improved a step that was not the constraint. That is a useful finding, and it is the sort of thing the free automation audit is designed to identify before you build rather than after.

Cost per booked job FAQ

How do I calculate cost per booked job?

Add everything you spent on winning work in a period - advertising, referrals, listings, the labour of handling enquiries, the tools, and the amortised cost of any automation - then divide by the number of jobs actually booked in that period.

Why is cost per booked job better than cost per lead?

Because leads are not revenue. A channel that produces cheap enquiries which never convert looks excellent on cost per lead and terrible on cost per booked job. Measuring at the booking stage tells you which spending actually results in work.

Should I include staff time?

Yes, at least proportionally, and leaving it out is the most common error. If an automation removes ten hours a week of enquiry handling, that saving is invisible unless the labour was in the calculation to begin with - which is precisely why automation often looks worse than it is.

How does automation reduce cost per booked job?

Three ways: converting enquiries that previously went cold through faster response, handling more volume with the same team, and reducing no-shows so more of what you booked actually happens. The third is often the largest and the most frequently forgotten.

What if the number did not improve after automating?

Then the automation probably improved a step that was not the constraint - which is a useful finding rather than a failure. Look at which stage is actually losing work: unanswered enquiries, slow quotes, no-shows or lost follow-up, and target that instead.

Should I look at anything alongside it?

The value of the customer over time. A channel with a high cost per booked job that produces customers who return for years can be your best channel, while a cheap one producing one-off price-shoppers may not be. First-job economics alone can mislead badly.

Primary source

Harvard Business Review - The Short Life of Online Sales Leads

Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.

Want this built rather than explained?

Knowing what cost per booked job means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.