User
Write something
Office Hours - Drop in & Chat is happening in 23 hours
TRAINING TUESDAY
Your Beta Readers Are Ghosting You (Here’s How to Find the Exact Paragraph Where They Quit) There is a specific kind of agony reserved for the six weeks after you finish a draft. You export the manuscript, attach it to an email, and send it out to four or five beta readers. Then you wait. Day four, you check your inbox. Day twelve, you check it again. By week three, you’re convinced everyone hates it and is just trying to figure out how to tell you gently. When the feedback finally trickles back, it usually falls into two categories: The Polite Lie: "I loved it! So good!" (Tells you nothing. Unusable.) The Vague Critique: "It was great, but the middle dragged a bit." (Which chapter? Which paragraph? What made you put it down?) Human beta readers aren't bad people. They’re busy, they’re tired, they read on their phones at 11:30 PM with one eye open, and they don't have the craft vocabulary to explain why their attention wandered. Today, we are skipping the six-week waiting room. I’m going to walk you through how to run a 5-Seat Reader Audit—a diagnostic workflow that simulates five distinct reader profiles reading your manuscript simultaneously. It doesn't give you generic praise. It hands you a map of the exact paragraph where attention drops, where the logic breaks, and where a reader decides to close the tab. The Architecture: Why One Reader Opinion Is Just Noise If you ask a single AI prompt "read my chapter and tell me if it's good," you get an opinion. One opinion from a machine trained to be polite is worth roughly what an opinion from your mom is worth: it feels nice, but it won't save your launch. The breakthrough happens when you split the reading act into five distinct, non-overlapping seats, each governed by strict behavioral rules, moderated by an impartial chair: MANUSCRIPT TEXT Mira - Target Reader Theo - Genre veteran Juno - Drift Reader Rhys - Hostile Reader Della - Emotional Reader ARBITER - Moderator --> DIAGNOSTIC REPORT &REVISION ROADMAP
TRAINING TUESDAY
Today's Writing/Editing Sessions
I do not expect folks to sit through all of these but will keep adding them today as I'm testing the new series tools on my own work, on something I care about instead of my usual throwaway so this matters. So I've spent about 30 hours or so researching and deep diving into how a series works and how the tools already built see them. The first was creating a missing character profile. Esmeralda is a character from an earlier book that I needed a full profile and I never created one because of how I wrote the earlier books. Whoops! I tried to keep this brief and I'll keep the others today much shorter.
Today's Writing/Editing Sessions
Friday Fixes: Your Series Bible Is Lying to You
One fix. One Friday. This week: the series that's been running on a document that stopped being true two books ago. The problem nobody names until book six Here's how it happens. You write book one. You build a Series Bible, careful and thorough, everything you planned for twelve books. You publish. You write book two. Things change, characters surprise you, a subplot goes somewhere you didn't expect. You mean to update the bible. You don't. You write book three. Same thing. By the time you're planning book four you're working from a document that reflects the series you intended, not the series you actually wrote, and the two have quietly diverged in ways that are going to cost you. This is the stale bible problem, and it is invisible until it isn't. It shows up as a character who somehow forgot something they learned in book two, a plot thread that was urgent in book one and simply never came up again, a tone that drifted between books without anyone deciding it should. The readers notice before you do. The emails are polite. The reviews are not. I know this because I'm living it right now with the Tales from the Hollow Bean. The Hollow Bean situation Twelve books planned. Three published. Books four, five, and six in production. And somewhere between writing book one and planning book four, the series got darker. Not accidentally, on purpose, the story needed it. Todd's world is more complicated than it looked from the cozy side of the counter, and the people sitting around that D&D table are carrying more weight than a sweet urban fantasy suggests. Mary's background is much darker still with a new subplot that she caused and has to deal with eventually. That's a real creative decision and I stand behind it. What I didn't do is update the Series Bible to reflect it. Which means the document that books four, five, and six are being planned against still describes a series with a warmer emotional register than the one I'm actually writing. The bible is lying to me, and I've been letting it.
Friday Fixes: Your Series Bible Is Lying to You
Friday Fixes: Nothing Is Free (Somebody Always Pays)
One fix. One Friday. This week: the free book that got you nothing back. So I did the thing again, and this time I did it in front of everybody. I gave a book away free for a week, shared it in a pile of groups, watched the downloads climb, felt great about it, and then realized I'd left the door wide open and never asked anyone to sign the guest book. No landing page. No email capture. Nothing. Sigh. Here's the part that stings, and it isn't the lost sales. The book did fine. It's actually my best seller now, which is funny and annoying in equal measure. What stings is that I handed a big, interested audience a gift and walked away with no way to ever talk to them again. The goodwill was real. It just had nowhere to go. The problem Free isn't generosity. Free is a trade where one side forgot to name the price. The reader who grabs your free book hasn't done anything wrong. They took what was offered. The obligation was mine to set up, and I skipped it, because giving feels nice and asking feels awkward. But every free thing creates a small debt that runs in one direction or the other. Decide which direction, or the debt quietly lands on you, and you eat the cost of the printing, the hosting, the time, the promo, all of it. (Tangent: "free" always has a bill somewhere. It's just a question of whose name is on it.) So the rule is simple, and I'm saying it out loud so you can hold me to it: never give anything away without a trade. A trade doesn't have to be money. It can be an email address, a review, a click on the next book. It just has to be something, named, in exchange. Whew. The diagnostic: three checks before any free promo 1. Is there a landing page that captures an email before the download? If the book goes straight from "free" to "in their hands," you've skipped the only moment you had to ask. 2. Does the back matter ask for something specific? A review, the newsletter, the next book. One ask, not a thank-you note and a list of titles. 3. Can I say, in one sentence, what I get in exchange? If I can't, the answer is nothing, and I'm about to do it again.
Friday Fixes: Nothing Is Free (Somebody Always Pays)
Errors in WordCrafter.Pro this week
I'm seeing a lot of errors related to API Key usage in the error logs and have put a quick two minute video on this below. What I'm seeing is the Wrong model being chosen for the wrong API key and API keys running out of funds. Happens to me all the time as I only put $20 on at a time. When you go to one of the skill rooms, just make sure you choose the provider for your API key and the model you want to use and the effort (if that model has efforts). Medium is good for most prose, low is good for Q&A to save some costs.
Errors in WordCrafter.Pro this week
1-30 of 74
Word Crafters
skool.com/ai-pro-writers-studio
Write & finish your novel fast with AI author personas for story, prose & marketing. Claude-powered skills for indie authors. Never write alone.
Leaderboard (30-day)
Powered by