Every ghostwriting proposal we have ever seen, including our own, describes the output as posts. Some number per week, in the founder's voice, on a lane, with a running order behind it. That is what gets invoiced and that is what the founder thinks they are buying.
It is not the most useful thing that comes out of the engagement.
The most useful thing is a document we started keeping by accident in the first quarter we were operating, because a client asked us to. It is a list of every question we asked on a voice sync that the founder could not answer on the spot. Not the ones they declined to answer. The ones where they paused, said "I'd have to check," and moved on.
We call it the unanswered question log. It is not a deliverable. It is the exhaust of the interview process. And for a meaningful share of the ecommerce founders we work with, it is the closest thing to an operational audit their business has had in two years.
Why a ghostwriter asks questions nobody inside the business asks
The founder already knows what their business does. Everyone who works for them knows what their business does. So nobody inside the building asks the founder to explain it, and the explanations never get tested.
A ghostwriter is paid to produce sentences a stranger will believe, which means every claim needs a number, a date, or a mechanism behind it. So we ask. What was the return rate on that SKU before the change? What month did the supplier raise the price? How many of the 3PL's invoices did you actually reconcile last quarter? What is your contribution margin per unit on the hero, after fees and freight, before ads?
Those are not content questions. They are the questions an acquirer's analyst, a retail buyer, or a senior operator would ask. We are asking them because we need the answer for a post. The founder is hearing them, in many cases, for the first time since they raised money or took the loan.
Most get answered. Some do not. The ones that do not are the log.
What actually ends up in the log
After a year of keeping these across clients, the unanswered questions cluster into a small number of shapes. None of them are embarrassing. All of them are expensive.
The number that lives in someone else's head. "What's our return rate on that SKU?" gets answered with "my ops lead would know." Fine, but the founder is the one making the creative and pricing decisions on that SKU, and they are making them without the number. The log records that the return rate on the hero lives with a person, not in a place.
The date nobody wrote down. "When did you change the hero image?" produces "spring, I think." We have written before about why listings have no version history. The log is where that gap becomes visible to the founder, because they are the one who cannot produce the date.
The cost that was never itemised. "What did that deal actually cost you after the discount on baseline units?" is the most common unanswered question we log on Amazon-first brands. The founder knows the revenue number. They do not know the incremental one, because nobody ever computed it, because the revenue chart said the deal worked.
The decision with no stated reason. "Why did you pick that 3PL over the other two?" produces a plausible story that changes slightly the second time we ask it, three weeks later. The reason was never written down, so the founder is reconstructing it, and the reconstruction drifts. This one matters more than it sounds. A business that cannot state why it made its last three major vendor decisions will make the fourth one the same way.
The claim that was true two years ago. "Is that still the case?" about a repeat-purchase rate, a supplier lead time, a category share. The founder believes it is. They have not checked. The log records the belief and the last time it was verified, which is frequently the same date.
The log is a map of where the business is run on memory
Put twenty of these in a document and read it back. What you are looking at is not a list of things the founder does not know. It is a list of the places where the business is operated from recollection instead of from a record.
That is the finding. And it is a finding no content deliverable would ever surface, because a post gets written around the gap. We ask, the founder cannot answer, we write the post without the number or with a rounded one, and the post is fine. The business is not fine. It is still making the decision without the number.
We started reading the log back to founders at the ninety-day mark because a client asked what we had noticed about his business that he had not told us. We had not planned to have an answer. We had a document with fourteen rows in it, and eleven of them were about the same three SKUs. He had assumed his catalogue problem was spread evenly across forty ASINs. It was concentrated in three, and the reason he did not know that was that nobody had asked him thirty questions about individual SKUs in a row.
Why this shows up in ghostwriting and not in a consultant's report
A consultant runs an audit against a framework. They ask the questions the framework contains, in the order the framework lists them, and the founder prepares for the meeting. The answers are the answers the founder has decided to have.
A voice sync does not work like that. The questions come from wherever the last post led, in whatever order the conversation goes, every week, for months. There is no preparation because there is nothing to prepare for. We are just trying to find out what happened in March. The founder is relaxed, the question is specific, and the answer is either there or it is not.
That is the difference between an audit and an interview. An audit finds what the founder is ready to show you. An interview, run weekly for two quarters, finds what the founder actually knows, because the founder cannot perform for two quarters straight and does not try.
Our job is to write posts. But the process that produces the posts happens to be one of the few processes in an ecommerce business that stress-tests what the founder knows against what the founder can produce, repeatedly, without an agenda. The log is what falls out of it.
What we do with it
We do not turn it into a service. We tried, briefly, and it made the syncs worse, because the founder started treating questions as tests. The log only works when the questions are honestly about the next post.
What we do instead:
We read it back once a quarter, in ten minutes, unsorted. No recommendations. Just the list. Founders react to it more strongly than to any performance report we have ever sent, because it is about their business rather than about their content.
We flag when the same gap comes up three times. One unanswered question is a Tuesday. The same question unanswered in March, May, and July is a process that does not exist. Usually it is a report nobody pulls, a number nobody owns, or a log nobody keeps.
We let the founder decide what to do with it. Sometimes the answer is to hire the person who would know. Sometimes it is a spreadsheet. Sometimes the founder decides, correctly, that it does not matter and they are fine running that part of the business on memory. That is a legitimate decision. It just should be a decision.
We do not publish it. Ever. The log is the most private document we hold about a client. Half of it would be competitive intelligence in the wrong hands and the other half would read as a list of things the founder got wrong, which is not what it is.
What this means if you are deciding whether to hire a ghostwriter
Do not hire one for this. Hire one because you have a pipeline problem and a positioning problem and no time, which is why everyone hires one.
But if you are evaluating what you got at the six-month mark, look at more than the posts. Ask the writer what questions you could not answer. A ghostwriter who has been interviewing you properly will have a list, whether they call it a log or not. A ghostwriter who has been writing from your profile and a monthly brief will not have one, because they never asked you anything you had to go and check.
That difference is most of the difference between ghostwriting and content spinning, and it is visible in a document that was never supposed to exist.
FAQ
Isn't this just the writer noticing the founder is disorganised?
No. Every founder we work with runs a real business and most of them run it well. The log is not a judgment about competence. It is a description of where the operating knowledge sits, in a person or in a record, and every business has a mix. The useful part is seeing which decisions depend on the first kind.
Why not just run a proper operational audit?
Run one. It answers different questions. An audit asks whether you have the right processes. The log records what you personally could not produce on a random Tuesday when asked in passing, which is closer to how decisions actually get made. Both are useful. Only one of them is free.
Does the log ever change what we write?
Constantly. An unanswered question is very often the seed of the strongest post in the quarter, because when the founder goes and finds the answer, they usually find something surprising, and a surprising finding with a date on it is exactly the material nobody else can publish. About a third of the log converts into posts within two months. The rest stays operational.
What if I don't want my ghostwriter knowing that much about my business?
Then you want a copywriter, and that is a fine thing to want. But the posts will be built from the general pool of what everyone in your category already knows, and that is the content that reads as interchangeable. The specificity that makes a founder worth reading comes from access, and access means the writer is going to ask about your return rates.
If you want to see what the first ninety days of that process looks like, we write about it here. If you would rather just talk it through, reach out.