Jul 142011

I am a long time member and BIG time fan of AgentQuery Connect.  For those aspiring writers who do not know AQ run don’t walk to the website as it is a fantastic source for information on every step of the road to being repped and published, a very supportive writing community, and (most importantly for the purposes of this post) good spot to get feedback on a query letter before you send one out.

Now anyone who’s ever drafted a query letter (the pitch letter writers send to agents) knows it takes time.  The letter is a vital sales document. Write it well and you snag the interest of an agent and a coveted request for a partial or full. Write it poorly and you may never even warrant a form rejection.  Writing a good query is not easy (there are hundreds if not thousands of articles and blog posts offering advice on how to compose a good letter).  BUT should it really take months and drafts in the double-digits?

At the risk of aggravating many I say no.  In fact I say, NO, NO, NO.  What I’ve noticed, watching query critique threads over the months and years, is that writers become paralyzed by fear and good intentions.  Writing their query becomes a Sisyphean struggle (you remember, the guy who had to push the big rock up the hill over and over) and in the process time, enthusiasm and confidence can be lost.  At some point the incremental improvements their letter is arguably making are not worth the agony.  More than this, letters can lose voice (see my post on this topic at From the Write Angle).  Looking at critique threads with ten, twenty, thirty, even fifty versions of a single query, I want to scream GET ON WITH IT, or SEND THE DARN THING.  But that kind of verbiage in individual critique threads would hardly be appropriate.

 So I am saying it here. Just DO it. Query.  I am not saying send your first draft.  I am not saying don’t seek critique.  I am saying all things in moderation.  How many drafts of my letter did I do – maybe four.  How many people did I show it to for review before it went out?  Five (and two of them weren’t even writers).  Did it work?  More than uncommonly well (I had a very high request rate, snagged an agent I adore and now have a publishing contract).  Could my letter have been better? Sure. But if I were still working on polishing it, then my book wouldn’t be coming out in March 2012 would it?

7 Responses to “Just DO It!”

  1. Well said! My query isn’t in the high two-figures, but I know it still needs work. Still, I agree that I shouldn’t keep revising and revising just for the sake of revising. Send it, already!

  2. Love this! It’s so true, too. I hope to be querying my current WIP by the end of the year, and I’ll be sure to follow your advice. I know I tend toward the paralyzed by fear side of things sometimes 🙂

  3. Very well said. I agree with the losing voice part. I’ve seen queries on AgentQuery Connect that I thought were better in the 2nd draft than the 15th draft. It’s a matter of opinion of course, but I think you can squeeze the life out of a query by revising it too much. Same thing with a novel.

  4. Well said!

    I’ve watched the same thing in the threads at AQC. The query, just like the manuscript, has a point in which you must say, “it is finished”

    I’ll add this to your Just Do It,

    Just Do It Now!

    Great points.

  5. I suspect the problem is that most authors have a perfectionist streak — give us a task and we will over-do it. But let’s face it the slippery slope of perfect can lead to the pit of never getting done.

  6. Hello Sophie~

    Do we get to see a copy of your query letter?? Pretty please?


    • Hi Ellise — The query that hooked my agent was for a project that, ultimately, did not sell. Because that manuscript may be back on submission later in my career I do not feel I can post the letter. Sorry.

Leave a Reply to Sophie Cancel reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>