Stop Flexing the World: Make Your Query Letter's Specificity Do the Lifting

10 min read
blog hero · recognition dread
Photo: Felicity Tai / pexels

TLDR

TLDR
Photo: Zhine Pics / pexels
  • Most query letters fail because they lead with worldbuilding and vibes instead of specific human pressure.
  • "Personalization" is a fit statement that points to something real about this book and this reader—one fast sentence, not a paragraph.
  • In YA fantasy, grief works best when it's shown as daily work: logging, routines, recurring fear, and what the protagonist can't stop thinking about.
  • When you have two grieving leads, you don't just "add romance." You build a connection engine where encounters force both characters to confront loss.
  • The last gut-check for your query: does it end on a sacrifice decision that costs something for both leads?
  • Include comp-style tone framing, but only as expectation-setting; the query still needs plot clarity and emotional stakes.

Opening

blog general · personalization stakes
Photo: kintsu / giphy

Writers keep saying it: "I'll just describe the setting better."

Then the query letter turns into a scenic tour. The fairy-tale vibe shows up. The liminal mood shows up. Snarky romance flavor shows up—fine. But the agent stops at the first paragraphs and thinks, Cool. Now where's the pressure?

We can all appreciate a cursed river and a ferryman framework. But here's the contrarian part: worldbuilding is not the hook. Specificity is. Not "cool magic." Not "mysterious atmosphere." Specific work someone does every day, specific fear that repeats, specific decisions that cost something at the end.

This deep dive is one narrow thing: how to write a YA fantasy query letter where the contrarian center is specificity—workday details, dual grief, and a choice with consequences—so the letter reads like a decision, not a summary.

Worldbuilding vs. specificity in the first 7 lines

blog general · stakes grief
Photo: Giphy / giphy

The first moment an agent decides whether to keep reading is early—often before the brain has finished translating your premise into a mental image.

When you lead with setting-as-a-flex, you force the reader to guess what matters, who deserves care, and why the book cuts emotionally. That guesswork kills reads.

Now imagine the same YA fantasy pitch anchored instead in workday behavior. The cursed ferryman isn't just "a character in a cool system." He has an actual routine: the daily logging of deaths, the small games that keep him sane, the drifting memories he can't fully control. Even the worldbuilding becomes evidence: the premise is supernatural, but the experience feels concrete—like you could recognize the pattern in a person.

That's the move: use your setting like scaffolding for character pressure. The river Styx framework functions as a job and a life sentence with paperwork, not as lore you're explaining to the reader.

If you're writing a query for YA fantasy and want the engine to click, use the first chunk to establish three things in rapid sequence:

1. What the book is (genre + vibe in comp-style positioning terms) 2. What the protagonist does every day because of the curse 3. What emotional cost is already happening before the "plot" even kicks

This is where contrarian beats matter. Agents already know how to process premises. They've seen "cursed X" and "dangerous magic" a thousand times. What they don't see often is the premise delivered as daily struggle—names logged, games played, nightmares returning.

Specificity makes your "YA fantasy" feel like YA fantasy, not just fantasy. It also makes the reader trust that you can deliver more than atmosphere later, when the query needs to explain stakes and the emotional arc.

Personalization examples that work without rambling

You want to feel personalized, but you're scared that whatever you write will sound generic anyway. So you start collecting "reasons" and turning them into a whole paragraph. It becomes vague praise wearing an author bio disguise.

Don't do that.

Personalization that works is not a tribute. It's a fit statement. A quick one. You're proving you didn't just fire the query into the slush like a paper airplane.

Here's a practical contrarian rule: the longer your personalization paragraph, the more likely it's hiding that your actual pitch is unclear. When the book itself is sharp—premise, emotional stakes, character role—the fit statement is short because the reason for fit is obvious.

For a letter built around grief and romance in a query, your personalization has to connect the recipient's taste to something specific in the manuscript's mechanics. Not "I think you love YA fantasy." That's useless.

Instead, personalize around one of these concrete anchors:

  • The manuscript's grief presentation as daily struggle (logging names, surviving the work, haunted repetition)
  • The liminal framework that creates a specific type of emotional pacing (waiting, ferrying, remembering, being stuck)
  • The tone blend: contemporary fairy-tale vibe + snarky romance energy, but with real emotional consequences
  • The relationship structure: dual grieving protagonists forced into each other's memories, not a slow-burn montage with no teeth

You can still mention MSWL or a known interest area. But the sentence should behave like: Your list/interest + my book's specific execution.

Example shape (not meant to be copied, just to show the logic):

  • "Because you've been championing YA fantasy that pairs liminal premises with character-driven grief and romance, I'm submitting X. You requested someone logging deaths and surviving the nightmares—until contact forces both into each other's hope memories."

That's the whole trick. Fit + specifics + immediate narrative implication.

If the reader has to reread it to find the actual match, it's too mushy. Don't waste word real estate on thanking the agent for reading. That's not fit; that's noise.

Grief as a daily work item, not a theme tag

Most "grief" pitches in queries announce the theme and then expect the agent to do the emotional lifting.

But grief isn't a mood. It's behavior. It's what the protagonist can't stop doing, what they avoid, what they fear will come back. In YA fantasy—especially fantasy that leans contemporary fairy-tale in tone—grief has to be embodied in the page mechanics, not implied through vague statements.

So how do you pitch grief and romance in a query without losing clarity? You show grief as daily work and recurring fear.

In the "At the end of the river styx" concept, the protagonist's curse turns survival into labor. They log deaths. They play games. They wander through memories. They keep going because the alternative is unthinkable. That means grief is not a single dramatic monologue at midpoint. It's a system they live inside.

Then you add the haunting element—a recurring nightmare tied to survival and death. That detail does two jobs:

1. It makes the supernatural premise feel specific (not abstract world lore) 2. It makes grief feel like ongoing pressure, not a one-time backstory element

If you can remove the recurring nightmare from your synopsis and nothing emotional changes, you treated grief like decoration. Put the recurring fear image back into the query—a haunting detail that drives action and makes grief feel like ongoing pressure, not a one-time backstory element.

Your query letter premise should read like an engine report, not a vibes statement:

  • Who is doing the work?
  • What does it cost them?
  • What repeats and why is it personal?
  • What forces them toward the other lead?

The dual-grief connection engine and the choice that costs

Here's where most writers mess up: how to make the plot engine feel personal and how to end the query on a decision that doesn't sound optional.

The standard approach is linear recap: premise, romance, conflict, ending.

But the best version of this concept relies on personal reciprocity. Encounters force both characters into each other's grief and hope memories, which creates momentum that's emotional first and supernatural second.

This is the connection engine: not "they fall for each other," but "their pain has consequences when they share a space they can't control."

You make the stakes beyond the obligation by letting the supernatural framework become a mechanism for transformation under pressure. The protagonist's centuries-long cursed work is a cage. The grieving second character's present-life reality is another cage. When the engine collides them, the story stops being about managing souls and becomes about confronting what both characters are refusing to admit.

That's how you create YA fantasy query letter stakes and emotional arc that feels inevitable. Consequences drive belief, not magic systems.

So what do you include to keep it readable?

1. Protagonist role (their centuries-long "work" and how it shapes their emotional survival habits) 2. Second grieving character (specific life circumstances and what grief looks like in their daily world) 3. Recurring nightmare image that ties their experiences together (why the haunt is personal and not just decorative) 4. Forced encounters that escalate emotional immediacy (their grief/hope memories bleed into each other) 5. The final conflict as sacrifice decision (both leads must give something up, and it costs them)

If your ending is "they overcome" with no price, the query won't land as YA. End with the decision that costs something for both leads. That means the query can describe the sacrifice without dumping exposition.

Clarity matters more than cleverness here. If the reader has to reconstruct what the protagonist must decide, you didn't write enough plot engine. If the reader understands the decision instantly but can't tell why it matters emotionally, you didn't write enough grief.

What to include in a query letter premise

Your premise section needs three layers working at once: the supernatural frame (the cursed system), the character's daily reality inside that frame (the logging, the games, the nightmares), and the emotional stakes (what they refuse to admit about loss). Don't bury any of these. Stack them fast. The agent should see the magical element, the human cost, and the emotional problem in quick succession.

Frequently asked questions

How does the article recommend starting a query letter?

Open with a clear statement that you're seeking representation and immediately explain why the manuscript is worth considering. Move fast from intent into concise genre and tone positioning.

What's the purpose of comp-style positioning in this query?

It anchors reader expectations by describing the manuscript's vibe and thematic blend—a contemporary fairy-tale feel with liminal, snarky romance energy, rooted in YA fantasy—without letting comps carry the entire weight.

How should a query present the protagonists and their emotional stakes?

Introduce one character bound by a long curse and another character grounded in grief, with concrete details of what they're struggling with day to day. Then connect them through forced encounters that push both characters to confront loss, love, and hope.

What plot details make the supernatural premise feel specific?

Include "workday" specifics—logging names, moving through memories, handling the cursed routine—and anchor it with a vivid haunting element: a recurring nightmare tied to survival and death. Those details make the premise visual and character-centered instead of purely worldbuilding.

Does the article include any real query statistics, and what do they show?

This article focuses on the mechanics of a single query letter for a specific concept. WQH process snapshots elsewhere document the full range: queries sent, full requests, offers of representation, time spent querying, years of writing beforehand—the concrete record writers need to debug their submissions like a craft problem.

The bottom line

If your query letter feels vague, stop polishing the setting and start tightening the specificity: the work the protagonist does, the grief that repeats, the nightmare image that haunts, the forced encounters that make the relationship unavoidable. Then end on the sacrifice decision—something that costs both leads—so the stakes don't look like optional flavor.

Write the letter like it's already trying to win a read, not like it's waiting to earn permission to be interesting.

We use cookies to ensure the site works, analyze usage, and support marketing. Could you do us a solid and accept?