Using AI as Your Developmental, Line, & Copy Editor

If you're an indie author, you've basically had two options when it comes to revising your manuscript.

One: do it yourself. Go back through the whole thing, catch what you can, tighten what jumps out at you, and just... hope you got the stuff you're too close to see. And you know the problem here, because every writer does — by the fifteenth read-through, your brain is basically autocorrecting the page for you. You stop seeing what's actually there.

Two: hire a professional editor. And look, a good one is worth every penny. There's absolutely no denying that. Or the need for an editor. The problem is the "every penny" part. Developmental, line, and copy editing, done by an actual human, can run well into the thousands per book. And if you're publishing more than once or twice a year like a lot of indies do, that adds up fast.

So we've had to pick our poison: a manuscript you polished as best you could on your own, always kind of wondering if an editor would've caught something you missed... or an editing bill that eats years of profits before the book's even out the gate.

Then one day, I got curious. I already used Claude for other stuff — brainstorming, research, just talking through plot problems — so I thought, I wonder if this thing could actually help me edit. Could it catch character development issues? Could it track my worldbuilding? Not just fix typos, but really dig into the manuscript the way an editor would. So I tried it. I fed it a full manuscript and just... asked.

Turns out, there is a third option!

So here's how it actually works, step by step.

Step 1: Developmental editing — is the story working?

This is the big-picture pass, and it has to come first, because there's no point tightening sentences in a scene that might get cut entirely (or changed significantly). I hand over the full manuscript — not chapters, not a synopsis, the whole thing — and we look at it the way an editor would look at the forest, not the trees: Is the pacing right across the whole arc? Does a big reveal have enough quiet before it to actually land, or does it feel like it came out of nowhere? Are the romance beats and the plot beats trading off well, or is one crowding out the other for too long? Did I introduce a subplot thread in chapter 4 and just... forget about it?

That's the stuff you genuinely cannot see by staring at one chapter at a time. You need the whole book in front of you (or in this case, in front of AI) to catch it.

Step 2: Line editing — is the prose working?

This is where it gets fun, and it happens in two passes.

First, chapter by chapter (sometimes paragraph by paragraph, if a scene needs it). This is the up-close, sentence-level work: cutting redundancies, tightening filler words, swapping a weak verb-plus-adverb combo for one strong verb. It's catching the stuff like when I've had a character sigh, nod, and shrug in the same page — none of which tells you anything specific about that character. It's making sure an emotional peak actually gets room to breathe instead of getting rushed past. It's varying sentence rhythm so tension actually builds instead of every sentence just... existing at the same pace.

Then, another full-manuscript sweep. This catches the stuff that no single chapter pass ever will, because each instance looks fine in isolation — it's only a problem when you see it repeated forty times across the whole book. My pet phrases (yep, I've got 'em... don't EVEN ask how many instances of "just" I've had to cut from each and every book). Body parts doing suspiciously repetitive things. A setting or a piece of worldbuilding I've now explained in full detail three separate times, apparently assuming my readers have the memory of a goldfish. Whether a character's voice stays consistent from chapter 2 to chapter 30, or whether they mysteriously started talking like someone else halfway through.

Step 3: Copy editing — is it correct and consistent?

Last stop before human eyes: grammar, punctuation, spelling, and continuity. Did my heroine's eyes change color between chapters 3 and 19? Did I forget it was supposed to be winter by chapter 25? Are the rules of my own world — what my shifters can and can't do, how a mate bond actually works — holding up from the first mention to the last?

Then, once all of that's done, it goes to my beta readers, and finally my proofreader — actual humans — before it's ever considered finished.

And yet... it still needs human eyes on it

Here's the thing I want to be really clear about: Claude doesn't write my books. It doesn't write a single sentence of the actual manuscript. It tells me what's not working, or what could be stronger, and then I fix it. And fix it. And sometimes fix it again, until we both agree it's right. The words are always mine.

And even after all of those editorial revisions, when Claude and I both agree the manuscript is done... well... Nope. The manuscript still isn't done.

It goes to my beta readers next — real, human readers, giving me their actual reactions. Did that twist land? Did they see it coming too early, or not enough? Did a character's decision make sense to someone who isn't me and hasn't been living inside this world for months? That's a kind of feedback no AI can give you, because it's not about craft, it's about how it actually feels to read the thing as a stranger.

Then it goes to my proofreader — a human, one final time — for the last typo-and-formatting catch before it ever goes to formatting.

So the process isn't "AI edits my book instead of people." It's AI doing the heavy structural and line-level lifting so that by the time actual humans get their hands on it, their time goes toward the things only a human can catch — not toward flagging the same dangling filler word for the tenth time.

So, why am I telling you this?

Because I stayed quiet about this for a long time. I use AI for creating art, I use it for marketing and business, and I've caught enough grief over both that I figured using AI for editing was one more thing I didn't need to hand the haters. But here's the thing — the haters are going to hate regardless of what I do or don't admit to. So why not actually be useful to the authors who don't hate AI, and simply never considered that using AI as their editor was an option?

So, If you're sitting on a manuscript right now, wondering whether it's really ready, or knowing it's not quite there but staring down an editing bill you can't possibly afford — you don't need special software, and you don't need thousands of dollars. You need a finished manuscript, a chatbot, and the willingness to go back and forth — sometimes over and over — until it's actually right.

It's not a shortcut. It's not "easier." I still do all the fixing, all the rewriting, all the decision-making about what stays and what goes. What it is, is a third option you might never have thought about: the developmental editor, the line editor, and the copy editor, all in one place, available anytime you want to sit down and work — for the price of a subscription you might already have.

And let me say this clearly: I am not taking business away from a human editor. I could never have afforded a professional editor — not for one book, and I've published 18. The choice for me was to use AI, or not get that level of editing at all. So nobody's losing a client, because I was never going to be one.

And honestly, this post was never for the authors who can afford a human editor. If you can afford one of course you're going to want to hire a real human — no argument here, and you absolutely should! This is for the rest of us. The ones who've been teetering on "hopefully edited enough by me" for years, because this third option simply didn't exist until recently.

And here's the part nobody warned me about: it's fun. Like, genuinely fun. Intellectually stimulating in a way self-editing on my own never was. I used to dread the editing phase. Now? I finish a first draft and I can't WAIT to dive into the developmental edit and delve into the plot, the pacing, the character arcs, the worldbuilding — all of it, and dig into how it all works together.