CipherWrite

How did Andy Weir self-publish The Martian? He posted it free on his own website, one chapter at a time, starting in 2009. Readers who were scientists and engineers emailed corrections, he fixed them, and when the book was done, readers asked to buy it. He put it on Amazon Kindle for 99 cents, and it sold about 35,000 copies in three months. The timeline: → c. 2000: his first novel finds no agent → 2009: The Martian goes up on his website, chapter by chapter, free → 2011: readers ask for an ebook, and at 99 cents it climbs the science-fiction charts → 2014: a major publisher releases it in print → 2015: The Martian becomes a hit film Why did it work? His readers became his beta readers. This chemistry wouldn't work. That orbital calculation was off. Every fix made the book more believable, and the readers who helped fix it became its first fans. Publishers didn't suddenly discover a software engineer's talent. Readers had already proved the book worked, in public, with numbers anyone could see. What can writers learn from Andy Weir? 1. Let readers in before the book is finished. 2. Publish on a schedule. The schedule is also your deadline. 3. Ask specific questions. "Where did you stop believing it?" beats "Did you like it?" 4. Follow the demand. When readers ask for a format or a sequel, that's your market research. The catch Some publishers and contests treat work posted online as already published, so check before you post a whole book. And asking readers what should happen next tends to produce a muddle. Use their feedback for clarity and accuracy, and keep the story yours. How do you get feedback like his without publishing your book? Send one chapter to three to five people who read your genre, not just friends. Ask one specific question, then fix the most common problem. For a first pass before that, our free AI beta reader reads a chapter the way a read

Free AI beta reader or a full manuscript assessment: which does your novel need? Before you pay $2,400 to $6,400 for a developmental edit, you should know where readers stop reading. We built two tools into CipherWrite to tell you. What is an AI beta reader? It reads a chapter the way a reader would and tells you where they'd put the book down. In about 60 seconds you get: → where a reader would quit, and what they'd skim → margin notes that quote your actual lines → the questions your chapter leaves open → your 3 best fixes, in order Your chapter isn't stored and isn't used to train AI. What is the Deep Read? Chapter feedback can't catch a problem that spans 30 chapters. The Deep Read is an AI manuscript assessment of your whole novel. It reads 15,000 to 150,000 words in order, then checks the book against itself: → facts that contradict each other across chapters → plot threads you set up and forgot → setups with no payoff, and timeline breaks → the chapters where readers stop You get an editorial letter, five scored craft dimensions, a readiness verdict and a ranked revision plan. Both tools follow one rule: every note quotes a line from your manuscript, checked against your text. If the quote can't be found, the note is dropped. AI feedback that invents lines from your book is worse than none. Does AI replace human beta readers? No. It's a first pass, so your human readers and editor spend their time on what only people can judge. A paid beta reader typically costs $50 to $300. What's free, and what does the full version cost? Free: one AI beta read of up to 3,000 words. No sign-up, no card. CipherWrite Pro: $11/month, or $7/month billed yearly ($84). It includes: → beta reads of up to 80,000 words at a time, on a monthly credit allowance → four more reader personas, including a Literary Agent and a Developmental Editor → the Reader Panel: five AI readers

Every writing app competes on the same grid: corkboards, outlines, character sheets, a place to store eye colours. None of that is what kills a book. What kills a book is one Tuesday when the writer doesn't open the file. Then it's March. So we shipped The Finisher: an accountability agent inside CipherWrite. It's in beta and it's part of Pro. How it works: It starts with a pact. Five minutes of questions about your actual week, not a fantasy schedule. It ends with an if-then plan anchored to a real day ("if it's 7am and the coffee is made, then I write 200 words") and the date you're aiming at. It notices the silence. Four days without words is the moment most books die. The check-in arrives then, and it opens by asking about the exact thing you committed to last time by email too, because the people who need it most have stopped opening the app. It names why you stopped. Not a streak counter. It knows the shape your stalls take, because you told it, and it hands you back the next scene so you never face a blank page wondering where you were. The part that made this hard to build: it remembers you, not your book. Your chapters are encrypted in your browser with a key we don't have, so a server-side index of your manuscript was never an option. The agent is never given the text, a summary, or an outline. It only knows what you typed into a check-in on purpose and you can read and delete all of it in one click. It won't write your book. It makes sure you keep coming back to it. 👉 https://cipherwrite.com/#finisher

Seasons: a calendar month, a target you pick yourself, and a cabin of six who can see whether you showed up. They see counts and dates — never a word of your manuscript, because it's counted in your browser and sent as integers. No post box in matched cabins, just preset reactions, so nobody has to moderate a room strangers land in. October opens now, free to join.

A personal writing teacher built on the same research as our guides: • Names the real problem under "I'm stuck" — usually structural, not motivational. • Builds a step-by-step roadmap for your book, in the order that unblocks you. • Sets exercises on your own manuscript and grades them honestly.

I have updated the ui and now its feels more smooth and its more secure