For tire, collision and auto repair shops

Keep your subscriptions. I build what they don’t do.

Your shop system writes the repair order, PartsTech finds the part and QuickBooks keeps the books. The work between them still lands on your counter: the tire quote that takes three phone calls, the supplement still waiting on the insurer, and the brake job a customer turned down in March. I build those pieces to fit beside what you already pay for.

Independent shops, from about 3 people up to about 40. Tire and collision shops first, and general repair is welcome too.

Sample app, invented data · 11 second loopA tire quote at the counter. Shown for an invented shop, Sample Tire & Auto. At the counter, someone types the customer’s vehicle, a 2021 Kestrel LX AWD. The fitment panel shows the original size, 235/55R19 101V, and two plus 1 sizes that also fit. A stock panel then lists three tires in that size, checked at the shop and two distributors: Northway Touring A/S at $172.00, In stock, 4 at this shop. Tidewater Grand HT at $149.00, from a distributor in 2 hours. Meridian Sport AS at $198.00, from a distributor tomorrow. The counter person clicks Pick on the Northway tire, and the quote builds line by line: four tires $688.00, mount and balance $100.00, a TPMS service kit $34.00, tire disposal $16.00 and the Florida new tire fee, 4 at $1.00, $4.00. Subtotal $842.00, sales tax at 7% $58.94, total $900.94. They click Text quote to customer. Two lines appear: Quote sent to customer by text, and Added to repair order in your shop system.
What owners run into

The repair order is handled. Everything around it isn’t.

Shop software has come a long way. It still stops at the edge of your own shop, and most of the waiting happens past that edge: on a distributor, on an insurer, or on a customer who said “not today.”

Three weeks is a long time for a customer to be without a car, and a lot of that time goes to supplements going back and forth. On the tire side it’s smaller and it happens all day: a customer at the counter while someone calls around to find out who has the size and when it can get here.

None of that means your software is bad. It’s built to run the repair order the same way for every shop. How you quote tires, chase a supplement and bring back declined work is different in every shop, and that’s the part I build.

Short quotes from public pages, as they read on November 7, 2026.

What I build

Six things your shop system leaves to you

Keep your subscriptions. I build what they don’t do. Tekmetric, Shopmonkey, Shop-Ware, AutoLeap, Mitchell 1, Shop Boss, PartsTech, CCC ONE and QuickBooks all stay where they are. Each of these is built to fit around them, and you can start with just one.

  • A tire fitment and stock bridge

    Type the customer’s vehicle and see the sizes that fit, then live stock from your own floor and your distributors with when each tire can be here. Pick one and the quote builds itself. It goes to your shop system and the same stock can show on your website.

  • A collision supplement tracker

    Every supplement on every job, with its photos, the insurer, the date it went out, the date it was approved and how many days it has been waiting. One page shows your cycle time by insurer, so the slow ones are easy to see.

  • Declined work recall

    It pulls declined recommendations from your shop system, waits a sensible time for each kind of job, and sends a reminder to customers who agreed to get one. When a customer books, the visit goes back into your shop system and the reminders stop.

  • A parts cost reconciler

    Your supplier invoices, matched to the parts lines on each repair order. When a part cost more than the repair order says, it’s flagged before the numbers reach QuickBooks.

  • An estimate checker for your state’s rules

    Before an estimate goes to the customer, it checks for the fields your state asks for, like Florida’s written estimate over $150 and its signed option box. Before an invoice goes out, it checks for the itemized parts, the used or rebuilt notes and your shop’s registration number.

  • Vehicle status texts with photos

    A customer who agreed to texts gets one with a link when the car moves along: checked in, waiting on parts, in repair, ready. A tech’s photo of a worn part can go with it, so the customer can see why before they approve the work.

Where tire shops start

From the customer’s car to one quote

A customer walks in and says the year and the model, and that’s all they know. Your counter types it in and sees the original size and the plus sizes that fit. Next to that is what’s on your own floor and what each of your distributors has, with when it can be here.

Pick a tire and the quote builds: the tires, mount and balance, the TPMS kit, disposal, any state tire fee as its own line, and the tax. It can go to the customer by text if they agreed to texts, and it goes onto the repair order in your shop system, so nobody types it twice. The same stock can feed the tire search on your website.

This is the part I know best. For 14 years I built the wheel catalog behind AllOEMRims, more than 26,500 items, each with the vehicles it fits, and the tire side of the business with it. A fitment lookup that has to be right every time is the same job, whether the buyer is on eBay or standing at your counter.

For collision shops

Every supplement, and how long it’s been waiting

Most shops track supplements in the estimating system, an email inbox and somebody’s memory. The tracker puts each one on a single list: the job, the insurer, the photos that went with it, the date it went out and the date it was approved. Anything waiting too long is at the top.

Over a month it adds up to your real cycle time, by insurer and by estimator. That’s the number insurer programs ask about, and you’ll have it before they do.

The rules

Five Florida rules, as an example

Every state writes its own repair shop rules, so the checker is built from yours. Florida’s five show what that looks like.

The written estimate, s. 559.905. When the work will cost the customer more than $150, the shop has to give a written estimate before it starts. The statute lists what goes on it, from the shop’s and the customer’s details to the odometer reading, the tag number and the proposed completion date. It also asks for a signed option box: a written estimate, a dollar limit, or no estimate. A charge the law requires has to be named on the estimate with the law and the amount.

Going over the estimate, s. 559.909. The shop can’t charge more than the estimate plus $10 or 10%, whichever is greater, up to $50, unless the customer approves it first, orally or in writing.

The invoice, s. 559.911. It has to itemize the labor and parts, say which parts are used or rebuilt, state the warranty and the odometer reading, and carry the registration number the shop gets from FDACS, the Florida Department of Agriculture and Consumer Services.

The new tire fee, s. 403.718. Florida charges $1 on each new tire sold at retail, stated separately on the invoice. The Department of Revenue says it applies whether the tire is sold on its own or on a vehicle.

Texting customers, s. 501.059. Florida’s Telephone Solicitation Act asks for a customer’s prior express written consent before automated sales texts. When someone replies STOP, the texts have to end within 15 days. The system asks for consent up front, keeps a record of who agreed and when, and a reply of STOP ends the texts right away.

From the 2025 Florida Statutes, s. 559.905, s. 559.909, s. 559.911, s. 403.718 and s. 501.059, and the Florida Department of Revenue’s new tire fee page, read on November 7, 2026. This is a summary, not the whole text. I’m not a lawyer and this isn’t legal advice, so check your forms with your attorney.

One person

You get me, not a ticket queue

Every shop runs its counter a little differently, and it’s easier to build the right thing after seeing how your writers, your techs and your estimator actually work. I do that over a screen share, wherever you are, and if the job needs hands on site, I’ll travel to you for a few days.

When you call, you get me. The same person who builds it is the one who fixes it.

How working with me remotely goes →

Who builds it

From 2012 to 2026 I ran the eBay side of AllOEMRims and built the system behind it.

AllOEMRims closed in 2026. The back office I built for it cataloged more than 26,500 items with their fitment, handled 130,000 photos and tracked more than 22,000 orders from eBay and our own site, and I built the tire side of it too. A fitment lookup that has to be right every time is what your counter does all day.

An AllOEMRims eBay listing photo: a silver multi-spoke OEM alloy wheel standing on the bright blue backdrop.
A real AllOEMRims listing photo.
14 yrssince 2012
$3.5M+in sales
22,000+orders
130,000photos

Sales and order figures from the business’s own records.

How it starts

Two easy ways in

A free map of your setup

Tell me what you run, how many bays you have and what keeps going wrong. It’s nine short questions. Within a few days I will send back a plain-English map: what your software already covers, what I’d build beside it, and roughly what that’s worth to you.

  • Free
  • In writing
  • No call
  • No password

If you want help after that, each stage is a fixed price, agreed up front, and everything is set up in accounts in your shop’s name.

Technical · advancedUnder the hoodFor the technical folks: how it connects, what it’s built with, and how it’s kept safe.

I’d rather you know exactly what you’re getting. This is how a shop’s system is set up, in plain technical terms. Where something is how my own back office works today, I say so. I don’t hold a security certification like SOC 2, and I won’t tell you anything is unhackable. What I can tell you is that these basics are always there.

How it connects

  • Your shop, parts and estimating software (Tekmetric, Shopmonkey, Shop-Ware, AutoLeap, Mitchell 1, Shop Boss, PartsTech, CCC ONE, QuickBooks) through the exports or reports it already makes, or through API access you or your vendor grant. Nothing reads its database without your written OK.
  • Distributor stock and prices come from whatever each distributor already gives its dealers, like a dealer portal, a feed or a file, signed in with your own account.
  • Texts to customers go out from a number in your shop’s name, only to customers who agreed to get them, and a reply of STOP ends them.
  • Photos are stored in your install, and the link a customer gets opens only their own vehicle.
  • New data is picked up each time a new export comes in, or as often as your software’s access allows. Distributor stock is checked when a quote needs it.

What it’s built with

  • Python, with FastAPI and SQLite, for the services and the back office.
  • JavaScript and TypeScript for the screens and for Cloudflare Workers. Next.js for websites, this one included.
  • Cloudflare for sign-in (Access), the encrypted connection to your server and hosting websites (Pages). Resend sends the email.
  • The same stack my own back office runs on today.

Where it runs and who owns it

  • Each shop gets its own install. It isn’t shared with any other shop.
  • It runs on a small cloud server in your name, with me as the admin, and its backups go to storage in your name too.
  • Your data lives in your install. My own back office doesn’t keep a copy, and I don’t sell or share your data.
  • It keeps only what the job needs. A card on file stays with your payment processor, so a card number is never stored in your install.

How it’s kept safe

  • Staff sign in through Cloudflare's single sign-on, so you decide who gets in and can take anyone's access away at any time.
  • Keys get only the access they need. If your software ever hands back less access than the job needs, it stops making changes and tells me.
  • Passwords and keys never live in the code. They sit in a locked down file on the server, and the key to your software is encrypted there and never leaves it.
  • Everything travels over HTTPS. Webhooks from outside services are checked against their signature before anything in them is used, and anything public has rate limits.
  • Every change it makes goes into an audit log the app has no way to edit or delete. In my own back office, a price change is a new entry and the old one is kept.
  • New features start in dry run, so you see what it would do before it does it. A kill switch stops all changes at once. It never changes a repair order total on its own, it never sends anything to an insurer, and nothing goes out to a customer until your shop has turned it on.

How changes are made

  • My own back office runs over 3,000 automated tests on every change, once on my machine and again on the server. Nothing ships unless both pass. Your system gets its own suite, run the same way.
  • A backup is taken before any database change.
  • Every release is versioned and can be rolled back.
  • A health check runs after each update, and monitoring keeps checking it every 5 minutes after that.
  • Updates are remote. A fix never needs a trip to your shop.

What you get at the end

  • A runbook for your system and a one page guide for your staff, plus a short training session.
  • The audit log, so you can see every change it ever made.
  • Admin access to everything, in accounts in your name.

Straight answers

Do I have to give up Tekmetric, Shopmonkey or the shop system I have now?

No. Your shop system, PartsTech, CCC ONE and QuickBooks all stay. Keep your subscriptions. I build what they don’t do, and if one of them already does the job, I’ll tell you that instead.

Which systems can it work with?

The usual ones are Tekmetric, Shopmonkey, Shop-Ware, AutoLeap, Mitchell 1 and Shop Boss for the repair order, PartsTech for parts, CCC ONE for collision estimates and QuickBooks for the books. Each one is reached through the exports and reports it already makes, or through API access you or your vendor approve. Before anything is built, I check that each one gives what the job needs. If one doesn’t, I’ll tell you up front.

Can it really show what my tire distributors have in stock?

It uses whatever each distributor already gives its dealers, like a dealer portal, a stock feed or a file, signed in with your own account. Most offer something, but not all of them offer it in a form a program can read. I check each of your distributors before anything is built, and if one can’t be reached, the map says so.

My shop system sells its own texting and marketing add-ons. Why would I need this?

You might not. If an add-on you already pay for does what you need, use it, and I’ll say so in the map. Where I help is the work that runs across more than one system: your shop system and your distributors, your insurers, QuickBooks, and the way your counter actually works.

Can I text customers about work they declined?

The system is built so you can do it carefully. It asks for consent on the repair order, keeps a record of who agreed and when, and ends the texts when someone replies STOP. I’m not a lawyer, and whether a reminder about declined work counts as a sales text is a question for your own attorney.

Does the estimate checker make my paperwork legal?

No tool can promise that. It checks each estimate and invoice against a list I build from your state’s rules with you, so a missing item gets caught before the customer signs or pays. I’m not a lawyer and it isn’t legal advice, so have your attorney look at your forms.

Does the supplement tracker talk to CCC ONE or to the insurer?

It works from what your shop already has: the supplements you write, the photos you send and the dates. Where your estimating system can export, it reads that export. It never sends anything to an insurer on its own. Your estimator still does that.

What does it cost?

Each stage is a fixed price, agreed up front before any work starts. Every shop is set up differently, so there’s no price list. The map is free.

Are you affiliated with any of the companies on this page?

No. I’m not affiliated with Tekmetric, Shopmonkey, Shop-Ware, AutoLeap, Mitchell 1, Shop Boss, PartsTech, CCC, Intuit or any tire distributor. I build beside what they make, with the access you give me.

Who are you?

Justin Zagar, and it’s just me. From 2012 to 2026 I ran the eBay side of AllOEMRims, an OEM wheel business, and built the system behind it, from the wheel catalog with its fitment to the tire side. Now I build the same kind of system for other businesses.