Why I Built Noren

We built Noren to solve a problem that was driving us crazy: the “AI Editing Tax.”

Like most Indie Hackers, we started using LLMs to draft emails, tweets, and investor updates. The generation took 30 seconds. But the output was... generic. It sounded like a hyper-enthusiastic ghostwriter. We'd then spend 15 minutes rewriting the draft so it sounded like us—killing the semicolons, changing the vocabulary, fixing the sentence rhythms.

The promise was speed, but we were just trading writing time for editing time.

To fix this, I tried doing it the hard way. I spent three weeks analyzing my own writing samples and documenting every single pattern. I ended up with a 300-line Markdown voice guide covering my analogy domains, rhetorical moves, and punctuation habits. When I fed that to Claude, the output finally clicked. It sounded like me.

But looking at that 300-line file, I realized: this is just pattern recognition.

If I can manually extract these patterns over three weeks, an engine should be able to do it automatically. So we built that engine.