
Feedback & Revision
Is My Book Ready to Query? A 10-Point Test Before You Contact a Single Agent (2026)
Romance novelist writing cozy, small-town love stories from a bookshop café in Asheville.
TL;DR: You usually get one chance per agent. A rejected query rarely gets a second look, even after a big revision. So "is my book ready to query?" is really two questions. Is the manuscript finished, revised and structurally sound? And is the query package ready: query letter, synopsis, comp titles and the first pages? This guide gives you a 10-point test for both, explains the warning signs that you are querying too early, and shows how StoryWith AI helps. It reads your whole manuscript, finds the structural problems agents reject books for, gives you a readiness check that names every blocker and spends no AI credits, and then drafts the query package from your actual book: logline, blurb, comp titles, query letter and a submission checklist. Free plan with unlimited books, paid from $19/mo.
Disclosure: StoryWith AI is our own product. We have tried to be fair about what software can and cannot judge, and about when you still need human readers.
Why "ready to query" matters more than "finished"
Finishing a draft is a huge achievement. It is not the same as being ready to query.
When you query a literary agent, you are asking a professional reader who gets hundreds of submissions a month to stop on yours. Most agents decide from the query letter and the first few pages. If they request the full manuscript, they are reading for a reason to say yes, and any reason to say no ends it.
And in most cases you cannot query the same agent with the same book twice. That makes querying early the most expensive mistake in a writer's career. Every agent you contact before the book is ready is an agent you have probably lost for this book.
So the question to ask is not "is it done?". It is "is this the strongest version of this book I can make, and is the package around it ready?"
The 10-point ready-to-query test
Work through these in order. The first six are about the manuscript. The last four are about the query package. If you fail any of the first six, stop there: no query letter can rescue a manuscript that is not ready.
Part one: the manuscript
1. It is finished, all the way to the end. For fiction, agents represent finished novels. No placeholder scenes, no "TODO: fight scene here", no ending you plan to write once someone is interested. (Non-fiction is different: it is usually sold on a proposal and sample chapters.)
2. It is the right length for its genre. Word count is the first thing an agent checks in your query. As a rough guide, most adult fiction lands between 70,000 and 100,000 words, fantasy and science fiction can run longer, and young adult usually runs shorter. A 40,000-word adult thriller or a 180,000-word debut fantasy is an easy "no" before anyone reads a line.
3. You have revised it, more than once. A first draft is you telling yourself the story. If you finished the draft last month and have only proofread it since, it is not ready. Most debut novels that sign have been through several structural revisions, not just line edits.
4. The structure holds. This is where most early queries fail, and it is the part writers find hardest to see in their own work:
- Does every setup get its payoff, or are there promises the story makes and never keeps?
- Does every scene change something, or are there scenes that are well written but do nothing?
- Does the protagonist actually change, or does the arc stall in the middle?
- Do the stakes keep rising, or does the middle sag?
5. It is consistent. Continuity errors are the fastest way to lose an agent reading your full: a character who knows something they were never told, an injury that heals three chapters early, two Tuesdays in one week. One is forgivable. A pattern says the book has not been carefully revised.
6. Someone other than you has read it. Beta readers or critique partners, people who are not your mother, should have read the whole book and told you where they got bored, confused or lost. If nobody outside your head has read it, you do not yet know how it reads.
Part two: the query package
7. You can pitch it in one sentence. A logline: who the protagonist is, what they want, what stands in the way, and what happens if they fail. If you cannot write it, that is often a sign the book has not yet decided what it is about, which brings you back to point 4.
8. Your query letter is tight and specific. Around 250 to 350 words: a hook, a short pitch that reads like back-cover copy, the book's title, genre and word count, comp titles, and a short bio. It should sound like your book, not like a template.
9. You have 2 or 3 recent comp titles. Comparable titles tell an agent where your book sits on a shelf and that there is a market for it. Good comps are recent (roughly the last few years), from your genre, and successful but not era-defining. "It's Harry Potter meets The Hunger Games" tells an agent nothing except that you have not researched the market.
10. Your synopsis and first pages are polished. Many agents ask for a one- or two-page synopsis that gives away the ending, plus the first five, ten or fifty pages. Your opening pages carry most of the weight of the query, so they need to be the most revised pages in the book.
Score yourself honestly. Ten out of ten: start researching agents. Seven to nine: you are close, and the gaps are probably in the package. Six or fewer, or any failure in points 1 to 5: keep revising. The agents will still be there in three months.
Warning signs you are querying too early
- You are still changing the ending. If the ending is not settled, the book is not settled.
- You finished the draft in the last few weeks. Distance is part of revision. Most writers need time away from a draft to see it clearly.
- You are hoping the agent will help fix it. Some agents are editorial, but none of them want to fix the structure of a book they have not signed.
- Your word count needs an apology. If your query has to explain why the book is 160,000 words, revise the book instead.
- You cannot say what happens in the middle. If the middle third is a blur even to you, it will be a blur to a reader.
- Your query letter was easier to write than the book's last chapter. It probably means the letter is generic.
What most "is my book ready?" advice misses
Most ready-to-query checklists are good at telling you what to look for. The trouble is that you are the person least able to find it.
In your head, the payoff exists. You know why the character makes that choice in chapter 14, because you know the backstory you cut. You remember the clue in chapter 3, because you planted it. A reader does not have any of that.
That is why points 4 and 5 sink so many first queries. Structure and continuity problems live across the whole book: a setup in chapter 2 and a missing payoff in chapter 31. You cannot see them by rereading one chapter at a time, and you cannot reasonably ask a beta reader to track every thread across 90,000 words.
This is the part where software actually helps.
How StoryWith AI helps you decide if your book is ready to query
StoryWith AI is a manuscript-aware story studio. It reads the book you wrote and answers editorial questions about it. It is built to answer exactly the question in this article's title, in two halves: is the manuscript ready, and is the package ready?
1. It reads your whole manuscript, not a pasted chapter
Import your draft as .docx, PDF or plain text. StoryWith AI rebuilds what is already in it: chapters, scenes, characters, places, timeline, and the promises your story makes to its reader. It builds your story bible from the text, so you do not have to.
Every analysis then runs across the whole book. When it tells you a setup has no payoff, it has checked all 31 chapters, not just the one you remembered to paste into a chatbot.
2. It finds the problems agents reject manuscripts for
Points 4 and 5 of the test are where software is genuinely stronger than a tired human reader, because it can hold the entire manuscript in view at once. StoryWith AI's analysers cover:
| Ready-to-query question | StoryWith AI analysis |
|---|---|
| Does every setup pay off? | Setups and payoffs, beat coverage |
| Does every scene earn its place? | Scene purpose |
| Does the protagonist change? | Character-arc analysis |
| Does the middle sag? | Emotional arc and pacing |
| Is it consistent? | Continuity, plot-hole and conflict detection |
| Does the dialogue work? | Dialogue analysis |
| Is the voice steady? | Style consistency |
Every finding is tied to the exact scene it came from. Click it and you are looking at the problem. All of the findings go into one ranked queue, so you fix the most serious problems first instead of polishing commas while the middle act is broken.
3. It gives you a readiness check that shows its working
This is the closest thing to a straight answer to "is my book ready to query?". StoryWith AI's readiness check runs six structural checks and marks each one pass, warn or fail:
| Check | What it looks at |
|---|---|
| Manuscript length | Whether the draft is full length, or still too thin to read end to end |
| Premise on file | Whether the book has a saved premise you can pitch from |
| Scene completeness | Whether any scenes are still stubs with almost no prose |
| No critical open actions | Whether any critical problems from your analysis are unresolved |
| High-severity actions | How many high-severity problems are still open |
| Continuity conflicts | How many continuity contradictions are still active |
Any failed check is listed as a blocker, and the book is only marked ready when there are no blockers. Because the check counts what your analysis has already found, it spends no AI credits, so you can run it after every revision session and watch the blockers fall. Each check is saved to the book's history, so you can see the draft move from four blockers to none.
A readiness score does not tell you whether an agent will love your book. Nothing can. It tells you that the book is complete, consistent and free of the structural problems that get a full request turned down, which is the part that is in your control.
4. It gets real readers to the book before agents see it
Point 6 of the test needs humans. StoryWith AI lets you send beta readers a private link to the manuscript, with no signup required for them and no draft files floating around in email. Their reactions map back to your chapters. Before that, you can run AI reader personas to predict where different readers might lose interest, then compare those predictions with what your real readers say.
5. It drafts your query package from your actual book
Once the manuscript passes, StoryWith AI's Pitch Kit helps with points 7 to 10. It works from your manuscript, not a blank template, and produces:
- A one-sentence logline you can test and refine.
- A back-cover blurb, which is the core of the pitch paragraph in your query letter.
- 3 to 5 comparable titles to research and choose from.
- A 250 to 350 word query letter draft built from your book's real plot, characters and genre.
- A short author bio and alternative titles.
- A submission checklist that tracks the full package: manuscript complete, logline locked, synopsis written, blurb finalized, comps chosen, bio, query letter, beta feedback collected, professional edit and metadata.
Treat the query letter as a first draft, not a finished letter. Agents read thousands of queries and they can hear a template. Use the draft to get the structure and the specifics on the page, then rewrite it in your own voice. Check every comp title yourself too: read the book, confirm it is recent, and make sure it really sits next to yours.
To protect you from a generic letter, the Pitch Kit will not run on a draft under 5,000 words. It needs a real manuscript to work from.
6. It never rewrites your manuscript
StoryWith AI's analysis tells you what is wrong and where. It does not rewrite your chapters to fix it. Your book stays in your words, which matters both to agents and to publishers who now ask about AI use.
7. It works for non-fiction proposals too
Non-fiction is usually sold on a proposal, not a finished manuscript. StoryWith AI builds a full non-fiction book proposal package, and its non-fiction analysers check argument soundness, facts against your sources and how concepts depend on each other, so your sample chapters hold up.
A ready-to-query workflow with StoryWith AI
- Finish the draft. Write all the way to the end before you analyse anything.
- Import the whole manuscript. Word, PDF or plain text.
- Save your premise. Two or three lines. If it is hard to write, you have found your first problem.
- Run the analyses. Continuity, setups and payoffs, scene purpose, arcs and pacing.
- Fix the ranked problems. Critical first, then continuity conflicts, then high-severity issues. Fill or cut stub scenes.
- Run the readiness check. Repeat after every revision session. It costs no AI credits.
- Send it to beta readers with a private link when there are no blockers.
- Revise from their feedback, then re-check readiness.
- Build the query package in the Pitch Kit: logline, blurb, comps, query letter draft and bio. Rewrite the letter in your voice and verify every comp.
- Write your synopsis and polish your first pages. Then work through the submission checklist.
- Query in small batches. Send to 8 to 12 agents first. If you get no requests at all, revisit the query and opening pages before you send more.
Ways to check if your book is ready to query, compared
| Self-checklist | Free AI chat | Beta readers | Paid editor | StoryWith AI | |
|---|---|---|---|---|---|
| Reads the whole manuscript | You do | Only what you paste | Usually | Yes | Yes |
| Finds structural problems across the book | Only what you can see | Rarely | Some | Yes | Yes |
| Ties every problem to a scene | No | Rarely | Sometimes | Usually | Yes |
| Clear ready / not ready answer | Your own judgement | Changes each time | Opinion | In a report | Yes, named blockers |
| Re-check after every revision | Yes | Yes, but forgets | Costs goodwill | Pay again | Yes, no AI credits |
| Query package help | No | Generic | No | Sometimes extra | Pitch Kit from your book |
| Judges taste and voice | You | Weakly | Yes | Yes | No, use humans |
| Cost | Free | Free | Free, paid in time | Hundreds to thousands of dollars | Free plan; from $19/mo |
The honest read: no single option covers everything. Beta readers and a good editor judge taste and voice in a way software cannot. StoryWith AI covers the parts that are hardest to do yourself, the whole-book structural check, a repeatable readiness answer and a query package built from the book, and it means the human readers you do use spend their time on what only humans can judge.
Frequently Asked Questions (FAQ)
How do I know if my book is ready to query?
Your manuscript is finished, revised more than once, the right length for its genre, structurally sound, consistent, and read by people other than you. Your package is ready when you have a one-sentence logline, a specific query letter, 2 or 3 recent comp titles, a synopsis and polished first pages. Use the 10-point test above.
Should I query before my book is finished?
For fiction, no. Agents expect a finished, revised manuscript. Non-fiction is usually sold on a proposal and sample chapters instead.
How many drafts before I query?
There is no fixed number, but a first draft is almost never ready. Most writers go through several structural revisions plus at least one round of beta feedback.
Can AI tell me if my book is ready to query?
AI can tell you whether the book is complete, consistent and free of the structural problems that get manuscripts rejected, and it can do that across the whole book. It cannot tell you whether an agent will love it. StoryWith AI's readiness check names the blockers and spends no AI credits, so you can re-run it after every revision.
Should I use AI to write my query letter?
Use it for a draft, not a final letter. StoryWith AI's Pitch Kit drafts a query letter from your actual manuscript, which gets the structure and specifics down. Then rewrite it in your own voice, because agents can tell when a letter sounds generic.
How many agents should I query at once?
Start with a small batch of around 8 to 12. Their response tells you whether your query and opening pages are working before you use up your list.
What if I already queried too early?
Stop querying, revise properly, and query new agents with the stronger version. Some agents will look at a substantially revised manuscript, so check each agent's guidelines.
Is there a free way to check if my manuscript is ready?
Yes. StoryWith AI's free plan includes unlimited books, Word and PDF import and a monthly allowance of AI actions, with no card required. The readiness check itself spends no AI credits.
The one thing to take away
"Is my book ready to query?" deserves a better answer than a feeling at 1 a.m. Run the 10-point test. Fix the manuscript before you touch the query letter. Get real readers to it. Then build a package that sounds like your book.
StoryWith AI covers the hardest parts: it reads the whole manuscript, finds the structural problems, tells you plainly what is blocking readiness, and turns your finished book into a query package draft. You only get one first impression with each agent. Make it with a book that is actually ready.
Check if your book is ready to query, free, at storywith.ai. Unlimited books, import from Word or PDF, no card required.
Related reading: Manuscript Readiness Score: How to Know When Your Book Is Actually Ready · First Chapter Analysis · Plot Hole Finder · Continuity Checker





