How to Forecast Service Business Revenue
A revenue forecast for a service business is a capacity model, not a target you pick and hope for. Revenue is produced by technicians completing jobs, so the forecast starts with four operating numbers: how many techs run calls, how many jobs each one completes in a day, what the average invoice is worth, and how many days the crew is actually dispatched in a month.
Core revenue formula
Monthly revenue = technicians × jobs per tech per day × average job value × working days per month
Annual revenue is that monthly figure multiplied by 12, and revenue per technician is monthly revenue divided by headcount. Per-tech revenue is the number worth tracking month over month, because total revenue can rise purely by hiring while every truck on the road becomes less productive. Two shops with the same top line can be running very different businesses once you divide by headcount.
Use per-tech revenue to make staffing calls. When techs are consistently booked out and per-tech revenue has flattened at a healthy level, capacity is the constraint and another truck is the answer. When per-tech revenue is falling, the constraint is usually scheduling, ticket size, or lead quality — adding headcount there adds payroll without adding output.
The calculator also applies 10%, 20%, and 30% growth to your baseline so you can compare a target against what it would take to staff and dispatch. Those scenarios are planning inputs, not guaranteed outcomes — run them alongside your payroll and overhead numbers before you commit to a hire.
What to Enter in Each Revenue Calculator Input
| Input | What to enter | Why it matters |
|---|---|---|
| Number of technicians | Billable field techs who run their own calls, counting a working owner only for the share of time actually spent on jobs | Counting office staff or apprentices who ride along inflates every number downstream. |
| Avg jobs per tech per day | Completed calls per tech on a normal day, pulled from the last 30 to 60 days of dispatch history | Using a best-week number produces a forecast the schedule cannot repeat. |
| Avg job value | Average invoiced total per completed job, including labor, parts, and trip charges | If a few large installs skew the average, forecast replacements separately from service calls. |
| Working days per month | Days the crew is actually dispatched — roughly 22 for a standard weekday month | Holidays, PTO, weather days, and seasonal slowdowns all reduce billable capacity. |
The calculator returns monthly revenue, annual revenue, and revenue per technician per month from these four inputs. It is a top-line forecast — it does not subtract labor, materials, or overhead, so pair it with job-level pricing before you treat any figure as profit.
Levers to Increase Revenue Per Tech
Only three of the four inputs are things you control day to day. Working days are largely fixed by the calendar, so growth without hiring comes from ticket size, travel efficiency, and schedule utilization.
Average ticket. Ticket increases fall straight through to revenue without adding a truck or a day. Give techs a current price book instead of a rate they memorized two seasons ago, present repair options at more than one tier so the customer chooses scope, quote the related work found on site rather than deferring it to a second trip, and convert eligible customers onto maintenance agreements that produce scheduled revenue in slow months.
Travel and dispatch efficiency.Windshield time is unbilled time. Cluster the day's work by geography instead of by call order, dispatch the nearest qualified available tech rather than the first name on the board, batch same-day add-ons into the zone a tech is already in, and stage common parts on the truck so a missing fitting does not cost an hour. Removing 30 minutes of drive time per tech per day is most of the way to another job on the board.
Schedule utilization. A cancelled morning slot is capacity that expires. Keep a standby list to backfill cancellations, book recurring maintenance into historically slow weeks, confirm appointments the day before to cut no-shows, and hold a small buffer for same-day emergency calls, which typically carry a higher ticket than a booked-out repair.
One caution: do not raise jobs per day by rushing the work. Callbacks, warranty returns, and refunds eat the gross profit the extra job created, and they consume a second slot to fix. Track completed jobs per dispatched day alongside callback rate so you can tell real productivity gains from ones you will pay for later.
Worked Revenue Forecast Example
This example is illustrative, not a projection of what your business will earn. Assume a shop running 5 field technicians, each completing 4 jobs per day, at an average job value of $250, across 22 working days per month.
- Revenue per tech per day: 4 × $250 = $1,000
- Revenue per tech per month: $1,000 × 22 = $22,000
- Monthly revenue: $22,000 × 5 techs = $110,000
- Annual revenue: $110,000 × 12 = $1,320,000
Now test the levers against that baseline. Raising the average ticket by $25 to $275 — with the same crew, same job count, and same calendar — moves monthly revenue to $121,000 and annual revenue to $1,452,000. Recovering enough drive time to add a fifth job per tech per day at the original $250 ticket moves monthly revenue to $137,500.
Compare either result with the 10%, 20%, and 30% growth scenarios the calculator produces, then check them against what you would have to spend to get there. A 10% lift earned through ticket size and routing costs far less than a 10% lift earned by hiring a sixth tech, and it arrives sooner. Save your assumptions and revisit them each quarter against actual invoiced revenue.
A Repeatable Forecasting Workflow
- Pull the last 60 days of completed jobs and invoiced revenue from your job records.
- Calculate your real averages: jobs per tech per day, average job value, and days actually dispatched.
- Run the baseline forecast and note revenue per technician per month as your working KPI.
- Pick one lever — ticket size, routing, or utilization — and model it as a single input change.
- Compare the lever scenario against the cost of hiring for the same revenue lift.
- Set the target, assign an owner, and track per-tech revenue and callback rate monthly.
- Re-run the forecast each quarter with actual results so the model reflects the business, not last year's assumptions.
Frequently Asked Questions
How do I calculate monthly service revenue?+
Multiply technicians × average jobs per day × average job value × working days per month. This calculator does that automatically.
What is a healthy revenue per technician?+
It varies by trade, but many service businesses target consistent monthly revenue per tech to cover labor, overhead, and margin goals.
How do I improve revenue per tech?+
Increase average ticket value, reduce travel time, and improve scheduling efficiency to maximize billable hours.
Are growth projections guaranteed?+
No. Growth projections are scenario-based estimates to help you plan, not guaranteed outcomes.