Most independent shops are not short on cars. They are short on service advisor time. The phone rings while an advisor is walking a customer through a digital inspection, a tech is waiting on approval for a brake job, and the declined timing belt from March never gets a follow-up call. Each of those gaps costs a repair order, and nobody sees the total.
InTheory acts as your fractional AI and technology lead. We would start with one expensive recurring workflow, such as missed calls, estimate approvals or declined-work follow-up, measure how it runs today, and improve it inside the shop management system you already use where possible. Advisors still approve every price, every recommendation and every message that goes to a customer.
One or two advisors answer phones, check customers in, build estimates, call for approvals, order parts and cash people out. When the counter gets busy, calls go to voicemail and approval calls slip. Techs stand at the bay waiting, which shows up as lost billed hours and a weaker effective labor rate by Friday.
A good digital vehicle inspection is only useful if the estimate follows quickly. Looking up labor times, pricing parts across two or three suppliers and writing a clear explanation for the customer takes real time. The longer the gap between inspection and approval call, the lower the approval rate on recommended work.
Every shop has thousands of dollars of declined recommendations sitting in its system. Most of it never gets a second conversation. Reminder postcards or generic texts go out on mileage guesses, and the customer who was told their rear pads were at 3 mm hears nothing specific until something grinds.
Car count, average repair order, parts and labor gross profit, tech efficiency and comebacks all sit inside the shop software. Owners often pull them by hand once a month, if at all, so a slipping parts margin or a tech who is clocking far fewer hours than flagged goes unnoticed for weeks.
We fix one at a time, starting with the one that costs you most. Each page shows the steps, the tools, what stays human and what we would measure.
Let customers book drop-off and waiter appointments online or by text, balance the board by bay and tech capacity, and send reminders that cut no-shows without the advisor playing phone tag.
See the workflow →Answer overflow and after-hours calls, capture the vehicle, symptom and preferred time, and hand the advisor a clean note instead of a garbled voicemail, without quoting prices or diagnosing.
See the workflow →Turn tech findings and inspection photos into a draft estimate with labor times and parts pricing pre-filled, so the advisor reviews, adjusts and sends it while the car is still on the lift.
See the workflow →Ask for a review after a clean pickup, not after a comeback, and route unhappy customers to the owner first so problems are fixed before they show up on Google.
See the workflow →Bring back declined work and due maintenance with specific, timely reminders based on the actual inspection notes and mileage, and spot regulars who have quietly stopped coming in.
See the workflow →Sort the texts, emails and calls asking for status updates, warranty questions and price checks, draft replies for the advisor and flag anything that sounds like a safety concern or a comeback.
See the workflow →Follow up on fleet accounts, warranty claims and charge customers who pay on terms, so receivables do not age while the counter is busy with today's cars.
See the workflow →See car count, ARO, effective labor rate, parts and labor margin, tech productivity and approval rate each morning, without exporting reports and building a spreadsheet.
See the workflow →How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
We start with what you already pay for. New tools have to earn their place.
Shop data includes customer names, phone numbers, addresses, VINs, payment details and service history. Texting customers requires clear consent under the TCPA and carrier rules, and card data should stay inside a PCI-compliant payment processor rather than in notes or spreadsheets. Colorado's Motor Vehicle Repair Act sets expectations around written estimates and customer authorization, so automated messages must never change an approved price. We would review vendor terms and access settings with you, but this is not legal advice.
General information, not legal advice.
Defaults are illustrative for auto repair shops (additional approved repair orders per month). Change them to your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Probably not. Modern shop management systems already include texting, digital inspections, online booking and reporting that many shops only half use. A typical first step is to configure what you already pay for, clean up canned jobs and message templates, and only add a separate tool where there is a clear gap the shop software cannot cover.
No. An answering assistant should collect the vehicle, the symptom and the customer's availability, then hand that to an advisor. It can share hours, location and general process, but pricing, diagnosis and repair recommendations stay with your advisors and techs. We would write the script and the escalation rules with you before anything goes live.
It depends on where the shop leaks. For some it is missed calls during the morning rush. For others it is the time from inspection to estimate, or declined work that never gets a follow-up. We would look at your call logs, approval rates and declined-work totals in the first weeks before recommending anything.
We agree the measures before building anything. For a shop that might be answered call rate, time from inspection to estimate sent, approval rate on recommended work, no-show rate or declined work converted per month. We take a baseline from your shop software in the first 30 days and compare against it at day 90.
Usually not as a paid engagement. The work is designed for established shops with several techs, steady car count and a measurable bottleneck. A small shop may get most of the value from turning on features it already owns, and we would say that on the first call rather than sell a project.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.