Field service software revenue, contractor revenue and the value of jobs processed through a platform are different measures. This September 8, 2026 source review uses a published financial example and explains what evidence is missing before any market-share or adoption claim can be made.
A public revenue example
ServiceTitan reported the following results for its fiscal year ended January 31, 2026. Values below are rounded to one decimal place in millions of US dollars. Company results, revenue table on PDF page 3.
| Reported category | Fiscal 2026 revenue, USD millions |
|---|---|
| Subscription | $712.3 |
| Usage | $213.1 |
| Platform subtotal | $925.4 |
| Professional services and other | $35.5 |
| Total | $961.0 |
The platform subtotal already includes subscription and usage. Do not add it to those components again. The company reports annual revenue here, not annual recurring revenue, US-only FSM sales or a total for the software category. Rounding can affect the displayed sum.
This is one company's disclosure, not a ranking or market-share calculation. Comparing it with estimates of another vendor's recurring subscriptions requires matching the measures first.
What a market-size estimate needs
A useful estimate states its publisher, publication date, base year, geography, included products and treatment of services and usage fees. A forecast must also identify its endpoint and assumptions. Without those boundaries, two plausible numbers can describe different markets.
| Proposed claim | Evidence needed |
|---|---|
| Total US FSM revenue | Defined product scope and comparable US revenue coverage |
| Global growth rate | Consistent base/end years, currency treatment and forecasting method |
| Vendor market share | Comparable vendor numerator and market denominator |
| Software adoption among small operators | Representative sample and definition of active use |
| AI adoption | Named task, users, usage period and actual deployment evidence |
The reviewed public sources do not substantiate the earlier draft's combined US/global totals, vendor shares or adoption rates. We have withdrawn those numbers rather than treating estimates of private-company revenue as audited facts.
Compare prices for your actual team
Use current official plan information: Jobber pricing, Housecall Pro pricing and ServiceTitan pricing. Jobber distinguishes team options and billing commitments; Housecall Pro publishes packages; ServiceTitan requests pricing for its packages. Confirm the terms offered to your business.
Build a comparison from the same requested workflows, number of office/field users and contract period. Record included seats, add-ons, implementation charges, usage fees, payment processing and any price change after an introductory period. Do not treat an annually billed promotional price as a cancellable monthly contract.
Illustrative budget: $150/month in subscriptions plus $40/month in add-ons and $500 in setup is $2,780 in the first year before taxes and variable fees. This is arithmetic, not a vendor quote. Internal training time and migration work need their own budget.
AI capability is task-specific
Official Jobber AI documentation describes assistance with quoting, workflows and customer communication. That makes the previous draft's blanket verdict that competitors offer only a chat assistant untenable. A product page still does not establish actual adoption across the industry.
Ask a vendor to demonstrate a task with realistic exceptions: ambiguous job scope, missing information, an unavailable technician or a duplicate request. Observe the proposed output, required human approval, retained history and recovery path. A recommendation, an approved draft and an automatically executed action carry different responsibilities.
SnapJobAI's dispatch suggestions use skills and open workload for office review. Configured AI can draft editable invoice items from text and an optional photo. This does not establish learned pricing, certification-aware automatic dispatch or end-to-end autonomous operations. See dispatch suggestions and AI invoice drafts.
Small teams and larger operations
Team size alone is a weak software-selection rule. Check the number of locations, permission boundaries, accounting connections, service windows, crew structure and data migration requirements. Demonstrate critical work on each device type, and test how an interrupted request recovers before committing to a rollout.
SnapJobAI publishes plan limits, but accounting synchronization, full historical import, inventory and multi-person crews remain unfinished. Native distribution and provider connections need verification. The ten-platform guide is a sourced starting point for comparison, not a scored product trial.
Source note
SnapJobAI publishes this article and sells software in the category. No evidence was retained for the earlier draft's claimed twelve-vendor trial audit; those findings are withdrawn. The financial example, current plan links and clearly labeled calculations replace that unsupported market narrative.
Related reading
Frequently asked questions
Is vendor revenue the same as annual recurring revenue?
No. Check what each measure includes. Annual revenue can include usage and professional services; it should not be relabeled recurring subscriptions or US-only field-service revenue.
How large is the field-service software market?
The sources reviewed here do not establish a comparable whole-market total. A defensible estimate needs a defined product scope, geography, period and treatment of services and usage fees.
Can a vendor list establish AI adoption?
No. Feature availability is different from measured use. Adoption requires a defined user population, task and observation period.