Most of this site describes how a book gets written: architecture first, then the manuscript, chapter by chapter. This page is for the author who has already done that part. The draft is finished. It sits in a folder, or a drawer, and you are circling one of two questions. Is it as strong as it could be? And is it ready?
Those are different questions, and they get different services. Both work on the complete manuscript. Both are standalone. Neither changes a word without your say-so.
The Retrospective Blueprint
For the manuscript that could be stronger
You wrote the book close up, over months or years. The Retrospective Blueprint reads it from the outside, in full, twice: once the way your reader will, and once the way an editor maps machinery. It reconstructs the argument the manuscript actually makes, sets that against the argument you meant to make, and finds the connections your own material supports but never quite states.
What comes back is not a verdict, and it is not a rescue. It is your book's real strengths named with evidence, its missed opportunities documented as findings, and its strongest possible version laid out as options you choose between. Nothing is changed. Everything is shown.
From the example report, produced on my own manuscript
Finding UC-7 · Unmade connection · Transformative tier. The book's central proof scene carries two opposite morals a hundred pages apart. Chapter 7 tells Lisbon as the demonstration that the settled identity held: the trick failed, the man did not. Chapter 12 tells the same Lisbon as the exposure of an identity still outsourced to results. An attentive reader meets contradiction at the heart of the argument, and every reader misses the book's deepest available teaching, which its own material fully supports: identities are layered, and they run on different clocks.
The Pre-Publication Editorial Review
For the manuscript that is about to go out
You believe the book is done. Before it carries your name into the world, it gets the read your future readers cannot give you: a full close read, a continuity audit, an independent fact-check of every checkable claim, a commissioning editor's assessment, a line edit, and a publication readiness check.
Everything found comes back as a numbered proposal: what it is, where it sits, what I propose, and why it matters, ranked by how much it matters. You approve, reject, or query each one. Nothing in your manuscript changes unless you decide it does.
From the example report, produced on my own manuscript
Proposal A2 · Fix before publishing.
Where: About the Author, final line.
Found: "Note: the paragraph above can be extracted and converted to third person for the book sleeve or back cover."
Proposed: Delete the line.
Why: An instruction to the production team, visible to every reader.
Which one, and in what order
If the question is "is my book as strong as it can be", start with the Retrospective Blueprint. If the question is "is it ready to publish", the Pre-Publication Editorial Review answers it. Authors who want both take them in that order: strengthen the argument first, then verify the final manuscript before it goes out. Reviewing a draft you are about to strengthen means checking work that is about to change.
Each is a fixed fee for a single manuscript, agreed before any reading begins. Both example reports exist in full, run on my own manuscript before anyone else's: ask on the call and I will send them to you.
What neither service is. Not ghostwriting, not a rewrite, and not a judgement on whether you should have written the book. The manuscript stays exactly as you wrote it until you approve a change. And where the work is already strong, the report says so, with evidence: a review that can only find faults is a sales letter.
One boundary worth drawing: these services are for complete manuscripts. If your draft is partly written, or written and then abandoned somewhere in the middle, the Book Blueprint is the right instrument: it assesses everything you have and builds the architecture to finish.