Samsara
Each of these is a real decision Samsara is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Samsara provides an IoT platform combining hardware and software for fleet telematics, driver safety, asset and equipment tracking, and site security, serving fleet operators and physical operations teams across agriculture, construction, transportation, warehousing, field services, manufacturing, retail, and logistics. Its Telematics Business Unit is its oldest business line and the core of its revenue. Its hardware includes battery-powered wireless environmental sensors, Linux-based IoT gateways, and internet-connected dash cameras, with a dashboard and APIs for consuming the sensor data. It also offers the Agentic Shipment Center. The industries it serves represent more than 40% of global GDP. Over 2.3 million IoT devices are deployed to its global customers, with hundreds of thousands shipped yearly to fleets, construction sites, and depots worldwide. Its hardware is deployed across 98% of US roads, with 70+ billion miles driven annually. It processes 25+ trillion data points annually across thousands of connected devices and deploys models across more than 2M dashcams. Its AI has helped prevent accidents that would have harmed an estimated 380,000 people per year.
Your first one is free. No card.
16 live right now.
The rest
Protect responder access while panic-button rules raise the stakes
Safety managers lack a clear record of who accessed an active worker alert. You have to weigh responder speed against access accountability during an emergency.
Commit the firmware fix before offline devices take the release
A replayed authorization request may alter device behavior after a dead-zone reconnection. You have to weigh a permanent firmware decision against uninterrupted SOS delivery.
Close the location IDOR in alert requests without delaying live updates
An authenticated account can retrieve another worker's incident location by changing an identifier. You must weigh a strict authorization check against uninterrupted incident updates.
Decide what drivers can see on a route plan
A review found restricted address details in 19% of pilot route plans, and drivers lean on those notes to finish unfamiliar stops. You decide what gets hidden before the release locks it in.
Decide if the driver scorecard is ready to ship
The scorecard matches manual safety reviews only 78% of the time, and the gaps cluster in a few enterprise fleets. You have a signed launch date and a setup that is hard to undo once fleets adopt it.
Cut over driver-hours reporting on time
The regulatory date is fixed, and a small set of driver-hours records still doesn't match across surfaces. You have to decide what gets verified before the old reporting path is switched off for good.
Decide on the repair path for damaged hardware
A signed enterprise deal needs the repair pathway live in twelve weeks, and it only works with a multi-year vendor minimum and rerouted returns. You have to weigh cash exposure against a date you cannot miss.
Prove the video evidence was not altered
An audit found 3.1% of sampled severe-event packages carry no verifiable record of privileged access or changes, and the date is fixed. You have to decide how far the control reaches before customers start relying on it.
Set targeting before the bundle launches
Predicted bundle response looks strong, but audits show heavy overlap with existing safety demand and attribution that disagrees across channels. You set targeting, message order, and measurement guards before the assets lock.
Delete the location traces without breaking reports
The deletion cannot be undone, and some traces carry labels a machine assigned, with no clean link to the reports built on them. You have to prove what stays valid before the first record goes.
Decide when to warn about towing risk
Vehicles left too long in restricted zones keep getting impounded, but location accuracy and alert delivery vary across dense cities. You set the threshold knowing false alarms disrupt work and missed alerts lose vehicles.
Keep history in the right region
Contracts require some fleets' vehicle locations to stay in a new regional store, but the history service can still read across that boundary. You have to prove residency holds without leaving gaps in historical route views.
Set the risk threshold before launch
One threshold sends very different numbers of drivers into coaching in each region, and reviewers there agree less often. You have to balance fair treatment of drivers against enough coverage to improve coaching.
Fix the duty records before the cutover
For 11% of active drivers, the legacy logs and the vehicle data disagree on duty status, and the launch date is fixed. You have to weigh a cutover you cannot unwind against parallel work through peak season.
Settle the reseller deal before the conference
The platform sent exclusivity language two weeks out from its conference, and 146 direct prospects sit inside the proposed territory. You have to protect direct access and pricing while still meeting their launch date.