Voice scribe for repair technicians · Built for Tekmetric shops

Hands on the car.
Notes on the RO.

Your techs find things all day that never make it onto the repair order — because writing them down means stopping, degreasing, and walking to a screen. LugnutAI listens instead. A tech says what they found, confirms it at a glance, and the front desk approves it onto the right RO. Nothing is ever written without two humans signing off.

THROUGH THE LENS — BAY 3

RO 4521 2019 SILVERADO 1500 84,212 MI SESSION
CONCERN Customer reports brake noise, front end
JOB 01 Brake inspection — in progress
NOTE Front pads 2 mm, rotors lipped ✓ ON RO
ADD NOTE · RO 4521
Front pads 2 mm, rotors lipped — confirm?
✓ ConfirmCancel
CONFIRM BY NEURAL BAND GESTURE — OR JUST SAY IT
TECH · MIC

AT THE FRONT DESK — LIVE

LUGNUTAI — ADVISOR REVIEW QUEUE LIVE
RO 4498Oil change done, filter replacedAPPROVED
RO 4512📸 CV boot, outer — tornAPPROVED
RO 4521 “Front pads 2 mm, rotors lipped” PENDING
→ writing to Tekmetric RO 4521 … verified ✓
A approve · R reject · open RO

How it works

Three steps. Two sign-offs. Zero typing.

The whole interaction happens at the car, in seconds, over whatever the tech already wears — a Bluetooth headset today, Meta's display glasses next.

01 · AT THE CAR

Say it

The tech speaks a finding, a status, or a lookup — hands still on the vehicle, phone still in the pocket.

“What's on my board?” · “Open RO 4521” · “Take a photo of the rotor” · “Add a note…”
02 · IN THE LENS

Confirm it

LugnutAI reads back exactly what it heard — a seven-word card in the glasses, or spoken aloud on a headset. The tech confirms with a gesture or a word. If anything is unclear, it asks. It never guesses.

03 · AT THE DESK

Advisor approves

Every note and photo lands in a live review queue at the front desk. One keystroke approves it onto the repair order — with a full audit trail of who said what, and when.

The line we don't cross

A scribe. Never a diagnostician.

Plenty of tools want AI to tell your techs what's wrong with the car. LugnutAI is built on the opposite conviction: the diagnosis belongs to the technician. The software's only job is making sure their findings actually get written down.

Never diagnoses

No repair suggestions, no “it might be the…”, no AI opinions about the car — in any version, ever. The note is the technician's own words, with the speech-to-text noise cleaned out.

Never guesses

Two trucks on the board and the tech said “the Silverado”? LugnutAI asks which one — or flags it for the advisor. Ambiguity is resolved by a person, never by a coin flip.

Never writes unreviewed

Nothing reaches the repair order without the tech confirming what was heard and the advisor approving it. Both sign-offs are logged.

Why it matters: a system that “suggests repairs” puts your shop's name on an algorithm's opinion. A scribe keeps the professional judgment — and the record of it — where your insurance and your customers expect it: with your people.

Integration

Made to sit on top of Tekmetric

LugnutAI is not another shop-management system — you already have one. It's the voice layer on top of it. Repair orders come from Tekmetric; approved notes and photos go back into Tekmetric, onto the right RO.

Shop floorvoice + photos
LugnutAIconfirm · review · approve
Tekmetricthe system of record
  • Read: the tech's board, ROs, vehicles, and statuses — answered by voice at the car.
  • Write: only advisor-approved notes and photos, attached to the exact RO.
  • Safely: every write is duplicate-proof (idempotent), verified by reading it back, and recorded in an append-only audit log.
  • Nothing replaced: estimates, invoicing, payments — that's Tekmetric's job, and it stays that way.
Tekmetric integration in development — currently demonstrated end-to-end against a sandbox adapter

Security

Built like it has to pass an audit — because it will

Shop data is business data. LugnutAI was engineered from the first commit to SOC 2-aligned practices, not retrofitted later.

Encrypted, per shop

Media and credentials are encrypted at rest with per-shop keys. Tekmetric credentials are never logged and never sent to any client.

Isolated at the database

Every shop's data is walled off with row-level security enforced by the database itself — not just the application — and tested on every build.

Audited, append-only

Every write, approval, rejection, and credential change is recorded with actor, timestamp, and before/after. The log can't be edited.

Voice data expires

Raw audio is auto-deleted on a retention schedule — with an automated test proving the deletion actually happens.

Hardware

Starts with a headset. Built for the glasses.

Working today

Any Bluetooth headset

Wake word or a press of the headset button, phone pocketed. The full say-confirm-approve loop runs on hardware techs already own.

In active development

Meta Ray-Ban Display

Built on Meta's Wearables Device Access Toolkit: the confirm card appears in the lens, the camera shoots what the tech is looking at, and the neural wristband confirms with a finger gesture. Silent, hands-free, glanceable.

Get in touch

See the three-minute demo

Live walkthrough of the full loop — voice at the car to approved note on the RO. Shop owners, service advisors, and integration partners welcome.

Goes straight to the founder. No mailing list, no spam.