Jayne Ponders Writing a Book Proposal
Here's the thing: I write whole books, not query letters, synopses and cover letters. And as for the first three chapters of my proposed book (which often accompany a formal book proposal) well, there's just no point. The sad fact is, I never know where my book is going until I write the last chapter. Then I have to go back to the beginning and rework those first three chapters and all of the others that follow until they fit my final vision of the story. Two or three and sometimes four times to get it right. Therefore, sending an editor the first three chapters when the rest of the book remains unwritten would be extremely misleading, to say the least.
Luckily, I am now working with an editor who understands that I write lousy proposals and who has seen enough of my work to trust me when I turn in two pages of ramblings and ruminations about a possible plot and character conflicts that she knows probably won't look anything like the final story.
Ah, you say, that's all well and good for you. You've published a lot of books so editors will now buy you on spec. Maybe. But I don't like to give editors rude surprises. So what do I do when I change publishers as I did a few years ago or when I want to sell an entirely different type of story -- the first two of what became my Jayne Castle Ghost Hunter books, for example? I do what I did back at the beginning of my career. I write the whole dang book first and then send in the proposal.
Yes, it is a lot of work but there are two big advantanges. First, no surprises for the editor (or me). Second: The editor won't judge my writing on the basis of something I don't do at all well: the Proposal.
What do you do when you're faced with having to do something you know you don't excel at? Got any secrets?


















