Why this memo.
FieldEdge is the second-most-common FSM in mid-market home services after ServiceTitan, and the most common in older PE-backed platforms that grew before ServiceTitan ate the segment. The platform that has 18 technicians on FieldEdge and 12 on ServiceTitan after acquiring two companies last year is a real and frequent shape. This memo addresses that shape.
The integration architecture: AI on FieldEdge that mirrors the AI on ServiceTitan, with consolidated dispatch logic that operates across both. Below: the workflows, the FieldEdge surface area, and the migration question.
The FieldEdge surface area we touch.
FieldEdge exposes a REST API with coverage of customers, work orders, dispatch, invoicing, and technician records. OAuth2 authentication. Webhooks for work-order state changes. Lower throughput limits than ServiceTitan's API, manageable for single-platform deployments.
For a platform straddling FieldEdge and ServiceTitan, we build a normalization layer that abstracts both into a common schema for the AI to read and write against. The AI sees a unified platform; the underlying FSMs stay separate.
Workflow I: 24/7 AI receptionist into FieldEdge dispatch.
Same workflow as the ServiceTitan version, adapted to FieldEdge's work-order model. AI answers, qualifies, books, writes the work order into FieldEdge. Logs to the right CSR group, the right customer record, the right service area. Morning dispatcher sees the night's calls as work orders ready to schedule.
Workflow II: Cross-FSM dispatch normalization.
The unique-to-FieldEdge workflow. Most platforms running mixed stacks lose 12-18% of dispatch optimization potential because the dispatcher cannot see across both FSMs at once. The custom AI normalizes work-order state, technician availability, and route geography across FieldEdge + ServiceTitan, surfaces the cross-FSM-optimal routing recommendations.
Recovery: 12-22% lift in revenue per technician day across the platform.
Workflow III: Technician priming and membership conversion.
Same as ServiceTitan version. AI reads customer + work-order history from FieldEdge, drafts the prime, pushes to technician mobile during truck-roll. Recovery: 4-9% recurring revenue uplift.
The migration question.
Most platforms eventually consolidate onto one FSM. The right answer for mid-market PE-backed platforms is usually ServiceTitan, but the migration timeline is 12-18 months and the bridge period is where capacity leaks.
The honest answer for a platform that's already on FieldEdge: don't migrate during a build. Run the custom AI on FieldEdge. When the platform decides to migrate, the AI integration is portable; we re-wire it to ServiceTitan as part of the migration. Migration without AI is what most platforms do; migration with AI in place is what compounds.