After ten years of unpublished novels, I built the editor I couldn't afford

I've been writing novels for ten years. Day job by day, manuscripts by night and weekend. I've finished multiple books. None of them are published.

The bottleneck wasn't talent or time. It was that the whole writing journey from idea to published book is fractured across a dozen tools and a $10,000 editing bill nobody can afford.

Every time I started a novel, I outlined in one app. Drafted in another. Asked AI to help and got generic prose that sounded like every other AI-written book. Finished a draft and hit the same wall every indie writer hits: a developmental edit costs $5,000 to $10,000, and most writers can't afford it. So the book shipped with structural problems the writer couldn't see, readers stopped at 30%, the book never found an audience, and the writer assumed they weren't talented enough. Usually they were one round of editing away from a book that would have worked.

So I built Inkett.

It's a writing platform for novelists with four tools that share one voice profile and one source of truth for the manuscript.

A visual Story Planner where you map a novel on a canvas. Acts, chapters, characters, plot threads, all in one view. The structural skeleton of the book before you write a word.

A Co-Writer that drafts beside you in your voice. Not generic AI prose. It learns your style from samples you choose and writes scenes, dialogue, transitions, descriptions in your cadence. You direct, it drafts. You revise, it learns.

A developmental Editor that reads a full manuscript up to 250,000 words and returns chapter-by-chapter notes on pacing, plot, voice, and tension. The kind of feedback writers usually pay a freelance editor thousands of dollars for.

A Publisher that lets writers take a finished book directly to readers. Subscription-based, with a revenue share that actually pays the writer instead of the platform.

The whole stack works together. The voice profile you train on day one carries across every tool. The outline you build in the Planner feeds the Co-Writer. The manuscript you draft flows into the Editor. The book that comes out the other end can be published in the same workspace it was born in. One platform, one voice, the whole book.

Each tool was hard to get right in its own way. The Planner went through three versions before it stopped feeling like a spreadsheet and started feeling like a writing tool. The Co-Writer was the longest fight because writers can spot generic AI in one sentence. Early versions sounded like ChatGPT in a serif font. The Editor had its own arc: early versions wrote feedback like a supportive friend, which writers found patronizing. Later versions overcorrected and felt like a critique partner with a grudge. The version that works now writes like a senior freelance editor would: honest, specific, anchored to a chapter, never vague.

Testing the Editor on classics was the moment I started to believe the whole platform could work. I ran it on Crime and Punishment. It flagged Raskolnikov's voice flattening in the middle act, something Dostoevsky scholarship has actually written about. I ran it on Moby Dick. It flagged the whaling chapters as tangentially related to the main plot. (Melville knew. I had to teach the AI that.) Watching it catch real structural things in books I've read three times changed how I thought about what was possible.

The strangest part of building this has been being the customer and the founder at the same time. I plan novels in the Planner. I draft in the Co-Writer with my own voice profile. I run my own manuscripts through the Editor. The dogfooding loop is unusually tight, which is both the best and the most uncomfortable part of building this.

There are millions of writers who shelved books because the next step cost more than they could afford, or because the tools to finish a novel are scattered across products that don't talk to each other. Inkett exists for them.

Curious to hear from anyone here who's built consumer tools in markets where the audience is deeply skeptical, or anyone who writes long-form and has thoughts on what the next generation of writing software should actually do.