The marketing strategist Jay Abraham tells a story I keep coming back to. Abraham has spent four decades advising businesses (everyone from Federal Express to thousands of small operators) and this is one of the parables he uses to teach the highest-leverage idea in his playbook.
A B2B software company called WDC Systems built a 14-step qualification process for every inbound lead. The first step in the process wasn't run by a salesperson, an account exec, or the founder. It was run by Aimee, the receptionist.
Aimee had a script. She had a checklist. She had a documented set of qualifying questions to work through, and a documented set of disqualifying answers to listen for. Her job at step one was not to sell anything. Her job was to edit. To filter out the leads that weren't a fit before they ever reached step two.
Here's the line from David Carrington, the founder of WDC, that lit me up the first time I heard it.
"We want Aimee to feel like she made the company $10,000 every time she edits a lead out, because she didn't permit that lead to go to step two."
A receptionist. With a script. Generating five figures of value per filtered lead, by being the right system in the right seat.
That's not a marketing story. It's a systems story. And it points at something most business owners have not internalised yet, which is that the highest-leverage role in your business might not be the one with the highest salary.
What does $10,000 a lead actually mean?
The math isn't magical. It's just visible once you look at it.
Every unqualified lead that reaches a senior team member costs you. They take a sales call that goes nowhere. They write a proposal that doesn't close. They send follow-up emails that bounce around for weeks. Multiply that by the hourly cost of senior time, multiply that again by opportunity cost (the qualified leads they couldn't focus on), and the cost of a single wrong-fit lead is rarely under $1,000. In a high-margin service business, it's often closer to $10,000 by the time you count the cascading downstream cost.
Now look at it from the other side. Every wrong-fit lead that Aimee filters at step one is a $10,000 cost the business never incurs. She's not generating revenue, technically. But she's protecting margin at five figures a pop.
That's the leverage. It only works because there's a documented system carrying the expertise of qualification, not Aimee's improvisation. If Aimee tried to qualify by gut feel, she'd let the wrong leads through and block the right ones. The system makes her decisions defensible, repeatable, and trainable for the next person who sits in that seat.
Why is the first-touch system the highest-leverage system in your business?
Ask most owners which of their systems matters most and they'll say something downstream. Sales conversion. Delivery quality. Client retention.
Those matter. But the first-touch system is upstream of all of them. Whatever Aimee lets through is what shapes the rest of the funnel. If the front desk lets in tyre-kickers, your sales team's close rate looks bad. If the front desk filters too aggressively, your pipeline looks dry. If the front desk has no system at all, your senior team is doing qualification work on top of their actual job.
Most front desks are reactive. They answer the phone, take the message, book the meeting. That's the leverage being left on the table.
Done well, the front desk is the most strategic seat in the company. It's the one role that touches every lead, every existing client, and every internal handoff. A documented first-touch system quietly amplifies every other system downstream.
Can a non-specialist really do specialist work?
This is the question that stops most owners from systemising properly. The fear is that documenting the work commodifies it, and that handing it to a non-specialist will cost quality.
Here's the answer in a sentence. A documented system holds the expertise. The human follows the system. The work gets done at specialist quality, by someone who isn't a specialist.
Shannon Smit runs SMART Business Solutions, an award-winning accounting and advisory firm in Melbourne with about 20 team members and a niche specialty in international transfer pricing. The firm's been a SYSTEMology client for years. They've used systems and automation to save over 1,000 hours of senior-team time on a single recurring task.
Shannon has her son Ryan working in the firm. Ryan was 18 months into an aviation degree, on track to be a pilot, when he came to his parents and told them he wanted to change degrees and study accounting. Not because the family business was an obvious next step, but because he'd been helping out in the firm and discovered he genuinely loved the systems.
Here's how Shannon tells it.
"Ryan was obviously studying 18 months into his aviation degree and then just came to my husband and I and said I want to change degrees and I want to do accounting. I like the systems. I like the logic and the maths."
Ryan is not a chartered accountant. He's not a bookkeeper by training. What he is, now, is the person managing the bookkeeping for three practices, since the firm's full-time finance manager left in May. Shannon's words again.
"He is not an accountant, and he is managing the bookkeeping for three practices."
The work gets done at the firm's standard. The senior accountants are freed up for the genuinely judgement-heavy parts of their day. Ryan gets meaningful work and develops fast. And Shannon has stepped back from being the bottleneck on the technical work she used to handle personally.
Ryan is the modern Aimee. The role is different. The industry is different. The leverage pattern is the same. A non-specialist, given a well-built system, doing work that on paper requires a specialist.
What does a Systems Champion actually do?
When Ryan started, nobody told him his job was to be the Systems Champion. Shannon didn't appoint him. He fell into the role because he was analytical, direct, and naturally allergic to broken processes.
"When he first started it wasn't like we said right your job is system champion. He just started in this support role and he was very direct, as you know people that are analytical, and he'd be like this system isn't good at all. This needs to be updated. This process makes no sense."
Then Ryan defines the role himself, in his own words.
"In my mind I think when I started I thought the systems champion would be the one writing the systems. You're almost really the one refining it and getting the systems off other people."
That's the part most owners get wrong. The Systems Champion is not the person who writes every SOP from scratch. They're the person who extracts the systems out of the people who already know how the work gets done. (We've written about what a Systems Champion actually is in more depth, and the three pillars that make the model work.)
Ryan now works three days a week at SMART while finishing his degree. He's also the firm's first AI Champion. One of his early projects was a bot that automates a compliance task that used to take him 10+ hours a week. He built it by Christmas.
In Shannon's words.
"He had to go into one of our platforms, download the information of client file notes and put it up in the other one. Took him over ten hours a week. So very boring. And so he actually created a robot by Christmas that does that and automates it."
That's the new ceiling. Not just non-specialists running specialist work via systems, but non-specialists upgrading specialist work via AI on top of the systems.
Why does this matter for the rest of your business?
This is the Systems Champion model in action. (And increasingly, the AI Champion version of it.)
Most owners assume that specialist work requires specialists. That assumption costs them.
The smarter assumption is that specialist work requires specialist systems, and that once those systems exist, the work can be performed by someone less senior, less expensive, and often more available than a specialist. The senior person stays in the loop for the parts that actually need their judgement. They're freed from the parts that don't.
Run that pattern across enough roles and you've changed the economics of your business. The same revenue, delivered by a lighter team, supported by stronger systems, generating better margin and putting less weight on any one person.
That's what Shannon has done. That's what Aimee was doing 20 years ago at WDC. The principle hasn't changed. The technology layer has just made it easier to actually build the systems.
How do you build a $10,000-per-lead front-desk system?
Five components. None of them are technical. All of them require an hour of thought you've probably never spent on the front desk.
1. Documented qualifying criteria. What does a "right fit" lead actually look like for your business? Write it down. Industry, revenue band, urgency, decision-maker access, budget signal. Specific enough that a non-specialist can apply them without calling you for a ruling.
2. A question script. What questions does Aimee (or your version of Aimee) ask to surface those criteria? Not a sales script. A diagnostic script. Five to seven open-ended questions that produce the answers, in order, in a way that doesn't feel like an interview.
3. A decision tree. Based on the answers, where does the lead go? Qualified leads go to the senior team. Disqualified leads get a kind, professional decline. Edge cases get logged for owner review at the end of the week. The decision tree should be a one-page document.
4. Disqualification language. This is the part most owners skip and it's the part that protects your reputation. The kind, specific, brand-respectful way to tell a wrong-fit lead "we don't think we're the right fit for what you need" without burning the relationship. Wrong-fit today is sometimes referral-source tomorrow. The language matters.
5. A performance review rhythm. Once a fortnight, the senior team reviews the leads Aimee filtered out and the ones she let through. Not to second-guess her on every call, but to spot patterns, refine the criteria, and make sure the script keeps up with how the market is shifting.
Five components. A documented one-page playbook. An hour to write the first version. A week to test it. A month to refine it. After that, you have a $10,000-per-lead system, and a non-specialist who is genuinely earning their seat.
The pattern goes way beyond the front desk
Once you've done this for one role, the pattern repeats. Every role.
Bookkeeping that used to need a CA, run by a uni student with a documented system. (Ryan at Shannon's firm.) Sales follow-up that used to need a senior closer, run by a trained admin with a documented sequence. Project management that used to need a senior PM, run by a coordinator with a documented status-and-escalation rhythm. Customer onboarding that used to need a founder's personal touch, run by a customer success rep with a documented welcome flow.
Each transition follows the same arc. Document the specialist's actual judgement until 80% of it is captured in the system. Hire (or redeploy) someone less senior. Keep the specialist available for the 20% the system can't yet handle. Compound the pattern over five or ten roles, and the shape of the business changes.
This is also where the moral case for systemising your business shows up at the operational level. The team can deliver the standard, on every day, regardless of who's in the room. The client gets the version they paid for. The owner gets to step away.
Where to start
Pick the one role in your business where the gap between "what the senior person actually does" and "what a junior could do with the right system" is biggest. Usually it's the front desk. Sometimes it's bookkeeping. In professional services firms, it's often technical document preparation. Different industries, different role, same pattern.
Document one process from that role this month. One. Not all of them. Pick the highest-frequency, highest-leverage task in that role and write down the system that runs it.
If you want a starting point that doesn't require an hour of guessing about which role to pick, take the Systems Strength Test. It's a nine-dimension diagnostic that surfaces which roles in your business have the biggest leverage gap between current state and a documented one.
Aimee isn't a marketing story. She's a leverage story. So is Ryan. Every business has its version of them, sitting in a seat where a documented system would make their work worth ten times what their salary suggests.
Most owners haven't built that system yet. The ones who do are the ones who get to step away.