I Used AI to Help Write My Novel. Here's What I Learned About Losing My Voice.

I was midway through a middle-grade adventure novel. Found family, satirical humor, the kind of story where kids outsmart systems that were never built for them. I loved the voice. I loved the characters. And then, about 35,000 words in, I hit a wall.

Writer's block. The kind where you sit down, stare at the page, and nothing comes. Not bad writing. Not wrong turns. Just... silence.

So I did what everyone does in 2026. I turned to AI.

The output was impressive. And completely wrong.

The first tool I tried generated a full scene in under thirty seconds. Clean prose, proper structure, even a decent cliffhanger. On paper, it was good writing.

But it wasn't my writing.

The humor was gone. The satirical edge that made the story work had been smoothed into something safe and pleasant. The characters spoke in complete, grammatically correct sentences, which is exactly how middle-graders don't talk. The voice, the thing that made the book mine, had been quietly replaced by something more... average.

I tried another tool. Same result. Different flavor of competent, generic prose.

The problem wasn't that these tools were bad at writing. They were good at it. Too good. They were so fluent, so confident, that it was easy to accept their output and keep moving. But every paragraph I accepted moved the book further from the story I was trying to tell.

The real problem: I couldn't see what was happening

Here's what I didn't realize at first: the danger isn't that AI writes badly. It's that AI writes well enough that you stop noticing when your voice disappears.

There was no record of what I'd asked, what the AI had suggested, what I'd accepted, and what I'd pushed back on. No trail. No evidence of my judgment. Just a document that was increasingly not mine.

And if someone had asked me, "How much of this is yours?" I wouldn't have been able to answer with certainty. Not because I hadn't done the thinking. But because no one was keeping track.

What I actually needed

I didn't need a tool that wrote for me. I needed a tool that helped me think through the block without taking over.

Something that could ask: "What's the emotional core of this scene?" or "What does this character want that they can't say out loud?" Not something that would answer those questions for me.

And I needed a record. A way to show, to myself and to anyone else, that the decisions in this book were mine. That the voice was mine. That the AI had been a thinking partner, not a ghostwriter.

That's the gap that became RedInkAI. Not because I set out to build a product. Because I needed something that didn't exist.

The lesson

Writer's block is real. AI can help. But "help" should mean: sharpen your thinking, surface what you already know, and get out of the way. Not: replace your voice with something more publishable.

If you're a writer using AI, ask yourself: could I reconstruct the trail of decisions that got me here? If the answer is no, you might be losing something more valuable than time.