Video summary

The #1 Way to Ensure Readers Love Your Book

Main summary

Key takeaways

Educational

Main ideas / lessons

  • A crucial step in writing for readers—especially with AI-assisted writing—is to deeply understand your book’s genre at a “formulaic” level.
  • Best-selling books follow recognizable templates and tropes. Even if there are many other skills involved (character, worldbuilding, etc.), failing to match genre expectations leads to reader disappointment, which commonly results in poor reviews.
  • Genre research should be practical and expectation-focused:
    • Identify the exact subgenre.
    • Determine non-negotiable tropes readers expect.
    • Determine obligatory scenes that should appear in a typical structure.
    • Use those outputs to generate a chapter-by-chapter outline template, which the author can later fill with story specifics.
  • AI can perform this efficiently because it has training on genre patterns and can help with web research, reducing the need to manually read many niche titles.
  • Generic writing tools (e.g., plot frameworks or some AI platforms) may teach storytelling well, but may not automatically encode subgenre-specific tropes and scene obligations in the same way.

Methodology / step-by-step workflow

1) Choose a genre and narrow to the subgenre

  • Start with genre research browsing on Amazon (or your local bookstore).
  • Navigate through categories and subcategories (example used: Mystery → Victorian mystery romance).
  • Use Amazon’s suggested keyword drilling (typed letters) to surface additional subgenre keywords.
  • Goal: find a subgenre that is clearly identifiable and has a recognizable expectation set.

2) Validate the subgenre commercially (optional, but recommended)

Look for books within the target subgenre that have:

  • Over 1,000 reviews
  • Average ratings above ~4.0

The speaker notes some covers may be AI-generated, but argues the key validation signals are review count and rating.

3) Gather “reader expectations” using an AI chatbot

  • Use Claude (or another chatbot) to research tropes.
  • Prompt idea (paraphrased): ask the AI to search and compile a complete list of essential tropes for the chosen subgenre, framed as: tropes readers would feel cheated on if missing.
  • Example output (Victorian mystery romance), including:
    • A body or disappearance early
    • An amateur sleuth with a personal reason to investigate
    • Fair play
    • Red herrings that hold up
    • The killer is someone already met
    • Escalation that makes it personal
    • A dramatized reveal scene
    • Justice resolved explicitly
    • Romance expectations such as:
      • First kiss
      • Confession of love
      • Proof of love
    • Additional non-negotiables

4) Request obligatory scenes (scene-level structure)

  • Send another prompt to the AI asking for a list of obligatory scenes for the same genre/subgenre.
  • Example output structure (as summarized by the speaker):
    • Act One setup
    • Act Two A: investigation and attraction
    • Act Two B: convergence and collapse

Key emphasis: these aren’t necessarily every scene that will exist in the final manuscript. But you want most of them present for the subgenre to “feel right.”

5) Generate a chapter-by-chapter template using tropes + obligatory scenes

  • Send one more prompt to the AI asking for a chapter-by-chapter template.
  • Constraint: do not include plot specifics—use generic placeholders (e.g., protagonist, antagonist).

Example features of the template described:

  • A structure created up through ~36 chapters
  • Guidance aligned to tropes and scenes per chapter
  • Example chapter naming/themes mentioned:
    • Chapter 1 conceptually about “constrained normal,” establishing competence, stakes/price of transgression, routine disruption, and planting an early “ordinary background” detail
    • Later chapters include the inciting incident (e.g., body found) and progress through the full template arc

6) Use the template during outlining

  • As you outline, use the template to ensure your manuscript aligns with genre traditions.
  • Then fill in specifics as you develop your unique story.

Key cautions / beliefs expressed

  • Genre mismatch can make or break a book. If it doesn’t fit, it “won’t fly” in the current market (as stated).
  • Generic plot templates alone (e.g., “Save the Cat”) may not fully teach AI what to include for a specific subgenre; they may be more useful for human-level storytelling guidance or pedagogy than for AI’s default completeness.
  • The speaker briefly mentions downloading/readings for AI analysis:
    • DRM may or may not be present.
    • Removing DRM would violate Amazon’s terms of service; the speaker discourages that.
    • The speaker argues it’s often unnecessary because AI can research and understand niche subgenres.

Speakers / sources featured

  • Speaker: Video narrator/instructor (name not provided in subtitles).
  • Primary tools / sources referenced:
    • Claude (AI chatbot used for prompts)
    • Amazon (browsing best sellers and reviews)
    • Local bookstores (alternative browsing source)
    • Sudowriter (mentioned as lacking this feature, per speaker)
    • Novel Crafter (mentioned as lacking this feature, per speaker)
    • “Save the Cat” (mentioned as a generic plot framework)
    • Story Hacker AI community (speaker promotes it)
    • Book in a Month Challenge (community program)
    • Colm (community manager who leads the challenge; name provided in subtitles)
    • Proprietary software released by the community (speaker’s tool; described as supporting the workflow)
  • No other named individuals or organizations are clearly identified beyond those above (based on the subtitles).

Original video