Deep 01_
Forced Migration off Verizon Connect
Failure mode: Forced platform migration — international Verizon Connect customers moving to Geotab on a published window. Retraining and integration rework either way; the question is whether they accept the default or re-evaluate.
Trigger · Public evidence of Verizon Connect use; HQ or ops in UK, IE, IT, FR, PT, PL, NL, DE, or AU; ~50–500 vehicles; inside October 2025–April 2027 migration narrative (confirm dates against Geotab's public statements before citing).
Persona · VP Operations or Director of Fleet — owns the rebuild of dispatch integrations and driver workflow.
PVP · One-page side-by-side: current VC → post-migration Geotab vs current VC → Samsara (feature parity, timeline, hardware path, integration touchpoints). Useful even if they stay on Geotab — it's the evaluation work they'd do internally.
Example artifact
No named fleet PDF on this page — the deliverable is built per account from public specs and the prospect's footprint. Use the menu email + PVP spec above as the template.
{{first_name}}, {{company_name}} has roughly 18 months of Verizon Connect access before the Geotab handover lands fully — October 2025 to April 2027.
Most VC customers we talk to during this window run the same evaluation: stay on a platform you didn't choose, or take the migration window as a chance to re-evaluate. Samsara is ranked #1 on G2 for fleet management 5 quarters running — 84% user satisfaction vs. Geotab 76% (G2 public reviews).
I built a 1-page side-by-side comparing what {{company_name}}'s VC setup would look like on Samsara vs. what it'll look like on Geotab post-migration — feature parity, deployment timeline, your hardware path.
Want me to send it?