ServiceTitan pricing: there is no number, so here are the eight questions that produce one

Search “ServiceTitan pricing” and you will find a dozen pages with a number on them. None of those numbers came from ServiceTitan. The company does not publish a rate on its pricing page — it routes you to a sales conversation, which is a legitimate way to sell enterprise software and a bad way to budget for it.

That does not mean the price is unknowable. It means the price is a function of things you can specify, and the work is making the vendor specify them before you commit.

Why there is no public price

Three structural reasons, and they matter because each one shapes what you should ask for.

Implementation is the product. A scheduling app is self-serve. A system that replaces dispatch, price book, payroll integration, marketing and reporting for a twenty-truck operation is not — it has to be configured against how the business actually runs. The vendor cannot quote the software without also quoting the work of installing it, and the work varies more than the software does.

Pricing is modular. The subscription covers a core; additional capability is bought in units. Two shops with the same truck count can end up with materially different bills depending on which modules they take and how many office seats need access.

The contract is negotiated. Term length, implementation scope, payment processing and reference commitments are all tradeable. A published list price would remove most of that leverage, so there isn’t one.

What is actually in the quote

When the proposal arrives, it will usually contain five separable lines. Treat them as separable.

Line	What it is	Negotiable?
Subscription	Per technician, per month	Sometimes, via term
Implementation	One-time configuration, migration, training	Yes, via scope
Modules	Per-feature add-ons	Yes, via which you take
Payment processing	Percentage of card volume	Rarely
Support tier	Response times, account management	Sometimes

The implementation line is the one that breaks first-year budgets. A shop comparing “$X per technician” against a competitor’s published price is comparing a subscription against a subscription-plus-project, and the project is frequently the larger number in year one.

The eight questions

Ask these before a demo, in writing, and ask for the answers in writing. A vendor that will not put them in an email is telling you something useful.

1. What is the all-in first-year cost, per technician? Not the subscription — the total of every line above, divided by the number of technicians. This is the only figure that is comparable to a published price from another vendor.

2. What is the all-in year-two cost? Year two drops the implementation and usually rises on subscription. If the answer is “similar,” ask for the renewal clause, not the summary.

3. How many office seats are included, and what does an extra one cost? Dispatch, accounting and management users are often priced differently from field technicians. A shop with two office staff and six techs has eight users, not six.

4. What exactly does implementation include, and what is billed as a change order? The scope document is the contract. Data migration of customer history, price book build, and on-site training are the three items that most often become extra.

5. How long is the initial term, and what is the notice period to leave? Multi-year terms are common. Auto-renewal with a 60- or 90-day notice window is common too, and it is the single most expensive clause to miss.

6. What does payment processing cost, and can I use my existing processor? Processing is often the largest recurring line after subscription and is frequently bundled. Ask for the rate in basis points, not as “competitive.”

7. What is the exit? Can you export customer records, job history, photos and attachments in a usable format, and is there a fee for it? Ask for a sample export before you sign, not after.

8. Who is the named implementation contact, and what happens when they leave? Implementation quality is a personnel question. Get a name and a timeline in the statement of work.

Normalising a quote

Once you have the numbers, do this arithmetic before comparing anything:

all-in year one per technician =
  (subscription × technicians × 12
   + implementation
   + modules × 12
   + support tier × 12)
  ÷ technicians

Then divide by twelve for the monthly equivalent. That is the number to hold against a competitor’s published rate — not the subscription line, which will always look competitive in isolation.

An illustrative shape, with numbers invented to show the method rather than to describe any real quote: six technicians, a subscription quoted per tech, a five-figure implementation, one module, and a three-year term. The subscription might be a third of the first-year total. In year two the same contract looks far cheaper, which is exactly why the vendor prefers you to think in year two and you should think in year one.

What is actually negotiable

Vendors in this category negotiate on four things, in roughly this order of willingness.

Implementation scope. Narrowing what the vendor does — you migrate your own customer list, you train your own staff — is the most reliable way to reduce the first-year number. It is also the most work, and it is the reason some implementations go badly. Only take this trade if someone on your side owns the project.

Term length. A three-year commitment buys a better rate. It also buys you three years of a decision you made before you had used the product. If you take the longer term, get a service-level commitment with a remedy attached, not a promise.

Payment processing. Moving card volume onto the vendor’s processor is worth more to them than the subscription discount costs. Ask what the rate becomes if you do, and compare it to your current effective rate including terminal fees.

Reference and case-study participation. Occasionally tradeable, usually small, and only relevant if you are comfortable being named publicly.

What is not negotiable: the pricing model itself. You will pay per technician. If the quote is structured another way, ask why, because it will affect how the bill grows as you hire.

When ServiceTitan is the wrong purchase

The honest test is not truck count, it is whether anyone owns the system.

• Under about five trucks. The implementation cost cannot be spread far enough, and the operational gain over a product with a published $60–$300 monthly price is small.
• No dedicated office role. These systems assume a dispatcher. If the owner dispatches from the cab between jobs, the software’s main advantage — a coordinated office — does not exist.
• No process to install. Implementation configures your workflow. If the workflow is “whatever the owner decides that morning,” you are paying to automate chaos, and it will be configured wrong.
• Cash-constrained first year. The subscription is smooth and the implementation is a cliff. Finance the cliff or wait; do not discover it in month two.

What to do this week

If you are considering it, do not start with a demo. Start with an email asking for the eight answers above. The quality and speed of that reply tells you more about the implementation than an hour of screen sharing, and it costs you nothing.

Illustrative arithmetic in this article is labelled as such and describes no real quote. ServiceTitan publishes no rate as of 24 October 2026; this page is re-checked monthly and will print a figure the day one exists on the vendor’s own site.

Sources: vendor pricing pages read on 24 October 2026; vendor documentation and help-centre articles where cited. Figures are reproduced as published by the vendor — no estimates are substituted for a missing price. Some outbound links are affiliate links; see the disclosure.