operate.
we run the department for you: your channels, our team and agents, humans directing and approving every piece before it goes out.
you own: the work · files, rights
case · 04aug 2026 in production
Operating System.The workshop.
a turbo arrives on a pallet with no paperwork and a phone number. nine stages later it leaves with a warranty, an invoice, and a customer who already knew it was ready. everything in between is the system we built.
chapter · 01
The Bench.
a turbocharger arrives on a pallet. no vehicle, no owner present, no paperwork. a number stamped on the housing, a phone number on the box.
four questions follow it around the shop: where is it, what does it need, what does it cost, who do we call. those answers lived on a whiteboard, in a notebook, and in the owner’s head.
a shop run that way does not fail loudly. it leaks. a unit waits because the one person who knew is off today. the same customer phones three times. a job is collected before anyone writes the invoice. none of it is a crisis, and the owner is the only one who can see it.
ONE TURBO · PALLET TO CUSTOMER9 STAGES · ONE BOARD
- INTAKEa number, a phonearrives with no paperwork
- BENCHnine stagesevery move, operator, minute
- STOCKparts off the shelfpurchase · shelf · order · loan
- PAPERSsix documentsnumbered in sequence
- CUSTOMERknows alreadya message, then a page to scan
NOTHING LEAVES THE SHOP WITHOUT PAPERS · JAN 2026
fig. 01 · one turbo, from the pallet to the customer
chapter · 02
What We Built.
an operating system for the whole shop, not a tool bolted to one corner of it. the job board and its nine stages. a bench kiosk the floor signs into with a PIN. the client book. turbo and parts stock, with purchasing, batch ordering, and loan units tracked out and back. six document types. customer messaging. a public status page. an audit trail under all of it and nightly backups under that.
we started at the bench, not at a spec, and kept the words the floor already used: intake, washing, inspection, machining, assembly, balancing, test, ready. nine stages, in an order nobody had written down because everybody knew it. the screens here are translated. the real thing speaks the shop’s own language, which is why it needed almost no training.
ONE SYSTEM · THREE AUDIENCESONE RECORD
- THE FLOORbench kiosk, job boardnine stages, blocking, rework
- THE OFFICEclients, stock, orderingloans, documents, history
- THE CUSTOMERmessage and a status pageplus the warranty that outlives the job
EVERY LANE WRITES TO THE SAME JOB RECORD
fig. 02 · what we built, and who touches it
chapter · 03
The Floor.
every unit is a card, grouped by the day it arrived, carrying the number, the vehicle, the client, the stage, and the price. one screen answers the question the whole shop keeps asking.
a mechanic moves a job in two taps at a bench terminal. each action writes a line: which stage, which operator, what minute. rework is recorded, not hidden. a job waiting on a part turns amber and says why from across the room.
all nine of the shop’s operators log through it. that is the number that matters, because a tracking system half the floor ignores is worse than no system at all.
the board · every unit in the shop, grouped by the day it arrived
the kiosk the floor taps · the record it leaves behind
chapter · 04
The Shelf.
a turbo shop is an inventory business in a workshop’s clothes. cartridges, actuators, gasket sets, housings, each carrying competing supplier numbers for the same physical thing. margin is made or lost on knowing what is on the shelf.
a part is bought, lands on a numbered shelf, and is consumed against a named repair. orders go to suppliers in batches. units loaned out while a customer waits are tracked and chased back. 2,472 part records, 2,427 logged movements, every one tied to a job.
and because consumption is always tied to a repair, the system learns which parts fit which turbo numbers by itself. 1,975 fitments so far, none of them typed in by hand. that catalogue is the most valuable thing in the database, and nobody set out to build it.
the shelf · two suppliers, one physical part, one record
chapter · 05
The Customer.
the question that ate the most hours was the cheapest one to answer: is it ready. so the shop stopped waiting to be asked.
a message goes to the customer’s phone when a unit arrives and again when it is ready, threaded to the client so a reply lands on the job instead of in someone’s personal inbox. every unit also carries a printed label. scanning it opens one page showing the stage and nothing else: no prices, no notes, no other customer’s work.
it turned a cost into a channel. the shop now reaches its customers directly, on the phone in their pocket, without buying the attention. 76% of the work now comes from customers who have been before, and one has sent 109 units through the door.
THE CUSTOMER CHANNELNOBODY PHONES
- SHOPunit receivedlogged at the bench
- MESSAGEstraight to their phonethreaded, so replies come back to the job
- ANY HOURscans the labelthe status page answers instead of the shop
- READYa message, then collection221 sent, 22 replied
THE STATUS PAGE ANSWERS IT INSTEAD OF THE SHOP
fig. 03 · the question that used to cost the most, answered without anyone picking up
the thread on their phone · the page behind the label
chapter · 06
The Paperwork.
six document types come out of the job: service sheet, invoice, cash receipt, delivery note, quote, warranty certificate. each numbered in sequence the moment it is issued, carrying the shop’s details and a code linking the paper back to the repair. a number that skips or repeats becomes somebody else’s problem months later, in an office, with penalties attached.
the description on the service sheet is written by an AI reading the job’s own log trail, so the customer gets a plain account of what happened to their turbo instead of a line item. it is fed the stages and the dates and nothing else. operator names and internal notes were deliberately cut out of that prompt after they surfaced on a document headed for a customer.
issued from the job · numbered in sequence, never by hand
the same job, todayfig. 02 · then → now
the usual way
hire for it, and wait.
software this specific normally means a salary line, a spec document nobody reads twice, and two quarters before anything runs on the floor. most shops never start.
hire.humanspec.doc
this build this
one operator, directing agents.
the process came out of the owner's head in conversation. agents wrote against it, one person directed, corrected, and approved every change, and the floor used it while it was still being built.
build.agentluka.human
the shop was using it before it was finished.
chapter · 07
What It Runs.
measured against the live database on 31 august 2026, over the last 90 days of trading. there is no before: the shop kept no records a system could read, so none of this is an improvement claim. it is what the business runs at now. no revenue figures, at the client's request.
3in 4jobs come from returning customers
27.5hmedian from intake to ready
1,975part fitments the system taught itself
they come backshare of all work from customers who had been before, 42% of clients returning76%
the best oneunits sent through the door by a single client since the record began109
turnaroundmedian hours from a unit landing on the pallet to being ready to collect27.5 h
the long tailrepairs finished inside 72 hours, with 39% done inside 244 in 5
qualitywarranty claims across 3,071 jobs, each one traceable to its original repair46
the flooroperators logging their own actions at the bench kiosk, out of nine on the books9 of 9
the shelfpart records across 2,427 logged movements, every one tied to a named repair2,472
what it learnedpart-to-turbo fitments recorded as a byproduct of the bench working1,975
paperworkservice sheets issued from the job, numbered in sequence, never handwritten784
the channelmessages to customers' own phones, with 22 replies threaded back to the job221
self-servicea scannable label on every unit, opening one page that shows the stage and nothing elseno calls
one systemfloor, office and customer writing to the same job record, on one login8 months
chapter · 08
Honestly.
there is no before. the shop kept no records a system could read, so nothing here is an improvement claim. these are the numbers the business runs at now.
and this is one shop’s system, not a product. the stages, the documents and the suppliers belong to that shop. we looked hard at selling it to every turbo shop in europe and decided against it, which is a different story than this one.
chapter · 09
Next.
the method points at any operation where the process is real, repeated, and currently held in somebody’s head. the trade changes. the shape of the work does not.
from this build to yours
we built one for a bench. now yours.
the same agent system that built this one reads your business and reports which parts of it still run on somebody's memory. the opportunities, named.
build.
we wire the system into your company, train your team, and hand you the keys. agents, prompts, gates, infrastructure: yours.
you own: the system · agents, prompts, training data, infrastructure