Field service management platform
A contractor runs insurance work and retail work in one place — job orchestration, dispatch, partner referrals, telephony, notifications, and a field app that keeps working without signal.
The problem
Contractors serving both insurance programs and retail customers are running two businesses inside one company: different intake, different approvals, different paperwork, different people chasing them. Most hold it together with two systems and a spreadsheet in between.
My role
Product leadership across the platform, then principal engineer on it — including the mobile field experience end to end.
Decisions worth defending
- One job model spanning insurance and retail rather than a product per channel, so a contractor works one queue instead of reconciling two.
- A native shell for the field rather than a web app, so capture keeps working when the connection does not — with one-handed operation as a hard constraint, because technicians work in gloves with one hand free.
- Communications built as platform infrastructure rather than a feature: browser telephony, SMS, and transactional email on a shared outbound layer with per-tenant template scoping.
Where it stands
Operating platform serving contractors across insurance programs and retail work.
A note on what is shown
Shown unbranded, with synthetic data. No client marks, client data, or client-specific workflow terminology appear anywhere in this demo.