Housecall Pro vs ServiceTitan: Public Price, 2026

As of the pages opened on September 1, 2026, neither Housecall Pro's fetched homepage body nor ServiceTitan Dispatch Pro help published a dollar SKU. Any $59-per-month figure from a third-party roundup is not allowed until housecallpro.com/pricing is opened and quoted with a date. US Tech Automations is not a substitute field-service system. Quote Growth $372/mo annual only as the orchestration layer, and only if the shop needs a join.

HVAC mechanics sit under SOC 49-9021 according to the U.S. Bureau of Labor Statistics. That code does not set a Dispatch Pro price. Owners still need a TCO sheet with technician count, official starting price, dispatch add-on, API access, and onboarding weeks. Empty cells stay labeled UNKNOWN. A sheet that fills those cells from a software roundup is not a TCO sheet.

Key Takeaways

• Neither opened page published a dollar SKU on September 1, 2026. Housecall Pro homepage body: no SKU dollars. Dispatch Pro help: no dollars. Roundup $59 is not a citation.

• Dispatch Pro is a subscription on top of ServiceTitan. Assist is the default. Auto is optional. Managed technicians only. Setup check up to 10 minutes, then every 10 minutes (help updated 24 June 2026).

• Growth $372/mo annual is the only public orchestration dollar on this page. It is not an FSM price.

• Build the TCO in 9 steps. Write UNKNOWN where the official page has no dollar. Do not sign a quote-only vendor from a blog table.

• Success for this page is a shop that returns a filled TCO sheet with UNKNOWN cells still labeled UNKNOWN.

• Home-grown dispatch plug-ins are a different job. Do not treat this page as that plug-in.

Two FSMs, one disclosure gap

Housecall Pro and ServiceTitan are field-service management systems. They schedule technicians, take payments, and run the job record. They are not interchangeable with an orchestration layer, and they are not interchangeable with each other on price disclosure. One vendor is widely rumored to publish a starting sticker. The other points Dispatch Pro buyers at a package picker. The rumor is not a source.

Housecall Pro published 0 SKU dollars in the homepage body opened for this article according to Housecall Pro (checked September 1, 2026). Until the official pricing page on that domain is opened and quoted, the starting-price cell is UNKNOWN. ServiceTitan commercial stickers were not on the Dispatch Pro help page. Contact ServiceTitan for a quote. Do not invent a per-tech price.

Specialty trade contractors sit in NAICS 238 according to the U.S. Census Bureau. Shops in that sector still buy software with a technician count, not with a NAICS code. Count techs first. Open official pages second. Write UNKNOWN third. Add Dispatch Pro fourth if the shop wants Assist or Auto. Add API access fifth if a home-grown system has to talk to the FSM. Add onboarding weeks only if a vendor page states a range. Add orchestration only if a join is required.

Inventory reorder, payroll joins, loyalty, and Google Business Profile work are not FSM stickers. Shops that need those maps can leave this page for small-business inventory reorder automation, Xero-to-Gusto automation, loyalty-program automation, or Google Business Profile checklists. Keep this page on published pricing.

How we evaluated published pricing

Evaluation used 4 disclosure tests dated September 1, 2026: did the opened Housecall Pro body publish a SKU dollar, did Dispatch Pro help publish a SKU dollar, is Dispatch Pro a separate subscription, and is a third-party $59 a valid citation. Scoring is binary. Feature laundry lists do not move the score.

The useful output is not a winner. The useful output is a TCO sheet that still says UNKNOWN where the official page was silent.

Dispatch Pro facts you already have

Dispatch Pro help, updated 24 June 2026, describes Assist as the default and Auto as optional. It applies to managed technicians only. The setup check runs up to 10 minutes, then every 10 minutes according to ServiceTitan. Those figures are timing facts, not prices. They still belong on the TCO sheet as operating constraints: a shop that wants Auto is buying a subscription on top of ServiceTitan, not "the ServiceTitan price."

Do not treat Dispatch Pro as free because Assist is the default mode inside the add-on. Default inside a paid add-on is not a $0 line. If a later commercial page publishes a Dispatch Pro dollar, quote that page with a date. Until then, the Dispatch Pro row is UNKNOWN dollars plus dated timing.

ServiceTitan remains the FSM. Dispatch Pro remains the dispatch add-on. A home-grown plug-in that talks to ServiceTitan over API is a third thing. This page will not rebuild that plug-in. If the shop has a home-grown dispatcher, add an API line to the TCO and read the vendor's API commercial terms. Do not paste a blog per-tech number into that line.

Checks after setup run every 10 minutes according to ServiceTitan. Plan onboarding around that interval only if Auto or Assist is in scope. Shops that will not buy Dispatch Pro should leave those rows blank, not zero.

Nine TCO steps for a shop

Nine steps produce a sheet a sales cycle can survive. Skipping step 3 is how an unofficial $59 re-enters the building.

1. Count technicians. W-2, 1099, and seasonal. Write the number at the top of the sheet. Do not count office staff as techs unless they run jobs.

2. Open both official pricing pages on the writing day. Housecall Pro pricing. ServiceTitan commercial pricing. Dispatch Pro commercial terms if Assist or Auto is in scope.

3. Write UNKNOWN where the page has no dollar. Do not fill from a roundup. Do not fill from a quote a neighboring shop remembers.

4. Add Dispatch Pro if the shop wants Auto or Assist. Keep it as its own row. Do not fold it into "the ServiceTitan price" without a source.

5. Add API access if a home-grown system must connect. Price that row from the vendor's API terms, or write UNKNOWN. Do not reuse a plug-in article as the whole TCO.

6. Add onboarding time as a range only if a vendor page states it. If the page is silent, the cell is UNKNOWN weeks, not "about a month."

7. Add orchestration only if the shop needs a join the FSM does not already perform. Growth $372/mo annual as of September 1, 2026 is the dated line. US Tech Automations can connect a job-complete trigger to a back-office write, queue failed syncs, and leave FSM scheduling inside Housecall Pro or ServiceTitan.

8. Compare five-year UNKNOWN versus a dated official quote. A five-year column that multiplies an unofficial $59 is still unofficial.

9. Do not sign a quote-only vendor from a blog table. The blog table is a checklist. The signature needs the vendor's paper.

US Tech Automations belongs on step 7 only. Steps 1 through 6 are the shop's homework. Shops that want Google Business Profile automation after the TCO is honest can use GBP ROI without putting GBP into the FSM sticker.

Feature matrix: disclosure, not a gadget list

Gadget lists hide the disclosure gap. This matrix is the gap.

Pricing and TCO table with UNKNOWN allowed

Columns are Housecall Pro, ServiceTitan, and orchestration. Rows are public starting price, dispatch add-on, API access, and onboarding weeks. Fill with dated quotes or UNKNOWN.

Repair and maintenance shops sit in NAICS 811 according to the U.S. Census Bureau. That code still does not publish a Housecall Pro SKU. If the official Housecall Pro pricing page later opens at a dollar amount, quote that amount with the fetch date. If it does not, leave UNKNOWN. The same rule applies to ServiceTitan's commercial page.

Dated numeric controls you can copy

Copy timing facts and policy counts. Do not copy unofficial stickers.

What a filled UNKNOWN cell is worth

Sales cycles die when one owner says Housecall Pro is $59 and the other owner says ServiceTitan is "enterprise, so more," and neither can point to a page. The honest sheet ends that argument without inventing a winner. UNKNOWN is a status. It means "we have not seen an official dollar," not "the product is free," not "the product is too expensive to print."

A composite shop with 8 technicians can still complete the sheet. Technician count is 8. Housecall Pro starting price is UNKNOWN. ServiceTitan starting price is UNKNOWN. Dispatch Pro is UNKNOWN dollars plus Assist default and Auto optional, managed techs only, 10-minute checks. API is UNKNOWN. Onboarding weeks are UNKNOWN. Orchestration is $372/mo annual only if a join is needed. Five-year column is UNKNOWN times 5 until official dollars exist. That sheet is qualified. A sheet that writes $59 in the Housecall Pro cell without a fetch is not.

Do not average two unofficial numbers. Do not take a percent off a competitor quote you heard at a trade show. Do not annualize a monthly rumor. Open the page or write UNKNOWN.

Package pickers that require a login are still official if they display a dollar after login. Quote that dollar with the date and the package name. Do not scrape a logged-in number into this article from memory. The article stays UNKNOWN; the shop's private quote belongs on the shop's sheet.

Limitations

A comparison page with two UNKNOWN prices is still useful if it refuses fake dollars. That is the point. Feature lists will not close the gap. Roundups will not close the gap. A neighboring shop's invoice will not close the gap unless you are buying the same package on the same date, which you should still confirm on the official page.

Do not invent a ServiceTitan per-tech price. Do not invent a Housecall Pro SKU from memory. Do not treat Dispatch Pro as included unless a source says otherwise. Do not treat Growth $372/mo as a replacement FSM. Do not fold API MAX, Dispatch Pro, and base ServiceTitan into one cell.

US Tech Automations is the wrong buy when the shop only needed a dated sticker and the FSM already exports what accounting needs. Pay for a join when a join exists. Do not pay for a join to avoid opening a pricing page.

Onboarding "weeks" without a vendor range are UNKNOWN. Implementation partners quoting 6 weeks are a quote, not a public page. Put partner quotes on a separate row labeled as partner quotes.

Loyalty-program automation does not belong in the FSM price row. Neither does inventory reorder. Keep add-on operations on their own sheets so the FSM disclosure stays visible.

Pilot: the TCO sheet is the deliverable

The success metric is a shop that emails a filled TCO sheet with UNKNOWN cells still labeled UNKNOWN. That reply is qualified. A reply that says "just tell us which is cheaper" is not, because cheaper is UNKNOWN.

Kill the exercise if anyone pastes $59 without a fetch. Reopen housecallpro.com/pricing on that day. If the dollar is there, write it with the date. If it is not, write UNKNOWN again.

Do not run a technician-time study as the pilot. Do not migrate job history as the pilot. Do not build the home-grown plug-in as the pilot. Count techs, open pages, fill cells, stop.

Composite walkthrough: a 12-tech plumbing shop wants Assist. Technician count is 12. Housecall Pro public starting price is UNKNOWN. ServiceTitan public starting price is UNKNOWN. Dispatch Pro is in scope, UNKNOWN dollars, Assist default, Auto optional, managed techs, 10-minute checks. API is out of scope because there is no home-grown dispatcher. Onboarding weeks UNKNOWN. Orchestration omitted because the FSM already pushes closed jobs to accounting. The sheet is done. The next step is vendor paper, not a blog signature.

How to count technicians without inflating the sheet

Technician count is the only number the shop fully controls on day one. Get it wrong and every later official dollar is multiplied by the wrong headcount. Count people who run jobs. Do not count the owner unless the owner still runs jobs. Do not count CSRs, dispatchers, or bookkeepers as technicians because a vendor later publishes a per-tech sticker. If Dispatch Pro is managed technicians only, write a second count: technicians who would be managed. That second count may be smaller than the first.

1099 techs belong on the sheet with a label. If a vendor later prices W-2 and 1099 differently, you will need the split. If the vendor does not, you still needed the split for labor law, which is not this article. Seasonal spikes belong as a range, not as a hopeful average. A shop that is 8 all winter and 14 from May to September should write 8 / 14, not 11.

Do not count "trucks" as technicians. A truck can sit. A technician can ride with a helper who is not licensed to close the job. Helpers who never take a job as the assigned tech stay off the tech count unless the vendor's page says otherwise. If the vendor page is silent, the helper cell is UNKNOWN, not a guess.

Office users who need login access are not a reason to invent a per-seat Housecall Pro dollar. Seats were not on the opened homepage body. If a later official page prices seats, add a seat row. Until then, do not backfill seats from a roundup.

Composite noise: 10 W-2 techs, 2 seasonal 1099s, 1 owner who still runs jobs, 3 helpers who never take the job. Tech count for the sheet is 13 in season and 11 in winter if the owner is included, plus a managed-tech count that may exclude the 1099s if Dispatch Pro would not manage them. Write the rule you used. Do not hide the owner.

How to record a later official dollar

Official dollars will show up after this article's September 1, 2026 fetch. Record them on the shop sheet, not by editing a rumor into the Housecall Pro cell. Write the date you opened the page, the URL, the package name, the dollar, whether tax is included, whether Dispatch Pro is listed separately, and whether the page required a login. If the page is a package picker with no dollar until a sales call, the cell stays UNKNOWN and the sales call becomes a quote row, labeled as a quote.

A quote is not a published SKU. Quotes expire. Published pages can change. Keep both. When a quote and a page disagree, the signature follows the vendor paper, not the older blog table. When two owners bring two quotes for two different packages, do not average them. Put both rows on the sheet.

Seasonal technician counts change the sheet even when the sticker does not. A shop that runs 8 techs in winter and 14 in summer should write both counts. Per-tech rumors become even less useful when the headcount is a range. If a vendor later publishes a per-tech dollar, multiply it by the count you actually staff, not by a round number from a forum.

Do not backfill last year's unofficial $59 into a five-year column "just to have a number for the bank." Lenders can read UNKNOWN. They cannot unwind a five-year model built on a roundup. If the bank requires a number, attach the vendor quote as of a date, and keep UNKNOWN on the public-price row until a page exists.

Composite noise: the 12-tech plumbing shop later opens Housecall Pro pricing and finds a dollar. They write that dollar, the date, and the package name. ServiceTitan remains UNKNOWN until their commercial page or quote arrives. Dispatch Pro stays its own row. The sheet is still honest. The shop can now compare one dated official dollar against one UNKNOWN plus a quote, which is a real comparison, not a roundup fight.

FAQs

Is Housecall Pro $59 per month on this page?

No. A third-party roundup is not a citation. The homepage body opened September 1, 2026 published 0 SKU dollars. Open housecallpro.com/pricing. Quote it with a date, or write UNKNOWN.

What does ServiceTitan cost per technician?

UNKNOWN on this page. Do not invent a per-tech sticker. Contact ServiceTitan. Keep Dispatch Pro on its own row.

Is Dispatch Pro included in ServiceTitan?

Not on the sources used here. Dispatch Pro is a subscription on top of ServiceTitan unless a source says otherwise. Assist is the default inside that add-on. Auto is optional. Managed technicians only.

Can orchestration replace Housecall Pro or ServiceTitan?

No. Growth $372/mo annual as of September 1, 2026 is an orchestration layer. Scheduling, dispatch, and the job record stay in the FSM.

Why keep UNKNOWN on a five-year column?

Because multiplying an unofficial monthly rumor produces an unofficial five-year rumor. Official dollars first. Then multiply.

What if we already have a home-grown dispatcher?

Add an API row. Price it from vendor API terms or write UNKNOWN. Do not treat this published-pricing page as the plug-in playbook.

Published pricing is a disclosure test, not a feature war. Open the official pages, keep Dispatch Pro on its own line, and leave blanks labeled UNKNOWN. US Tech Automations can connect a closed-job trigger to a back-office write and queue failed syncs only after that sheet exists and only if the FSM export is not enough.