Book Proposal Structure: What Publishers Expect

Book Proposal Structure: What Publishers Expect

The Standard Book Proposal Structure (Order and Purpose)

Editors skim in a fixed order. Give them a clean road through your pitch. Use this sequence, keep each section tight, and show proof at every turn.

Overview and Hook

Purpose: win attention fast and frame the sale.

Positioning formula:

For [specific reader] facing [clear problem], [Book Title] offers [distinct solution], unlike [named comps] which focus on [narrow angle] or [different audience].

Example:

For first-time engineering managers drowning in meetings, The First 90 Days of Tech Leadership gives a 12-week playbook with scripts, metrics, and team rituals, unlike classic management guides aimed at general business readers.

Open with a quick scene, a stat with a source, or a sharp question. Then state the promise in one sentence. Keep buzzwords out.

Target Audience

Purpose: show buyers exist and know where to find them.

Example:

Primary: new managers in North American tech firms, ages 25 to 40, first leadership role, 1 to 3 years experience. Secondary: HR leaders seeking scalable training for new managers. Use cases: promotion kits, team workshops, manager roundtables. Market size: 380,000 engineering managers in the U.S., Bureau of Labor Statistics, plus 120,000 annual promotions, LinkedIn Workforce Report.

Market Analysis and Comparative Titles

Purpose: prove demand and show difference without dismissing strong books.

Example entry:

Close with one paragraph on your angle. Use specifics. Scope, audience, structure, features. No vague claims.

Author Platform and Credentials

Purpose: reduce risk. Show reach, trust, and access.

Lead with top credentials linked to the topic. Then numbers.

If gaps exist, name them and give a plan. For example, quarterly webinar series, podcast tour, strategic co-marketing with two associations.

Marketing and Publicity Plan

Purpose: show a credible path to sales.

Organize by channel with timelines and numbers.

Pre-launch, 3 to 6 months out:

Launch window, month 0:

Months 1 to 3:

Include budget lines you own. Ad spend, design, travel. Assign owners and dates.

Book Details

Purpose: set expectations for product and schedule.

Chapter Outline, Annotated Table of Contents

Purpose: show logic and momentum, plus outcomes for readers.

Provide 1 to 2 paragraphs per chapter. State purpose, key ideas, evidence types, and takeaways.

Example entry:

Chapter 3, One-on-One Meetings That Build Trust, 4,800 words. Purpose, turn weekly meetings into a performance engine. Covers a simple agenda, question bank, and a note system. Evidence from two internal studies at mid-size SaaS firms and three manager interviews. Readers leave with scripts for tough moments, a template, and a 20-minute cadence.

End the section with total chapters, expected length per chapter, and notes on features by chapter.

Sample Chapters

Purpose: prove the voice and the promise match.

Include the introduction plus one representative chapter. Total 5,000 to 10,000 words. Polish to near-publication quality.

Quality bar checklist: