Crafting a Book Proposal That Academic Publishers Cannot Ignore

The academic book proposal is one of the most consequential documents a scholarly author will write, and one of the least taught. Doctoral programs train authors to write dissertations. The proposals that convert those dissertations into books are, as a rule, left for the author to work out, even though the proposal, and not the manuscript, is what gets the manuscript read in the first place. It is also the first piece of the author's writing an acquisitions editor sees. An editor who receives a strong proposal will ask for the manuscript; one who receives a weak proposal will pass, however good the work behind it.

A strong proposal starts from what an acquisitions editor is actually evaluating when she reads one. She weighs the scholarship against practical questions. Is there an audience for this book, and is it large enough to justify the press's investment? Does the argument occupy its own space in the conversation, or does it sit so close to existing books that it becomes redundant? Can this author write for the audience the press serves, or will the manuscript need more developmental work than the press can support? The proposal has to answer all of these, and it has to answer them before the editor thinks to ask.

The overview. The overview, typically two to four pages, is the core of the proposal. It should open with a statement of the book's central argument clear enough for an educated non-specialist to follow and compelling enough to make the editor want to read further. Then it establishes the argument's significance, both to the field and to questions that educated readers outside the field might care about. Academic presses publish for academic audiences. The best academic books still speak to questions that extend beyond the specific disciplinary conversation, and proposals that articulate that extension have a clear advantage over those that do not.

The chapter descriptions. Chapter descriptions do two things at once: they describe the content of each chapter, and they show the argumentative logic connecting the chapters. Reading them, an editor should be able to see how the book builds, with each chapter advancing the argument in a way the previous chapter made possible. Many descriptions summarize content without revealing structure. That is a common proposal weakness, and it suggests the book's architecture may not yet be fully developed.

The market analysis. Authors are most likely to underestimate this section and most likely to write it poorly, and the editor needs to know, specifically, who will assign, buy, and read this book. What courses, at what level, would assign it? What professional organizations serve the primary readership? What is the size of the relevant graduate student population, and how does this book fit into their training?

A line such as "this book will appeal to scholars interested in X," with no account of the size or composition of that group, expresses an aspiration. It gives the editor nothing to measure.

The competing titles section. This section demonstrates that the author understands the books already in the field and can position the proposed book among them with precision. The books selected for comparison should be real comparators — books the same reader would consider alongside the proposed book — and the comparison should be specific: here is what that book does, here is what this book does differently, and here is why the field needs both.

The manuscript status section. The proposal should be honest about the current state of the manuscript: its word count, its completion status, and the work remaining to prepare it for submission. Authors who overstate the manuscript's readiness create expectations they cannot meet. Understating it creates doubt about whether the project will be completed at all. Give the honest account. Add a realistic timeline.