TL;DR
A book proposal is a business pitch. Editors are asking whether they can sell it, not whether it’s beautiful. Learn to make the market case, to play fiction and nonfiction by their different rules, and to build each part of the submission for its job. The course also shows how to use AI as an assistant to assemble a professional package, never to make the case for you.
Most writers approach a book proposal as if it were an audition for their prose, and that misunderstanding is why so many proposals fail. A publisher isn’t a patron of the arts. A publisher is a business that needs to turn a profit, and when an editor reads your proposal they’re not asking whether it’s beautiful.
They’re asking whether they can sell it to their boss. Whether the boss can sell it to the sales team. Whether the sales team can convince a bookstore to stock it. This course teaches you to write the document that answers those questions.
Writers who treat a proposal as an audition lose years to it. They polish a sample chapter until it gleams and attach a paragraph about how much the book means to them. Then the silence comes, and they decide the industry hates them, when the industry simply never saw a reason to say yes. That silence is avoidable, and it frustrates me how few writers are told so.
Stop thinking of a proposal as a sample of your writing. Think of it as a business pitch, because that’s what it is. Write it as one and your odds change.
The pitch you didn’t know you were making
Your proposal is a business case, and it works like a startup pitch.
Investors don’t fund a company because the founder is passionate. They fund it because it shows a market opportunity, a competitive advantage, and a plausible path to profit. Your proposal makes the same case for your book. You understand the market. It positions your book against its competitors. It proves you know who the audience is. And it shows you can help sell the thing once it exists.
The writing quality matters, but it’s one factor among several. This reframing changes what you put in the proposal and how you frame it. Don’t lead with how much the book means to you. Lead with who will buy it and why. What space it fills that competing books don’t. How many of those readers there are. You’re answering the editor’s real question. Can I make money on this? A proposal that answers it directly stands out immediately from the pile that only asserts the book is wonderful. Passion is assumed. Market awareness is rare, and it’s what opens doors.
A proposal that opens with how much the book means to the author makes my eyes glaze. Every writer cares. What’s rare is a writer who can tell an editor where the buyers are, and I think that writer gets taken seriously on page one.
Watch: How to write a Non-Fiction Book Proposal, Reedsy
Fiction and nonfiction play different games
The most common proposal mistake isn’t knowing that fiction and nonfiction sell completely differently.
Writers pitch one as if it were the other. Nonfiction sells on the proposal, often before the book is written, because the idea, the author’s authority, and the market can be judged without a finished manuscript. Fiction generally sells on the finished manuscript, because a novel’s value is in the execution, which can’t be evaluated from a summary. Confusing these two wastes everyone’s time.
The practical consequence is that a nonfiction writer should be perfecting the proposal itself, the argument for the book’s market and their platform to reach it, while a fiction writer should mostly be finishing and polishing the novel, because that’s what will be judged. A nonfiction proposal is the product you’re selling at this stage. A fiction proposal is a door-opener whose job is to get someone to request the manuscript that will do the real selling.
Knowing which game you’re playing tells you where to put your effort, and playing the wrong one, sending a detailed proposal for an unfinished novel, marks you instantly as someone who doesn’t understand the business. A detailed proposal for an unfinished novel is the mistake I’d most like to stamp out. It’s an understandable error, born of reading nonfiction advice and assuming it applies to everything, and it costs the writer months they could have spent finishing the book.
The submission package and its parts
A submission has distinct components that do distinct jobs, and confusing them is another way writers stumble. The query letter is the short pitch whose only job is to get someone to ask for more. The proposal is the fuller business case, mainly for nonfiction. The manuscript is the work itself. Each has its own purpose, and each is judged differently, so you have to know which one you’re writing and what it needs to accomplish instead of blurring them together.
The query in particular is misunderstood. Its job isn’t to tell the full story or make the complete case. Its job is to open the door, to be interesting and professional enough that the reader asks to see the proposal or the manuscript. A query that tries to do everything, cramming in the full plot and every selling point, defeats itself, because the query is only a hook.
Understanding the job of each part, the query to intrigue, the proposal to make the business case, the manuscript to deliver, lets you build each one to do its actual work instead of asking one document to do a job that belongs to another.
What opens doors versus what closes deals
There’s a useful distinction between the things that get you noticed and the things that get you a contract, and mixing them up leads writers to over-invest in the wrong stage. What opens doors is a sharp hook, a clear sense of market, a professional presentation, the things that make an agent or editor want to look closer. What closes deals is the substance behind the hook, the actual quality and viability of the book, the proof that the opportunity the hook promised is real. Both matter, at different moments.
The mistake is treating the door-opener as the full job, polishing the pitch to a shine while the underlying book or platform can’t support the promise, and that leads to requests that go nowhere. The pitch gets you in the room, and then the substance has to deliver, so building both is the work, a hook strong enough to open the door and a book and case solid enough to close once you’re through it.
Polish without substance bothers me more than a rough pitch does. A sloppy query just gets ignored. A gleaming query for a book that can’t deliver burns a request, and sometimes a relationship with an agent who won’t open the next one. Writers who understand this sequence stop pouring all their energy into the query and start making sure that what the query promises is there to be found, and that turns interest into a deal.
How can AI help with Book Proposals?
The book is yours and the pitch is yours to make. No tool sells your work for you. But a tool helps with the mechanical parts of assembling a professional submission. You can use AI to draft several versions of a query hook so you have options to react to and sharpen. You can have it check your proposal against the standard components to catch what’s missing.
You can use it to research comparable titles so your positioning is grounded in the actual market. It handles the assembly. You make the case.
A writer who learns to think like the editor’s boss walks into the conversation as a business partner, and I think that shift does more for a writer’s odds than any amount of prose polishing. A book pitched as a sales case can feel cold at first, and that pitch is the most respectful thing you can offer for the busy person reading it.
Explore the hub
Writing Courses: the full set of writing courses, gathered in one place.