Hi everyone,

After building and refining a suite of AI critiquing tools to support my own novel writing, I’ve packaged them into a web app to act as a critique workbench (providing developmental and line editing feedback) for novelists. I'm looking for a few beta testers from this community to help evaluate its quality and overall utility.

Currently, the app features customized support for Fantasy and Science Fiction (though I can spin up support for other genres in a few days if needed).

Note: The app provides manuscript upload and analysis; you continue writing and revising in your word processor of choice.

What is it?

Unlike standard chat prompts or one-off report generators, this is a dedicated critique and analysis workspace:

• Scope-Specific Analysis Levels: It structures your analysis at the Scene, Chapter, Act, and Book levels. Crucially, each level analyzes different structural aspects of your story. For instance, a Book-level critique evaluates overarching narrative arcs and holistic prose style, while Scene and Chapter levels drill into specific pacing, micro-tension, and scene dynamics.
• Just-in-Time, Context-Aware Critiques: Monolithic critiques usually become obsolete the moment you rewrite Chapter 1. This workbench allows you to request and deliver feedback only for the specific section you are currently revising, while still taking the whole story (via an auto-deduced or provided Story Bible) into account. Over a full novel, the available feedback is about 1,000 pages—but delivered just-in-time, in manageable pieces, where your current writing/editing focus is.
• Objective Analytics: The app generates comprehensive, structured analytics to guide your revision efforts—providing a level of objective, data-driven and quality trend analysis that is difficult or impractical to get from human editors or beta readers.
• Laser-Focused & Simple to Use: Because the workbench is dedicated strictly to analysis and feedback (rather than a jack-of-all-trades), the interface is streamlined. This keeps the in-depth, multi-layered reports highly accessible and easy to digest without a steep learning curve.
• Critique vs. Ghostwriting: To be clear, this is not an automated draft generator. While it will suggest specific, granular line-editing snippets and phrasing adjustments (just like a human editor would), it is built to refine your writing, not replace your voice.
• The Goal: While it doesn't replace the final polish of a professional human editor, it aims to deliver highly rigorous developmental and line editing feedback—quickly, iteratively, and at a fraction of the cost, supplemented by detailed analytics a human editor cannot easily provide.

Technical Specs & Current State

• The Engine vs. the UI: The core critiques, analytics, and backend workflow are highly developed and ready for rigorous testing. However, the front-end web app is built on a prototype framework—meaning you will likely encounter minor UI quirks (like occasionally needing to click a button twice).
• Manuscript Ingestion: The beta currently supports .docx files. To help the engine automatically map your book's structure, you just need consistent headers using Word styles or text strings (e.g., "Act 1", "Chapter 1", "Scene 1.1", or "* * *").
• Strict Data Privacy: Under the hood, the app runs strictly on paid Gemini API services. Under Google's API terms, your data is kept completely private and is never used to train AI models. Your intellectual property remains entirely yours.

What I'm hoping to learn from Beta Testers:

1. Critique Quality: Does the analysis help you spot pacing issues, character consistency gaps, structural weak points, and how well does it compare with human feedback?
2. App Workflow: Does the progression from Scene up to Book level make sense for your editing routine? Does the app flow well, and are the views intuitive?
3. Missing Features: As you use the app, what tools or features do you find yourself wishing were there?
4. Credit Quotas: To simulate a future monthly subscription, I’m giving testers 40k credits. I’d love your feedback on whether this quota feels adequate for a standard month of writing, revising, and critiquing.

How to join:

Because this is a self-funded project, I’m keeping this initial tester group small to manage API costs.

If you write SFF and want to try it out, please leave a comment below or send me a DM with a brief description of your current project. I’ll send over your private login credentials, free testing credits, and a quick-start guide.

Thanks for reading, and I look forward to your feedback!