The demo is the whole program with a made-up shop loaded. Your key turns it into your board.
Windows · version 1.0.5 “Njord” · no outside servers to wait on
Three questions your shop cannot answer today
You are running the floor on a whiteboard and a memory.
The estimate lives in CCC. The schedule lives on a wall. What actually happened lives in somebody’s head until Friday, and by then it is a guess with a number attached.
Unanswered
Who earned what hours this week?
Body, paint and mech hours are sitting in every estimate you have. Nobody credits them to a technician until somebody sits down with a highlighter, and that person is guessing about half of it.
Unanswered
When did that car actually hit paint?
Not what the whiteboard says now — what happened, and on what day. Without a record you are reconstructing last month from memory and old copies of a spreadsheet.
Unanswered
Is the board telling the truth right now?
A spreadsheet somebody exports each morning is a photograph of yesterday. Every hour after that, the board and the shop disagree, and only the shop is right.
What it does
It reads your estimates and watches your floor.
Point it at your CCC ONE EMS exports. It reads the newest estimate for every repair order, every time — so there is no sync step, and nothing can be out of date. Every stage change writes a timestamped event. Nothing is inferred later.
01Tow In
02Scheduled
03Teardown
04Waiting on Insurance
05Waiting on Parts
06Body
07Paint
08Reassembly
09Sublet
10Wash / Buff / QC
11Complete
The marked stages are the ones that pay hours. Sublet is deliberately not one of them — sending a car out is not painting it.
Overview. Every car in the shop, sitting in the column it is actually in — nine on the floor, one waiting for pickup. Read across in one glance, the way the whiteboard was supposed to work.
Paint integrations
The estimate says what the paint job is worth. Your mixing system knows what the liquid cost. Nothing joins those two numbers up today, which is exactly why the paint margin screen got pulled instead of shipped on a guess.
Coming soon
AI integrations
Reading a stack of estimates and telling you what is off in them is work a machine is good at. It is also the one addition that could break every promise on this page, so read the sheet below before you get excited.
Coming soon
Invoicing
The board already knows the RO, the vehicle, the hours, the parts and what the job is worth. Today you re-key all of it into something else to get paid. That is the gap.
Coming soon
Production Board
One card per repair order, collapsed to a strip you can read at a glance: RO, customer, vehicle, hours, stage, technician, checklist and parts progress. Open one for the detail. What you left open stays open.
The floor
A magnet board across the top of the Overview — not a tab you go to, the first thing you see. Columns are phases, one row per car, a token sitting in the column it is in: the thing shops ran on a whiteboard for fifty years. Position carries the meaning, so a greyscale printout still reads correctly.
Tech Hours
Labor hours credited by week and by technician. Half the body and mech hours at the booth, half at delivery, all paint hours to the painter — and every single credit traces back to a timestamped stage change you can go and look at.
Overview
The first screen. Revenue for the week against your goal, four numbers that matter, and a worst-first list of what needs attention — every row clicking straight through to the tab that fixes it.
Estimate reviewer
Every CCC estimate checked against your shop’s own written rules, not somebody else’s idea of best practice. The things you always catch on a Friday, caught on a Tuesday.
Backups that are checked
Daily, automatic, thirty kept. Every backup is opened, integrity-checked and row-compared against the live database before it counts — one that fails is thrown away rather than quietly kept. Restore renames what it replaces instead of deleting it.
Scheduler
Hours per week per technician, every booked job counted against them, and a straight answer when a week is over — before you promise it to somebody on the phone. A job too big for the week it lands in spills into the next one instead of pretending it fits.
Parts
Your own parts list, checked against every estimate, so a part already sitting on your shelf is caught before anybody orders a second one. One avoided bumper cover pays for the whole program.
Exports that print
The schedule as a spreadsheet, the schedule as a PDF, the completed-jobs log — written on demand. The spreadsheet is an output. It is never an input, so nothing you do in it can ever break the board.
The part nobody else will put in writing
Independence from the cloud
Your shop’s numbers belong to your shop.
Every other board on the market rents you access to your own production data and calls it a service. It lives on somebody else’s computer. It needs their permission to open. It can be repriced, redesigned, discontinued or taken away while you are standing in the booth, and there is no version of that story where you have a say in it.
Minuteman is the other thing. It is one program, on one computer, in your building.
It doesn’t depend on outside servers. Your board lives on your computer, not on somebody’s server, so you’re never stuck waiting on us.
There is no account and no login. Nothing to sign up for, no password to reset, and nothing about your work ever leaves the building. The only thing that calls home is a once-a-week check that your key is still your key, and if it cannot get through, the board carries on.
Your data lives in one folder, and an upgrade never touches it. The program gets replaced. Your jobs, ticks, notes and hours stay exactly where they were.
No telemetry. The program never reports anything about your shop — not your jobs, not your cars, not your people. The only thing it ever sends is a weekly check that your key is still your key. Nobody watches your shop but you.
You buy it once. There is no monthly bill and no renewal date. The copy you install keeps working whether or not anything else ever ships.
One program · one computer · one shop
Two tiers, one program
All of it for one payment. Not a subscription.
Same download either way. A fresh install is Enlisted. Officer is a key you paste into Settings — and if that key is ever lost, damaged or missing, the program quietly drops back to Enlisted.
A front bumper for a 2021–23 F-150 lists north of nine hundred dollars. A grille for a Sierra runs six to eight hundred. Find one of those on your own shelf, once, and the program has paid for itself and every year after it.
Enlisted
Everything that is built.
— one time
All six tabs — Overview, Production Board, Scheduler, Parts, Tech Hours, Settings
Reads your CCC ONE EMS exports, live
Scheduler — five weeks of capacity, per technician, per week
Parts — your shelf, checked against every estimate before anybody orders
When it exists, it is a key for the installer you already have
Flip it and the whole page is set again for that rank.
Say hello
Come say hello.
Built from experience, for the people doing the work. Want to watch it run on your own numbers, or got a question about your setup? We would like to hear from you.
Shirts, a hoodie, a hat and a sticker, printed to order and shipped from the United States. Every one carries the same clock that sits in the corner of the board.
