Chapter 5
Finding His Voice
Twenty Days
He sent it on the Monday.
Not the version he wrote standing up — a version he sanded for another forty minutes first, because at seven in the morning the sentence about three of his five customers being able to read had looked less like courage and more like a lawsuit. He took out the part that named the behavior. He took out the word worse. What went up was true and careful and had most of its teeth pulled.
It got thirty-one likes and one comment worth having, from a servicing manager in Boise who said this matches what we see and nobody will say it out loud. Marcus read that comment more times than he'd admit.
Not a thunderclap. Not nothing. He has since decided it was the most expensive result available, because it taught him exactly the wrong lesson — that the danger is in being wrong, and that the cure is care.
Ten days of posting later, the numbers say it's working. Followers up from two hundred and sixty to a little over four hundred. Twenty-five or thirty likes on an average post. Comments from people he's never met. Two DMs that turned into actual conversations.
Twenty days left on Rachel's ninety.
And he is sitting here at 11:40 on a Tuesday morning, on hour two of three paragraphs about the hidden cost of client churn.
A hundred and fifty words. Two hours. He writes a sentence, reads it in the voice of a stranger who has decided he's a vendor, deletes it. He opens two posts from people with bigger audiences to check the shape of his against theirs. He wonders whether the observation is original enough, and specific enough, and defensible enough.
Yesterday's post took three hours and got twenty-eight likes. Respectable. The one he wrote last Thursday in twenty minutes — a thing a customer said on a support call, typed with his coat still on — got forty-seven and six comments.
He has now produced this result four separate times and has drawn no conclusion from it whatsoever.
David stops in the doorway with a coffee he isn't drinking.
"You started that this morning."
"It needs to be right."
"Does it need to be right," David says, "or does it need to be real?"
Marcus doesn't answer, because he isn't sure he knows the difference anymore, and because he suspects finding out costs something.
David looks at the screen a second longer.
"Also, the model could've written forty of those while you slept. That's not a compliment."
He leaves.
Marcus reads his three paragraphs again, and now he can't unhear it. Polished, balanced, structurally sound, and indistinguishable from a competent stranger's summary of a thing he happens to know from the inside. It is, precisely, the average.
He selects the whole draft and holds delete.
Then he opens a blank one and types the thing he'd have said out loud.
Had a call yesterday with a loan officer who's been doing this twenty-two years. He said something I can't stop thinking about.
"I used to know every client's kids' names. Now I can barely remember their faces. The technology was supposed to help me stay connected. Instead it just gave me more people to forget."
I don't have a solution in this post. I just think he described the whole problem better than any deck I've seen this year.
He doesn't sand it. Hits post and goes to get coffee, mostly to be away from the screen.
Three hours later it has sixty-seven likes, twelve comments, and a message from a woman at a lender he's been trying to reach since January.
The Only Part That Was Ever His
He does something that evening he wouldn't have done a month ago, and it works, which he finds mildly insulting.
He takes the loan officer's line — the one true thing, twenty-two words a man said on a Tuesday — and asks the machine to cut it four ways. A version that names the problem and stops. A version that turns it into a model somebody could use. A version that tells it as the story it already is. A version that picks the fight.
Four drafts, forty seconds, all four competent.
Three of them are wrong and he can see it instantly. The framework version turns a man's grief into a maturity curve. The contrarian version picks a fight with a straw lender nobody has met. The story version is fine and is worse than the original, because it explains the quote.
The problem-naming one is close. He rewrites its last sentence, which was doing the thing where it reassures you, and posts it two days later.
That is the whole operation, he thinks, and it took him three months to find it. He supplies the twenty-two words. The machine supplies four ways to hold them. Then he throws away three, which is the part nothing else can do, because choosing requires having been in the room.
Real Beats Right
He starts reading his own analytics as evidence instead of as a scoreboard, which is a different activity.
Ten days of posts, and there is a clean split he's been refusing to see because the losing category is the one he works hardest on.
The posts that land are specific — not client retention matters but a number and the part of it nobody says. They're unfinished; he names a problem instead of resolving it, which invites people in rather than closing the subject. They're sourced from somewhere only he is standing: a customer call, three lenders' usage data, a question a woman from an Ohio credit union asked a consultant who couldn't answer it. And they read like one side of a conversation with a single person rather than a broadcast.
So he starts posting daily and stops rewriting.
It costs him. Not the hours — the hours got cheaper. It costs him something at about eight every evening, when the day's post is up and mediocre and there's no version of the night where he gets to go back and fix it. He is spending nerve now instead of time, and nerve doesn't refill by morning the way hours do.
Some land flat. Single digits, no comments, and one he still thinks was right.
Content That Converts
Here is the thing the last three months have been teaching Marcus in the slowest possible way: production was never the constraint, and it isn't yours either.
He could have published forty posts a week from the first day. So could anyone. That is the problem — the limit on content stopped being how fast you can produce it at roughly the moment everyone's feed filled with grammatically perfect nothing, and moved upstream, to whether you have anything that would survive being said out loud. Expertise is the source. The machine is the scaler. Point it at an empty source and it scales the emptiness, faster and more fluently than you could manage alone.
Which means the discipline runs in an order most people invert.
The mix. A working ratio is roughly 60/25/15 — educational, insight, personal. Sixty percent that makes a reader smarter about a problem they already have. Twenty-five that makes them think differently, including the takes that will cost you somebody. Fifteen that makes you a person rather than a byline.
This is a heuristic, not a finding. Nobody has measured it, it isn't a law, and it will be wrong for your market in some direction. It's useful only because it corrects the two failure modes that are actually common: leading with personal, which is a diary, and leading with pitch, which is an ad.
And note what it's a ratio of. All three categories come out of the same place — your own accumulated evidence. The machine can help you hit the ratio across a month; it cannot supply any of the three. A personal post it wrote is a lie, an insight post it wrote is the consensus, and an educational post it wrote is a summary of what everyone already published.
The four shapes. Every post worth writing takes one of four forms, and each one has a structure you can copy.
Problem analysis. Open with the specific — a number, a quote, a moment. Say what it means for the reader, in their language, not yours. Then stop. Do not solve it. The trust is built by the naming and spent by the solving, and the reader who finishes thinking that is exactly my situation will come find you for the second half.
Framework. Name the thing, give it three or four parts, make each part a decision rather than a topic. It has to work without you in the room; if it needs your voiceover, it's an essay wearing a diagram.
Story. One moment, one scene, one person. Concrete detail before meaning. End one beat earlier than feels safe and let the reader do the last step — the explaining is what kills these.
Contrarian. State what everyone says. State what you have seen instead. Then, and this is the whole thing, say what it cost you to find out. A take with no evidence behind it is a mood; a take with a scar on it is a position.
Notice which of the four a model produces convincingly on its own. Framework, easily. A plausible imitation of problem analysis. It can produce something with the shape of a story, but not a true one, because it wasn't there — and true is the only version that survives being retold by a stranger at a conference. Contrarian it cannot do at all, because it has no stake and nothing to lose, and what comes back when you ask for a hot take is the average opinion wearing a leather jacket.
Why less pitching sells more. Every call to action tells the reader the post was about you. Every piece of pure value tells them it wasn't, and that compounds in a way that is difficult to fake because faking it is more expensive than doing it. When somebody has read you for two months, the sales conversation doesn't start at persuasion. It starts in the middle, where they describe their situation and you already know what they mean.
And why it compounds. A cold email reaches one person once. A post reaches some people now and a few more later — pulled up by someone in a comment thread, forwarded into a channel you will never see, found late by a person who has just been handed the problem. Marcus has posts from three weeks ago still bringing in strangers, which is three weeks of evidence and not a law; the honest version of this claim is that outreach stops the day you do and content mostly doesn't.
This is also where the leverage is genuinely worth taking, and where almost nobody takes it: one real observation is four posts, or a talk, or the spine of a guide, and cutting it four ways is exactly the mechanical work a machine is good at. Just keep the order straight. You have the thought. It has the labor. Reverse those two and you have automated the only part that was ever yours.
The Call She Started
Fifteen days left. Marcus lays the month out.
Followers: 612, from 260 the day he started.
Engagement: forty-five to sixty likes on a good post, six to eight comments. Better than that on anything sourced from a real conversation, worse on anything he sanded.
Email list: 52, from a plain PDF Tom made him write in an afternoon. Five Questions to Assess Your Client Retention Strategy. No design. No funnel.
Inbound: five conversations opened in DMs. Three went nowhere — wrong size, wrong quarter, wrong problem. Two are alive, and neither is close.
Pipeline, in the sense Rachel means it: still thin. He writes that down too, in the same list, because Friday is coming and she will ask.
And then Karen Walsh.
Her message arrived three hours after the loan-officer post went up, which he did not register at the time and has thought about since. VP of Sales at Regional Home Lending. Two hundred loan officers. Exactly the shape of company VaultPath was built for, and exactly the kind of person who has never once answered a cold email from him.
"I've been reading your posts for a week or so. The one about the LO who can't remember faces — that's my whole problem, and you didn't try to sell me anything at the end of it, which is why I'm writing. Would like to hear what else you're seeing."
She wrote to him.
He screenshots it and sends it to Tom.
"First real inbound from content. VP, right company, right title. What do I do."
"Nothing you'd call a plan. Don't pitch, don't demo, don't bring slides. Ask her what her people actually do on day ninety after a closing. Then be quiet for longer than is comfortable."
Then, a moment later:
"And notice what got you this. It wasn't the post you worked hardest on."
Marcus scrolls back to check, and Tom is right, and it is faintly irritating that he'd know that from Austin without seeing a single number.
Then he sits with the thing that is actually bothering him, which isn't the call.
Eight weeks ago he sent two thousand four hundred emails in fourteen days and got nineteen replies, fourteen of them asking to be removed. Since Tom, he has written forty posts. Six of them are genuinely his. One of the six brought Karen Walsh, and two of the other thirty-four brought conversations that went nowhere in the polite way.
The machine could have written the thirty-four. It could have written them in an afternoon, and they would have performed about as well, which is to say they would have performed.
That was never the constraint. It took him forty posts to believe it.
Tomorrow at two he has thirty minutes with somebody who came looking for him.
He opens a blank document and, instead of preparing, writes down every question he actually wants the answer to — not the ones that lead anywhere, the ones he is curious about. There are nine before he stops, and he does not put a single one in an order.
Endnotes
This chapter carries no external citations, and the absence is deliberate rather than an oversight.
The 60/25/15 content mix is presented in the text as a heuristic because that is what it is: a working ratio, widely repeated, that I have never seen measured under conditions that would make it a finding. Ratios like it circulate as though they were research, get cited by people who assume somebody upstream checked, and harden into fact. This book's rule is that a number carries a source or is labeled as judgment. That one is judgment.
The 60% recall figure Marcus uses as an example of a specific post is the same piece of industry lore discussed at length in Chapter 4, note 1 — untraceable to a primary source, retained anyway, and flagged there rather than here.
The engagement figures throughout are Marcus's, and Marcus is invented.
Draft completed: December 2025 | AI-era rewrite: August 2026