The CRM Layer

CRM for
Specialty
Automotive Shops.

QuickBooks knows what you made. Your shop software knows what's on the lift. Neither one of them knows the guy who called Tuesday and never got called back.

01
The Starting Point

How Most Specialty Automotive Shops Run Their Front Office Today.

Most specialty shops are not missing a marketing budget. They're missing the layer that holds onto a customer between the moment they find you and the moment they hand you a card — and every moment after that. That layer has a name, and almost nobody in this industry has one.

Across every shop we've talked to — 4x4, diesel, powersports, restoration, paint, coatings — the front office runs one of three ways.

One: QuickBooks Online and nothing else. This is the biggest group by a wide margin. Invoices go out of QBO, the accountant reconciles it, and everything else lives in a phone, a notebook, a whiteboard, and the owner's memory.

Two: QuickBooks plus a shop management system. Shopmonkey, Tekmetric, Shop-Ware, Mitchell 1, AutoLeap, Protractor — pick one. These shops already figured out that a ledger doesn't run a shop. They bought the tool that runs the bay. And a lot of them are reading this page because they found out that still wasn't the whole thing.

Three: nothing. Paper files, a phone that rings, and an accountant who shows up in March. This shop has been profitable for twenty or thirty years doing it exactly this way, and the owner is not wrong about that. He's here because something has started to feel off, and he can't quite name it yet.

None of the three has a CRM. That's not an accident and it's not a failure of judgment — it's that nobody has ever explained to a shop owner what the thing actually does, in terms that sound like his shop instead of somebody's sales deck.

So let's take them one at a time.

02
The Most Expensive Confusion

QuickBooks Online Is Not a CRM.

Start with the biggest group, because the confusion here is the most expensive one in the industry.

QuickBooks has a screen called Customers. It has a list of names, addresses, phone numbers, and a history of what each one paid you. It looks like a customer database. Understandably, a lot of owners conclude they already have one.

Here is the problem, and it's one sentence:

QuickBooks only creates a customer when there's money attached.

An invoice, or an estimate that turns into one. That's the trigger. Which means every single person who called your shop, asked a question, got a number from you, and then went quiet — does not exist in QuickBooks. There is no record that they ever contacted you. There is no record that you never followed up.

That is not a flaw in QuickBooks. QuickBooks is an accounting ledger and it is very good at being one. A ledger's job is to be a permanent, accurate record of transactions that already happened. It is backward-looking by design, and it should be.

But the money in a specialty shop is not in the transactions that already happened. It's in the fifteen quotes sitting cold, the eleven-month customer who hasn't come back, the deferred work somebody declined in March, and the six people who called last week and got voicemail. None of that is in your books, because none of it turned into a transaction. That's the whole point.

03
Nothing Moves

What QuickBooks Should Keep Doing.

We are not going to tell you to move your books. QBO stays exactly where it is, doing exactly what it's been doing. Your accountant does not have to learn a new system. Nobody re-keys a year of history. Nothing about your close process changes.

QuickBooks owns:

  • Invoicing and collection, if that's where it currently lives
  • Profit and loss, balance sheet, cash flow
  • Sales tax
  • Payroll
  • Bank reconciliation
  • Job costing and margin
  • Anything your accountant or bookkeeper touches

A CRM does not replace any of that, and any vendor telling you otherwise is trying to sell you a bigger invoice. The CRM sits in front of the books, not on top of them. Money that closes flows into QBO the way it always has.

The two systems answer different questions. Once you see the split, you can't unsee it.

04
Two Different Questions

What a CRM Does That QuickBooks Cannot.

The question
Answered by
What did the shop bring in last month?
QuickBooks
What did that build actually cost me in parts and labor?
QuickBooks
What do I owe in sales tax this quarter?
QuickBooks
Who called yesterday and never got a call back?
CRM
Which quote went out twelve days ago and has gone cold?
CRM
Which customer hasn't been in since last September?
CRM
Who declined the second half of the job and never got asked again?
CRM
How many of last month's jobs came from Google versus a referral?
CRM
Who left us a review, and who did we never ask?
CRM
Which lead sat untouched longest last week, and why?
CRM

Every row on the right side is revenue. Not projected revenue, not brand awareness — actual jobs that were available to your shop and left because nothing in your building was holding onto them.

A CRM is a memory. That's the cleanest way to say it. It remembers every person who touched your shop, what stage they're at, what they were quoted, when you last spoke, and what's supposed to happen next — and it does that whether or not anyone in the building remembers to.

05
What Makes It Worth Having

Automation Is What Makes the CRM Worth Having.

A CRM by itself is a filing cabinet with better search. Useful. Not worth much on its own.

Three kinds of automation run inside it: the work you already do that depends on someone remembering, the work you know you should do but never had the manpower for, and the things most shops don't know are possible yet.

What makes it worth having is what happens without anyone touching it.

The lead that comes in at 8:40 on a Saturday night gets a real response before you've read it. The missed call gets a text back the moment it goes to voicemail. The quote that hasn't moved in nine days surfaces itself instead of aging quietly in a folder. The review request goes out after the job closes, every time, not just after the ones that went unusually well. The customer who declined the second half of the job hears from you again on a schedule you set once. The eleven-month customer gets a reason to come back.

None of that is a person remembering. All of it is a rule that runs whether the shop is busy, short-handed, or closed.

The automation layer is deep enough to deserve its own explanation — what a shop used to do by hand and now doesn't, what shops always knew they should do and never had the manpower for, and the handful of things most owners don't know are possible yet.

06
Where It Shows Up

The Cost of Running QuickBooks Alone.

The gap is not abstract. It shows up in the same six places in almost every shop we audit.

01

The Missed Call

The phone rings while both techs are under a truck. Nobody picks up, nobody calls back, and there's no record it happened. Nothing in your business ever knew about that person. In a high-ticket vertical, one of those a week is a very large number by December.

02

The Cold Quote

You wrote a real number for a real build. He said he'd think about it. High-ticket buyers take four to eight weeks to decide — that's normal and it's not a bad sign. But if nothing follows up during those weeks, the shop that does follow up gets the job. The quote didn't lose; it just went quiet and nobody was there.

03

The Reviews You Never Asked For

Reviews are the single most controllable input to your map-pack ranking and to whether a stranger calls you or the shop across town. Almost every shop asks when they remember to, which is after the jobs that went unusually well. Everything else — most of your happy customers — never gets asked.

04

The Customer Who Drifted

Somebody who came in twice in a year and hasn't been back in eleven months isn't gone. He's just not being reminded. Nothing in QuickBooks will ever surface him, because from the ledger's point of view he's a closed transaction — and closed transactions don't come back on their own.

05

The Declined Work

You told him the rear end was next. He did the front. That's a live job sitting in a filing cabinet with no timer on it.

06

No Idea What's Working

When you can't tell which jobs came from search, which came from the map, and which came from the guy who sent his buddy, you either spend on everything or you spend on nothing. Both are expensive.

We measure and report calls, booked appointments, closed jobs, and revenue. Not impressions, not likes, not "traffic is up." If a channel isn't producing jobs, you should be able to see that in one screen and stop paying for it. That reporting sits alongside the search work described in The Foundation.

07
The Second Group

When You Already Have a Shop Management System.

Now the second group — the shops that already worked out that QuickBooks isn't enough and bought real shop software.

If that's you: you made the right call, and we're not here to unwind it.

A shop management system is the system of record. It holds the truth about the vehicle, the job, and the money. Estimate, digital inspection, customer authorization, the work-order board, parts and POs, tech time, invoicing, payment, job costing, and the sync back to QuickBooks. That's a genuinely hard problem and the good platforms solve it well. Rebuilding any of that somewhere else would be stupid.

A CRM is the system of engagement. It holds the truth about the person and the relationship — before there's a vehicle, before there's a repair order, before there's a dollar. And then again after the vehicle leaves.

Those are two different jobs on two sides of one seam, and the seam is where a lot of money falls through.

08
The Seam

Where a Shop Management System Stops.

Every shop management pipeline starts at the estimate. That is the earliest moment the software knows a human exists.

Which means the entire courtship before the estimate — the call, the form fill, the text at 9pm, the answer to "what would something like this run me," the four weeks of thinking about it — happens somewhere your shop software cannot see. And the long tail after the invoice clears is thin in the same way. Most platforms will fire one or two follow-up messages with no conditional logic behind them. Some gate the marketing and review tooling behind a paid tier on top of what you already pay. Shopmonkey, to pick the one most shops we talk to are on, sells its CRM tooling as a monthly add-on and describes its own review request as basic and one-step.

That's not a knock on them. It's an honest read of what those products are for.

So the split for a shop that already runs shop software looks like this:

CRM owns
  • Lead comes in
  • Speed-to-lead response
  • Missed-call text back
  • Quote follow-up
  • Booking
Shop software owns
  • Estimate
  • Digital inspection
  • Authorization
  • Repair order
  • Invoice + payment
  • Sync to QuickBooks
CRM owns again
  • Review request
  • Declined-work reactivation
  • Win-back / next service
  • Reputation monitoring
  • Referral credit
Hands off at “booked” →
← Re-enters at job close

Nothing is duplicated. Nothing gets two text messages from two different numbers. Each side owns what it's actually good at, and the handoff is the only thing that has to be built.

Which brings up the part most people selling you software will not bring up on their own.

09
Before You Sign Anything

Open Integration: The Question to Ask Before You Buy Shop Software.

Here's the honest version, and it's worth more to you than anything else on this page.

There is no single piece of software that does all of this. Not today, and not soon. Anybody who tells you their platform is the one system that runs your bay, your books, your website, your leads, your reviews, and your follow-up is selling you something that is excellent at one of those and mediocre at the rest.

The stack is the answer. And a stack only works if the pieces can talk to each other.

That's what "open integration" means: whether a platform can send information out and accept information in, automatically, without a person copying it between two screens. Two things make that possible — webhooks (the software tells another system the instant something happens: appointment booked, RO closed, payment taken) and a public API (another system can read from and write to it on purpose).

A lot of shop management systems don't have both, and some have neither.

Some publish a full REST API and webhooks on every plan tier — that's the good case, and it's the case for a few of the major platforms. Others put the API behind an enterprise tier you'd never otherwise buy. Others run a partner-only program, where you can't get access yourself and neither can your vendor unless they're an approved partner. Some white-labeled platforms are somebody else's software with a new logo, and integration has to go through the parent company's partner program rather than the one you signed with. And some are simply closed, with a support-ticket process instead of a webhook.

So when you're evaluating shop software — now or three years from now — ask these four questions before you sign:

  1. Do you publish a public API, and is it documented where I can read it?
  2. Do you send outbound webhooks, and which events?
  3. Is that on my plan, or is it an upgrade?
  4. Can I configure a webhook myself, or do I have to open a ticket every time?

A salesperson who can answer all four quickly is selling an open platform. A salesperson who has to check is selling a closed one.

And if your current system is closed, that is not a dealbreaker. We still run everything before the car arrives and everything after it leaves — that part doesn't depend on your shop software at all. What we lose is the automatic handoff, which means somebody in your office moves a job forward manually instead of it moving itself. It works. It's just one more thing on a person instead of on a machine. Worth knowing the cost, and worth weighing the next time a software contract comes up for renewal.

10
The Third Group

If You Are Not on Any Software Yet.

Third group. The accountant does the taxes at the end of the year, the files are paper, the board is a whiteboard, and it has worked for a very long time.

First thing worth saying: it did work. Shops built on that system have outlasted a lot of shops that bought every tool that came along. The instinct that keeps you skeptical of software has protected you more than once.

Second thing: something has changed, and it isn't the work. Your craft is the same. Your process is the same. Your reputation in this town is the same.

What changed is how a customer decides to call you, and what he expects in the first ten minutes after he does.

11
Where to Start

Front of House Is the First Software a Specialty Shop Needs.

If a shop with nothing is going to buy one system, it should not be an accounting system and it should not be a shop-floor system. It should be front of house. Here's the reasoning, and it's structural.

Already Works

Your Accountant.

Twenty years of books, a process he knows, a March that goes fine. Adding software to that solves a problem you do not have.

Already Works

Your Bay.

The board, the tickets, the guys who know what's on the lift and what's waiting on a part. You built that. It's tuned to your building and your crew. Software will not improve it in year one — it will slow it down while everyone learns it.

Does Not Work

Your Front of House.

And that isn't your fault, because the job description changed underneath it.

Consider what a customer does now, before he has ever spoken to you:

  • He finds you on a phone, on a map, standing in a parking lot somewhere. He sees your building for the first time after he's already decided to call.
  • He compares your review count to the shop nine miles away, in about four seconds.
  • He will text you. If your number can't receive a text, he texts the shop that can.
  • He expects a response in minutes. Not "we'll get back to you Monday." The shop that answers first wins a startling share of the time, and it usually isn't because it was the better shop.
  • He'll book at 9:40 on a Tuesday night if you let him, and he'll move on if you don't.
  • If he leaves a message and doesn't hear back the same day, he calls the next shop. Not out of disloyalty. Out of momentum.

None of that is a judgment about how you run your business. It's a description of a customer who now behaves like every other purchase he makes, because every other business he deals with has trained him to.

The paper file is fine for the customer who's already yours. It does nothing at all for the one deciding between you and two other shops right now, in a parking lot, on a phone. That's the job front of house software does, and it's the only one of the three you can't do with people and a whiteboard anymore.

You don't have to change anything else on day one. Keep the accountant. Keep the ledger. Keep the board and the tickets and the way the shop has always run. Put a system on the front door and leave the rest alone.

12
How You Get It

What the Osiris CRM Is.

The CRM Osiris deploys runs on GoHighLevel. That's the platform under it, and we'd rather say so plainly than dress it up. What matters more is how you get it.

You are not buying a software license. You don't get a login and a training video and a wish of good luck. You don't administer it, you don't build the workflows, you don't configure the pipeline, you don't wire the integrations, and you don't troubleshoot it at 7pm.

It arrives built. The pipeline stages, the follow-up sequences, the missed-call handling, the review generation, the reactivation timers, the reporting — all of it is built, tested, and maintained by us, on the same specialty-shop template we've refined across every shop in the network. It gets better for you when it gets better for anybody.

And it isn't a separate line item. The CRM is part of the infrastructure, alongside the website and the local search work, and the Google Business Profile management. It is not sold on its own, it is not priced on its own, and there is no version of this where you buy the CRM by itself. There is one position in a market and one set of infrastructure that comes with it — and the shops holding those positions are listed publicly in the Osiris Auto Guild.

The same rule that governs the website governs this: Osiris builds and maintains it, and it runs as long as the partnership does. You don't own the machine. You own the results it produced while it was running — the customers, the reviews, the reputation, the jobs.

13
Straight Answers

CRM Questions From Shop Owners.

No. QuickBooks stays and your accountant's process doesn't change. The CRM sits in front of the books, holding onto people before and after they become transactions. Closed money flows into QBO the way it always has.

No, and we'd talk you out of it if you asked. Your shop software owns the vehicle, the job, and the money — the estimate, the inspection, the repair order, the invoice. We own everything before the car arrives and everything after it leaves. Those are two different jobs.

Most shop platforms describe their CRM as roughly 70 to 80 percent of one, and that's their own number, not ours. In practice it means the pipeline starts at the estimate, the follow-up is one or two messages with no conditions behind it, and the deeper tooling is a paid add-on. It covers the bay. It doesn't cover the six weeks a high-ticket buyer spends deciding.

Depends on the system, and we'll tell you straight after we look at it. If it publishes webhooks and an API, we build the bridge and the two systems hand off automatically. If it's closed, everything before and after the job still runs — the handoff just becomes a manual step for your service writer instead of an automatic one.

QuickBooks records money that already moved. A CRM tracks people who haven't paid you yet and people who haven't come back. Almost none of the revenue a CRM recovers is visible in your books, because by definition it never became a transaction.

No. Osiris sells one thing: the full infrastructure for one shop per niche per market. There's no CRM-only product, no à la carte menu, and no starter tier. The CRM is part of what an anchor client gets.

It's a smaller jump than it sounds like, because you're not changing how the shop runs. The board stays. The tickets stay. The accountant stays. What changes is the front door — the phone, the texts, the forms, the follow-up — and that's the part that's currently costing you jobs you never knew about.

We do, both. It's deployed configured, it's monitored, and it's improved on an ongoing basis as part of the partnership. You never touch a workflow builder.

The rest of the system
Territory Check

One Shop Per Niche,
Per Market.

The CRM doesn't get sold on its own, because on its own it's half a system. It comes with the site, the local search work, and the Google Business Profile management — the whole front end of your shop, built and run as one thing, for one shop in your market.

Check whether your slot is open.

No pitch. No deck. A direct conversation — about your market, your front office, and whether the position is still open.