Chapter 12
Teaching the Method
Why a Person
The job posting will not write itself, and by the fourth attempt Marcus understands why.
He keeps starting it the old way — the tasks he wants off his plate, the hours he wants back — and every draft dies in the same place, because the tasks are already handled. Research, first drafts, sequencing, the follow-up that goes out on time: the machine does all of it, tirelessly, and doesn't need managing. He deletes responsibilities include for the fourth time and sits looking at the empty field. He isn't drowning anymore. He's a little bored on the volume and sharp only where the work is genuinely hard — and you cannot hire for that by listing duties.
So the honest posting is a strange one. He doesn't need hands. He needs a second head that knows something he doesn't.
He already knows whose. A few weeks back a comment had appeared under one of his posts — not a compliment, a correction, a sharp and exact point about what loan officers actually resent, which he'd gotten slightly wrong. He'd looked her up. Aisha Thompson, twenty-eight, five years a loan officer at a mid-size lender, no formal sales training of any kind, and visibly tired of the desk. He'd meant to reach out. She reached out first, which he should have read as the tell it was.
What he wants from her is the one thing he does not have and the machine never will: five years on the buying side of the desk, and the instinct that only comes from having been the person the pitch was aimed at.
On her first day he tells her the truth about what she is. "You're not here to take calls off me. The software does more of that than a person could. You're here because you know something I don't, and because I need to find out whether what I built is a real method or just me."
The Reading List
Her first assignment lands like a joke she doesn't get.
"For the first month," Marcus says, "I don't want you to make a single sales call."
Aisha waits for the rest of it. "...Okay. What do I do instead?"
"You read. Everything I can find you on where lending is actually going — not the vendor version, the real one. And you write. Three posts a week, about what you learned on the front line that the industry pretends isn't true. That's the job, for a month. No pipeline. No quota."
"Let me make sure I heard that." She sets down her pen. "You're telling me to spend my first month studying and posting. Not selling."
"It's the only order that works," Marcus says. "Everybody does it backwards — they put the new person on the phones day one, because calls feel like work and reading feels like stalling. Then they wonder why the new person sounds like every other cold caller. You already know the field better than I do. The month is for turning that into something people can see, so that by the time you ever get on a call, the person on the other end already knows you're worth talking to." He shrugs. "Expertise first. Everything else is built on it. If I put you on the phones tomorrow, I'd be wasting the best thing about you."
She picks the pen back up. "That is the opposite of every sales job I've ever heard of."
"I know. It's also the only one that survives what's coming."
What You Can't Hand Over
The trouble starts when Marcus tries to teach her the part he can't explain.
He has a playbook — How Marcus Sells VaultPath, the one he wrote in a weekend and handed to the machine, and the machine took it and ran without a single follow-up question, because a machine only needs the explicit part. Aisha needs the other part, and the other part won't go onto a page.
How do you know when a prospect is actually interested versus just being polite? She asks it in her second week, and Marcus opens his mouth to answer and finds he has no answer, only a feeling he's had a thousand times and never named.
He calls Tom that night, irritated. "I wrote all of it down. The machine runs it fine. But the stuff that actually matters — knowing when someone's real, knowing when to shut up — I can't put it in the document. Why can I teach it to a model and not to a person?"
Tom laughs, which Marcus was expecting. "You've got it backwards. You didn't teach it to the model. You gave the model the explicit part — the steps, the templates, the sequence — and it's very good at the explicit part. The part you can't write down isn't a gap in your documentation. It's the other kind of knowledge entirely."
"What's the other kind?"
"The kind you earned instead of read. Explicit knowledge is what fits in a playbook. Tacit knowledge is what's left over after you've written everything down — the judgment, the taste, the pattern you recognize without being able to say how. You can't transfer it. You can only set up the conditions for someone to grow their own."
Marcus sits with that. It reorganizes something.
Because the line Tom is drawing — between what goes in the playbook and what doesn't — is the same line he has been living on all year. The machine gets the explicit half and does it at a scale no human can touch. What it never gets, no matter how good the model, is the tacit half: the fascination that makes you go deep, the taste that tells you which insight matters, the read on the unspoken thing in a prospect's voice. That half can't be automated for exactly the same reason it can't be handed to Aisha in a document. It isn't information. It's judgment, and judgment only grows in a person who cares enough to earn it.
Which is the case for hiring a human in an age of machines, and maybe the only case. Not to add volume — the machine wins volume, forever. You hire a person when you want a second source of the one thing the machine can't produce: another center of judgment, ideally one fascinated by a corner of the world you can't see. Aisha isn't a second pair of hands. She's a second pair of eyes on a market Marcus only ever saw from one side.
So he stops trying to write her a script and does what Tom did for him. He gives her the framework — LISTEN, the qualification, the playbook's explicit bones — and then he gives her rooms to practice in and permission to be wrong in them. The playbook is the training wheels. The riding is hers to learn.
Her First Lead
It comes, when it comes, from a post.
By the end of her first month, Aisha writes the truest thing she's put up yet — a piece about the quiet arithmetic a loan officer does when a new tool lands on their desk, the calculation of whether it will save them time or just become one more thing they're audited on. It is not a post Marcus could have written. He has never once been the person being audited.
By the end of the week a VP of sales at a lender in the mountain West has messaged her — not a lead she chased, a lead that arrived, because the post found the one person for whom it was true. You clearly get what this is actually like. Can we talk?
Aisha reads it twice and turns to Marcus with a look he recognizes, because he had it himself in the spring the first time Karen wrote to him.
"I think," she says, "I have a lead."
"You have a lead," Marcus says. "One you didn't make a single cold call to get. One that came to you because you were worth finding." He lets her have the moment. "Welcome to being a sales team of one."
She takes the call the following week. Marcus sits in, muted, and watches her run the framework he taught her — and then do the thing he didn't teach her, because he couldn't.
The VP is describing her loan officers' resistance to yet another tool, and Marcus watches Aisha decide not to argue with it. Instead she says: "Can I tell you what I think is actually going on? When I was on the desk, every new system showed up as one more way for my manager to watch me not use it. It wasn't the login I hated. It was that the tool made my number everybody's business before it ever helped me hit it."
A pause on the line. "That's it," the VP says, quieter than before. "That's exactly it. How did you—"
"Because I lived it," Aisha says.
Marcus writes nothing down. There is nothing to write down; it isn't in the playbook and it never could be. The VP starts describing VaultPath without knowing the name, the way they do when the fit is real. Aisha doesn't pitch. She asks what an ideal fix would actually look like, writes down the answer, and books the next meeting.
After it ends she says, "She basically talked herself into it. I just asked questions."
"You asked your questions," Marcus says. "That's the part that isn't in the playbook."
The Fork
That night Marcus does the arithmetic he's been avoiding.
The method is real. He knows that now, in a way he only suspected before, because it survived contact with a second human being — and not by turning Aisha into a small copy of him. It survived by becoming hers, fed by an expertise he doesn't have. What he built is transferable, and the transfer makes it stronger, not thinner.
Which means the question he set down at the end of the summer is standing back up, and it's larger than it was. He can scale this two ways. He can add more people like Aisha — each one an expert in some corner he can't see, each one a team of one in their own right, the whole thing a federation of judgment. Or he can add more machine around himself — more leverage, more reach, one expert at the center running an engine that keeps getting bigger. Both work. He's now watched both work. They are not the same company, and they do not ask the same thing of him.
He doesn't have to answer tonight. But he can no longer pretend the question isn't there, and somewhere in the last month it stopped being can I even scale this and became what do I actually want to build.
He'd spent a year proving one person could be a whole sales team. He had just watched the method work in someone else's hands, in her voice, better than it would have worked in his — and it occurs to him, closing the laptop, that autonomy was never the same thing as alone. The thing worth building was never a solo act. It was a way of working, and it turned out you could hand it to someone worth handing it to.
Endnotes
Aisha, Janet, and Mountain West Lending are invented, and the metrics of her onboarding are deliberately absent — the first draft carried a page of them (pipeline up sixty percent, call load down forty) and they added nothing except the false precision this book keeps trying to avoid. The claim that matters is not a number. It is that a real method survives being taught to another person and comes back changed for the better, which is exactly what an automated process cannot do, and exactly why the human hire earns its cost.
The distinction between explicit and tacit knowledge is not mine; it's Michael Polanyi's, from The Tacit Dimension (1966) — "we can know more than we can tell." I've used it the way Tom uses it, as a working idea rather than a citation, but the phrase and the concept are his and worth reading in the original.