Software production has changed. What used to require a venture-backed team and a multi-million dollar burn rate now requires one owner and a well-architected machine. At Total Ventures, we don't build side projects. We build, keep, and operate AI-native digital products as permanent equity.
Inky is our latest build—an AI storytelling app designed to turn fragmented ideas into structured narratives. Building an AI story app in the current climate isn't about who has the best prompt; it is about who builds the most resilient system to manage the output of an agentic workforce.
Here is how we are shipping today and what I have learned the hard way about building software meant to be kept forever.
The Shift in Software Production
The cost of generating code has collapsed. This is the fundamental shift that makes Total Ventures possible. When the cost of production drops to near zero, the value migrates to judgment, taste, and the architecture of the system.
When I began building an AI story app, the goal wasn't to see if the AI could write a story. We already know it can. The goal was to build a product where the AI acts as the workforce, managed by a single human operator. This requires a move away from traditional software engineering toward what I call agentic engineering.
In this model, the software is not a static tool. It is a series of interconnected agents that handle narrative logic, character consistency, and world-building. My job as the owner is to architect the operating system that allows these agents to execute without constant human intervention.
Architecture for a Permanent Asset
Because Total Ventures is a permanent-equity company, every technical decision is viewed through the lens of long-term maintenance. We build to keep. This means avoiding complex, brittle stacks that require a team of specialists to debug.
For Inky, the architecture is built on a shared engine that powers all our properties. It consists of:
A Managed Data Layer
We use a relational database to maintain the state of every story. In narrative applications, state is everything. If the system forgets a character's motivation in chapter three, the product fails. We treat the database as the single source of truth for the agents, ensuring that every inference call is grounded in the existing story data.
The Orchestration Layer
This is where the agentic engineering happens. Instead of one massive call to an inference engine, we break the storytelling process into discrete tasks. One agent handles the outline. Another handles the prose. A third agent acts as an editor, checking for tone and consistency. This modular approach allows us to swap out underlying models as better ones become available without rebuilding the entire application.
The Frontend Framework
We prioritize a clean, functional interface that stays out of the way. The value of building an AI story app is in the output, not in flashy animations. We use a standard, server-side rendered framework to ensure speed and SEO performance from day one.
