business

Verdict

Submitted 5/15/2026, 8:56:03 AM · Completed 5/15/2026, 8:57:06 AM

5.5
pivot
The idea

Show HN: We built a narrative analysis engine for fiction writers

Show original source text →
Our app (LaoTzu Writer Studio) has a feature called The Guardian which catches continuity errors and contradictions in manuscripts. So if you say your character has blue eyes in one chapter, but someone stares longingly into their green eyes in a later chapter, it'll flag that as a discontinuity. On a single thread, that's easy to track, but as a body of related attributes it gets very complicated, especially without discreet input from the user. We originally tried a named entity recognition-based approach with the goal of tracking entities, attributes, and relationships across the manuscript. We benchmarked on 96 novels from Project Gutenberg with various inconsistencies injected into each one, then ran the "The Guardian" layer across them to ferret them out. Unfortunately this presented 2,500 false positives across 96 novels, so ~26 false positives a novel. It's not technically bad but it's enough to become an unreliable nuisance of a feature For our next approach, we instead opted to build our own model, which we call "Confucius". This is a purpose-built narrative world model that sits underneath the entire analysis layer. It consists of five structures which I'm just lazily copying and pasting from our docs here: PropertyGraph - entities as nodes, relationships as weighted edges, co-occurrence counts CausalDAG - setup/payoff chains, unresolved narrative threads IntervalTree - precise word-position intervals for every entity (where is each character in the manuscript at every point) FenwickTree - entity density over word position, O(log n) range queries Trie - fuzzy entity lookup, name variants, partial matches Confucius is passive in that it only knows what you tell it via an event emission system. We then slot in an LLM for the extraction layer. We tested three approaches for said LLM 1. NER Only 2. Local GGUF Model only 3. Anthropic Haiku Only NER, in any combination, made things worse, it was low detection and generated the same high number of false positives. GGUF resulted in 100% detection, with zero false positives, and likewise for Anthropic So based on this, we opted to ship with 3 tiers - heuristic only (no AI required, but basic surface metrics), local GGUC (Qwen3, ~500mb one-time download which enables full Guardian features), or a managed API subscription (Haiku on our key) We're certainly proud of the result, but unto itself its been a fascinating journey as we surface additional features with each model refinement (e.g. "voice fingerprint" is our newest - essentially the consistency of the characters voice over the span of the book) We've got a kickstarter going to help fund refinements and model expenses[1], and a roadmap for additional apps down the line which we'll have on the main site[2]. We'd love for folks to try out the app so we can get some real user feedback for UI/UX refinements so please do check out the demo, or just ping us on the side 1. https://www.kickstarter.com/projects/laotzustudio/laotzu-wri... 2. https://www.redwoodrhetorica.com/
TRIZ inventive level: 3/5· Principles: parameter changes, mechanical interaction
Synthesis verdict
**Pivot**: The LaoTzu Writer Studio's 'The Guardian' feature has a strong technical foundation, but its market viability and monetization strategy require refinement. The target market of writers is identifiable, but the competition from bundled AI writing suites and the potential cost of external AI solutions pose significant risks. The tiered pricing model is sensible, but lacks concrete pricing and margin data to assess scalability.

Strengths

  • - Technically impressive continuity detection solves a real author pain point
  • - Tiered pricing leverages AI accuracy as a premium upsell
  • - The 'voice fingerprint' feature is genuinely differentiated

Weaknesses

  • - Dependence on external, potentially costly AI solutions
  • - Pricing model may not align with the target market's budget
  • - High false positive rate of the heuristic-only tier might frustrate users

Best angle

Refine the pricing model and explore integrations with existing writing software to reduce customer acquisition costs and increase the value proposition for writers.

Panel verdicts

Viability

meta/llama-4-maverick-17b-128e-instruct

4.0

“The technical complexity of building a robust continuity error detection feature like 'The Guardian' makes it challenging for a solo or 2-person team to achieve within 4-12 weeks.”

Building a feature like 'The Guardian' that catches continuity errors and contradictions in manuscripts is technically complex, especially when dealing with a large body of related attributes. The initial approach using named entity recognition (NER) resulted in a high number of false positives (~26 per novel), indicating the need for a more sophisticated solution. The new approach, 'Confucius', involves a custom-built narrative world model with five complex structures (PropertyGraph, CausalDAG, IntervalTree, FenwickTree, and Trie) and integrating a large language model (LLM) for the extraction layer. While the results with GGUF and Anthropic Haiku were promising (100% detection with zero false positives), implementing and fine-tuning such a system requires significant expertise in natural language processing (NLP) and machine learning (ML). For a solo or 2-person team to build v1 in 4-12 weeks, the task is highly ambitious, if not unrealistic, given the complexity of the task and the need to develop a robust and reliable system. The team would need to have a deep understanding of NLP, ML, and software development, as well as the ability to integrate multiple complex components. While it's possible to build a basic version, achieving the desired level of accuracy and reliability within the given timeframe is a significant challenge.

Risk

nvidia/llama-3.3-nemotron-super-49b-v1

4.0

“Dependence on external, potentially costly AI solutions and a pricing model that may not align with the target market's budget could undermine the venture's sustainability.”

The LaoTzu Writer Studio's 'The Guardian' feature, despite its technological advancements with 'Confucius' and effective LLM integration (notably with GGUF and Anthropic Haiku), faces significant challenges that could lead to its demise within 6-12 months. **1. Platform Risk (High):** Dependency on external LLMs (especially Anthropic Haiku, which may have cost, access, or policy changes) could disrupt the premium tier. **2. Churn (Medium-High):** The high false positive rate of the heuristic-only tier might frustrate users, leading to churn if the AI-enabled tiers are not widely adopted due to cost or the one-time download size of Qwen3. **3. No-Budget Customers (Medium):** The target market (writers) often has limited budgets; the tiered pricing might not convert enough users to the paid, AI-enabled versions to sustain the business, especially with Kickstarter funding being uncertain and potentially insufficient for long-term model maintenance and refinement.

Competition

no model

This agent failed to return a verdict (executor exception: 'NoneType' object has no attribute 'strip'). The synthesis ran with the remaining agents.

Monetization

mistralai/mistral-medium-3.5-128b

7.0

“Tiered pricing leverages AI accuracy as a premium upsell, but lacks concrete pricing and margin data to assess scalability.”

The revenue model has clear tiered pricing (heuristic-only, local GGUF, managed API) with a concrete value proposition: reducing continuity errors in manuscripts. The free/low-cost heuristic tier lowers friction for adoption, while the GGUF (~500MB download) and API tiers monetize power users. Unit economics are plausible - AI inference costs are offset by subscription fees, and the Kickstarter validates demand. However, the model lacks granularity: no pricing numbers, no conversion benchmarks (e.g., % of free users upgrading), and no margin analysis (e.g., cost of Haiku API calls vs. revenue). The false-positive issue in early iterations could deter trust, but the 100% detection/zero FP claim for GGUF/Haiku is a strong differentiator. The 'voice fingerprint' upsell potential is intriguing but unproven. Channels (Kickstarter, demo, direct outreach) are narrow; broader distribution (e.g., integrations with Scrivener, Reedsy) could scale revenue.

Market

moonshotai/kimi-k2.6(fallback #1)

6.0

“Technically impressive continuity detection solves a real author pain point, but as a standalone subscription it competes against bundled AI writing suites with better distribution, making customer acquisition cost the likely killer.”

The core problem - continuity errors in long manuscripts - is real and painful for authors, especially series writers and pantsers who don't outline rigidly. The target market (self-published authors, developmental editors, writing software users) is identifiable: ~1.2 million active fiction writers on platforms like Reedsy, Scrivener, and Vellum, with growing AI-tool adoption. However, the execution reveals critical market risks. First, the technical journey - NER failure, custom 'Confucius' architecture, three-tier LLM fallback - signals product complexity that may outpace user willingness to pay. The 26 false positives/novel in early testing, even if improved, creates a trust cliff: writers are perfectionists who'd rather miss one error than clean up 26 false alarms. The three-tier model (free heuristic, local GGUF, API subscription) is sensible but fragments the value proposition. Kickstarter dependency for 'model expenses' suggests insufficient capital reserves for a B2C SaaS play. The 'voice fingerprint' feature is genuinely differentiated but buried under technical jargon in the pitch. Bigger concern: this competes directly with ProWritingAid, AutoCrit, and emerging AI editors (Sudowrite, Novelcrafter) that are bundling similar features into $10-20/month subscriptions with established distribution. The 'Guardian' as a standalone feature isn't clearly $10-15/month sticky; it's a power-user feature, not a workflow hub. The team seems technically capable but may be building for themselves - 'fascinating journey' language - not solving a burning budget-line problem. Demand exists, but willingness to pay separate from integrated writing suites is unproven. The demo/kickstarter phase is correct for validation, but scaling requires either enterprise licensing (publishers, editing services) or aggressive bundling into a must-use writing environment. Score reflects real niche demand offset by go-to-market uncertainty and feature positioning challenges.

Synthesized by meta/llama-3.3-70b-instruct · 5.2s