How to Write a Nonfiction Book Proposal That Editors Actually Read

Nonfiction is usually sold on a proposal, not a finished manuscript. An agent or editor reads the proposal and decides whether the book is worth buying.

A strong proposal does three jobs. It tells the editor what the book is in a paragraph they can repeat to colleagues. It shows that readers are waiting and that you can reach them. And it proves, through the outline and sample chapters, that you can actually write the thing.

This guide walks through each part with worked examples. It ends with the problem nobody warns you about: keeping the proposal and the book in agreement once you start writing.

Key points:
1. A proposal is a sales document with five core parts: overview, market and comps, platform, chapter outline and sample chapters.
2. The overview and chapter summaries carry the most weight, because they show the shape of the book.
3. Choose sample chapters that prove the book's promise, then keep the proposal updated as the draft changes.

What a Nonfiction Book Proposal Contains

Agents and publishers each have their own preferences, so check the submission guidelines first. Most, though, expect the same core sections.

Section	The question it answers	What to include
Overview	What is this book, and why now?	Hook, central argument, what the reader gets
Market and comparable titles	Who buys it, and what sits beside it on the shelf?	Target reader, a handful of recent comps and how yours differs
Author platform	Why you, and how will readers find you?	Credentials, audience, newsletter, speaking, media
Chapter outline	Does the book hold together?	A paragraph or two per chapter
Sample chapters	Can you deliver?	Usually the introduction plus one or two chapters

A comparable title, or comp, is a recently published book that shares your audience. It shows the editor there's a proven market for what you're offering.

Writing the Overview

Everyone reads the overview, so write it last and revise it most.

1. Open with the problem or question the book answers, in concrete terms.
2. State your central argument in one or two sentences.
3. Say what the reader will know or be able to do by the end.
4. Explain why you, and why now.
5. Close with the format: approximate length, structure, anything unusual.

Here's a before and after for a hypothetical book on sleep and shift work.

Before: This book explores the many fascinating aspects of sleep and how it affects our lives, drawing on research and personal stories.

After: Night-shift nurses, drivers and warehouse staff are told to sleep eight hours, but nobody tells them when. Drawing on fifteen years as an occupational health nurse, I argue that shift workers need a schedule, not more willpower, and I show them how to build one around a rotating roster.

The second version names a reader, a claim and a reason to trust the author. That's what an editor carries into an acquisitions meeting.

If you can't squeeze the book into that paragraph, the central argument probably isn't settled yet. Try writing a single sentence stating the claim the book defends and keep it in view while you work. In a project workspace that holds your central thread, next writing move and status, that sentence sits beside the draft, so the overview has something firm to grow from.

Market, Comparable Titles and Platform

Keep this section specific. Editors aren't looking for "everyone who sleeps." They want the reader who'd pick your book up in a shop, and evidence that such readers buy books.

For comps, choose recent books from reputable publishers that share your audience. Skip the giant bestsellers everyone compares themselves to, since they tell the editor very little. For each comp, write two or three sentences: what it does well, and what your book does that it doesn't.

Platform is your existing ability to reach readers. That might be a newsletter, a podcast, teaching, speaking, a professional network or a track record of published articles. If your platform is thin, say what you're building and start building it now. Short pieces in relevant publications are one of the quickest routes, and a reusable article pitch template for editors makes it easier to send more of them.

The Chapter-by-Chapter Outline

The outline is where editors check whether you have a book or a magazine feature stretched thin. Each summary should do more than list topics.

For each chapter, write:

• A working title.
• The question the chapter answers, or the step it moves the reader through.
• The key material: stories, research, examples.
• How it hands off to the next chapter.

A sample summary:

Chapter 4: The Roster Is the Prescription. Most sleep advice assumes a fixed day. This chapter shows readers how to treat a rotating roster as a set of sleep windows, using the rosters most common in hospital nursing. It introduces anchor sleep through the story of a paramedic who rebuilt her week around one protected block, and sets up the question Chapter 5 answers: what to do on days off.

Read your summaries in order. If a chapter could move anywhere unnoticed, the argument has a gap. If two answer the same question, merge them.

Choosing and Polishing Sample Chapters

Choose samples for proof, not convenience.

1. Include the introduction if it states the promise clearly. It's often the chapter editors most want to see.
2. Add one chapter from the middle that shows your method at full strength, with evidence and story working together.
3. Avoid a chapter that only makes sense after three earlier ones.
4. Polish the samples to finished quality. A sample that reads like a draft suggests the whole book will too.

Starting each sample from the same chapter template with room for the aim, key points and handoff keeps the samples structurally in line with your outline.

Before you submit, read each sample against its summary. The chapter should deliver everything the summary promised, in roughly the same order. Then ask a trusted reader what the chapter argues. If their answer doesn't match your summary, one of the two needs to change.

Keeping the Proposal and the Book From Drifting Apart

Once the book sells, you'll write for months or years. Research turns up surprises, chapters split and merge, and the argument sharpens. That's healthy. The trouble starts when the proposal, which your editor still treats as the plan, quietly stops describing the book you're writing.

A few habits keep them aligned:

• Keep the proposal as a living document next to the draft, not in an old email attachment.
• When a chapter changes purpose, update its outline summary the same day.
• Save a named version of the proposal at key moments, so you can show your editor what changed and why.
• Keep sources attached to the claims they support, so the evidence you promised is easy to find later.

That last habit matters most for research-heavy books. With a research notebook that answers questions with page citations, you can check whether a source really supports a claim in your proposal before it turns up in chapter seven.

We built Strut for this kind of long project. Here's how Strut works for nonfiction authors: notes, imported sources, the proposal and the chapters live in one project, with version snapshots and a frozen review link you can send your agent. The free plan gives you one project with up to three documents, and Pro removes those limits. You'll find the details on Strut's plans and pricing page.

The Short Version

A nonfiction book proposal sells the book before it exists. Nail the overview in one paragraph, pick comps that share your reader, show how you'll reach that reader, and write chapter summaries that make the argument visible. Choose sample chapters that prove the promise, polish them fully, and keep the proposal updated as the book grows so your editor is never surprised.