Sandra Proudman

10 Tips for a Stronger Query

#DVPit is right around the corner! 

Many people will be querying for their first time, or may be querying for a second, third, fourth, seventh manuscript. 

I’ve sent out more queries than I probably care to admit…but I’ve learned so much along the way. And I wanted to share 10 tips for a stronger query! 

ELIMINATE THE WHY?/HOW? I participated in a query bootcamp last year, and the agent that I worked with wrote Why? throughout my query. It was such an eye opener! The number one goal now when I write a query is to eliminate any chance for an agent/editor to ask Why? a certain fact is how it is. Or why a certain character makes a certain choice. i.e. Samantha is a vampire with a soul who goes on a secret mission. Well: Why/how did Samantha turn into a vampire? How did Samantha lose her soul? Why is she going on a secret mission? And what is this secret mission? 

DON’T BE VAGUE: This one definitely lends itself to cracking Tip #1. There’s no reason to be vague in a query. Being mysterious isn’t really a good thing. It’s okay to reveal some juicy info that a reader won’t find out until the last chapter to an agent/editor you’re trying to hook. And you want to be as specific as you can so that your query makes sense.

 

IT’S OKAY NOT TO INCLUDE EVERY STANDARD PART OF A QUERY: I spent so much time stressing out about my bio when I started querying. It’s okay not to include one at all! Focus on telling an agent/editor about your story. You also don’t have to include a note on why you’re pitching said agent/editor.

ASK A FEW PEOPLE TO READ YOUR QUERY LETTER: Having at least five other people read your query is so key. You NEED the feedback. Trust me. You may think you’ve written the perfect query and then someone will spot a mistyped word you’ll be shocked to know you missed!

FOCUS ON YOUR STORY: I’ve been seeing a lot of agents on Twitter post the crazy things people include in their queries. Like commenting on how an agent looks. Guys, this is a professional cover letter. Don’t be weird. And don’t be rude or mean or demeaning to someone you’re asking to consider you for a business partner.

COMP TITLES: My biggest suggestion here is to read widely! You’ll be surprised how comp titles start coming to you when you read and keep track of books within your genre.  You can also compare your writing to that of another author. Even a feeling another book gave you. It’s perfectly okay to say your MS is written in a similar voice as X, Y, and Z.

 

ONLY USE THE NAMES OF THREE CHARACTERS: I love this rule of thumb! Only using the names of three characters, which are usually your MC, your antagonist, and your romantic lead, helps you figure out Tip #8!

CHOOSE ONE STORYLINE: How do you condense a novel that’s 50,000-120,000 words down to one page? UGH! So hard sometimes! The biggest thing is to focus on your turning points. Set the stage with your MC’s wants and your setting. Then describe the turning point that sends your MC down X path and mission. And then describe the challenges your MC faces to get their mission done. And finally describe the consequences your MC will face if they fail. And what they’ll get if they’re victorious.

IT’S OKAY TO DESCRIBE YOUR WORLD FIRST: A lot of people will tell you to start with your main character. But there are times when you NEED to describe your world first so that the rest of your query to make sense. That’s OK!

USE YOUR QUERY TO REALIZE YOU MAY NOT BE READY TO QUERY: I wish I’d have known this before when I first started to query. My query for my first manuscript was A MESS! And the reason was because there was too much going on in the manuscript itself. If you’re finding you can’t make your query concise enough any way you turn it, it’s time to relook at your manuscript. And it’s a good thing to do this before your start to query!

 

Whelp! I think that’s all I have for today. I hope that these query tips have helped you in any small way. If you have any questions, don’t be afraid to chat me up on Twitter @sandraproudman!

And as we enter #DVPit: