The moves are teachable.

There was a podcast I listened to this week with two UK car dealers, very different in scale. The big group does 1000 cars a week across their sites. The smaller one does a fraction of that.

The smaller dealer's reaction to the number was the following.

First: "Wow, that's so much paperwork."

And then: "See, our business couldn't do that. I have a great team around me, but I need to be involved in every deal to ensure we win the business and that it has maximum profit in it."

He's clearly very good at his job, which is why the business is successful. But those two sentences are the ceiling of his business stated in his own voice, and I don't think he realised what he was really saying.

What he was really saying

There are two beliefs sitting in those quotes, that I would challenge.

The first is the fear of systems dressed as a comment about paperwork. "Wow, that's so much paperwork" isn't really about a volume of forms. It's a quiet flinch at the thought of all the documenting, standardising and process that scale implies. At higher volumes, paperwork is actually more efficient per deal, because the bigger operations have built systems that scale. His nervousness about the volume suggests he already suspects his current system would break long before he got there.

The second belief, the heavier one, is that the way he wins deals and protects margin can't be passed on. Those moves are his moves. They came out of years of doing it, and because he can do them but can't quite describe them, they feel like something only he can do. The interesting thing is, he once didn't know how to do them either. Someone taught him. He learnt. (In fact, it was his Dad.) He's assuming no one else is capable of learning what he did, or that no one else will care as much.

Neither belief is unreasonable. They are very common, and they are usually completely wrong.

What he was actually right about

He wasn't wrong about the paperwork. Most regional systems do hit a point where they stop scaling, and the worry that things would buckle before getting near a thousand a week is, in most cases, exactly correct. The useful question if he wants to grow isn't "what would a 1000-cars-a-week system look like?" It's "where does my current system start to wobble?" That's where the next piece of the process that needs to be built.

Building a 1000-cars-a-week system for a 50-cars-a-month business isn't sensible either. Know where the current system breaks, build the small thing that gets through the next stage, and let the stage after that be the next conversation.

What we could try

If I was sitting down with him to chat about his business, this is where I'd start.

The first piece is a way to capture the moves. After every deal worth capturing, a ninety second voice memo from him on what won it or lost it. Not a report. A quick verbal note while it's fresh, on the way back to his desk. The point isn't documentation, it's evidence of his thinking, in his own words.

The second piece is a place for those captures to be transformed into something teachable. A living Google Doc, organised by deal stage, where the recurring patterns get pulled out of the voice notes over time. "When a customer goes quiet for more than three days, here's what I do." "When a trade-in valuation looks off, here's how I reframe it." "When the finance team needs the deal to be a certain shape, here's how I steer it there without losing the customer." That document isn't a script, it's the closest thing to him another salesperson can carry around. What they learn from. And when it works, and they make more commission, you can bet they start to lean in more.

The third piece is an automated deal pipeline in Monday or Notion, structured around the stages he intuitively works through. Every live deal sits in one of those stages, with the playbook entries linked to the cards. The whole team can see where every deal is, who's responsible, and what the next move should be. He's not signing off on every conversation. He's in the system, even when he isn't in the room.

Three small pieces that capture the work and the knowledge. Almost nothing in terms of cost or complexity.

For a fellow LEAN reader, this is just standard work applied to a knowledge job. The same logic any factory floor would recognise, lifted into the showroom. Capture the variation, find the pattern, write the standard, train against it, refine it. Eliminate the heroics. The owner doesn't stop being the best salesperson in the building. The owner stops being the only one.

What it actually takes to set up

The board and the doc take a week of building and tweaking. The voice note habit is the harder bit, because it's a new behaviour for the owner, not a new tool. Two weeks of one short note per meaningful deal builds the muscle. After a month there's enough in the doc to train a second salesperson against it. After three months the team is running off a shared playbook, and the owner is back at his actual job, which is running the business, not approving every conversation.

There's no dramatic cost to putting it off, and nothing breaks, the business just stays the size it is.

The smaller dealer shared his beliefs on the podcast and they mirror a lot of owner operator concerns. However, the way he wins deals isn't magic. It's a system that has never been written down.

The gap between his current volume and the bigger group's isn't more hours from the owner. It's whether anyone else in the building can run a deal the way he would, (or potentially even better) and whether a system can be built that supports the paperwork in the background.

Until that's true, the owner IS the ceiling. It's not his team holding him back from the bigger numbers, it's him.