How to Write a Cookbook Proposal
How do you write a cookbook proposal? You write a short business case for the book: what it is, who buys it, why you are the person to write it,…
How do you write a cookbook proposal? You write a short business case for the book: what it is, who buys it, why you are the person to write it, what else is already on the shelf, and a sample that proves you can deliver. A proposal is not the cookbook — it is the document that convinces a publisher to pay you to write the cookbook. Most proposals run 15 to 30 pages, and the sample recipes matter more than anything else in it.
What is a cookbook proposal, and who needs one?
A cookbook proposal is the pitch you send a publisher when you want a traditional publishing deal instead of self-publishing. The publisher reads it to answer one question: will this book sell enough copies to earn back its advance and its production cost? Cookbooks are expensive to produce — photography, food styling, testing — so publishers are careful, and a strong proposal is what gets you past the first read.
If you plan to self-publish, you do not need a proposal. You need the book. The proposal only earns its effort when a publisher’s money and distribution are the goal. Know which route you are on before you start writing one.
What goes in a cookbook proposal?
A standard proposal has six parts. Write them in this order, because each one answers the objection the previous part raises.
1. Overview. One to two pages: what the book is, in one sentence, and why now. Name the promise — the reader’s problem and the food that solves it — and say what makes this book different from the cookbooks already on the shelf. If you cannot state the difference in one sentence, the concept is not ready.
2. Audience. Who buys this book, described precisely. “People who like cooking” is not an audience. “Home cooks in their thirties cooking weeknight dinners for a family, who own an air fryer and want faster meals” is an audience. Say how big it is, where those readers gather, and why they would pick your book over the free recipes online.
3. About the author. Why you, specifically. Your cooking background, your audience, your platform — a newsletter, a social following, a restaurant, a column, a community. Be honest about the numbers: a real audience of a few thousand engaged readers is more convincing than a vague claim of reach. If your platform is small, say what you will do to build it, and say it concretely.
4. Competitive titles. Four to six cookbooks already selling in your space, each with its title, author, publisher, year, and price — and one line on how your book differs. This section proves you know the shelf you are competing for. Never claim there is no competition: a shelf with no competition is a shelf with no buyers. Pick titles that are close enough to prove the market exists, and different enough to leave your book room.
5. Outline and structure. A chapter-by-chapter outline with a recipe count per chapter. Show the shape of the book: how it opens, how recipes are grouped, how many recipes in total. A cookbook of 80 to 100 tested recipes is a common shape for a first book — but the right number follows the concept, not a rule. Include the features that carry the book: headnotes, technique pages, menus, substitutions.
6. Sample recipes. Three to five finished, tested recipes, written exactly as they will appear in the book, with headnotes. This is the part editors actually cook from and judge. Choose recipes that show your range — one simple, one signature, one that shows the book’s idea at its best. Test every one more than once, and have someone else cook from the written instructions to catch the steps you skipped because you already knew them.
How do you write the sample recipes?
Write them as finished pages, not as notes. Each recipe needs a headnote that says why this recipe and what the reader gets, a yield, a time, an ingredient list in the order used, and numbered steps a stranger can follow without you in the room. Use exact quantities, name the pan size, say what “done” looks like. A recipe that only works when the author is standing next to the reader is not a recipe yet.
Test each sample recipe at least twice, and get at least one other person to cook it from your written text alone. The gaps they find — an oven temperature you forgot, a step in the wrong order — are the gaps a publisher’s recipe tester would find, and finding them first is the point.
What mistakes sink a cookbook proposal?
- A concept with no difference. “A cookbook of family recipes” is a starting point, not a proposal. The difference is the book: one cuisine, one method, one constraint, one reader.
- An audience described as everyone. A book for everyone is a book for no one, and an editor knows it. Name the reader precisely.
- Competitive titles missing or dismissed. Skipping this section, or claiming no competition exists, tells the editor you have not looked at the shelf.
- Untested sample recipes. Recipes that have only been cooked once, by you, from memory, will not survive a test cook — and a failed sample ends the read.
- A platform claim you cannot back up. Inflated follower numbers are easy to check. Honest numbers with real engagement win over big numbers nobody believes.
A proposal checklist
- The book’s promise fits in one sentence, and the difference from existing books is named.
- The audience is described precisely — who they are, where they gather, why they buy.
- The author section is honest about background and platform, with real numbers.
- Four to six competitive titles are listed with title, author, publisher, year, and price, each with your difference.
- The outline shows every chapter and a recipe count per chapter.
- Three to five sample recipes are finished, tested twice, and cooked once by someone else from the written text.
- The whole proposal has been read aloud once, to catch the sentences that only made sense in your head.
Finish that checklist and you have a proposal an editor can say yes to — or a clear answer that the concept needs more work before it is ready to send. Either outcome is better than sending a half-built proposal and getting a silence you cannot learn from.
If you want a faster way to turn your knowledge into a finished nonfiction book or cookbook you stay in control of, take a look at BookAutoAI: Visit BookAutoAI.com
Start here: new to cookbooks? Read our Cookbooks hub and our guide How to Write a Cookbook and Get It Published.


