A Book Doesn’t Want a Funnel. It Wants a Place to Keep Reading.
Why I built a module that turns a stuck idea into a finished manuscript — and then cut the part that would have turned it into a website.
The software I built to take a book from a stuck idea to a finished manuscript has a worker in it called Builder. Sitting right next to its name, in the same record the interface reads that name from, is a line I wrote myself: “Not a website — that was cut.”
I put that line there on purpose, and it’s worth explaining why, because “build a website for your book” is advice everybody hands out for free, and I spent a real stretch of time trying to automate exactly that before I understood what I was actually automating.
What stopped me
I’d open a page builder with a finished manuscript in one hand, and within about forty minutes I’d be picking a typeface for a testimonials section. For a book nobody had read yet. There were no testimonials to put in it — I was building the empty room where testimonials would eventually stand, on the theory that a website needs one. Above that room, a hero section wanted a one-line promise, which is a completely different piece of writing from the book itself. Below it, an email capture wanted a lead magnet, which meant chopping a chapter down into a PDF — and somewhere in that sequence, the book had quietly stopped being the thing and become raw material for a different thing built on top of it.
Every one of those steps was reasonable, taken on its own. That’s exactly what makes the sum of them so easy to miss while you’re inside it.
A book doesn’t want a funnel. It wants a place to keep reading.
What changes once you actually say that
Once I’d put it that plainly, the scope of the problem collapsed, because a finished book already contains its own structure, and I had been quietly building a second structure on top of it without noticing. The question the book opens with is the homepage. The chapters are the pages. The reason you wrote it in the first place is the about page, and it’s already written — sitting in your own introduction, almost always in better shape than you’d manage rewriting it on a Tuesday afternoon inside a page builder, working from memory of why you started.
You don’t need to invent an information architecture for a book. You need to stop adding to the one you already wrote, chapter by chapter, before you ever opened a website tool.
So Builder builds what a book actually needs — the manuscript, the file that goes to a store, the cover — and then it stops there. And rather than let the name imply more than that on its own, its record carries what the name gets wrong in the same place a person would look for the name, so there’s no way to see one without the other sitting right beside it.
What that costs me, said plainly
That decision costs me something real, and I’d rather say so than pretend it’s free. “Turns your book into a website” is a better line on a sales page than “does not do that.” Nobody’s landing page reads better for admitting a gap. I’d rather undersell the thing in a field where anyone can check it than oversell it in a sentence that reads well and doesn’t survive contact with the product.
And I should be exact about where I stand in this story, because it would be easy to let the essay imply more than is actually true: I haven’t built the companion site for my own most recent book. That’s a decision I’ve made about how to spend my time, not a result I’m reporting back from having already done it and finding it worked. I do have a website built out of writing rather than out of a template — this one — so I know the underlying shape holds together in at least one real case. That’s one example, and I’m not going to lean on it any harder than one example can carry.
What I’d actually ask you
Everyone tells you the book needs a website. If you picture “the website for it” right now, what’s actually on the page in your head? Is it a chapter, in something close to its own words — or is it a hero section and a sign-up box wearing the book’s cover as a background image?
The book needs one page. There’s a decent chance you already wrote it — it’s the question you opened with, before you ever got to the part where someone tries to sell you a website builder.
More of what I’m building, slowly and honestly, at thequietai.com.