Proposal packet
A no-API proposal and statement-of-work packet for selling the first ServiceTitan-ready website pilot with clear scope, commercial terms, customer responsibilities, exclusions, and future API boundaries.
Example customer
Residential HVAC
The public website promotes stale services, has no explicit Titan Map, and cannot show how campaign pages connect to booking paths, zones, memberships, or proof reports.
A ServiceTitan-ready website, manual Titan Map, booking fallback, and launch packet.
60-day pilot minimum
Refresh the public site around approved services, service areas, campaign pages, booking CTA rules, and proof-ready tracking context.
Map pages, CTAs, forms, job types, business units, campaigns, zones, memberships, pricebook intent, and booking providers from customer-reviewed inputs.
Use PageToJob appointment request fallback, phone-first rules, or Scheduling Pro install support if the customer already has Scheduling Pro enabled.
Deliver mapped URL list, coverage score, drift baseline, booking path status, notification fallback status, and API boundary notes.
Campaign, service-area, membership, and offer pages with monthly manual drift review.
3-month minimum
Create pages with source/UTM plan, service-area intent, mapped campaign/service objects, and booking fallback.
Review customer-supplied updates for job types, campaigns, zones, offers, memberships, booking path, and page alignment.
Customer supplies redacted lead, booking, job, or revenue exports for proof reports until approved API access exists.
Ongoing Titan Map updates, capacity-aware CTA review, and drift findings.
3-month minimum after Launch or Growth
Update mapping decisions when services, zones, offers, campaigns, memberships, or booking rules change.
Review phone-first, request-form, emergency, service-area, and Scheduling Pro rules with operations.
Available only after customer authorization, approved app access, scopes, secure token storage, and sandbox validation.
PageToJob needs a ServiceTitan admin for future access review and a business owner for launch scope decisions.
Customer provides job types, business units, campaigns, zones, memberships, offers, booking path, and optional outcome exports using the intake packet redaction rules.
Customer confirms which services, zones, campaigns, offers, memberships, and booking paths should be promoted before launch.
The pilot does not store ServiceTitan credentials, call ServiceTitan APIs, process webhooks, or claim approved app status.
Public offer and service pages may reference customer-approved pricebook intent, but PageToJob does not write to ServiceTitan pricebook or accounting records.
Manual outcome summaries require customer-supplied exports and visible match-quality labels; API-backed attribution remains future scope.
Customer approves target services, service areas, first mapped pages, booking path, and pilot option.
Customer confirms screenshots and exports exclude credentials, customer records, invoice notes, payment details, and private dispatch data.
Operations or owner approves mappings, inactive object handling, booking path, and drift baseline.
Customer reviews leads, booked jobs or supplied outcomes, drift fixes, next-page opportunities, and API readiness path.
Launch starts as a fixed 60-day pilot. Growth and Operations Monitor require a 3-month minimum when selected.
Setup is due at kickoff. Monthly recurring fees begin at launch or when ongoing campaign/monitor work starts.
Additional markets, brands, complex campaign sets, custom integrations, or API-backed work require written scope approval.
Revenue Layer and API-backed automation may be described as future scope, but are not active deliverables until approval and sandbox validation are complete.