How to Write a Cookbook Proposal - Tips for Getting Started
If you want your cookbook to be published by a major publisher, you will need a platform and a .
Writing a cookbook proposal requires more than just having a stash of recipes. As cookbooks include not only writing, but recipes and, most times, photographs, cookbook proposal is a has some special requirements:
Your cookbook proposal should have a personal vision
, which she did in Mastering the Art of French Cooking. My co-author Janice Fryer and I wanted to systematize and simplify decorating, which we did in .
More than with many other non-fiction books, readers interact with cookbooks, and help create the experience. They feel incredibly personal. So whether it's sharing little-known recipes from your homeland, creating low-calorie versions of favorite meals, or allowing your customers to take home your restaurant's favorite dishes, your cookbook proposal should have a consistent, identifiable concept that feels so you that only you can write it.
Here are some .
Know your audience and how they cook
Is your reader a busy mom or dad with little time to spare cooking meals? Or a wannabe chef, who likes to challenge herself or himself on the weekend with 30 ingredients? Or Julia Child's audience of "servantless American cooks." It's important to be able to articulate who the end user of the cookbook will be, and how your concept will appeal to them.
And it's essential that your recipes match your intended cooks in simplicity vs. complexity, ingredient and equipment needs, etc. If you're writing about food for campers, you don't want to include recipes that require three different pots and pans.
Even better if you can make your working title really, succinctly convey the concept. If you'd like some cookbook titling insights, read this case study on to a much broader market.
Thoroughly test the proposal recipes
As in any book proposal, your cookbook proposal will have a sample chapter — and that sample chapter needs to include recipes.
Many of the best cookbook editors can tell if a recipe will "work" just by reading it, and there are some who will test proposal recipes to make sure they work. So, especially for the proposal, test the recipes you include to make sure they're foolproof and delicious. Here's
Read more about recipe development:
Have an idea of your photography plan
Do you envision a photo for each step of the recipe in your book, or just finished dishes? Photography (often the author's responsibility) and color printing production cost money for, so it's good to have an understanding of photography costs and planning before you commit to providing 500 color photos you can't afford to produce.
Read more about cookbook photography:
Be realistic on what and when you'll deliver a manuscript.
That is, don't underestimate the work involved for the finished cookbook. Developing a cookbook makes demands on its author that writing, say, a or doesn't — that is, not only recipe and recipe headnote writing but recipe testing and photography. The amount of author resources (time, energy, money) a cookbook takes shouldn't be underestimated.
When you write a proposed number of recipes or the estimated manuscript delivery date in your proposal, make sure you understand how much time it will take to get the writing and other work done.
And read these . That is, what constitutes professional-level cookbook content, including organization, recipe titles, and more.