My Lessons From the Query Trenches

Querying for traditional publishing is less about perfecting a single email and more about managing the business realities, emotional strain, and manuscript mechanics that sit behind every “yes” or “no.” The most practical lesson from the trenches: before sending queries, authors benefit from understanding how the publishing pipeline works—because it directly shapes expectations, communication with agents, and even decisions about whether traditional publishing is the right path at all.

A major early gap was business knowledge. The author learned that traditional publishing doesn’t work like a customer delivering a finished product: sending cover art along with a query and expecting the agent to package it with the manuscript isn’t how the process typically runs. That kind of misunderstanding can lead to mismatched expectations about what agents and publishers do at each stage. To close that gap, she recommends leaning on communities such as Reddit Pub Tips, where traditionally published authors, agented writers, and querying authors trade practical guidance—especially around query letters and submission norms. The point isn’t to turn every writer into a publishing executive; it’s to make conversations about submissions, contracts, and publishing houses less opaque.

The next core focus is query-letter quality and feedback. Agents receive hundreds of queries, so the query letter functions as the gatekeeper for whether a partial manuscript request follows. Because revision fatigue can blur what’s working, Pub Tips’ free query critiques are positioned as a high-leverage way to tighten letters without paying for low-value “AI-generated” feedback. Paid critiques are treated with caution unless the provider has a strong industry reputation; otherwise, the service may simply run the letter through ChatGPT and sell the output.

But the emotional dimension matters just as much as the craft. Traditional publishing involves years of rejection and public scrutiny of work-in-progress materials like queries. If harsh feedback and rejection are genuinely unmanageable, the author warns that the process may be a poor fit. Pub Tips is framed not only as a tool for improving the letter, but also as a stress test for how an author handles criticism.

Several workflow and craft lessons follow. One is operational: separate the publishing inbox from personal email to avoid waking up to adrenaline-fueled bursts of rejections, requests, and acknowledgements. Another is diagnostic: if an author can’t nail the standard three-paragraph query structure, the problem often sits in the manuscript—especially plotting. In her case, overlapping events failed to connect cleanly to a single thread, and fixing that structure made summarizing the story far easier.

Finally, the author urges careful attention to submission rules and timing. QueryTracker and an agent’s website guidelines can conflict, and the website version is often the correct one. Wish lists that look like a perfect match may still not convert into requests, while agents with broader genre framing may request more often. Self-rejecting out of overly strict interpretation can cost opportunities.

While waiting for responses, she recommends building a “waiting game” to-do list to break the inbox-refresh loop—through community engagement, optional social media platform-building, and, most importantly, writing the next project. The strongest mindset shift: write in a way that makes the current book feel replaceable—so the author can mourn the first project and stay excited about the next. Consistency and small wins keep momentum alive even when the process is slow.