AI Story Hub

Following up on my previous post about building AI Story Hub with a filesystem and versioning mindset, I wanted to dive a bit deeper into how we're tackling the "controllable AI" part and share some early insights from getting the first users onboard.

Building a tool where AI is a helpful co-pilot for complex, long-form creativity, rather than an unpredictable text generator, presented some unique engineering and product challenges.

Engineering Controllable AI: It's All About Context & Pipeline

The biggest technical hurdle (and opportunity) was moving beyond the standard "throw a prompt at an LLM" approach. For a story spanning potentially hundreds of thousands of words, consistent characters, complex plots, and specific world rules, generic prompting falls apart fast. The AI needs deep, structured context from your world.

This led to two key architectural decisions:

1. Treating Story Data as Rich, Structured Context: This goes back to the 'filesystem' idea. Instead of just having a character name, we have a Character object with fields for traits, backstories, and crucially, their Dialogue Style. When you generate a scene with that character, the AI isn't guessing their voice; it's given the specific "How does this character speak?" description you wrote. The same applies to Configuration Files (config.genre, config.bannedwords, etc.). These aren't just suggestions; they are processed and included as explicit, structured instructions in the prompt sent to the AI. Implementing these detailed input fields and ensuring they reliably format into prompts the AI understands is a constant process of prompt engineering baked into the feature development itself.

2. The Multi-Model Optimization Pipeline: Sending a massive block of raw story data and user instructions directly to a single LLM can be inefficient and less predictable. Our pipeline was built to optimize this:

   • Your current context (scene data, active configs, character details, user instructions) is first processed.

   • This structured data is then fed to a smaller, fast model (currently Gemini Flash) whose specific job is to act as a prompt engineer. It takes the structured context and your request and crafts a highly optimized, concise, and effective prompt tailored for the final generation LLM.

   • This optimized prompt is then sent to the user-selected main AI model.

This pipeline isn't just a technical flourish; it's a product decision for control and agility. It ensures the AI consistently understands the nuanced context you've built, and it allows us to quickly integrate new powerful LLMs as they become available (sometimes literally minutes to wire in a new model) because the prompt optimization layer handles the heavy lifting of formatting the input correctly.

Getting Those First Users: Early Marketing Signals

Getting the first 200+ users onboard in the first month has been a crash course in marketing a niche AI product.

• Where they came from: Early traction has been primarily organic. Posting on relevant communities like r/WritingwithAI, r/worldbuilding, and yes, r/indiehackers, generated the initial sign-ups. Direct outreach to a few contacts interested in AI/writing helped kick things off. Paid ads haven't been tested yet.

• What messaging resonated: Initially, I focused heavily on the "AI writing tool" aspect. What resonated more was highlighting the specific problems it solves: "Stop inconsistent characters," "Manage your complex world," "Never lose a draft with versioning." Framing it as a structured storytelling tool powered by AI seems more accurate and appealing to users frustrated with chaos.

• Biggest Challenge: Discovery. The AI writing space is noisy. Cutting through that and clearly communicating the unique value proposition – the focus on structure, control, and versioning over just raw text generation – is the main hurdle. It requires potential users to understand the value of these underlying principles for their long-term projects.

• Surprises: The immediate adoption of features like "Character Dialogue Style" was a pleasant surprise. It validated that users are indeed looking for granular control over elements often overlooked in simpler tools. Also, the sheer volume of 1200+ AI generations in the first month shows that once users understand the tool, they really put it to work!

Lessons Learned (So Far):

• Solve a Specific Pain Point: Don't just build an AI wrapper. Identify a genuine, felt problem within a niche (lack of structure/control in complex creative writing) and build a targeted solution.

• Engineering as a Feature: For certain audiences (like here on Indie Hackers), the how you built it (structured data, specific AI pipeline, versioning) is part of the value proposition and differentiation.

• Messaging Matters: It's not just an "AI tool," it's a "Structured Creative Workspace powered by AI." Finding that clear language is crucial.

• Listen to Usage Patterns: The popularity of certain features (like character dialogue) is a strong signal for what users value most and helps prioritize the roadmap (e.g., doubling down on character management features, explaining less used ones like the Scratchpad better).

The journey is just beginning, and the focus remains on iterating based on how creators are actually using the platform and the feedback they provide. Adding collaboration next feels like a big step in making this structured environment even more powerful for building worlds together.

Happy to answer any questions about the tech, the early marketing grind, or the product itself!

https://aistoryhub.co

For years, my professional life as a Head of Software Engineering has revolved around building complex systems. My mental model is structured: think modular components, clear organization, robust version control (thank you, Git!), and reliable deployment pipelines. It's about managing complexity through structure.

But when I'd switch gears to my creative passion – writing stories, building intricate fantasy or sci-fi worlds – I felt like I was stepping back into the digital Stone Age. My writing process felt like a chaotic mess of scattered documents, inconsistent notes, and the terrifying risk of making a change only to realize hours later I'd broken something fundamental without an easy way back. It was the antithesis of everything I knew about managing complex projects.

I needed a tool that didn't exist: an AI-powered platform for creative writing that felt like a well-organized filesystem and offered the non-negotiable safety net of version control, not just for the final output, but for every single component of my story.

The Problem I Had to Solve:

Existing writing software, even good ones, are often built around the linear document model. Great for drafting linearly, bad for managing a growing universe of characters, locations, magical systems, plot points, and stylistic rules that need to remain consistent across hundreds of pages and potentially multiple books. AI writing tools, while powerful, often felt like a black box – unpredictable, and hard to steer consistently for long-form narratives. How do you ensure the AI remembers your obscure world rule or a character's specific speech quirk from 50,000 words ago?

My engineering brain kept asking: Why can't I git commit my character's backstory? Why can't my setting details live in their own structured 'directory'? Why is there no version history for that crucial plot outline I just tweaked?

The Build: Applying Engineering Principles to Creativity

So, I decided to scratch my own itch and build AI Story Hub (https://aistoryhub.co). The core philosophy from day one was simple: bring the power of structured data management and version control from software engineering into creative storytelling, and integrate AI as a controllable, contextual co-pilot.

• Story as a Filesystem: The platform is built so that every character, location, item, and importantly, configuration setting (config.genre, config.tone, config.bannedwords, config.ai for deep control) is its own distinct, manageable entity. It's a structured database disguised as a creative writing environment. This modularity is key to managing complexity.

• Element-Level Versioning: This was non-negotiable. Every single one of those distinct components – a character profile, a scene, a configuration file – has its own version history. You can make radical changes to a character's personality or rewrite an entire scene, knowing you can instantly revert to any previous version if needed. This eliminates the fear of experimentation.

• Controllable AI via Context: The AI isn't just prompting a large model blindly. Our architecture (built with TypeScript, Svelte, Vite, and Firebase) includes an intermediate step where we gather ALL the relevant context from your structured story elements (the character's defined dialogue style, the active config files, the details of the current location, the last few scenes) and use a model like Gemini Flash to optimize a prompt that precisely captures your world's current state and your instructions before sending it to the main generation model. This is how we aim for consistency and control.

Launch & Early Traction (1 Month In):

Launched AI Story Hub about a month ago. It's still very early, but seeing initial usage is incredibly validating:

• 200+ users have signed up.

• They've started 145 stories and are building 23 distinct universes.

• They've collectively run over 1200 AI generations.

It seems other creators also feel the need for more structure and control, even if they don't articulate it in terms of filesystems and versioning! The features users are engaging with most are the ones that embody this control: detailed Character Creation, setting per-Character Dialogue Styles, and generating Scenes that respect the established world rules.

Challenges and Lessons Learned:

• Translating Engineering to Creativity: One challenge is explaining the value of structure and versioning to users who aren't engineers. The benefits (consistency, safety, iteration speed) are clear to me, but communicating them effectively through UI and onboarding without making it feel overly technical is an ongoing process.

• The "Black Box" Perception: Despite building a system for controllable AI, many users come with the expectation (or fear) of a black box. Educating on how configuration files and structured context actually give them control is key.

• Finding the Niche: Creative writing is broad. Focusing on users who build detailed worlds for long-form projects helps, but articulating that specific value prop in a crowded AI space is a marketing challenge.

What's Next:

Applying more engineering paradigms! Next up is introducing collaboration features. Because complex projects, including stories, are often best built together. Bringing multiple creators into the same structured, versioned environment feels like the natural evolution.

If you're an indie hacker, especially one who writes creatively or appreciates applying structured thinking to non-code problems, I'd love for you to check out AI Story Hub and share any thoughts or feedback on the approach.

Thanks for reading about the build!

https://aistoryhub.co