Analytics

Your shop’s own data, paired with the network’s.

Every repair order, line item, technician, and customer interaction your shop produces is a signal. CSA structures those signals into patterns you can read — what closes at what price, which jobs come back, which parts fit which makes — and compares them to the rest of the network.

Request alpha access →
001 — What gets measured

Categorized as it happens.

Every line item is auto-categorized by what was actually done, not by the words on the invoice. Search by intent, group by category, compare across the network.

Auto-categorize

Brake jobs land in brakes. Cooling repairs land in cooling. Diagnostics are diagnostics, not "shop supplies." Closed ROs are reclassified as the system learns.

Fitment confidence

Every labor item carries a fit-to-vehicle percentage drawn from your shop’s history and the network’s. Verified means another shop has done it on this exact make.

Often done with

Pair-this-with-that suggestions derived from co-occurrence in real ROs — not a vendor’s template, not someone’s opinion.

002 — Comeback rate

The one number every shop quietly tracks.

A customer returning within 30 days for a related issue is one of the clearest signals of work quality. CSA computes comeback rate per category, per technician, per make — and surfaces the repeat lines so you can act on them.

Per-category, per-tech

Brake work, cooling, suspension, electrical — with each technician’s rate relative to the shop and the network. Coaching signal, not a scoreboard.

The repeat lines

Top recurring failure patterns surfaced as a list, with the vehicles and miles between visits. Catch a parts-quality drift or a procedural gap before it spreads.

003 — Ask Otto about the shop

Whole-shop questions. Table answers.

From the side panel, ask in plain words. Otto reads your data, draws on the network where it helps, and answers in a table or a short summary — with the rows he’s referencing.

"What’s my comeback rate this month, and which jobs are showing up twice?"
Comebacks ran 4.1% on closed ROs (84 / 2,061). Top repeat lines: front brake noise (n=11, mostly 2018+ Subaru), check-engine after fluid service (n=6), pulse on braking (n=5).
"Pull every 2018+ Subaru that came in for head-gasket symptoms in the last 90 days."
14 ROs match. 9 closed with HG repair, 4 declined and rebooked, 1 in WIP. Pre-paired the typical job and parts on the open one.
"Which RO has been sitting in ‘awaiting parts’ the longest?"
RO 38240 — 11 days. Vendor ETA slipped twice. Suggested action: re-quote with secondary supplier or call the customer with a ready-by update.
"Which technician is closing brake jobs the fastest on European makes this quarter?"
Diego — 17 closed, median 1.84h (book 2.10h). Next: Marcus, 12 closed, median 2.05h. Both running ahead of book.
004 — Where this fits

The same data, three places.

In the workflow

Open a job: the labor (your shop’s average), the parts (your usual), the tech with availability are already on the page.

In the side panel

Ask Otto a whole-shop question. He answers with a table, the rows he’s referencing, and the action you can take next.

In the reports

Comeback rate, margin by category, technician throughput — the numbers the manager already tracks, sourced from the same model.

Built on the work your shop already does.

Private alpha, in production. Partner-reviewer slots open in waves.

Request alpha access →