Comparison
Holdfast vs ServiceTitan Pro

Outcome-priced vs per-seat / usage. Five axes that decide which one actually books the missed call.

ServiceTitan Pro is a paid add-on tier over ServiceTitan. Holdfast is an outcome-priced missed-call-recovery layer that writes to the same dispatch board. The comparison below grounds each axis in the same page it appears on elsewhere on this site.

Side by side

Five axes, side by side.

Pricing model, scheduling-integration breadth, after-hours coverage, missed-call-recovery focus, and execution risk — the five places where the two products diverge. Holdfast’s column leans on the pricing page, the audit-request scheduler dropdown, and the per-shop ROI math.

Pricing model

Holdfast

Outcome-priced, on the booking.

A small monthly retainer plus a per-booked-job bonus aligned to the invoice the booking actually generated. The bonus is never billed unless a confirmed slot lands on the tech’s calendar — same as the pricing worked example.

  • Bonus is invoiced one week in arrears, after you see the recovery
  • No booking, no bonus — the calendar drives the bill, not the meter
  • Retainer is refundable against the first booked invoice during pilot

ServiceTitan Pro

Per-seat / usage, billed by the seat.

ServiceTitan Pro is positioned as a paid add-on tier over ServiceTitan, priced per-seat and by usage tier. The meter follows the seat and the active add-on, not whether a recovered call actually landed a job on the schedule.

  • Flat per-seat line item regardless of recovered-call lifetime
  • Overages on add-on usage are billed even when a call doesn’t convert
  • ROI depends on seat count and tier usage, not on booked jobs
Scheduling-integration breadth

Holdfast

Three ecosystems, native writeback.

Recovered calls write directly to the dispatch board in ServiceTitan, Housecall Pro, OR Jobber — the three schedulers the audit-request dropdown confirms a shop runs. The tech sees one job alongside everything else they already manage.

  • Native writeback to ServiceTitan, Housecall Pro, and Jobber
  • Works for the Housecall Pro / Jobber shop too — not just ServiceTitan
  • No double-entry: jobs live in one system, not in a side notification

ServiceTitan Pro

A ServiceTitan add-on, inside one ecosystem.

ServiceTitan Pro is an add-on over the ServiceTitan CRM — useful shape for the shop that already runs ServiceTitan, but it doesn’t carry a Housecall Pro / Jobber shop. The integration is single-platform by definition.

  • Useful only where ServiceTitan is already the dispatch board
  • A Housecall Pro / Jobber shop is out of scope by design
  • Coverage is gated by CRM choice, not by the caller’s channel
After-hours coverage

Holdfast

24/7/365, included.

The voice agent covers off-hours calls every day of the year — weekends, holidays, one-tech-on-call nights. Coverage is included in the retainer; there is no after-hours meter and no separate add-on line item.

  • No separate after-hours add-on in the invoice
  • Holidays, weekends, and one-tech-on-call nights are all covered
  • SMS handoff routes back to the shop’s own follow-up workflow

ServiceTitan Pro

Mostly inside the in-app CSR queue.

ServiceTitan Pro augments the in-app CSR / dispatch workflow over ServiceTitan. Voice answering is limited and typically scoped to the same Pro tier; the after-hours coverage shape is whatever the shop already runs the dispatch board for.

  • Voice answering is a smaller surface than the in-app CSR queue
  • After-hours gaps stay where the shop’s on-call model leaves them
  • Coverage scope depends on which tier is active, not on a flat retainer
Missed-call-recovery focus

Holdfast

A missed-call-recovery layer.

Holdfast is built around the after-hours / overflow missed-call path — the calls that never reach the dispatch board. The product’s job is to land those calls on the calendar and surface them on the weekly ROI report as attributed revenue.

  • Voice agent + SMS handoff tuned for the missed-call path
  • Weekly ROI report ties recovered calls to invoice dollars
  • Same shape as the per-shop audit the pricing worked example walks through

ServiceTitan Pro

A broader Pro tier, not a recovery layer.

ServiceTitan Pro is shaped as a broader Pro-tier enhancement over the ServiceTitan CRM — reporting, automation, and add-on capacity — not as a missed-call-recovery product. The after-hours voice path is one surface within a wider Pro tier.

  • Recovery is a sub-feature, not the product’s reason for being
  • Reporting reads as a breadth-of-Pro view, not as attributed revenue
  • Missed-call metrics that exist are operational, not dollar-attributed
Execution risk

Holdfast

Risk shifts to Holdfast, on the booking.

The bonus bills against the calendar, not the meter. If a recovered call doesn’t land a confirmed slot on the same dispatch board the shop already runs, the bonus is never billed. Execution risk stays with Holdfast on every call.

  • Bonus bills one week in arrears, after the tech sees the recovery
  • A call that doesn’t book is a call Holdfast doesn’t get paid on
  • Risk ownership is on the same calendar the shop already pays for

ServiceTitan Pro

A flat fee, win or miss.

ServiceTitan Pro is paid per-seat / usage regardless of whether a missed-call leads to a booked job. The shop carries the conversion risk: the invoice is the same whether the recovered call turns into a slot or not.

  • Per-seat / usage line item is invoiced the same, win or miss
  • The shop carries the gap between seat and recovered call
  • Conversion is the shop’s problem; the meter is not on it

Proof framing

The fee follows the booking — not the seat or the meter.

The same per-shop math the pricing page walks through — calls recovered, jobs booked, invoice dollars attributed, Holdfast invoice, contractor’s net — applies here.

From /pricing
Effective fee, applied to recovery dollars.

The pricing worked example reads an effective fee as a small fraction of the revenue the booking actually generated — the contractor keeps over 90% of every dollar the recovery layer actually produced. On a per-seat / usage model, that same fraction depends on tier usage and seat count, not on whether a missed call landed a job on the calendar. That is the source of the gap this page is named for.

The 20-minute audit fills the same per-shop table for a real shop — ten recent recordings, last quarter’s ticket values, and confirmation the shop runs ServiceTitan, Housecall Pro, or Jobber.

Next step

See your own number on this sheet.

A 20-minute audit uses ten of your recent inbound calls and your last quarter’s ticket values to fill the same per-shop table for your shop — no install, no commitment.

Book an audit

What we need

  • Ten recent inbound recordings (or a calendar link)
  • Last quarter’s service-ticket value range
  • Confirmation you run ServiceTitan, Jobber, or Housecall Pro

FAQ

The CRM-AI objection.

The question every contractor-on-ServiceTitan asks before signing /pricing — answered in the same plain voice as /faq.

Why not just use my CRM’s AI?

See also
  • /pricing — the outcome-priced worked example and the per-shop ROI math.
  • /faq — ten contractor questions, including how missed-call bookings are written back to the dispatch board.

Sources & methodology

Where each claim comes from.

Holdfast claims on this page are sourced inline from in-repo pages: the outcome-priced model and worked example math on /pricing; the ServiceTitan / Housecall Pro / Jobber scheduler dropdown on /audit-request; the 24/7 voice coverage on /plumbing, /hvac, and /electrical; and the per-booked-job risk-shift framing surfaced across the dashboard shell.

ServiceTitan Pro claims on this page reflect publicly listed product positioning for a typical ServiceTitan Pro tier — per-seat / usage add-on shape, in-app CSR augmentation, and the broader Pro-tier framing — and are framed here as such, not as a verbatim reproduction of any specific ServiceTitan marketing copy. For an exact side-by-side against ServiceTitan Pro’s current offering, request the audit and ask for the Pro-specific comparison sheet.