HOW TO USE THIS PROMPT

Export the following files from your KDP dashboard and upload them together:

• KENP Read report (12–18 months minimum)

• Orders Summary report (same period)

• Payments/Royalties report (same period)

• Amazon Attribution data and Ads data if you run Facebook/external ads (optional but recommended)

Upload all files to your AI of choice and paste the prompt below. For best results, run it on two different models and compare – each will surface different patterns.

Read more

The lab is dark. Your manuscript is marked “Stable.” The structural bugs are purged. Now comes the phase where most indie authors break: Deployment.

Most writers treat marketing like a casino. They throw a $4.00 book at a $2.00-per-click keyword campaign and act surprised when they’re bleeding out by Tuesday. In the Iteration Lab, we don’t gamble. We build a Flywheel – a mechanical system that uses small, calculated inputs to generate self-sustaining velocity.

This is how I moved from a Google “Golden Cage” layoff to selling 8,131 copies and clocking 2M+ page reads in a single year.

Read more

There’s a failure mode that traps most authors who try AI editing.

They paste a chapter in and type: “Edit this.”

What comes back is confident, plausible, and mostly useless. The AI performs edits to justify its existence – smoothing things that didn’t need smoothing, proposing changes that technically work but make nothing better. It’s a vending machine that dispenses the appearance of helpfulness.

“Edit my book” gives you the same results as “Write me a book.”

Precision is the only way in. And precision requires knowing what editing actually is – which most authors, and every AI prompting guide I’ve ever read, skips entirely.

So I did what an engineer does with a system he doesn’t understand. I read the manuals.

The Research

Three books. Not craft books – editing books.

The Artful Edit by Susan Bell. Dreyer’s English by Benjamin Dreyer. The Copyeditor’s Handbook by Amy Einsohn.

I read them like API documentation. I was looking for specific, nameable operations – not taste, not instinct, not vibes. Discrete editorial activities precise enough for a language model to execute without hallucinating its way toward “helpfulness.”

What they revealed: editing has distinct layers that should never run simultaneously. Mixing them is why AI editing fails. It’s also why human editors charge differently for developmental work versus copyediting. The tasks are not the same thing. They don’t even ask the same questions.

Read more

If Module 4 was the Build, Module 5 is the Forensic Audit.

A lot of writers fail at the editing stage because they fall into the “Placebo Edit” Trap. They ask an AI to “edit” their text, and the AI – wanting to be helpful – shuffles deck chairs. It replaces a few words with statistical equivalents, smooths out some “clichés” that actually served the lore, and generally makes the prose feel like a polished, flavorless paste. It edits to satisfy you, not to fix the story.

In the Iteration Lab, we don’t do Placebo Edits. We do Forensic Debugging.

Read more

Architecture is useless if you never break ground. You have the Concept Doc (The Spec) and the Narrative Architecture (The Blueprint). Now, we move into the Build Phase.

Read more

You have a Concept Doc that survived the stress test. You have a 10% Delta that readers are actually hungry for. Now, we stop “thinking” and start building.

In the Iteration Lab, we don’t “sit down and see where the characters take us.” That’s a recipe for spaghetti code – a plot that wanders aimlessly until it crashes into a dead end. We map the structural skeleton before we ever touch a scene. This is Narrative Architecture.

Read more

Module 1 was the blueprint. You have an Idea, a 10% Delta, and a Designing Principle. But right now, that idea is a “local build.” It works on your machine. The question is: Will it survive the wild?

Most authors fail here. They fall in love with their first draft of a thought. They spend six months building a product for a ghost market, only to realize they’ve built a bridge to nowhere.

In the Iteration Lab, we don’t guess. We perform a Forensic Audit.

Read more

Most authors write a book, hit “publish,” and then spend three days agonizing over a blurb. They treat the blurb like a shiny wrapper for the “real” art inside.

In the Iteration Lab, we don’t start with a book. We start with a Blueprint.

Read more

A few days ago, Ariana – a psychologist and reader here – sent me a message that hit like a bug report in production.

She wanted to know about my “outside-in” approach. She noticed I didn’t start with the “craft of writing.” I started with the engineering of it.

She’s right. And it’s time I’m honest about how I actually built this machine.

The “6-Figure” Lie

First, a disclaimer: I am not a coach. I don’t sell “freedom” or 6-figure dreams while wearing a headset. I hate that vibe.

What I am is a an engineer who got laid off and decided to reverse-engineer the Amazon black box. I’ve made mistakes. I’ve burned cash on ads that didn’t convert. I’ve written dialogue that sounded like a broken thermostat.

I’m not sharing “The Truth.” I’m sharing my logs.

They Want a Fix, Not “War and Peace”

Literary gatekeepers love to talk about the “soul of the work.” But here is what they won’t tell you: Most readers aren’t looking for high art. They’re looking for a fix.

If someone just finished a 20-book series about a female starship captain, they don’t want a prose-heavy meditation on the human condition. They want another ship. They want the tropes, the tension, and the payoff.

I don’t look for “art” when I read for fun. I look for entertainment.

There is a massive, hungry space for “decent” books that respect the reader’s time and their love for the genre. If you can provide that, you win.

Killing the 20-Year Tax

The standard advice is a death sentence: “Write shitty books for 20 years, pay your dues, and maybe one day you’ll be a Real Writer™.”

I didn’t have 20 years. I had hundreds of stories in my head, but I lacked the “craft.” I didn’t want to live in the wilderness; I wanted to tell my stories now.

AI killed the tax. The barrier between the “story in your head” and the “words on the page” has collapsed. If you approach it with care – if you actually steer the machine instead of just letting it hallucinate – you can ship books people love without waiting for permission.

Engineering the Craft

I didn’t ignore the rules. I just treated them like a technical manual.

I read The Anatomy of Story and Save the Cat Writes a Novel like I was studying a new API documentation. I applied engineering logic to narrative structure. I debugged the plot.

If you compare the first book of The Lightning War to the last, you can see the engine getting tuned. The prose is tighter. The stakes are sharper. Not because I found a “muse,” but because I optimized the pipeline.

The Mini-Course: Engineering Indie Success

Starting next week, I’m opening up my “Internal Logs.”

I’m putting together a series of posts for my paid subscribers. I’ll show you exactly how I start from the outside (the market and the process) and work my way into the production.

What we’re actually doing:

• Trope-Stacking: How to build a story spec before you write a single word.

• The Bridge: Using AI to turn an “Idea” into a “Draft” without losing the soul.

• The Manuals: The specific books and tools that helped me “debug” my writing.

• The Failure Log: The mistakes that cost me time (so you can skip them).

I’m building this for the Arianas of the world – the ones who have stories to tell but are tired of being told they’re on the “wrong path.”

Next week: Module 1 – The Market Spec. Why your blurb is actually your source code.