The IDE and data layer for long-form fiction, built to own the creative AI stack for serious writers.
Raising $3M seed to get to MVP + 1,500 heavy-use authors and a defensible narrative data graph.
The market for creative software, tools, and services represents over $10 billion in annual spend — yet it sits on top of broken or nonexistent data models.
Hundreds of millions of people write fiction or long-form stories worldwide. Millions already pay for tools, courses, and coaching.
Today's dollars are scattered across Scrivener, Notion, Google Docs, specialty tools, and editors. No one owns the underlying narrative data.
The same infrastructure powering novel-scale fiction extends to game narrative, screenwriting, interactive fiction, and IP/franchise management.
The winner becomes the system of record for narrative IP — a $1B+ outcome on software and data alone, before tapping adjacent verticals.
AI made it trivial to crank out high-volume, low-quality text, flooding the world with generic content that dilutes the market.
Fiction writers and narrative teams face a binary: tools either try to ghostwrite for them or treat a 100,000-word novel like a long Google Doc.
The few "AI for writers" tools using story bibles or codices just dump siloed data on models, drowning them in irrelevant context.
Manuscripts are treated as static files instead of living, structured worlds the AI can reason over and understand at scale.
Scribsy is an IDE and data layer for long-form fiction. This is an infrastructure product disguised as a writing tool: whoever owns the narrative data layer owns the creative stack.
Built for multi-million-word projects and real-time collaboration. Handles the scale and complexity professional authors demand.
A rich knowledge layer over characters, locations, timelines, plot threads, and themes. Your story becomes a queryable world.
Routes the right slice of context to models so AI actually works at novel scale. No more drowning in irrelevant information.
We're starting with serious fiction authors and narrative teams — users who already spend real money and time building ad-hoc "story bibles" in Notion, Scrivener, and wikis, then fight their tools instead of focusing on story.
Scribsy becomes the place where that work actually lives — and where AI can finally use it.

Authors writing large, complex series need tools that scale with their ambition and handle interconnected storylines.
Teams building games, TV shows, and films who manage shared worlds and intellectual property across multiple projects.
Professionals who need to move through many manuscripts with shared context and consistent world-building.
We're not measuring vanity metrics. We're asking: Will serious writers reorganize their workflow around a narrative IDE, not just play with it?
3–5 "inner circle" authors are running real chapters through the Scribsy prototype on active projects.
20–30 additional serious writers using Scribsy for active manuscripts, not just demos or experiments.
We're tracking completion rate (% who finish a full scene/chapter in Scribsy), multi-week retention, and whether they'd be upset if we turned it off.

We're conducting structured interviews and offers to our early cohort, including "founding author" plans.
The signals we care about go beyond interest — we're looking for people who commit to a waitlist with price attached, say "I'd pay $X for this right now," or pre-commit to early paid access.
These aren't curiosity clicks. These are serious writers willing to put money down for a tool that finally gets how they work.
Every manuscript, edit, and entity becomes part of a structured narrative graph. Switching tools means giving up that history and context.
We fine-tune and rank on narrative-specific outputs: completion rates on complex editing tasks, "stay in voice" scores, character consistency.
We become how serious writers and narrative teams plan, draft, revise, and manage worlds. The longer they stay, the more painful it is to recreate elsewhere.
Plugin and API surface around the narrative graph means other tools (editors, game engines, analytics) plug into your data model instead of replacing you.
Monthly and annual plans for serious authors and narrative teams. Simple, predictable pricing starting at $20–30/month for solo authors.
Higher-priced plans ($60–100/month) for heavy users who need multi-project scale, advanced AI tools, and collaboration features.
Plugin and API revenue share as the narrative graph becomes infrastructure for adjacent tools like editors, game engines, and analytics.

Custom enterprise pricing for narrative teams in games, TV, and publishing who need white-glove onboarding and support.
Founder & CEO (Chief Empathy Officer)
Systems thinker with 10+ years as Chief of Staff in deep-tech and blockchain. Bridges product, infrastructure, and operations seamlessly.
Co-founder & Chief Science Advisor
PhD and post-doc in adaptive behavior and cognition. Expert in distributed/agent systems and bounded rationality.
Co-founder & Head of Engineering
14+ years shipping complex, high-scale systems in games and SaaS environments.
Hire 5–6 senior engineers, 1 design/UX lead, and 1 part-time GTM specialist to execute the roadmap.
MVP shipped, 1,500 heavy-use authors onboarded, and 35–45% WAU/MAU on that core cohort.
Proven CRDT + semantic graph stack on multi-million-word projects with rock-solid performance.
$1–1.5M ARR from power users, with a clear path to $3M ARR if traction continues.
This is the infrastructure play for the next generation of narrative creation. We're building the system of record for story — and we need partners who see it.
Scribsy