Pilot qualifier

ServiceTitan-ready audit checklist

Score whether a contractor is ready for a manual ServiceTitan-ready pilot before API access exists. The output becomes the first discovery artifact for the Titan Map, campaign pages, and launch packet.

58
of 114
Manual-first
readiness
Launch
package

access

needs-review

Customer can provide a ServiceTitan admin or operations owner for review calls.

Manual Titan Map work needs someone who understands job types, business units, campaigns, zones, and booking rules.

Job types, business units, and service areas can be exported or reviewed manually.

The first offline map can be built from screenshots, CSVs, or a guided review before API access exists.

website

ready

Current website pages, CTAs, forms, and phone paths are known.

PageToJob needs a baseline inventory before it can identify drift or missing campaign pages.

Priority services and cities or ZIPs are known.

Campaign and service-area pages need a defined market/service matrix.

booking

blocked

Booking path is known: Scheduling Pro, phone-first, or PageToJob request form.

Every page needs a safe conversion path even before live ServiceTitan booking sync exists.

After-hours and emergency routing rules are known.

Capacity-aware CTAs depend on when to route visitors to phone, request form, scheduler, or manual review.

campaigns

blocked

Active campaigns, lead sources, UTMs, or call tracking numbers are known.

Campaign pages need source binding before they can support revenue attribution later.

Membership, maintenance, or recurring-service offers are documented.

Repeat-customer and tune-up pages are a differentiated ServiceTitan-ready wedge.

operations

blocked

Capacity constraints by trade, service area, or season are known.

The website should avoid creating demand the contractor cannot fulfill.

Inactive, paused, or low-priority services are known.

This powers the first drift monitor findings without API access.

proof

needs-review

Recent lead, booking, job, or revenue outcomes can be reviewed manually.

A proof packet can start with manually reviewed outcome data and later move to API-backed attribution.

A launch approver is named for page copy, offers, booking rules, and disclaimers.

The manual product needs a clear sign-off owner before publishing operationally sensitive pages.

Strengths

  • - Customer can provide a ServiceTitan admin or operations owner for review calls.
  • - Current website pages, CTAs, forms, and phone paths are known.
  • - Priority services and cities or ZIPs are known.
  • - A launch approver is named for page copy, offers, booking rules, and disclaimers.

Discovery gaps

  • - After-hours and emergency routing rules are known.
  • - Membership, maintenance, or recurring-service offers are documented.
  • - Inactive, paused, or low-priority services are known.
  • - Recent lead, booking, job, or revenue outcomes can be reviewed manually.