ClearSync for fleets.

Onboarding is a four-step rollout coordinated with your fleet ops lead: (1) a 30-min discovery call to map your asset list, regions, and any existing telematics or dispatch platform, (2) a small pilot batch (typically 5–10 vehicles) installed at a single site, (3) a 4-week evaluation window with weekly check-ins, and (4) a phased rollout to the rest of the fleet on your schedule. There is no all-at-once contract requirement — most fleets start with a pilot batch and expand once they've validated ROI in their own routes.

No multi-year lock-in at the pilot stage. The pilot program runs month-to-month during evaluation, and the production program is structured as an annual agreement with a 30-day out for either side. If ClearSync doesn't meet the ROI bar you validated in your pilot batch, you can walk before the annual term converts. Volume pricing is locked for the term of the agreement.

We expose a documented REST API and a webhook stream for tint-state events; most major fleet platforms (Geotab, Samsara, Verizon Connect, Fleetio) can ingest those events through a standard middleware layer. For platforms without a native integration, we provide a Zapier-style connector and a CSV-on-demand export. During onboarding we map your existing data shape (vehicle ID, zone, timestamps) to the ClearSync event model in the discovery call so the integration is configured, not built from scratch.

Each installed vehicle receives a ClearSync control module (about the size of a deck of cards, mounted behind the dash) plus wiring to the tint elements. Compatible with standard OEM side and rear glazing on most sedans, SUVs, vans, and light trucks produced after 2015. Vehicles with aftermarket tint film, curved panoramic roofs, or laminated acoustic windshields are evaluated case-by-case — the discovery call confirms compatibility before any commitment.

Fleet customers get a dedicated account lead plus a 24/7 incident line for any vehicle that fails to enter a tint state — P1 hardware-failure response is 4 business hours, software/API incidents are 1 business hour, non-urgent questions are answered same-business-day. RMA replacements for failed control modules ship within 48 hours for fleets inside our continental-US install regions. SLAs are written into the annual agreement.

Tint-state events and vehicle metadata are stored in US-based PostgreSQL infrastructure (currently Neon). We do not transfer fleet data outside the United States, and we do not sell or share it with third parties. Public-sector and defense-adjacent fleets can opt into a GovCloud-isolated environment on request — discuss with your account lead during onboarding. Driver-identifying data is never collected unless you explicitly opt in for a specific feature.

Yes — the pilot program is explicitly designed this way. Most fleets start with a 5–10 vehicle evaluation batch, validate the ROI on their own routes over 4–6 weeks, then expand in waves. Pricing for the expanded fleet is recalculated against the new volume at that point; you do not lose your early-pilot pricing on the original batch.