Motive
Each of these is a real decision Motive is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Motive provides a B2B software-and-hardware platform for managing physical operations, primarily commercial vehicle fleets, combining telematics, AI cameras, compliance, maintenance, and spend management. It serves businesses from small fleets to large enterprises in trucking, logistics, construction, energy, field services, and the public sector. SMB customers make up the majority of its customer base and are its largest revenue stream. The Motive platform spans SaaS, Mobile, and Embedded/IoT products. Motive runs cloud infrastructure, services, APIs and data platforms behind Fleet Management, Driver Safety, Spend Management, Workforce Management and AI Vision, plus a connected device fleet. Its backend services process telemetry from hundreds of thousands of IoT devices, including sensors, beacons, and asset gateways. Its Financial Products team operates a commercial lending and spend management program, Motive Card, built on partnerships with issuing banks and card networks. Its engineering organization supports Golang, Ruby on Rails, and Python services, plus Kotlin and C for Mobile and Embedded products.
Your first one is free. No card.
24 live right now.
The rest
Investigate equipment departures when device signals disagree
Fleet managers cannot quickly tell whether a machine moved unexpectedly or whether the available device signals are incomplete. You have to weigh a useful recovery workflow against claims the hardware cannot support.
Choose the gateway build while refrigerated trailers vanish from the map
Location history goes silent on refrigerated trailer routes, then returns without a repair. You must weigh a carrier-approval deadline against evidence that still does not agree on the failure mechanism.
Protect battery life while beacon sightings stay reliable
Affected Asset Gateways are reaching low-battery status early while still reporting equipment locations. You must weigh a faster power-saving change against the visibility fleet managers expect from their Beacons.
Protect asset transfers while crews move equipment between sites
Fleet managers cannot reliably trace who reassigned a connected device when equipment changes hands. You must weigh faster asset handoffs against controls that keep device ownership trustworthy.
Secure FOTA recovery while field gateways keep coming back
Some asset gateways fail to return after updates, while others can accept a recovery image without verified identity. You must weigh uninterrupted field recovery against a firmware state that cannot be cheaply undone.
Close debug access before the next manufacturing build
A test unit accepts debug access after secure boot, putting device integrity at risk. You must weigh a fast firmware control against keeping FOTA validation on schedule.
Move a known failure in Tekton to engineer review under 10 minutes
Known Tekton failures are consuming release windows while engineers reconstruct the same evidence. You have to weigh faster recovery against keeping every production-changing step under human review.
Trace gateway resets without guessing at the physical cause
Recurring gateway resets interrupt tracking for fleet vehicles and leave engineers sorting conflicting evidence. You have to weigh a faster investigation path against the proof required before a hardware corrective action.
Build a connection module for 60 trucks before the supplier window ends
A 60-vehicle pilot must capture required emissions signals on at least 95% of installed vehicles. You must weigh broader vehicle coverage against a connection module installers can build, qualify, and service at rate.
Choose the Dashcam build before the supplier slot moves
AI Dashcams are resetting during shifts on rough-service vehicles, leaving fleet managers without some safety footage. You must weigh a physical change that protects uptime against the evidence and production time needed to trust it.
Recover engine hours while tracking still works
Engine-hours updates freeze after accessory installs while vehicle tracking continues. You must weigh a fast connection change against repeatable coverage across wiring variants.
Surface equipment dwell before missed maintenance becomes expensive
Fleet managers currently discover prolonged equipment dwell after missed maintenance work, not when it first becomes actionable. You must weigh broad coverage against a first signal people trust enough to act on.
Choose the history cutover while equipment logs disagree
False trips appear in 4.8% of stationary equipment records, but some field evidence suggests the disputed signal is real. You must weigh audit-ready corrections against losing valid movement history for off-highway equipment.
Fix late-event handling in Flink so duplicate alerts drop below 0.5%
Duplicate geofence alerts reached 7.0% after a stream-processing deployment. You must weigh a fast event-time correction against an Embedded payload change that affects device data contracts.
Set expiry for temporary access without slowing urgent handoffs
Broad operational roles remain active after maintenance and compliance handoffs end. You have to weigh fast delegation against controls customers can actually use under pressure.
Decide whether to rotate a shared credential before card processing
A red-team exercise reached a production workload through a compromised corporate session, and you have to decide whether to rotate a shared credential before card processing. Closing the path now could interrupt driver fuel authorizations, while waiting leaves the exposure open.
Cut 18,000 hourly alerts in six hours, but keep telemetry flowing
Denied telemetry calls jumped to 18,000 an hour after one deployment. You have to weigh tighter access against uninterrupted vehicle records.
Choose guidance or a cohort programme while evidence stays thin
Early customers open maintenance views but do not return for a weekly operating review. You must weigh a repeatable cohort programme against the different maintenance routines each fleet needs to protect.
Decide card cutover while vehicle assignments still misroute purchases
Eleven percent of 300 tested driver-vehicle swaps assigned purchases to the wrong vehicle. You must weigh month-end spend-control savings against the proof required before 900 drivers receive cards.
Activate stalled vehicles without resetting every installed gateway
Forty-four of 120 installed vehicles still lack usable tracking records after seven days. You must weigh a fast targeted activation plan against a broader reset that consumes the remaining implementation window.
Provision test environments for Maintenance without permanent capacity
Telemetry-dependent Maintenance changes wait on shared integration capacity and reach validation later than other releases. You have to weigh a narrow pilot that ships quickly against a reusable path that avoids one-off environments.
Hold the Dashcam rollout until firmware and cloud config match
A growing set of Dashcams shows cloud configuration that may not match installed firmware. You have to weigh a durable release gate against a manual pin that protects the immediate rollout.
Stabilize Go checks while this week’s releases wait
Pull-request checks pass only 86% of the time, and reruns have pushed median duration to 18 minutes. You have to weigh a quick rollback against a fallback path that protects future build speed.