Two Books Came From the Same Author. One Worked.

I was on a coaching call recently helping someone work through a book project. The guy is a real expert. Knows his subject cold. Smart, articulate, experienced. And he's working with a collaborator he's worked with before - same ghostwriter, same general process, same general topic area.

Except this time, the book isn't coming together the way the last one did.

We spent a good chunk of the call going chapter by chapter, and I kept hitting the same wall: the frameworks were there, the structure was there, the section headers were there. But when I dug in and asked okay, but what does this actually look like in practice - what tools, what steps, what does someone do on Monday morning - the chapter just kind of trailed off into vague gesture territory.

So I asked him directly: what was different about the last book? The one that worked?

His answer was immediate. The last one had all the case study examples, all the scripts, and extreme detail. This one - we had the outline, and we were going to add the examples later.

That's it. That's the whole forensic report right there.

The Controlled Experiment You Didn't Know You Were Running

Most authors never get this kind of clarity, because most authors only write one book. They don't know if it worked because of the topic, the timing, the cover, the publisher, the marketing, the word count, their existing audience, or something else entirely.

But this guy had a genuine controlled experiment: same collaborator, same general subject domain, same process, adjacent audience. And one book worked and one isn't working. So you can actually isolate the variable.

It wasn't the framework. Both books had frameworks.

It wasn't the writing. Same writer.

It wasn't the structure. The current one actually has better chapter structure - more organized, cleaner sub-headlines, more logical flow.

What it didn't have was the material. The documented, specific, teachable, been-there-done-that, here's-the-exact-tool-and-here's-the-exact-script material that only the author can actually provide.

The Ghost Can't Make It Up for You

Here's something I've seen over and over when people hire writers to help build their books or content systems. They think the writer's job is to create the expertise. And I've heard my collaborator say almost exactly what I believe: if I just make the book up myself, what's your contribution?

A ghostwriter's job is to take your expertise and make it readable. To take 14 hours of rambling explanation and turn it into 300 clear pages. To structure what you know so that someone who knows nothing can follow it. That's real value. That's genuinely hard work.

But if the author shows up with a half-baked idea and says you're a good writer, so just write it - what you get is a book about the idea, not a book from someone who actually did the thing. And readers feel that difference immediately. The specificity gap is obvious on page one.

I told him: you need to imagine you're explaining this to someone who knows absolutely nothing about it. Walk me through it like it's a course. Not the concept - the actual steps. What platform do you go to? What are the five questions you ask first? What does the research process look like on day one? What does "good" look like versus "bad"? Name the tools. Show the examples.

That's the material. And only you have it.

The Cold Email Manifesto Lesson

I know this trap well because I lived it building my own book. When we did The Cold Email Manifesto, the way it actually came together was I was essentially reading off PowerPoint slides - going through actual course material, live, in painful detail. Every claim had an example behind it. Every framework had a script. Every strategy had a real number attached to it.

We didn't write about cold email. We showed cold email, step by step, script by script, case study by case study. There's a Magento agency story in there. There's a mobile development script. There's a breakdown of exactly what happens when a campaign goes badly - not a vague reference to "learning from failure" but an actual failed email, reproduced verbatim, with an explanation of exactly what was wrong with it and what I'd write instead today.

That level of specificity is what makes a practical book actually work. It's not more impressive writing. It's more documented reality.

And the process of extracting that reality - going through a framework like it's a course, chapter by chapter, with real examples on every page - is work that only the author can do. You can't delegate that part. The ghostwriter can shape it, tighten it, make it compelling. But they cannot invent your experience for you.

What "Adding the Examples Later" Actually Means

The phrase that stuck with me from this call was: we had the outline, and we were going to add the examples later.

I've heard this exact thing so many times. The idea is that structure comes first, detail comes second. And in a certain narrow sense that's true - you do need to know your chapters before you fill them. But there's a version of this that becomes a trap: you finish the structure and then the examples never materialize, because examples require the author to do something hard. They require the author to sit down and document in excruciating detail what they actually do.

Not what they conceptually believe. Not the principles behind their approach. Not the philosophy that underpins their method. What they actually, physically, tactically do - the platform they open first, the search filters they apply, the script they use in the first thirty seconds, the decision tree they run through when something doesn't go right.

That material exists only in the author's head (and maybe in some notes or recordings). The ghostwriter cannot access it. They can prompt for it, they can ask the right questions, they can create a structure that makes room for it. But they cannot go retrieve it from inside your brain.

And when it doesn't make it into the manuscript, the book feels - and this is the exact word my guy used - vague. Not wrong. Not poorly written. Just vague. And in business and sales and anything practical, vague is fatal. Vague means the reader can't actually do anything with it.

The Specificity Test

Here's a test I use for any chapter in any practical book or course or training program. Read the chapter and ask: could someone who has never done this before actually take a concrete action tomorrow based only on what's written here?

If yes - real action, not "think about their approach to X" but actual tangible steps - the chapter is doing its job.

If no - if the reader finishes the chapter knowing more about the concept but still not knowing how to actually do anything - it needs more material. Not better writing. More material.

When I'm building out outbound systems with clients, the same principle applies. The best lead strategy in the world doesn't work if it stays at the level of "identify your ideal customer and reach out to them." That's a concept. What works is: here's the specific search you run in a B2B database, here's the filter combination that gives you qualified contacts, here's the exact subject line, here's the follow-up sequence with timing, here's what you say when someone replies with an objection. Named tools. Real scripts. Actual numbers from real campaigns.

The same principle that makes a cold email campaign work is the same principle that makes a book work. Specificity is the whole game.

What the Fix Actually Looks Like

So what did I tell him to do? Go through each underdeveloped chapter like it's a module in a course. Record it if you need to. Speak it out loud. Imagine someone in front of you who has zero background - what are the five things they would need to know to actually do this? What tools would you tell them to open? What would you caution them against? What mistake does everyone make the first time?

Once that material exists - even as rough audio, even as a brain-dump document - a good collaborator can shape it. That's the part where the writer adds real value: turning your documented expertise into something readable. But they need the documented expertise first. That's the raw input. Without it, they're building furniture with no wood.

On the specific chapter we talked about longest - the one covering the exit process for a business - he flagged that it was barely touched. And that's actually a significant omission, because the whole point of certain business-building frameworks is that you're building toward something sellable. If you skip the exit mechanics, you've described how to build a car but never explained how to drive it out of the lot.

So we talked about what that chapter needs: the platforms (there are a handful of established marketplaces where businesses actually get listed and sold - Flippa being one of the most recognized for digital businesses), the questions a buyer actually asks, the preparation work that determines whether you get a good multiple or a bad one, the things founders consistently forget to document before a sale. That's teachable material. It exists in the author's experience. It just needed to be surfaced and written down.

That's the work. Not glamorous. But it's what separates a book that people actually recommend to other people from one that sits on shelves.

This Problem Isn't Just About Books

I'm writing about books here, but the underlying lesson applies to anything you're trying to teach or sell through content. Courses. YouTube videos. Email sequences. Cold outreach. Sales calls.

Vague authority doesn't convert. People can smell the difference between someone who has actually done the thing at a granular level and someone who has a general familiarity with the concept and is packaging it as expertise. The specificity is the proof. The case study is the proof. The named tool, the real script, the actual number from an actual campaign - that's the proof.

When I'm helping people build outbound systems, the cold email scripts that work aren't the ones with the best creative writing. They're the ones with the most precisely documented offer - a real result, for a real type of client, in a real amount of time. That's what gets responses. The same dynamic is at play in every other form of content you produce.

If you want to see how this plays out at the outbound level - where list quality, script quality, and follow-up sequence all interact - the 7-Figure Agency Blueprint is a good starting point. The core principle there is the same one I'm describing here: you have to actually document your process at a granular level before any external system can amplify it.

The One Variable

Same author. Same collaborator. Same process. Same general subject area. One book worked. One isn't working yet.

The difference is not the talent. Not the structure. Not the quality of the writing. Not even the importance of the topic.

It's whether the author sat down and extracted their real expertise into documented, specific, teachable material - or handed over the memory of having done something and called it a manuscript.

The fix is available. It just requires the author to do the one thing that can't be outsourced: actually documenting what they know at the level of detail that lets a stranger do it too.

That's the book. Everything else is a placeholder until you deliver that.

If you're building out your own content systems - books, outbound sequences, course frameworks - and you want to work through the specificity problem with people who've actually done it, check out Galadon Gold. That's where the real work gets done.