Pilot flow
A buyer-facing sequence for selling the manual product without database writes, ServiceTitan credentials, live API calls, or marketplace approval claims.
Start with the readiness auditIs the current website misaligned with ServiceTitan services, zones, campaigns, or booking path?
Decision: Continue only when the buyer wants a manual ServiceTitan-ready rebuild or review.
Exit criteria: Buyer agrees Launch, Growth, or Operations Monitor is worth scoping before API access exists.
Open artifactWhat does a ServiceTitan-ready website look like in practice?
Decision: Use the demo to make the product tangible before discussing implementation work.
Exit criteria: Buyer understands this is a public website layer, not a replacement for ServiceTitan.
Open artifactWhich job types, business units, zones, offers, memberships, and campaigns should the site reflect?
Decision: Confirm the first mapped services, first mapped areas, and booking path before pricing the pilot.
Exit criteria: Owner or operations reviewer accepts the first manual Titan Map scope.
Open artifactShould the customer start with Launch, Growth, or Operations Monitor?
Decision: Select a fixed pilot package that can be delivered without live ServiceTitan access.
Exit criteria: Buyer selects a pilot package and accepts the no-API boundary.
Open artifactWhat is included, what is excluded, and what does the customer need to provide?
Decision: Use the proposal packet to avoid accidental API, pricebook, or attribution promises.
Exit criteria: Pilot scope, artifact responsibilities, redaction rules, and review owners are accepted.
Open artifactWho approves the ServiceTitan context and which redacted artifacts can PageToJob use?
Decision: Gather only the manual inputs needed to build the Titan Map and site.
Exit criteria: Customer supplies approved, redacted, source-labeled inputs or agrees to screen-share notes.
Open artifactWho can approve future ServiceTitan access, and what is not needed during the pilot?
Decision: Record future access path without requesting credentials or live tenant authorization.
Exit criteria: Admin contact, module checks, and no-credential boundary are documented.
Open artifactWhat evidence proves the launch happened safely and what should happen after 30 days?
Decision: Review launch proof and decide whether to continue Growth, Operations Monitor, or API-readiness work.
Exit criteria: Launch packet is approved and next review date is assigned.
Open artifactDecide whether the fixed pilot is worth buying before API access exists.
Open lane artifactPick the first campaigns, offers, service areas, and source plan to map.
Open lane artifactConfirm the website will not promote stale services, unsupported zones, or wrong booking paths.
Open lane artifactConfirm modules and future authorization path without sending credentials.
Open lane artifactLaunch, Growth, and Operations Monitor must stand on website, Titan Map, drift, and proof deliverables before API access exists.
Do not request ServiceTitan passwords, app keys, client secrets, tokens, tenant secrets, or admin logins during manual onboarding.
Do not claim live sync, webhooks, marketplace approval, pricebook writes, or closed-loop revenue attribution until the evidence exists.
Customer-reviewed Titan Map and launch packet evidence must control public claims, campaign pages, and booking path changes.