Investor Q&A

Three structural shifts have converged simultaneously in 2025–2026, creating a window that did not exist before.

Creator economy maturity. Substack crossed 35M paid subscriptions in 2024. Patreon pays out $2B+ annually to creators. Itch.io has over 700K published games. Creators have demonstrated they will pay for professional tools and that audiences will pay for creator-produced content. The revenue model is no longer speculative — it is proven infrastructure.

Platform vacuums. StoryNexus (Failbetter Games' interactive fiction platform) was sunsetted in 2022. Wattpad's interactive fiction tools have stagnated following its sale to Naver. Inkle's Ink language remains developer-facing. No new creator-first IF tool has reached scale since 2019. There is a five-year gap in the market and an audience of 2M+ Twine users who have never been offered a commercial alternative with monetization built in.

LLM capability inflection. GPT-4o and Claude-quality models now generate structured narrative output reliably enough to serve as an AI placeholder-fill assistant — a Phase 3 feature that was not feasible at acceptable quality before 2024. This isn't a pivot to AI; it's a differentiator that deepens the platform moat once the core product is established.

The comparison surfaces four fundamental differences — not feature-level improvements, but architectural ones.

The deepest distinction: Twine, Ink, and ChoiceScript treat narrative as the primary object and logic as something the creator must hand-write around it. Arcanum treats narrative intent as the primary object and derives all logic automatically from templates. That inversion is the core product insight.

This is the right question to challenge. The failure mode of every "no-code" tool is that it works for simple cases and breaks down the moment a creator wants to do something sophisticated. Arcanum's answer to this is architectural, not cosmetic.

Templates absorb complexity by design. A creator building a skill check ("pick the lock: Dexterity vs DC 15") selects the Skill Check template. They fill in: target stat, difficulty rating, success outcome, failure outcome. The template generates the rule (1d20 + stat vs DC), the outcome range split (≥15 success / <15 failure), and the transition logic automatically. The creator never touches a single rule field if they don't want to.

Placeholders decouple architecture from writing. A creator can build the entire story graph — all 200 nodes, all branches, all rules — with placeholder content. The structure is validated, tested, and playable before a single line of prose is written. This is how professional game designers work. Arcanum brings that workflow to fiction writers.

The complexity ceiling is high but optional. Creators who want dice expressions, custom DSL conditions, or multi-variable fight mechanics can access them. Creators who don't can publish compelling stories with three templates and never see the advanced panel. The UI surfaces power progressively — it does not demand it upfront.

Target time to first publish: 14 days. This is a hard onboarding target. If a creator cannot reach a playable, shareable story in two weeks without support, the product has failed. That constraint drives every UX decision.

Arcanum's monetization is structural — it lives at the graph level, not injected into the prose. This is the key distinction from ad-based models or pop-up paywalls.

Three monetization primitives:

• Story-level paywall. The entire story is purchasable — one transaction, full access. No interruptions during play. Creator sets the price; Arcanum takes its commission on sale.
• Episode gating. Stories are structured as chapters. Each chapter after the first may be paid. The player completes Chapter 1 free, then unlocks subsequent episodes. Common in serialized fiction and validated by Choices and Episode at $2.4B annual revenue.
• Premium branch unlocks. Specific transitions — an alternate ending, a secret route, a high-stakes path — are flagged as premium in the node graph. The player hits a locked branch node; a single tap unlocks it. The paywall is a narrative beat, not an interruption: "Do you risk the tunnel? (Unlock for $0.99)"

All three are configured in the node editor — not injected at runtime. The player experience is native to the story structure. There are no ad units, no banner breaks, and no subscription prompts mid-scene. The commercial layer is invisible when done correctly; when done incorrectly, creators hear about it immediately from their audience.

Creator incentive alignment. Because Arcanum earns commission on player transactions, Arcanum's revenue grows only when creator revenue grows. There is no scenario where Arcanum benefits from a monetization pattern that frustrates players and hurts creator retention.

Scale at the story graph level is a genuine engineering challenge and one Arcanum has designed for from the start — not retrofitted. Three mechanisms address it.

Graph traversal is scoped, not global. The live validator does not re-validate the entire graph on every edit. It maintains a dependency map of each node's inbound and outbound connections, and re-validates only the affected subgraph when a change is made. A 300-node story with a change to node 147 triggers validation of nodes reachable from and leading to 147 — not all 300.

State snapshots compress history, not full state. The state engine does not store a full copy of world state at every node. It stores a base snapshot at story start and a delta log of effects applied. Player session replay traverses the delta log forward from the nearest checkpoint. This keeps session storage linear in the number of effects fired, not the number of nodes visited.

The UI provides structural navigation tools. Node search, tag filtering, chapter grouping, and path highlighting allow creators to navigate large graphs without losing orientation. At 300+ nodes, the graph is not a wall of spaghetti — it is a structured document with chapters, tags, and visible coverage metrics (what percentage of nodes are reachable from start? what percentage have been playtested?)

The Creator Studio tier includes path coverage analytics specifically because the platform expects serious creators to build at this scale. The product grows with the creator's ambition.

The MVP is deliberately narrow: the minimum set of features that allows a creator to go from blank canvas to published, monetized, playable story — and for a player to buy and complete it. Everything else is Phase 2 or Phase 3.

The MVP does not include AI features, team collaboration, white-label, or mobile apps. Those are roadmap items funded by growth after the core loop is validated. The question we are answering in Phase 1 is: can a non-technical creator build a structured, rule-driven story and have players pay for it? Everything else is predicated on a yes.

This is a product philosophy question as much as a technical one. The answer is: the rule system is intentionally constrained, not accidentally limited.

Restricted DSL, not a scripting language. Arcanum's expression parser accepts a defined grammar: arithmetic on state keys, comparison operators, boolean combinators, and dice notation. It does not accept arbitrary function calls, loops, recursion, or side effects. The DSL is parsed into a validated AST before execution; expressions that reference undefined state keys or produce type mismatches are rejected at authoring time, not at runtime.

Templates are the primary authoring surface. The DSL is accessible only in the Advanced / Custom template — the fifth and most powerful template. The other four templates expose structured forms that compile down to DSL internally. Most creators never write a DSL expression; they fill in forms and the platform writes the expressions for them.

Validation catches expression errors early. The undefined_state_key and impossible_condition validation issues specifically target broken or unreachable logic in rule expressions. A condition that can never be true (e.g., a stat check against a value higher than the stat's defined maximum) is surfaced as a warning before the story is published.

The design principle: expressiveness within boundaries is more valuable than unlimited expressiveness. A creator who can write player.dexterity + 1d20 >= 15 has everything they need for a compelling skill check. A creator who wants to write arbitrary JavaScript has different needs — and different tools exist for them.

The early adopter profile is precise: the Hybrid Creator. Age 22–38. Has already written interactive fiction in Twine, Ink, or ChoiceScript. Has shipped at least one project on itch.io. Has a following — Discord server, Tumblr, Substack, or Twitter — but has not successfully monetized their work. They know what they want to build; they've been blocked by tooling complexity or the absence of a commercial layer.

Why this profile converts. They do not need to be educated about interactive fiction. They already believe in the format. They are frustrated by current tools, not satisfied by them. They have an audience ready to pay if given a purchase mechanism. Arcanum removes their blockers, it does not create new behaviors.

Acquisition channels ranked by expected efficiency:

Anchor creator programme. 10–15 established IF creators are onboarded in the six months before public launch with free Creator Pro access and direct support from the founding team. Their published stories become the first catalogue. Their audiences become the first players. Their public testimonials and devlogs become the first content marketing. This is the single highest-leverage pre-launch activity — more valuable than paid acquisition at this stage.

State consistency is the hardest unsolved problem in interactive fiction tooling. Every branching story faces the same challenge: the player makes a choice in Chapter 1 that should affect Chapter 7 — but Chapter 7 has 30 possible entry paths, and not all of them know about that choice. Arcanum addresses this at three levels.

Global state space, defined upfront. Before a creator can reference a state key in any rule or effect, that key must be declared in the Story Defaults — with a type (stat / flag / inventory / counter) and a default value. There is no implicit state. No variable is created on the fly. This means the full state space is known at authoring time, and the validator can catch references to undeclared keys before the story is published.

Effect groups, not direct mutations. No node directly writes to state. Transitions carry Effect Groups: ordered lists of typed effects (set, increment, decrement, add_item, remove_item, toggle). These effects are validated against the declared state definition — you cannot increment a flag, add an item to a stat, or set a counter to a non-integer value. The type system eliminates the most common class of state bugs.

State snapshot at every session checkpoint. The player session records a full state snapshot at configurable checkpoints (chapter boundaries by default). Between checkpoints, a delta log of effects is maintained. If a consistency issue is detected — a state key referenced in a condition that has never been written by any reachable effect group — the validator surfaces it as a continuity_warning during authoring, not during play.

The result: creators get a validation error at authoring time, not a bug report from a player who found an impossible door. State consistency is a structural guarantee, not a QA task.

The Series A case is straightforward: prove the two-sided marketplace works at small scale, then raise to accelerate the supply side (creators) and the demand side (players) simultaneously.

The M+18 targets that unlock Series A readiness:

Why these metrics, not others. ARR of $400K at 82% gross margin demonstrates the unit economics are real, not model assumptions. 1,000 active paid creators demonstrates supply-side retention, not just acquisition. A proven LTV:CAC ratio above 10:1 demonstrates that creator acquisition is a highly efficient investment — meaning Series A capital deployed into creator acquisition has a calculable and attractive return. Story completions prove the platform produces content that players engage with to the end — the demand side signal. One B2B partner proves the API is real and that institutional buyers see value beyond the consumer product.

Series A use of funds (planned). $3–5M to scale the creator acquisition programme internationally (DACH, Nordics, Japan), hire a full growth team, accelerate Phase 3 AI features, and build the mobile-optimised player shell. At that scale, the marketplace dynamic becomes self-reinforcing: more creators attract more players, which attracts more creators.

Long-run strategic position. Arcanum is not a tools company. It is a content infrastructure company. The tools are the moat that creates supply. The supply is the catalogue that creates the player marketplace. The marketplace is the recurring revenue that funds everything else. The exit path is acquisition by a media platform (Wattpad successor, Amazon, Netflix Games division) or an IPO as the dominant narrative gaming creation infrastructure.