Why Elias Altman's AI-hook query got an agent to move the cursor (breakdown)

9 min read
blog hero · curiosity dread
Photo: Zhine Pics / pexels

A successful query letter isn't a "tell me about your book" email. It's a push-button. The agent reads it and decides whether they're going to spend real time digging into your manuscript.

In this case study, we're looking at a query for _Elias Altman and In Our Likeness_ by Bryan Vandyke, because the agent response highlights something writers often struggle to articulate: what makes a query move from interest to action. The query does a few things very clearly—especially around premise, pacing, and a standout AI-assisted hook that feels timed to the moment.

Here's the core takeaway I want you to steal: the query doesn't have to be flawless prose. It has to be specific enough to trust and confident enough to prompt a start-reading action.

"A query's job is to make the agent start reading—not just admire your idea."

TLDR

TLDR
Photo: Alexandro David / pexels
  • Your query needs to push the agent into reading the manuscript, not just nod politely at the concept.
  • The "Three Ps" (premise, promise, provenance) give your query its structural clarity.
  • Even if comparative titles or personal targeting aren't perfect, a sharply stated premise can still carry the first read.
  • An AI-assisted hook can act like an extra P by signaling cultural timing and novelty.
  • Matching the book's tone in the query builds trust faster than polish alone.
  • Strong pacing signals early—especially if the query shows the direction the first chapter controls.
  • When the query feels delivered and human (not overworked), it can create warmth even with only average craft polish.

AI-assisted hook as an extra "P" (and why it worked fast)

AI-assisted hook as an extra "P" (and why it worked fast)
Photo: Felicity Tai / pexels

Let's start with the thing that made this query memorable immediately: the AI-assisted aspect.

Most writers treat the hook like a magic spell. Sprinkle something "cool," get attention, ride the wave. But agents aren't impressed by cool. They're impressed by why you're worth their time. In this query's case, the AI-driven hook reads as both a craft choice and a timing choice—like it understands the conversation people are having right now.

The agent's feedback emphasizes that the AI-written hook was captivating, and that the cultural timing mattered. Translation: the hook wasn't "AI because AI is trending." It functioned like an attention lever—an added premise-adjacent signal.

"Novelty counts when it clarifies the book's world. Otherwise it's just glitter."

So how do we turn that into something usable?

What the query did (mechanism, not magic)

  • It created instant curiosity without forcing the agent to do homework. The hook gives a question-shaped entry point.
  • It matched the book's hyper-contemporary material. The AI angle didn't feel stapled on; it felt like it belonged in the same room as the novel.
  • It reduced the agent's risk. When the hook feels culturally prescient, it signals the author isn't guessing—they've been paying attention.

Generalizable lesson

If you're wondering whether to experiment with AI to strengthen a query, don't ask "Will it sound polished?" Ask: Does the AI help you write a hook that's specific to your story's experience and timing?

That's the difference between gimmick and signal.

Also—pause. If you're thinking, "Okay, but what exact wording do I copy?" don't. We're breaking down function. Your hook should be yours: the agent should feel, "This query is landing the same punch as the book."

The Three Ps stack: premise, promise, provenance (and where it mattered most)

The Three Ps stack: premise, promise, provenance (and where it mattered most)
Photo: Amar Preciado / pexels

Now we get to the part writers want but often can't execute consistently: the query letter premise promise provenance structure.

The feedback describes the "Three Ps" the way agents themselves talk about it: nobody officially calls them that, but the agent points to a simple reality. A good query states clearly:

  • the premise (plot and pacing),
  • the promise to readers (what you'll feel / what you'll get / why it matters),
  • the provenance (why this agent and what essential author info matters).

Here's where this case study is extra useful: it also shows that you can still succeed if your query misses some of the Three Ps.

In this example, the query didn't fully nail comparative titles or personal targeting. The prose wasn't especially remarkable either. Yet it still earned a manuscript request because it handled premise with confidence and curiosity.

What to copy (the structural intent)

When you map this query's success back to your own, you should see the order of operations:

1. Premise first, clean and specific. The agent should understand what the book is doing and how it moves. 2. Promise next, in plain reader terms. The query should tell you what kind of reading experience is coming. 3. Provenance last, but still present. Even if it's not perfect, it's still where the query proves you did basic matching work.

Where comparative titles and targeting fell short (and didn't destroy it)

This is the anxiety part for writers: "If I don't nail comps or feel special in my personalization, I'm doomed."

But the agent's note is basically: comps and targeting help, not because they're magical, but because they're signals of fit. If you're weak on those signals, you'd better compensate by being strong on the premise.

That leads to the second big lesson:

Generalizable lesson

If you're drafting and you feel torn between "sound like a pro" and "be precise," pick precision for the premise. It's the part that stops the scroll. It creates the curiosity that survives imperfections elsewhere.

And yes, the cluster phrase matters here: query letter premise promise provenance isn't just jargon. It's the checklist that keeps you from writing a query that's all vibes and no decision-making.

Tone match: the query felt like the novel (so trust arrived early)

Tone match: the query felt like the novel (so trust arrived early)
Photo: Daniwura TCI / pexels

Here's a subtle thing: the agent didn't just request because the premise was intriguing. They requested because the query felt like it belonged to the same book—the voice, the level of specificity, the energy all matched what they'd find on page one.

That's the part many writers miss when they try to "write like a bestseller." They chase the wrong target. Your query isn't a trailer for the genre. It's a rehearsal of the book's experience.

In this case study, the AI hook did more than signal novelty. It reinforced the novel's hyper-contemporary world. The agent saw that the query sounded like the book itself, and that resemblance created genuine trust and interest.

What this looks like on the page

When writers ask "How do I make a query feel specific without sounding weird?" this case study answers indirectly: specificity lives in the details that carry the book's lived experience, not in fabricated flourishes or attempts to sound professional. It's the texture of your language matching the texture of your story.

If your book is modern and fast and concept-literate, your query should read like it belongs in the same atmosphere.

"Trust grows faster when the query feels like the novel, not like a generic pitch."

Generalizable lesson

How to make a query feel specific isn't "add five details." It's: pick the details that carry the book's lived experience. Then make sure your language choices don't betray that experience. A query that sounds like it's trying to impress an agent in an abstract way feels less trustworthy than one that sounds like it understands the story's world.

First pages control: pacing and direction signal in the query

First pages control: pacing and direction signal in the query

The agent's feedback emphasizes early manuscript execution as a deciding factor. Early pages matter: if the first chapter shows control of pacing and confidence in direction, it signals the author can deliver what the query promises.

This matters because a query does two jobs at once: 1. Promise the premise cleanly 2. Signal that the manuscript can execute the pacing

The agent is thinking: If this premise is interesting, can this writer actually carry it to page 100?

What this case study suggests

Even if your prose polish is only average, your query can still land if it:

  • describes the story's movement clearly,
  • doesn't stall on setup,
  • and implies momentum rather than fog.

Remember, pacing isn't random in what agents care about. It's core. Agents want to know the plot doesn't just exist; it moves.

Generalizable lesson

When you're drafting your query, treat the pacing signal as a decision point, not a craft afterthought. If the query's premise makes the story sound like it'll wander, you're quietly telling the agent the first chapter might wander too.

Aim instead for premise clarity that carries energy. And when you're wondering what makes an agent request a manuscript, here's the blunt version that matches this case study: the query makes them curious, and then the early pages make them feel safe continuing. The query is the front door; the first chapter is where the agent tests the locks.

When the prose isn't "slick": it can still work if it feels delivered and human

When the prose isn't "slick": it can still work if it feels delivered and human

This case study includes a detail that should calm down a lot of writer-brain spirals: the agent notes that the query prose wasn't especially remarkable. It also points out that the query "didn't try too hard," and that it felt delivered and human, which built warmth and confidence.

That's a weird comfort if you're the kind of person who wants to weaponize perfect sentences. But it's also fair. Query writing is not an MFA exam. It's a functional memo with personality.

What "don't try too hard" probably means in practice

It usually means:

  • fewer overwrought sentences,
  • fewer attempts to sound impressive,
  • fewer layers of "as you can see" explanation.

And it often means you're writing from the premise outward, not from the style outward.

Your voice should serve the premise, not distract from it. A literary agent responds to confidence and clarity more than they respond to adjectives.

Generalizable lesson

If you're asking how to write a successful query letter and thinking it's only about polish, read this case study again. The agent response points to these core elements:

  • Premise confidence
  • The query sounds like the book
  • Hook attention
  • Early momentum signals

Polish can help. But it isn't the gate. Fit-by-function is the gate.

Lessons / Takeaways

Lessons / Takeaways
  • Make premise the anchor. Even when the query doesn't fully nail every "Three Ps" element, a clear premise can still earn action.
  • Treat pacing as decision-making info. Use language that implies movement, not just plot existence.
  • Use AI to strengthen the book's signal, not to pad the draft. If AI helps you write a hook that's timely and story-specific, it can act like an extra "P."
  • Match the novel's tone for faster trust. The literary agent reads your query like a sample of your book's experience.
  • Don't let average prose scare you. A query that feels delivered and human can create warmth even if the sentences aren't showy.

The bottom line

blog section image · blank page rewrite

Open your query draft and look for the one thing you've been quietly avoiding: the decision point in the agent's head. If your premise doesn't feel confident, your tone doesn't match the book, or your pacing signal is fuzzy, fix those first. Everything else is background noise. Then go back to your manuscript and make sure the first pages earn the trust your query claimed.

Continue reading

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