The Real Cost of Traffic Control Software: A Total Cost of Ownership Breakdown

Every software comparison starts with a price grid, and every price grid is misleading in the same direction. It shows the smallest line.

This works through the whole cost of putting a field service platform into a traffic control company — using pricing published on vendors' own pages as of August 29, 2026 — and then the costs that never appear on any page.

A note on sourcing: every dollar figure attributed to another vendor below comes from that vendor's own public pricing page, accessed on the date above. Pricing changes; check the source before relying on a number. Where a vendor does not publish pricing, this says so rather than guessing.

Line one: the subscription, and why headcount decides it

The structural fact about this market is that most field service software is priced per user, and traffic control is crew-heavy. That combination is why the sticker price and the invoice diverge so sharply.

Jobber publishes four plans: Core at $21 a month billed annually against a $49 regular rate with one user, Connect at $70 against $139 with five users, Grow at $105 against $199 with ten users, and Plus at $280 against $499 with fifteen users, with additional users at $29 a month each.

Housecall Pro publishes Basic at $59 a month billed annually or $79 monthly with one user, Essentials at $149 annually or $189 monthly with five users and additional users at $100 a month each, and Max at $299 annually or $329 monthly with eight users and additional users at $75 a month each.

ServiceTitan does not publish plan prices at all; its pricing page presents Starter, Essentials, and The Works tiers behind a "Request Pricing" button and describes the model as per-technician pricing designed to fit your business.

Now put a real company against those numbers. Take a traffic control operation with six office staff and thirty-four field staff — forty people who need access, which is modest for this trade.

On Jobber's Plus plan, fifteen users are included and the other twenty-five bill at $29 each: $280 plus $725, or $1,005 a month at the annual rate. On Housecall Pro's Max plan, eight users are included and the other thirty-two bill at $75 each: $299 plus $2,400, or $2,699 a month at the annual rate.

Neither of those is a criticism of the product. Both are priced for trades where the crew count is small and the ticket is a single technician at a single address. Traffic control is not that trade, and the per-seat model prices accordingly. We take this apart in more detail in per-user versus flat-tier pricing.

For comparison, Traffic OS is flat-tier: Starter at $499 a month with two admins and eight drivers, Pro at $949 with five admins and twenty drivers, and Enterprise at $1,499 with ten admins and fifty drivers. It is not free of headcount either, and the Traffic OS pricing FAQ says so directly: "Beyond the included headcount, add drivers at $20/seat/month or admins at $40/seat/month." The same forty-person company on the Pro plan is $949 plus fourteen additional drivers at $20 and one additional admin at $40, or $1,269 a month. The point is not that flat-tier is free. It is that the marginal seat costs $20 rather than $75, which is what changes the decision about whether to give a flagger an account at all.

That last point is the one that matters operationally, and it is the reason this pricing structure exists. If a seat costs $75 a month, someone will decide the seasonal crew does not need one. The consequence is not a smaller invoice — it is a foreman texting photos to the office and a daily ticket typed in by someone who was not on site. The seat you did not buy becomes a data-capture gap, and the gap becomes a ticket dispute three weeks later.

Line two: implementation and setup

This is the line most often left out of the comparison entirely, because it is one-time and buyers mentally discount it.

Traffic OS charges a one-time setup fee of $1,000 on Starter, $1,750 on Pro, and $2,500 on Enterprise, covering data migration, training, and thirty days of priority email support. Other vendors handle this differently — some bundle it, some quote it per engagement, some sell it as a professional services package. ServiceTitan's implementation is quoted as part of the sales conversation rather than published.

What to actually evaluate here is not the number but the scope. Three questions decide whether an implementation fee was money well spent:

Who migrates the data? Your customer list, your rate sheet, your equipment catalogue, your open jobs. If the answer is "you export a CSV and we import it," the real cost is your office manager's month, not the fee.

Who configures it? A field service platform out of the box does not know what a Type 3 barricade is, what your MSA rate sheet looks like, or that your daily ticket needs a GPS-stamped customer signature. Somebody spends time on that. Whether it is billed or absorbed, it is spent.

Who trains the crews? This is the one that determines the outcome, and it is the one most likely to be quietly scoped down.

Line three: payment processing

If you invoice through the platform and take cards, this becomes the largest software-adjacent line in the business, and it usually is not counted as software at all.

Jobber publishes payment processing at 2.9% plus 30 cents for credit cards, 2.7% plus 30 cents for tap to pay, and 1% for bank payments. Those rates are broadly conventional across the sector.

Scale it. A traffic control company doing $2 million a year with half of that collected by card pays roughly $29,000 annually in processing on the card half. Push card collection to everything and it is closer to $58,000. Against a subscription of $12,000 to $32,000 a year, processing is frequently the bigger number.

The evaluation question is whether the platform lets you route ACH cheaply, whether it lets you bring your own merchant account, and whether it surcharges. For a business whose customers are general contractors and municipalities paying on thirty-day-plus terms, the answer often should be that most money arrives by ACH or check anyway — which makes this line smaller than it looks, but only if the platform makes ACH easy. Our piece on getting paid faster covers the collection side.

Line four: add-ons

Modules sold separately are where a quoted plan price drifts. Jobber publishes a Marketing Suite at $99 a month, a Receptionist add-on at $29, and Pipeline at $49 — roughly $177 a month if you take all three, which is more than the base Grow plan.

Add-ons are not inherently bad; unbundling means you do not pay for what you do not use. The failure mode is comparing a base plan against a competitor's all-inclusive tier and concluding the base plan is cheaper. Build the comparison from the feature list you actually need, then price each platform's route to that list.

For this trade, the features that turn out to be add-ons somewhere are usually: a customer portal, recurring or rental billing, purchase orders, advanced reporting, and anything to do with equipment as a rentable asset rather than a consumable. That last one is worth checking carefully, because equipment rental billing is core to a barricade company and peripheral to a plumbing platform.

Line five: integrations and the accounting seam

Almost every company in this trade runs QuickBooks Online. Almost every platform claims to integrate with it. The claims are not equivalent.

The cost here is not a licence fee, it is reconciliation labour. A one-way integration that pushes invoices but does not sync payments means somebody marks invoices paid twice — once in each system — every week, forever. At two hours a week and a loaded bookkeeping rate, that is a real annual number attached to a checkbox that said "QuickBooks integration: yes."

Ask specifically what syncs, in which direction, and what happens on edit. Our QuickBooks integration piece sets out the questions worth asking before the demo ends.

Line six: the cost of the thing it replaces

This is the line that makes the whole exercise worthwhile, and it runs in your favour.

A company running operations on spreadsheets is already paying for the alternative — in dispatcher hours rebuilding the schedule each morning, in the office chasing signed tickets, in invoices that go out late because nobody could confirm what happened on Tuesday, and in devices that walk off with nobody able to say from which job.

Put a number on it before you shop. If your invoicing runs a week behind because ticket collection is manual, that week is working capital. If your dispatcher spends the first ninety minutes of every day reassembling the board, that is roughly 375 hours a year. If unattributed device loss runs a few thousand dollars a season, that is a line item too, and one that tracking devices by job site addresses directly.

You do not need these numbers to be precise. You need them to exist, because otherwise the software decision is a cost with no offsetting benefit on the page.

Line seven: non-adoption, the expensive one

The worst outcome is not overpaying. It is paying and not switching.

A platform the field never adopts leaves you with the full subscription, the full setup fee, and the full manual process still running underneath — because the office cannot stop maintaining the spreadsheet while half the crews are still texting photos. That is strictly worse than not buying, and it is common.

Non-adoption has a small number of predictable causes, and most of them are visible before purchase. The app is unusable on a cracked phone in gloves in the sun. It requires a signal in places with none — worth testing against offline-first field apps, because a rural closure with no bars is not an edge case in this trade. Or the crews were never trained, because training got scoped out to hit a number.

The mitigation is not a contract term. It is a pilot with one real crew on real jobs before you commit the fleet, which is the substance of rolling out software to your crews.

Line seven and a half: field-only seats

Some vendors split seats by capability, and for a crew-heavy trade this is the single most important structural question to ask.

FieldPulse describes a seat-based model with full-access seats carrying complete platform permissions and field-only seats limited to the mobile app, and does not publish figures — its pricing page directs visitors to request a custom quote. That structure, where it exists, is usually much friendlier to this trade than a flat per-user rate, because a flagger genuinely does not need the permissions an office coordinator needs.

So the question to put to every vendor is not "what does a seat cost." It is "what does a seat cost for someone who only clocks in, opens a job, and signs a ticket?" If there is one price for everybody, your forty-person company is paying office rates for thirty-four people who will never open a report. If there are two prices, the marginal cost of covering the whole crew may be small enough that you stop rationing accounts — which is the outcome that actually matters, because a rationed account is a data gap.

Where pricing is not published at all, as with ServiceTitan and FieldPulse, you cannot do this arithmetic before the sales call. That is not disqualifying, but it does mean the comparison has to wait for a quote, and you should ask for the quote in the same shape: base, included seats, marginal full seat, marginal field seat, setup, and add-ons.

Line eight: the exit

Nobody evaluates the exit, and everybody eventually uses it.

Three years in, some portion of the companies reading this will change platforms — because they outgrew one, because a vendor was acquired, because the product moved away from their trade. The cost of that move is set by decisions you make now.

What can you export, and in what form? Customers and invoices are usually fine. The things that tend to be trapped are the ones you most want: signed daily tickets with their photos and signature images, time clock records, equipment history by job. If a signed ticket exports as a row of text without the signature image, your chargeback evidence does not survive the migration.

How long do you retain it? A daily ticket dispute can surface a year after the work, and a payment-bond or lien question later still. If your retention window is shorter than your dispute window, the platform is deleting your evidence on schedule.

What is the notice period? Month-to-month terms cost more per month and are worth it during the period when you do not yet know whether the thing works.

None of this is expensive to ask about before signing. All of it is expensive to discover afterwards.

Line nine: how it is treated on the tax return

Worth a paragraph because it changes the after-tax comparison, though the specifics belong to your accountant rather than to a blog post.

A subscription is ordinarily an operating expense deducted in the year incurred, while purchased off-the-shelf software is capital property that may be expensed under Section 179 or depreciated. IRS Publication 946 sets out the rules for depreciating property, including which computer software qualifies and the Section 179 election. For a SaaS platform billed monthly, the practical answer is usually the simpler one — it is an operating cost, deductible as incurred — but the implementation fee, hardware bought to support the rollout, and any perpetual licences are a different question.

Two things follow for a TCO comparison. First, do not compare a subscription against a capital purchase without accounting for the timing difference. Second, if you are weighing an annual prepay against monthly billing near a year end, the deduction timing is a real if minor input, and it is exactly the sort of question worth putting to your accountant before you commit twelve months.

Putting it together

For the forty-person company above, over the first year, the honest comparison looks roughly like this — subscription at published annual rates, plus setup, plus a modest allowance for processing and add-ons:

A per-seat platform at $75 per additional user lands near $32,000 in subscription alone. A per-seat platform at $29 per additional user lands near $12,000. A flat-tier platform with $20 marginal driver seats lands near $15,000 plus a $1,750 setup fee. Processing sits on top of all three identically if your card mix is the same. Add-ons vary by what you need.

The spread between the cheapest and the most expensive of those is real money, but it is smaller than the spread between a platform your crews use and one they do not. That is the actual decision. Price the seats honestly, because the seat count is what per-seat pricing punishes, but choose on whether the field will pick it up.

The comparison worth building is not a price grid. It is a one-page sheet with subscription at your real headcount, setup, processing at your real card mix, the specific add-ons your feature list requires, and an honest line for what the current process costs. Every vendor's page gives you the first column. The rest is yours, and it is where the answer lives.

If you want ours in that format, the pricing page publishes the plans, the included headcount, the marginal seat rates, and the setup fees without a sales call. Compare it against whatever else you are considering — with the seat count filled in.