Company

We build the decision layer fleet operations was missing.

Enterprise fleets already run telematics, maintenance systems and supplier relationships. What they lack is a layer that reads those signals together, states what is failing and how confident it is, and turns that into an action their existing systems execute — with the evidence retained for audit.

Legal entity
Routiq LLC
Category
Fleet decision infrastructure
Deployment
Cloud, no hardware
Systems of record
Remain the customer's

Why we exist

Fleet data has never been the constraint. Deciding on it has.

Three structural problems show up in every fleet we assess, regardless of size or telematics provider.

  1. A fault code is a record of a failure, not a warning about one

    By the time a lamp is on, the component has already degraded. The decision available at that point is where to tow it, not when to schedule it.

    Our position

    Rooutiq scores degradation from the signals that precede the code, so the work can be planned into an existing service window.

  2. The evidence is spread across systems that do not talk to each other

    Telematics holds the signal, the CMMS holds the history, procurement holds the part. No single system can state whether a repair is justified.

    Our position

    Rooutiq resolves all of them to one vehicle identity and fuses the evidence, so a decision is made against the whole record rather than one feed.

  3. Unplanned repairs are priced by urgency, not by parts

    The component costs the same on a Tuesday as it does on a Friday night. Labour, towing, expedited freight and the lost load do not.

    Our position

    Moving a repair from unplanned to scheduled is the entire economic case, and it requires advance notice measured in days.

Leadership

The team behind Rooutiq

Two founders, accountable for the platform end to end.

Myles Williams

Co-Founder & COO

Myles built Rooutiq's product and operations infrastructure from the ground up. He owns every integration, customer onboarding and system that keeps the platform running in production.

LinkedIn

Aiden Brooks

Co-Founder & CEO

Aiden leads revenue and growth at Rooutiq. He has closed enterprise fleet accounts across multiple verticals and is responsible for every commercial relationship on the platform.

LinkedIn

Origin

We got tired of watching fleets lose money to failures their own data was already describing.

Rooutiq started from one observation: telematics platforms are powerful and almost universally underused. Operators were holding years of vehicle signal data that no system was converting into a decision.

We built the layer that was missing — not another dashboard and not another alert feed, but an engine that reads the signals a fleet already collects and states which component is degrading, how confident it is, and what to do about it.

We are deliberately a small team working directly with the fleets that run the platform. Every integration and every model change is decided against real operational outcomes rather than a roadmap written in advance.

How we operate

Commitments an enterprise can hold us to

These are the rules the platform is built on. Each one is either visible in the product or verifiable in our documentation.

Every prediction states its own reliability
A score is published with the evidence behind it — which independent signal groups fired, what was unavailable, and how confident the model is on its own scale. A confidence figure is a model output, not a measured accuracy rate, and we label it that way in the product.
Reasoning is inspectable, never a black box
When a component is flagged, the underlying signal history, fault record and contributing factors are shown. A maintenance director has to be able to defend the decision to a CFO without taking our word for it.
The customer's systems stay the systems of record
Rooutiq does not replace telematics, a CMMS or a procurement platform. It reads from them and writes decisions back into them, so removing us does not strand the operation.
Automation is opt-in and policy-gated
Automated purchasing is off by default, runs in shadow mode until a fleet enables it, and is bounded by per-transaction and daily ceilings the organization sets. It can be halted immediately without affecting predictions or alerting.
Operational data is not a product we sell
Vehicle and maintenance data belongs to the customer. We use aggregated, de-identified patterns to improve models. We do not sell, broker or monetize a fleet's operational data.
Where we are unproven, we say so
Model calibration requires verified repair outcomes, and coverage varies by signal and by provider. Both the product and our documentation distinguish what has been measured from what has not.

Security & governance

Controls, and what we do not yet claim

Rooutiq handles operational data and, where a fleet enables it, participates in purchasing decisions. Both warrant a direct answer on controls.

Tenant isolation
Every record is scoped to one workspace and enforced at the data layer, not in the interface.
Encryption
Data is encrypted in transit and at rest. Third-party credentials are encrypted with a dedicated key.
Access control
Role-based permissions with owner, admin and member separation, plus optional enforced MFA and directory sync.
Auditability
Decisions are written as immutable records carrying their inputs, the policy version in force and the actor.

Attestations

Rooutiq does not currently hold a SOC 2, ISO 27001 or third-party penetration-test report, and we will not claim one before an assessment exists. The controls above are engineering controls we implement and can walk through in technical diligence. If a formal attestation is a requirement for your organization, raise it with us early — we would rather tell you where we stand than have it surface late in a security review.

See how Rooutiq fits into your fleet architecture.

Connect your existing telematics and operational systems, evaluate the decision layer, and see how predictive maintenance moves from detection to execution.