When should I revise my query letter?
- Revise based on response patterns, not individual rejections.
- A weak query shows up as a low request rate across many sends.
- A rough benchmark: few or no requests after 8-10+ personalized queries.
- Lots of requests but passed fulls points at the manuscript, not the query.
- Change one variable at a time so you can read the result.
Revise your query after a pattern emerges, not after a single rejection. If you have sent eight to ten or more personalized queries to well-matched agents and gotten few or no page requests, the query (or the hook) is likely the problem and is worth reworking. If agents request pages but pass on the fulls, the query is working and the manuscript is the issue. Let the request rate, not any one reply, drive the revision.
Chapter i·Why it matters
The query and the pages fail in different ways, and the response pattern tells you which. Revising the query when the real problem is the manuscript — or vice versa — wastes a fresh batch of agents on the wrong fix. Waiting for a pattern of roughly a dozen responses, then changing a single element, lets you actually learn from the next batch instead of guessing.
Chapter ii·What to include
- A minimum sample — about 8-10 personalized queries — before judging.
- A request-rate read: are agents asking for pages or not?
- A diagnosis: low requests points at the query; passed fulls at the book.
- One change at a time (the hook, the comps, the opening line).
- A fresh batch to test the revised version.
- A tracker that makes the pattern visible.
Chapter iii·Example
A writer queries twelve well-matched agents with a personalized letter and gets zero requests. The pattern says the query, not her list, is the problem. She rewrites only the hook — leaving the rest constant — and sends the next batch of ten. Three request pages. Because she changed one variable after a real pattern, she knows the hook was the issue and can keep going with confidence.
Chapter iv·Related questions
WriteLoom's Pitch tracker shows your request rate across batches, so you revise the query at the right moment and change one thing at a time.
See your request rate