How Allison Hunter's query letter (and One on One) used revisions, comps, and a teased secret to get agent attention

TLDR

• A successful query letter isn't "one-and-done." It's revised like a living draft, using feedback loops until the submission version actually earns its spot.
• For romance, the query works when it nails tone (fun + seriousness) and keeps the romance central with clear stakes.
• The sweet spot for how much to reveal in a query secret is "curiosity now, explanation later." Too much becomes backstory; too little becomes noise.
• Comps aren't decoration. They're brief proof of fit—so improving hook and comps in a query starts with matching reader expectations, not impressing taste.
• The best openings get rewritten under pressure: the hook and comparison references should be stress-tested until they read clean and specific.

Opening — subject context

A lot of writers approach querying like it's a test of worth. Like, if the match is "perfect," then admiration should mean we should feel scared to submit. That fear is real—even for competent writers who can absolutely finish a manuscript.

But here's the uncomfortable truth: admiration doesn't block your chances. It just makes the page feel heavier. In this case study, the writer revised the query multiple times and reworked it again after helpful feedback from earlier submissions—until the pitch felt sharper and the manuscript felt more right alongside it.

The subject here isn't just "a query that worked." It's a writer treating the pitch as something to refine with intent: tightening tone, sharpening the hook, adjusting comparative references, and experimenting with how much to reveal in a query secret so the agent gets curiosity without the query turning into backstory-heavy recap.

And the agent response tells you what mattered: romance subgenre signals landed fast (including sports romance, enemies-to-lovers, and workplace expectations), the character-driven intrigue clicked, and at least one memorable line kept echoing beyond the initial pitch.

If you've ever stared at your own query letter thinking, I'll fix it later, this is the opposite approach. The "later" happened—over and over—until the submitted version was the strongest one.

"Revise the pitch like a living draft—feedback and reworking can create your best submission."

Body — structural breakdown

How they treated the query letter as a living document

The big structural choice wasn't just what got written—it was what got changed, when, and why.

This writer revised the query multiple times, then went back again after feedback from earlier submissions. That pattern matters because it attacks two problems at once:

1. The manuscript pitch isn't stable. When you revise the story, your opening, your stakes, and even your character choices shift. If the query never shifts with it, the pitch starts lying by accident. 2. The first version is a guess. Your earliest draft might be "accurate," but it's not yet "agent-readable." Revision is how you turn your good intentions into a document that lands quickly.

Here's the move: the writer reworks the hook and comparative references when stressed. Not by spiraling into "maybe I should change everything," but by treating specific components—opening line, framing, comps—like they're mechanical parts you can swap until the engine runs.

"Tone, romance focus, and clear stakes beat vague summaries every time."

Treating the query letter as a working document rather than a final artifact changes everything. Each revision cycle teaches you what's actually landing with agents and what's still muddled.

What to copy (practical):

• Write Draft 1 as a full pitch, not a masterpiece.
• Submit it (or use it) long enough to learn what feedback you actually get.
• When feedback arrives, don't just edit for correctness. Edit for readability and attention—especially the first paragraph and your comp sentences.
• Treat "final" as a moving target until the submitted version feels like the cleanest version you can defend.

What to skip (common waste):

• Don't assume your query is done because the plot summary is technically accurate.
• Don't polish comps as if they're decorations. Comps are for fit proof, so they have to match the romance reader expectations your story is promising.

This is also where the "perfect match" intimidation pain point gets defused. If you're worried that submitting means you're admitting the agent is judging you personally—yeah. That feeling is dumb and real. The cure is process: revision cycles reduce anxiety because the pitch becomes something you actively shape, not something you hope will be interpreted kindly.

If you're tracking revisions across multiple submissions, tools like Query Dashboard are basically spreadsheets for sanity—so you're not re-learning the same lessons every time you reopen the file.

---

How they balanced mystery and clarity in a secret

Romance queries live or die on pacing—yes, pacing. The query is not the book, but it still needs a rhythm: promise, pressure, payoff.

In this case study, the writer experimented with how much to reveal in a query secret early on. The goal wasn't to be coy. It was to be strategic.

Too much reveal and you kill the forward motion. The secret stops being tension and turns into backstory. Readers (and agents) start skimming because they feel like they've already gotten the emotional core.

Too little reveal and you create a different problem: confusion. If the agent can't tell what's at stake, the intrigue reads like random fog instead of character-driven compulsion.

So the writer tested a range—enough to create curiosity, without turning the query into "chapter one minus the romance."

This maps directly to the audience pain point: writers struggle with "mystery vs clarity"—how to handle a protagonist's withheld information so it lands as compelling rather than evasive.

The structural mechanism was character-driven intrigue. The agent responded specifically to hints that the protagonist was withholding information for a reason. That's the difference between:

• "I refuse to explain because plot reasons"

and

• "I'm hiding this because my character's motives are dangerous and complicated."

That distinction can't be faked with vague language. It has to show up as choice.

Here's what it looks like in principle (not as copied wording):

• The query sets up the protagonist and her surface situation.
• Then it hints at the secret early enough that the agent wonders how it will matter.
• It gives enough clarity for the stakes to be obvious.
• It holds back the full explanation until the manuscript can do the heavy lifting.

If you want the one-sentence rule for how much to reveal in a query secret, it's this: reveal the reason the secret matters, not the entire history of the secret.

What to copy (practical):

• Identify the secret's function: Is it protecting someone? Destroying someone? Saving the protagonist from consequences?
• In the query, explain the effect of the secret on decisions—then cut to the manuscript for the why.
• Run a quick cut test: if a paragraph would feel like "backstory exposition" in a novel, trim it.

What to skip (common waste):

• Don't over-explain the secret to prove you're "being clear." Clarity isn't the same as full disclosure.
• Don't treat the secret like trivia. In romance, the secret should bend the relationship, not just color the plot.

---

Comps and tone as romance signposts

The agent in this case didn't just react to prose vibes. They responded to specific romance subgenre signals—and those signals do real work.

This is where sports romance, rom-com, and workplace expectations matter. Subgenre signals quickly establish audience expectations, which helps an agent answer the question: Who is this for, and why will they care right now?

Your query can be beautiful and still fail if it doesn't guide the agent to "this belongs on the shelf with X readers."

In this case study, the agent highlighted tropes like:

• sports romance
• enemies-to-lovers
• workplace romance

Agents use these signals as a fast filing system: they read the book's subgenre markers and immediately know which shelf readers will expect to find it on.

The writer also used comparative references (comps) to support pitch and tone. Comps in a romance query aren't there to show off reading history. They're there to briefly explain why each comparison fits the book—and whether the tone matches.

So improving hook and comps in a query starts with a brutal question: If an agent believes the comps, do they also believe the emotional experience?

If the comps are wrong, the reader expectations you build in the first pages of the pitch will contradict what the manuscript actually delivers.

What to copy (practical):

• Use comps to reinforce both content and vibe.
• Put comps near where the hook sets up tone and central tension.
• Keep the comp sentence short enough that it doesn't become a mini-essay.
• Verify that your comps support the same romance promise the hook makes (sports-romance energy should feel consistent, not swapped for generic sweetness).

What to skip (common waste):

• Don't use comps that match theme but not romance texture.
• Don't sprinkle romance words as decoration ("romantic," "feels," "chemistry") without subgenre clarity.

The writer treated the hook and comparative references as reworkable instead of fixed—not as precious elements but as parts to refine. When stress hit, they reworked the hook and comps because those are the pieces you tend to sabotage under pressure—your brain reaches for generic phrasing instead of exact signals.

If you're building a romance pitch from scratch, it helps to think in subgenre terms—especially if you're aiming at a sports romance enemies to lovers query. The query should act like a sign at the entrance of the store: it tells the right people they're in the right aisle.

---

Hook rewrites when stressed: what changed and why it mattered

Here's the part writers hate to admit: under stress, we stop editing with intention and start editing with panic.

This case study shows the opposite. The writer reworked the hook when stressed—refining it under pressure rather than freezing. Not by spiraling into "maybe I should change everything," but by treating specific components—opening line, framing, comps—like they're mechanical parts you can swap until the engine runs.

When the writer revised the hook and comparisons, that tells you something important about the craft mechanics:

• The hook isn't just "a good first line." It's the first contract with the agent.
• Comparative references aren't just "supporting context." They're part of the contract too.
• If either contract piece is sloppy, the agent's brain works harder than it should—and effort costs attention.

A case-study-worthy query doesn't just describe the book. It gives the agent an easy "yes" path.

So the hook rewrite functioned like a clarity lever: tighten what's promised, tighten what's compared, tighten what the reader is about to feel.

What to copy (practical):

• Rewrite the hook last, after you finalize the secret reveal amount.
• Make sure the hook sentence does three jobs fast:
• establishes tone
• ties romance to stakes
• signals subgenre expectations (sports romance / enemies-to-lovers / workplace romance)

What to skip (common waste):

• Don't keep the hook if your secret reveal strategy changed.
• Don't keep "almost right" comps if the tone promise changed.

What to include in a romance query is clarity about what makes your story distinct in its subgenre. When you're revision-ready, the hook and comps should both point the agent toward the same emotional terrain.

And because this is a case study about submissions, it's worth noting that you're not submitting to "prove you're ready." You're submitting to learn what the market and agents actually respond to—and then revising toward the strongest pitch you can write.

If you're building a habit around revision and tracking submission states, Query Dashboard is one of the least glamorous but most powerful ways to stop losing time in the loop.

Lessons / Takeaways

A few moves in this case study are copyable across romance subgenres (including sports romance and rom-com):

• Revise more than once. If the query is a "living document," feedback from earlier submissions teaches you what clarity actually sounds like—so each new draft gets sharper.
• Balance mystery and clarity through the secret's function. Use how much to reveal in a query secret to create curiosity without backstory sprawl.
• Let romance subgenre signals do the heavy lifting. Tropes like enemies-to-lovers or workplace romance give agents a fast map.
• Check whether comps match what your hook promises. Comps should support the same emotional experience that your hook sets up.
• Use stress editing as a trigger to rework, not freeze. When you're stressed, your first instincts tend to get generic—so rewrite the hook and comp sentences until they're specific again.

Frequently asked questions

The bottom line

If you're waiting for a "perfect match" moment before you submit, this case study gives you a better target: revision until your pitch stops guessing and starts signaling. Take your current query letter, rewrite the hook with your subgenre promise in mind, and test how much to reveal in a query secret until it creates curiosity without backstory sprawl. Learn how to revise a query letter by submitting and revising based on real agent feedback, and make sure what to include in a romance query centers on tone, subgenre signals, and the secret's emotional weight. Then submit the strongest version you can stand behind—and let feedback earn the next revision.