Perifleet Rule: Adopt Only When the Client's Liability Window Exceeds 90 Days
Should our agency resell Perifleet to a given fleet client, and which tier do we put them on? Only sell Perifleet where the client's claims horizon outlasts their camera vendor's retention, and default them to Plus at $15/mo so the 1-year Azure ZRS archive covers the gap.
By InnovaAI ResearchPublished
“Should our agency resell Perifleet to a given fleet client, and which tier do we put them on?”
Only sell Perifleet where the client's claims horizon outlasts their camera vendor's retention, and default them to Plus at $15/mo so the 1-year Azure ZRS archive covers the gap.
Agencies default clients to the $12 Standard tier because it looks cheapest, then discover 90-day retention deletes exactly the clips the client needs when a claim lands eight months later, forcing a mid-contract upgrade and undermining the liability promise the retainer was sold on.
Perifleet's entire value rests on retention: Standard caps at 90 days, Plus extends to a 1-year Azure ZRS incident archive, and Premium reaches 2 years, which is the only tier that matches the 6 to 18 month lag before insurance claims arrive. Because it installs as a native MyGeotab add-in, there is no separate portal to train fleet managers on, so the delivery effort concentrates in storage provisioning and camera adapter work rather than user adoption. The Claude-powered assistant and custom report builder sit at Plus and above, which is where a managed safety retainer becomes defensible.
- •The client already runs MyGeotab and has at least one AI dashcam vendor whose clips currently expire in 30 to 90 days
- •The fleet carries commercial liability exposure where insurance claims typically surface 6 to 18 months after an incident
- •Vehicle count and incident volume justify a $12 to $18 per-vehicle monthly line item on top of the existing Geotab subscription
- •The client wants driver coaching and safety scoring delivered as an ongoing service rather than a one-off install
- •Your agency can absorb 12 hours of setup work to provision Azure Blob or AWS S3 storage and validate incident triggers per client
More on Perifleet
- StrategyWhy Perifleet Turns Fleet Video Retention Into Agency Retainer Revenue
- ConceptPerifleet Retention Window Math
- Decision FrameworkPerifleet: Buy vs Skip (Geotab Fleets With Long-Tail Liability Exposure)
- Failure PatternThe Perifleet Retention Illusion Trap: When Agencies Sell 2-Year Archives That Never Get Written
- Implementation BlueprintPerifleet Fleet Safety Retainer Build (7-10 days)
- Operating ProcedurePerifleet Incident Clip Retention Setup (Onboarding)