What has everyone been up to this week? Post a response below: ***** This is unfortunately yet another one of my long wordy posts If you've kept up with some of the postings of late I've been spending a lot of time with genre's and and the new BookWeaver app. Below is a sample of a Chapter from a BookWeaver book I'm about to publish. This is the first one I have brought in to WordCrafter.Pro to run through the editorial room and finish. It is unfortunately not a favorite story, but the writing is very good. This was a test of multiple things. This was a budget model, Gemini 2.5 Flash, which doesn't write bad prose, but does need a good outline and beats to stay consistent. Enter the story threading engine for this, that does some interesting tings under the hood that I need to add in to the editorial team or a light chapter by chapter pass in the Writer's room. Because the apps are FUNDAMENTALLY different in operation there are a couple jumps to make. There is NO N8N in use here at all. I do not like its outputs and how slow it is. 22K Words in half an hour from a basic premise. I read through the Story Bible and Outline created and did some light edits here and let it roll. I ran the consistency checker on it and dis some more editing a couple regenerations. Any guess's as to the cost to create this? 25K Words, 9 Covers, Editing, and export to epub. Answer is at the bottom of this post. Okay, so I did cheat on this one. Remember I said I took this to WCP for final editing? I do not yet have an accounting of how much I spent there in the editorial room, so that function has been added as well. I spent several hours last night in the editorial room in WCP with this one and cleaned it up a bit more and followed their suggestions for most of the fixes. And also learned something new and interesting I will document in a video later today. In the Editorial skillroom I let Oracle do her cold read and let the editorial team do their first pass analysis. I answered their questions and asked them to "show me their fixes" and reciedved a very long chapter by chapter set of repairs to copy/replace or do by hand. This is supposed to be a mostly automated book right? My response to them after this was this "make the changes above to the actual chapter context chapter by chapter, stop at the end of each chapter so I can save them" And it did just this for the 4 chapters that need major fixes. I saved them to the binder, renamed them properly, moved the old versions to a folder named "old" and read through it.

I spent last night actually writing again to try to finish and publish something from my backlog. Discovered some wonderful minor issues in formatting that will be fixed this weekend so you might also see a new addition to WordCrafter.pro's feature set by Monday And I have a new skill for the pro tier to use directly in Claude, a consistency and continuity checker. This does NOT replace the editorial room's 50 point checklist but was built to test BookWeaver's story threading engine. Every Tom, Dick and Mary is throwing out a new automation engine every couple of days and most of them are producing really pretty crap. Each one i look at teaches me something new. Mostly what NOT to do, that's why Im taking more time with this. I've written over 20 books in the BookWeaver system testing and reiterating and its about ready to roll Full books - Word, PDF, Epub Audio books Basic Editting Kindle Metadata Raw export to take to another tool like WordCrafter.Pro or your other favorite editor My question and what has really held me up is how to charge for this one. Currently there's no config or api keys to setup. You log in, answer a few questions, have the option of editting at each stop or just say go and you can have 100k words in an hour that is pretty good. Still could use polish and editting (because if AI was perfect we'd all be out of work). 50K or less in about a half hour. Pick your title and pen name, get your Kindle Metadata and decide to export or create an audiobook version. So each AI call costs, I currently have it at 3 levels of quality none of which are bad, just different models. Audiobooks are using 3 engines at different voice levels, elevenlabs is the most expensive. Final edits, rework/regenerate and calls to nanobanana for covers and editting covers. Leaving audiobooks out the most expensive book Ive created was $20. This was not the longest, this was the one I liked the most and spent more time editting, regenerating and doing backside coding for found errors. The average cost for the infrastructure overhead right now is $200/month, this will scale as more people use it but this figure is good for about 100 users or so. And the average cost per book is under $10. Would you want to pay $20 or so for 100K word publishable book? How many books a week or month would you want to use this for?

Building a Story Bible That Actually Gets Used Most story bibles are graveyards. You build them with good intentions. You name the continents. You map the magic system. You write three paragraphs about the royal succession. And then you open your draft and just... write from memory anyway, because pulling up the bible feels like a context switch that breaks the flow. Six chapters later you've given your protagonist two different eye colors and forgotten the name of the inn from chapter two. A story bible that doesn't get used isn't a bible. It's procrastination formatted nicely. Here's how to build one that actually works during the draft, not just before it. The Two Failure Modes Before the workflow, it helps to name what goes wrong. The Over-Built Bible. You spend three weeks building world lore before a single scene is drafted. The bible has texture and depth and almost zero relevance to the story you're about to tell, because you don't actually know what the story needs yet. By chapter four you're ignoring most of it. The Never-Updated Bible. You build a decent one up front, start drafting, and then never add to it as the story grows. Characters develop details in the draft that never get captured. Plot decisions accumulate. By book two you can't remember what color your protagonist's apartment was. The solution to both is the same: build the bible in layers, during the work, not before it. The Layered Build Layer 1: The Foundation (before drafting) Keep this short. Under three pages if you can manage it. You only need what you can't discover in the draft: The premise in one sentence. The world rules that constrain your plot (magic system limits, technology level, geography if it affects plot). Your main characters, one paragraph each: name, role, want, wound, voice note. The timeline anchor: what happened before chapter one that made chapter one necessary. That's it. Resist the urge to go further. The rest gets built as you need it. Layer 2: The Running Log (during drafting)

Why I'm Publishing Every Day for the Next 30 Days ******* The article below and some of the next few are going to sound more generic than most of my stream of consciousness posting as these are *planned*. The marketing Team and I have had a few discussions and this is the outcome. This is also a way to force myself to get the marketing scheduler done, so I do not have to post each of these to 3 places, create graphics, possibly add tiktok and instagram images, etc.. whew. So yeah thats coming soon to. These are designed for my substack page and facebook but will be cross posted here and you get the benefit of the creations that are coming out of some of these. I have a huge upgrade coming already for the Pro level manuscript-analyzer I posted last week, I use these myself and as I see gaps or something else that might beneifit it gets added ( and sometimes removed). I'll also be posting a new story below that came from some testing last night but its not *quite* done yet. Playing with Hallmark style cozy romances. And btw...In WCP I selected this whole article and sent it to the Gallery to create an image and selected *landscape* as the format and received the graphic attached. ******* Today's the start of something I've been threatening to do for months and never actually committed to. For the next 30 days, I'm publishing one article every day Monday through Saturday. Six days a week. Five weeks. Thirty pieces of content for authors, all walking the path from blank page to publishing to backlist. I'm telling you out loud so I can't quietly stop. This is the Show Your Work Saturday post that explains the plan. Marketing Monday kicks off the actual journey. From here on, every day has its own lane: Marketing Monday for sales and visibility tactics. Throwaway Tuesday for free plot prompts and story sparks. Workflow Wednesday for practical step-by-step processes. Thoughtful Thursday for the reflective pieces I usually write. Friday Fixes for one specific problem solved per Friday.

This is unedited, minor issues dealt with mostly chapter length. My attempt at a Hallmark Style Romance with something new....Anyone want to guess how much time is invested? At least scan the first chapter or so before making a guess. It helps if I actually post the book too.