# MVP Mammoth > **Self-containment note (R20):** the external documents this report references are vendored under `canon/` as of 2026-07-05. Its citations are the historical record of what the report read when it was written, and they're left verbatim; to follow one as a live pointer, resolve the doc under `canon/`. :::animation HERO **HERO: four bosses between an idea and the money** - **What it shows:** an idea enters a world map and walks a staged path toward revenue, passing four lit gates in sequence, HELLO WORLD, HELLO USERS, HELLO REVENUE, HELLO EXIT, each drawn as a boss the venture must beat before the next gate opens, a graveyard of dead side projects visible off the path for anyone who skipped a gate - **Narrative role:** sets the thesis and serves as the share/card thumbnail; the whole deck argues that the idea-to-revenue journey is a staged, gated path, not a build - **What it teaches:** MVP Mammoth lays out the whole staged journey from idea to money, with real gates the venture must clear - **Intended impact:** the reader stops picturing an app builder and starts picturing the staged path to a business that makes money ::: | Field | Value | |---|---| | Project | MVP Mammoth | | Looikos cluster | Infrastructure & Agent Platforms (the venture-planning layer: idea to revenue to exit, staged) | | One-line | The venture-planning engine that takes a problem and a solution idea and lays out the whole staged path to making money, tracked through Hello World, Hello Users, Hello Revenue, and Hello Exit, each broken into stages and phases, using PRD Master under the hood and grounded in the nine-rung operational hierarchy | | Status | Concept (depends on PRD Master, which it uses under the hood, and on the harness it runs on) | | Existing code | None as a standalone product yet; uses PRD Master (`prdmaster`) under the hood, connects to Notion/ClickUp/Linear, runs on the harness, and shares the video-game-engineer UX standard with Agent Design Pro | | Desk | desk-infra (written by desk-brands-finish) | | Coverage | VERIFIED-heavy on the seed (Andy's transcript is first-party and current) and on the AI-build-tool and venture-planning market plus the build reality (Perplexity, cited, with named competitors and the staged-lifecycle alpha; PRD Master's build is first-party from its repo). INFERRED on the three-angle valuation comps and persona PST depth (tagged inline) | | Date | 2026-06-21 | --- ## Nine-rung frame (this research task) - **Purpose (the rails):** give the ecosystem the depth to build and run MVP Mammoth with agents, not headcount. MVP Mammoth is the layer that turns an idea into a money-making venture on a staged path, which is the mechanism by which the ecosystem (and its customers) ship brands that actually make money rather than dead side projects. - **Mission (rung 1):** convert Andy's recorded MVP Mammoth breakdown into a research-grounded ~10k brand deck, so the venture-planning brand is built and sold from understanding the idea-to-revenue pain, not from an app-builder's-eye view. - **Objective (rung 2):** a finished deck at `symphony/stack-recon/projects/mvp-mammoth.md`, ~10k words, three-angle valuation modeled, 5+ PST personas to world-experience depth, build section grounded in the venture-planning and PRD-Master-under-the-hood reality, graded CLEAN by desk-qc-final and the lead. - **Initiative (rung 3):** the symphony-recon Track-P run; one of the ~11 unwritten decks. - **Project (rung 4):** the desk-brands-finish lane. - **Task (rung 5):** this one brand deep-dive, run against `_PROJECT_TEMPLATE.md` and PST. - **Action (rung 6):** A1 ingest the transcript and the PRD Master repo it builds on (done). A2 skeleton (done). A3 sequential Perplexity: market/alpha, Lexicon of Pain (done; build reality drawn from Query 1 plus the first-party PRD Master repo; valuation comps reused). A4 PST on five personas. A5 incremental section writing. A6 self-check. A7 hand to the lead. - **Decision (rung 7):** the evolution stage of the venture-planning capability (app-building and business-plan-drafting are heading to commodity; the staged full-lifecycle make-money planning wired to execution, grounded in the operational hierarchy and gated by validation, is the genesis-stage own-it lane); which personas carry the deck (the built-something-nobody-wants builder, the users-but-no-money founder, the AI-build-tool-disillusioned, the technical solo founder frozen on business, plus the public buyer); ADOPT/HARVEST on the build (use PRD Master under the hood, use the app-builders as engines inside the plan, own the staged-milestone model and the validation gates and the planning-to-execution wiring). - **Data (rung 8):** N/A (this doc is the artifact). It later seeds the metagraph as BrandDeck:MVPMammoth, with edges to PRD Master, the harness, WikiDesignCo, and the project tools. - **Event (rung 9):** N/A (this doc is the artifact). Deck written, progress posted, grade recorded. ## 1. What it is (the one-paragraph truth) MVP Mammoth is the venture-planning engine of the ecosystem: the tool that takes a problem and an idea for solving it and lays out the entire staged path to turning it into something that makes money. You don't write each individual spec sheet in it; that's the job of PRD Master, the ecosystem's tool for writing product requirement documents (PRDs), which MVP Mammoth uses under the hood. MVP Mammoth is the layer above, the one that answers what stages and phases you have to move through to get from an idea to a business. :::animation 1a **ANIMATION 1a: the layer above the spec sheet** - **What it shows:** two stacked layers, the lower one labeled PRD MASTER stamping out individual spec sheets, the upper one labeled MVP MAMMOTH drawing the whole staged journey and reaching down to summon specs from the layer below as each stage needs them - **Narrative role:** anchors the §1 altitude distinction, the venture-planning layer above the spec engine - **What it teaches:** MVP Mammoth plans the journey at the venture level and uses PRD Master underneath to write the specs - **Intended impact:** the reader grasps the two altitudes and why the planning layer is the higher-value one ::: It tracks the journey through four high-level milestones, each broken into stages and phases. Hello World is making the thing real: it works, it's effective, it produces the results you want. Hello Users is when people actually find value in it, multiple people, using it consistently, who would be devastated to lose it, and ideally the most meaningful and valuable users rather than the low-value ones. Hello Revenue is when strangers, not friends, go through a funnel and pay you, and keep paying you, because of real value, profitably. Hello Exit is the strategy: where you're taking the thing now that it makes money, the wow moment, the close of the loop. Because the whole ecosystem is obsessed with its nine-rung operational hierarchy, the ladder that ties every task back up to a mission and a purpose, MVP Mammoth grounds everything in it, so the dependencies line up, the research and competitive intelligence connect, and the user gets an easy interface and a maintained world model, all processed from one place and connected to Notion, ClickUp, and Linear under the hood. And because the average non-developer won't have a great time bouncing between tools and softwares and interacting with agents, it's built to the video-game-engineer UX standard: easy and fun, a clear journey. For the people it serves, MVP Mammoth is the answer to the most common and most painful failure in building: shipping something nobody wants, or getting users who won't pay, or generating an app in an hour with an AI tool and realizing the building was the easy 10% and the business is the hard 90%. :::animation 1b **ANIMATION 1b: the easy tenth, the hard nine-tenths** - **What it shows:** a task bar labeled BUILD THE THING fills to ten percent in a single fast burst and then a vast remaining ninety percent lights up labeled MAKE IT A BUSINESS, get users who stay, get strangers to pay, plan the exit, the small easy slice dwarfed by the hard remainder MVP Mammoth exists to navigate - **Narrative role:** anchors the §1 pain the brand answers, the building was the easy part - **What it teaches:** shipping the app is a small fraction of the work, and the business is the hard majority the brand navigates - **Intended impact:** the reader feels why generating an app fast does not solve the real problem ::: ## 2. Andy's seed, expanded **Andy's words (verbatim from the recording):** "Last one for this section, is MVP Mammoth. So this is a little bit similar to PRD Master where MVP Mammoth would be something that would be using PRD Master under the hood. So what MVP Mammoth is about is planning out what the hell is it you're actually building. So you're not writing each individual spec sheet at this point. No, no, MVP Mammoth is more about, okay, we have this problem and we have this idea of how we think we can solve it. What are the stages and phases we're going to have to go to to navigate from hello World to hello Users to hello Revenue to hello hello Buyout or hello Exit... The idea behind MVP Mammoth is that we want to track through those four... those four high level things are broken down into stages and phases. And what MVP Mammoth does is it helps you to take your idea and then actually lay it out into something that can make you money. And again the idea is a whole hello World. So make sure the damn thing is real, make sure it works, make sure it's effective, make sure that it's going to produce the results you're wanting. Hello Users. Someone actually finds value in it and in fact multiple people find value in it and are using it consistently and would be devastated if they could no longer use it... you want to intensely avoid what we all know are low value users. Hello Revenue is all about, okay, having users is one thing, but having people who are paying you profitably is another thing... money is exchanging hands from other people, complete strangers and they're going through some type of a process. We call that a funnel. And they're paying you because of some kind of value and they continue to pay you... when you have enough hello Revenue, that means you've decided on your business model, you likely have a direction and you now can move towards hello Exit. Hello Exit is what is your strategy? Where are you taking this thing? It's making money now... the green light has been achieved and I like to take it one step further. The wow moment... hello exit is where we really close the loop. Because if we can ground everything again, we're obsessed with the operational hierarchy, the nine rungs, they help align everything it makes it to where now we can leverage something like PRD Master to actually mass produce all the underlying pieces. We can make sure the dependencies are lined up, we can make it so that the user has an easy access and interface and create the world model. We can go and do the research, competitive intelligence... and of course it's likely just connected to notion ClickUp and linear under the hood. But again, we're about creating an experience. And let's be real, the average non developer is not going to have a great time bouncing between all of those tools... we need to make it easy, we need to make it fun. And again, that's where we need to take that video game engineer, video game designer to excellent user experience." **Reading between the lines:** Andy's seed compresses four claims, each load-bearing. First, the altitude distinction between MVP Mammoth and PRD Master is the structural key, and it maps onto the gap the market leaves. PRD Master writes the specs (the individual documents); MVP Mammoth plans what you're actually building at the venture level (the staged journey). That difference is what the 2026 market doesn't bridge: the app-builders build the thing and the business-plan tools write the document, and neither owns the journey from idea to revenue to exit (VERIFIED, Query 1). MVP Mammoth sits at the venture-planning altitude and uses PRD Master as its spec engine underneath, which is the planning-to-execution connection the market is missing `projects/prd-master.md`. :::animation 2a **ANIMATION 2a: the gap between build and document** - **What it shows:** an app-builder on one side ships a running thing, a business-plan tool on the other prints a document, and between them a dark canyon labeled THE JOURNEY FROM IDEA TO REVENUE TO EXIT that neither reaches across, until MVP Mammoth drops a bridge into the canyon - **Narrative role:** anchors the first claim, the altitude distinction mapping onto the market gap - **What it teaches:** the market builds the thing or writes the document but no one owns the journey between them - **Intended impact:** the reader sees the precise gap the brand fills ::: Second, the four-milestone staging (Hello World, Hello Users, Hello Revenue, Hello Exit) is the core model, and it's the validation-gate structure the market lacks. Andy's definitions encode real thresholds: Hello World is a working, effective thing that produces the wanted results (more than an app that runs); Hello Users is consistent use by multiple people who would be devastated to lose it, the Sean-Ellis must-have bar, with an explicit warning to avoid low-value users; Hello Revenue is strangers paying profitably through a funnel and continuing to pay; Hello Exit is the strategy and the wow moment. The existing tools don't impose that staged validation: the AI MVP builders celebrate code-shipping and the business-plan generators celebrate document-completion, but revenue, retention, and exit are where success gets measured, and almost no tool treats anything short of Hello Revenue as incomplete or models the gates per stage (VERIFIED, Query 1). The four milestones are the boss-fight structure of building a real business: the implementation boss, the value-and-retention boss, the funnel-and-economics boss, the scale-and-liquidity boss (VERIFIED, Query 1, the boss-per-milestone framing). :::animation 2b **ANIMATION 2b: four gates with real thresholds** - **What it shows:** four gates stand in a row, each with a lock that only opens on a real threshold, HELLO WORLD on a working effective product, HELLO USERS on people who would be devastated to lose it, HELLO REVENUE on strangers paying profitably through a funnel, HELLO EXIT on a strategy and a wow moment; a build tool tries to pass on a shipped-app token and the second gate stays locked - **Narrative role:** anchors the second claim, the four-milestone staging as validation gates the market lacks - **What it teaches:** each milestone is a real threshold, not a celebration of shipping code or completing a document - **Intended impact:** the reader sees the gates as the validation structure the existing tools skip ::: Third, "obsessed with the operational hierarchy, the nine rungs, they help align everything" plus "leverage PRD Master to mass produce all the underlying pieces" is the rigor and the planning-to-execution wiring. MVP Mammoth grounds the whole journey in the nine-rung operational hierarchy so the milestones and gates ladder from vision down to tasks, the dependencies line up, and PRD Master generates the underlying specs, all connected to Notion, ClickUp, and Linear under the hood. The market analysis names this as the alpha, the edge nobody has claimed: encode a rigorous operational hierarchy as first-class product structure, use the spec engine to translate milestone goals into concrete PRDs and validation experiments, and make planning and execution two faces of the same object so moving a task moves the venture forward (VERIFIED, Query 1). The existing tools produce static outputs (docs, decks) and don't compute progress from what actually happens in the workspace tools; MVP Mammoth is the living, staged operating system on top of them. :::animation 2c **ANIMATION 2c: planning and execution, two faces of one object** - **What it shows:** a nine-rung ladder grounds a venture from vision down to tasks; the tasks live in Notion, ClickUp, and Linear, and when one is completed there, the venture's progress bar advances on the plan side in real time, planning and execution rendered as two faces of a single rotating object - **Narrative role:** anchors the third claim, the operational-hierarchy grounding and planning-to-execution wiring - **What it teaches:** the nine rungs ladder the journey and moving a real task moves the venture, computed from actual workspace activity - **Intended impact:** the reader sees the living system that static plan-generators lack ::: Fourth, "the average non developer is not going to have a great time bouncing between all of those tools, we need to make it easy, we need to make it fun, video game engineer" is the UX thesis, and it's the gamification standard of the sibling brand Agent Design Pro, applied to the venture journey. The market analysis confirms the opportunity: almost no tool treats the founder journey as a game with a world map, zones, quest lines, and visible progress, and adoption research shows that UX and structured onboarding matter as much as raw power (VERIFIED, Query 1). Andy's instinct to present Hello World through Hello Exit as a navigable, rewarding journey for non-developers is the framing that converts the overwhelm into motion, and it shares the video-game-engineer craft standard the ecosystem applies across its customer-facing tools `projects/agent-design-pro.md`. :::animation 2d **ANIMATION 2d: the journey as a game the founder can play** - **What it shows:** a non-developer stares at a tangle of disconnected tools and agents, overwhelmed; the tangle resolves into a clear world map with zones, quest lines, and a visible progress bar, the founder now moving from one lit checkpoint to the next instead of freezing - **Narrative role:** anchors the fourth claim, the video-game-engineer UX thesis for non-developers - **What it teaches:** presenting the journey as a navigable game converts overwhelm into motion for the non-technical founder - **Intended impact:** the reader sees the UX as the mechanism that turns paralysis into a playable path ::: ## 3. The three-angle valuation (the core of a self-standing brand) MVP Mammoth sits at the intersection of three growing markets (AI MVP builders, AI venture-planning tools, and founder operating systems), and its distinctive valuation property is that it occupies the planning-and-orchestration layer above the commoditizing app-builders, the layer that owns the journey rather than the build. Its software angle is a staged venture-OS, its service angle is venture-planning delivery, and its finance angle benefits from the planning-to-execution control-plane position. ### 3a. Finance (credit and capital access) The category read places MVP Mammoth in a multi-billion-dollar opportunity by 2026: the AI-assisted MVP-building and agentic-workflow-design space is in the low-to-mid single-digit billions annually growing over 20% year over year, the AI business-planning and venture-planning software has emerged as its own SaaS category plausibly in the $200M-$500M+ annual range, and both sit inside the broader AI-workflow and hyperautomation spend (the hyperautomation market projected toward $249B by 2032) (VERIFIED, Query 1). The comp logic that matters: the app-builders (Lovable, Bolt, v0, Replit Agent, Base44, Bubble) are valued as build tools, and the business-plan generators (LivePlan, PrometAI, Venturekit and peers) are valued as document tools, but MVP Mammoth is the venture-planning-and-orchestration layer that uses the builders as engines inside its plan and the spec engine underneath, which is a higher-leverage position than either. The relevant multiple ladder is the one established in the PRD Master deck: a pure document or plan generator at roughly 3-6x ARR, a tool with workflow embedding at 5-9x, and an execution-driving control plane at 8-12x ARR when retention and strategic importance are proven (VERIFIED, valuation query, referenced from `projects/prd-master.md` §3a). MVP Mammoth is built for the control-plane reading: it's the living staged operating system on top of the workspace, computing progress from real execution, not a static deck. :::animation 3a1 **ANIMATION 3a1: the multiple ladder climbs with the position** - **What it shows:** three rungs rise, a plain document or plan generator at three-to-six times ARR, a workflow-embedded tool at five-to-nine, and an execution-driving control plane at eight-to-twelve, a MVP MAMMOTH marker climbing to the top rung as it proves retention and strategic importance - **Narrative role:** anchors the finance read, the control-plane valuation position - **What it teaches:** owning the living execution-driving control plane earns a higher multiple than a document or a build tool - **Intended impact:** the reader sees why the orchestration position is worth more than either neighbor ::: MVP Mammoth's revenue is the staged-venture-OS subscription plus the venture-planning service, both recurring, with a retention profile that benefits from the journey structure: a founder mid-journey (between Hello Users and Hello Revenue) has the venture's whole plan, dependency graph, and progress state in MVP Mammoth, which is sticky in the way a system of record is sticky. That recurring, sticky revenue is underwritten like SaaS (revenue-based financing and ARR-backed debt on the standard terms), with the better terms accruing to the higher-retention orchestration position (VERIFIED, valuation query). MVP Mammoth also has a second-order finance angle: because it explicitly models Hello Revenue (funnel economics, CAC, LTV, payback) and Hello Exit (the exit-readiness proof assets) as first-class objects, it generates the structured venture data that makes its users more credit-worthy and capital-accessible, a natural adjacency to the ecosystem's broader finance-angle thesis. The accumulated proprietary state an acquirer pays for is the library of staged journey templates, the validation-gate definitions, and the per-category exit-path models, plus the real progress data across many ventures, which a competitor can't clone by building another app-generator. :::animation 3a2 **ANIMATION 3a2: the venture-state a mid-journey founder cannot leave** - **What it shows:** a founder sits between Hello Users and Hello Revenue with the whole plan, dependency graph, and progress state held inside MVP Mammoth; a departure door is drawn but the cost of walking away, rebuilding all that state elsewhere, looms so large the founder stays, the system sticky like a record of the venture itself - **Narrative role:** anchors the credit-and-retention read, the system-of-record stickiness - **What it teaches:** a founder mid-journey has too much venture state in the system to leave, which makes the recurring revenue sticky - **Intended impact:** the reader sees the retention that underwrites the finance story ::: The ecosystem's standard open-source model applies here too: build the tool for internal use, then open enough of it to recover 1.6 to 1.8 times the internal spend, with the open tool as the wedge and the orchestration layer as the moat, as the PRD Master deck sets out `projects/prd-master.md`. The tri-level market-maker read looks at fundamentals, technicals and sentiment. On fundamentals, the brand holds the venture-planning-and-orchestration position at the intersection of three growing markets, grounded in a real operational hierarchy and a real spec engine underneath. On technicals, the supply of full-lifecycle staged make-money planners is near zero (the field is builders and plan-generators), while demand is exploding because AI made building cheap and made idea-to-revenue the binding bottleneck, which is a steeply favorable order book. On sentiment, the "AI made building trivial, now what" realization is the rising 2026 founder narrative. The named risk is that an app-builder bolts on a thin planning layer or a plan-generator bolts on a thin builder, and the hedge is the depth (the operational-hierarchy grounding, the validation gates, the PRD Master spec engine, the planning-to-execution wiring) that a bolt-on can't replicate. ### 3b. Software (the interface stack) MVP Mammoth's software is a staged venture-OS, and its architecture composes existing pieces rather than building primitives (VERIFIED, Query 1 and the PRD Master repo). The staged-milestone model is the core: the four milestones (Hello World, Hello Users, Hello Revenue, Hello Exit) as first-class objects, each broken into stages and phases, each with explicit validation gates encoding real thresholds (a working effective product for Hello World; consistent use by must-have users for Hello Users, the would-be-devastated bar; strangers paying profitably through a funnel for Hello Revenue, with funnel and CAC and LTV and payback modeled; the exit strategy and proof assets for Hello Exit). That structure is the difference between celebrating an app shipping and treating anything short of Hello Revenue as incomplete (VERIFIED, Query 1). The operational-hierarchy grounding is the second piece: the nine-rung hierarchy as the first-class product structure that ladders the milestones and gates from vision down to tasks, so the venture's state is always answerable (which rung is weak, what must be done to promote to the next milestone) (VERIFIED, Query 1, the operational-hierarchy alpha). The PRD Master integration is the third: MVP Mammoth uses PRD Master under the hood to translate milestone goals into concrete PRDs, task breakdowns, and validation experiments, which is the planning-to-execution connection `projects/prd-master.md`. The workspace integration is the fourth: Notion, ClickUp, and Linear as the execution backbone, where each rung and stage is expressed as tasks and docs, and progress is computed from what actually happens in those tools (completed tasks, metrics logged, experiments run), making planning and execution two faces of the same object (VERIFIED, Query 1, the planning-to-execution alpha). :::animation 3b1 **ANIMATION 3b1: four pieces compose the venture-OS** - **What it shows:** four modules click together into one engine, STAGED-MILESTONE MODEL with its gates, OPERATIONAL-HIERARCHY GROUNDING laddering vision to tasks, PRD MASTER translating goals into specs and experiments, WORKSPACE INTEGRATION wiring Notion, ClickUp, and Linear as the execution backbone, the assembled whole computing progress from real activity - **Narrative role:** anchors the software architecture, the four composed pieces of the staged venture-OS - **What it teaches:** the venture-OS is composed of a milestone model, a hierarchy grounding, a spec engine, and a workspace backbone working as one - **Intended impact:** the reader sees the concrete architecture rather than a vague platform claim ::: The interface is the gamified, video-game-quality UX: the whole journey as a world map (Hello World to Hello Exit), each milestone a zone, each stage a quest line, each phase a quest, with visible progress and unlocking playbooks, which taps intrinsic motivation and makes the vague goals concrete (VERIFIED, Query 1, the gamification alpha; shared craft standard with Agent Design Pro, referenced). On product surfaces and monetization, the staged venture-OS is the SaaS (subscription by venture and seat), the app-builders are engines inside the plan (MVP Mammoth orchestrates them rather than competing with them), PRD Master is the spec engine underneath, and the whole thing runs on the shared agent harness (Symphony AGI's Hermes `projects/symphony-agi.md`) with the chatbot-plus-dynamic-forms interview-me interface that's the ecosystem standard `projects/swarm-layer.md`. The architectural signature is that MVP Mammoth is the governance-and-measurement layer on top of the founder's existing workspace and tools, computing venture progress from real execution, which is the living-system property the static plan-generators lack. :::animation 3b2 **ANIMATION 3b2: the whole journey as a world map** - **What it shows:** the interface renders as a game world map, the four milestones as zones, each stage a quest line, each phase a quest, with a visible progress meter and playbooks that unlock as gates clear, the vague goal of build a business turned into concrete lit checkpoints - **Narrative role:** anchors the gamified, video-game-quality UX - **What it teaches:** the journey is presented as a navigable world map with zones and quests that make vague goals concrete - **Intended impact:** the reader sees the UX that taps intrinsic motivation and drives the engagement retention needs ::: ### 3c. Service (premium-at-accessible boutique delivery) The service angle is venture-planning delivery: doing the staged journey planning for founders and teams who have an idea or a built thing and can't find the path to revenue. The target operator is the technical founder, the small team, or the operator who can build but freezes on the business, who has shipped something nobody wants or has users who won't pay or has generated an AI MVP and hit the now-what wall. The premium-quality-at-accessible-pricing model is delivered through the staged model and the operational-hierarchy grounding: instead of a consultant who writes a business plan and leaves, the engagement installs a living venture-OS that grounds the journey in the nine rungs, gates each milestone on real thresholds, uses PRD Master to generate the underlying specs and experiments, and computes progress from the founder's actual workspace, so the founder always knows which boss they're fighting and what promotes them to the next milestone. :::animation 3c1 **ANIMATION 3c1: a living venture-OS, not a plan-and-leave** - **What it shows:** a consultant writes a business plan, hands it over, and walks out the door leaving the founder alone; that scene dissolves and instead a living venture-OS installs itself, grounding the journey in the nine rungs, gating each milestone, generating specs, and reading the founder's real workspace so it stays alive after the engagement rather than going stale on a shelf - **Narrative role:** anchors the service angle, venture-planning delivery as an installed living system - **What it teaches:** the engagement installs a maintained venture-OS instead of a consultant who writes a plan and leaves - **Intended impact:** the reader sees the delivered thing as an ongoing system, not a one-time document ::: The retainer economics follow the ecosystem standard: $1-2k accessible at entry, $2-12k+ for the real engagements, structured as a venture-planning retainer (we plan and stage your journey to revenue and keep the venture-OS maintained) plus the productized open-tool subscription. The 100-250-customer target puts the service angle's floor around $1M/month, with room to scale above it (VERIFIED, `THE_FLOOR.md`). The trust differentiator answers the deepest fears in the Lexicon of Pain, the words founders use for their problem when they think no one is watching: the dread of building another dead side project ("a GitHub full of corpses"), the paralysis of "I have an idea but no clue what step 1 is," the AI-era despair that "the idea-to-MVP bottleneck is gone, now the bottleneck is idea-to-revenue," and the technical founder's shame of "LARPing as a founder" who freezes on go-to-market and pricing. MVP Mammoth's staged path removes the paralysis (it tells you the next stage and the gate to clear), its make-money focus removes the build-something-nobody-wants trap (Hello Users and Hello Revenue are gates, not afterthoughts), and its grounding gives the technical founder the business structure they freeze without. :::animation 3c2 **ANIMATION 3c2: the three fears the staged path answers** - **What it shows:** three shadows loom over a founder, a GITHUB FULL OF CORPSES, an I-HAVE-AN-IDEA-BUT-NO-STEP-ONE paralysis, and an I-AM-LARPING-AS-A-FOUNDER shame; a staged path lights up beneath him and each shadow lifts as a gate answers it, validation before build, a defined next stage, business structure made concrete - **Narrative role:** anchors the trust differentiator, the deepest fears the staged path removes - **What it teaches:** the staged path answers the dead-project grief, the paralysis, and the technical founder's shame each with a gate - **Intended impact:** the reader sees the emotional payoff mapped to concrete mechanisms ::: What gets partnered to the sister affiliate network is the ongoing venture-planning support and the template maintenance, run through the shared-floor model, where rotating people and AI agents work from one shared workspace (VERIFIED, `THE_FLOOR.md`). The vertical doesn't matter; any founder or team that needs the path from idea to revenue planned and staged qualifies, and the service angle is the proving ground for the productized tool, because the journeys planned for clients refine the staged templates and the gate definitions the open tool ships. ## 4. The personas (5+, modeled to world-experience depth) The language here is pulled from the actual Lexicon of Pain mined in the voice-of-customer research. The texture of this pain is the specific grief of building something nobody wants, the paralysis of not knowing the path, and the AI-era shame of a technical person whose building superpower got commoditized while the business they avoided turned out to be the real work. :::animation p0 **ANIMATION p0: five founders, one stalled journey** - **What it shows:** five founders stand at different dead ends, one before a graveyard of dead projects, one stuck at a line marked users but zero revenue, one drowning in AI-generated prototypes, one frozen at the edge of the business work, one holding a build tool and a plan tool that both leave a gap, and beneath all five runs the same stalled path labeled MY IDEA IS NOT MAKING MONEY - **Narrative role:** frames section 4, the shared buyer under the five personas - **What it teaches:** five surface stories trace to one founder whose idea has stalled short of revenue - **Intended impact:** the reader holds the personas as one stalled founder seen from five angles ::: ### Persona 1: The builder who shipped something nobody wants I'm a builder with a graveyard of dead projects. "I spent 6 months building this and literally nobody cares." "I launched to crickets, not one organic sign-up that wasn't a friend." "I poured my soul into this app and I can't even give it away for free." "Turns out I built something for me, not for a market." "I'm great at building, terrible at getting users." "This is my 3rd SaaS with zero real users, I'm starting to think the problem is me." "I have a GitHub full of corpses." "I shipped the perfect solution to a problem nobody has." "I validated with upvotes, not dollars, big mistake." "I keep falling in love with the solution instead of the problem." The failure hits me where my identity as a maker lives. "Maybe I'm not actually cut out to be a founder, I'm just a coder who likes toys." "Real entrepreneurs get traction, I just make pretty things no one wants." "If I can't make this work after all this effort, maybe I'll never build something people want." "I'm embarrassed to tell friends and family, they think I'm working on my startup and I know it's another dud." I got here because I built before I validated, falling in love with the solution and skipping the question of whether anyone wanted it. Most builders in my seat fail because the building is the fun dopamine hit and the validation is the scary part they skip. The cost to stay stuck is another project in the graveyard and the creeping belief that the problem is me. The cost to get out is letting a staged process force validation before the build. MVP Mammoth gives me the staging that breaks the build-first habit: Hello World and Hello Users as gates I have to clear, with the would-be-devastated bar made explicit, so I find out whether anyone wants it before I pour in six more months, and my GitHub stops filling with corpses. :::animation p1 **ANIMATION p1: validation before the six-month pour** - **What it shows:** a builder reaches for the fun build button but a Hello Users gate drops in front of it, forcing a would-be-devastated check first; the check passes for a real project and fails for a corpse, so the six months of building only pour into things people actually want, and the graveyard stops growing - **Narrative role:** anchors persona 1's transformation, the staging that breaks the build-first habit - **What it teaches:** gating on validation before the build stops the maker from filling a graveyard - **Intended impact:** the builder sees the habit broken by a gate he has to clear first ::: ### Persona 2: The founder with users but no money, or an idea but no path I'm a founder stuck on a line I can't cross. "I have active users but $0 MRR, I don't know how to cross that line." "People say they love it but ghost the second I mention pricing." "I accidentally built a free tool everyone loves and no one will pay for." "Free users are killing me, server bill goes up, revenue stays at zero." "I'm stuck in freemium hell." Or, before that, "I have an idea but no clue what step 1 is." "I keep asking, do I build more, get users, or try to charge, and then I do nothing." "I don't have a roadmap from here to revenue, just a bunch of blog posts in my head." "My brain keeps screaming, what if you pick the wrong thing and waste 3 years?" It shows up as a paralysis braided with shame. "What if the moment I charge, I find out my product isn't valuable?" "Real businesses make money, I'm just running an expensive hobby." "I don't understand pricing, packaging, or offers, and I'm ashamed to admit it." "Everyone online looks like they know exactly what to do next, I feel clueless and behind." "I've been working on my idea for years with nothing to show." I got here because building has a clear next step and monetizing doesn't, so I default to building or to nothing. Most founders in my seat fail because no tool sequences the journey, so the paralysis wins. The cost to stay stuck is freemium hell and the expensive hobby. The cost to get out is following a staged path instead of spinning. MVP Mammoth hands me the roadmap from here to revenue that I don't have: Hello Revenue as a defined stage with the funnel and pricing and profitability gates, and the sequence decided so I know whether to build, get users, or charge next, so I cross the line out of freemium hell instead of doing nothing. :::animation p2 **ANIMATION p2: the line out of freemium hell** - **What it shows:** a founder spins in place between three signs, BUILD MORE, GET USERS, CHARGE, doing nothing; a staged path resolves the spin into a decided sequence with a Hello Revenue gate defining the funnel, the pricing, and the profitability bar, and he steps across the line from free users to paying strangers - **Narrative role:** anchors persona 2's transformation, the roadmap from here to revenue - **What it teaches:** the paralysis breaks when the sequence is decided and Hello Revenue is a defined stage with real gates - **Intended impact:** the stuck founder sees the spin replaced by a next step ::: ### Persona 3: The AI-build-tool user who hit the now-what wall I'm someone who used an AI tool to build fast and slammed into the real problem. "AI built my MVP in an afternoon and I realized building was never the real problem." "I used Lovable to generate a full-stack app in an hour and then hit a wall: what now?" "We're drowning in auto-generated MVPs that nobody uses." "AI made the first 10% trivial, the hard 90% is still on me." "The idea-to-MVP bottleneck is gone, now the bottleneck is idea-to-revenue." "Bolt spat out a decent SaaS in 45 minutes, I've spent 3 months stuck on positioning and GTM." "AI gave me a product, not a business." "AI made building so cheap that now I'm competing with 100 clones of my idea." "The fun dopamine hit is hitting generate, the pain is everything after." It turned into a deeper identity question than I expected. "If building was my advantage, and AI took that away, what do I bring to the table now?" "I thought AI would make me unstoppable, instead I just build more junk faster." "How do I stand out if my superpower, coding, is commoditized?" "What if this proves it was never about time to build and always about am I good enough to sell?" I got here because the AI tools made building so cheap that I kept generating, and the cheapness exposed that building was never the bottleneck. Most people in my seat fail because they keep hitting generate and avoiding the business. The cost to stay stuck is the hoard of AI-generated prototypes that make no money. The cost to get out is adopting the layer above the build tool. What I get from MVP Mammoth is the layer that starts where the AI build tool stops: it uses Lovable and Bolt as engines inside a staged plan, then owns the hard 90% from the generated MVP to Hello Revenue, so the cheap building becomes a real business instead of another prototype in the hoard. :::animation p3 **ANIMATION p3: the layer that starts where the build tool stops** - **What it shows:** an AI build tool spits out an MVP in an hour and halts at a wall marked NOW WHAT; MVP Mammoth picks up exactly at that wall, using the build tools as engines inside a staged plan and carrying the generated MVP through the hard ninety percent to Hello Revenue, the prototype hoard turning into one real business - **Narrative role:** anchors persona 3's transformation, the layer above the build tool - **What it teaches:** the fix is a layer that starts where the build tool stops and owns the journey to revenue - **Intended impact:** the AI-tool user sees the now-what wall become the start of the real path ::: ### Persona 4: The technical solo founder frozen on the business I'm a developer who can build anything and freezes the moment it's time to do business. "I'm a developer trying to LARP as a founder." "I can ship code but I freeze when it's time to talk to customers." "I'm terrified of sales calls, I'd rather refactor my entire codebase than send one cold email." "Real founders seem to just know how to do GTM, pricing, etc., I feel like I missed that class." "I would rather rewrite the onboarding flow 10 times than reach out to 10 potential customers." "Pricing makes me physically anxious, I just undervalue it or make it free to avoid the discomfort." "I keep hiding behind I'm still building because I'm scared to put it in front of real people." It plays as a constant shame soundtrack. "I feel like a fraud every time I say my startup." "I'm supposed to be smart, but I don't understand CAC, LTV, funnels, ICPs, I feel stupid." "I don't feel like a real founder, I feel like a fanboy of real founders." "I'm gambling years of my life and I might have nothing to show except GitHub repos and Medium posts." "Everyone thinks I'm working on my startup, inside I feel like I'm playing startup." I got here because building is where I'm competent and safe, and the business work is unfamiliar and exposing, so I hide in the code. Most technical founders in my seat fail because they keep hiding in the build. The cost to stay stuck is years gambled with nothing to show. The cost to get out is letting a system structure the business work I freeze on. MVP Mammoth supplies the business structure I freeze without: the journey from idea to revenue laid out as a clear, gamified, staged path with the GTM and pricing and funnel work made concrete at each gate, so I stop hiding in the code and start fighting the actual bosses, with the structure a real founder seems to just know. :::animation p4 **ANIMATION p4: the business work made a concrete quest** - **What it shows:** a developer hides inside a wall of code while a void marked GTM, PRICING, FUNNEL looms outside; the void resolves into concrete quests on a gamified path with each business task made navigable, and the developer steps out of the code to fight the actual bosses with the structure laid in front of him - **Narrative role:** anchors persona 4's transformation, the business structure made concrete and navigable - **What it teaches:** the go-to-market and pricing stop being a void when they are laid out as concrete staged quests - **Intended impact:** the frozen technical founder sees the exposing work turned into a path he can walk ::: ### Persona 5: The public buyer who wants the staged venture-OS I'm a founder or an operator who has seen the app-builders and the business-plan tools and wants the thing in between. The app-builders give me a product and stop; the business-plan generators give me a document that goes stale; neither owns the journey or connects planning to execution. What I want is a living, staged operating system that takes my idea, grounds it in a real framework, gates each milestone on real thresholds, generates the underlying specs and experiments, connects to the tools I already use, and computes my progress from what actually happens, presented as a clear journey rather than a spreadsheet. It lands on me as the person accountable for whether my venture reaches revenue or joins the graveyard. The fear is concrete: buying another app-builder and drowning in prototypes, or another plan-generator and getting a static deck, while the real work (the journey from idea to revenue to exit) goes unsupported. I got here because the market sells builds and documents and the staged-journey orchestration doesn't exist off the shelf. Most buyers in my seat fail by buying a build tool or a plan tool and getting neither the journey nor the revenue. The cost to stay stuck is the prototype hoard or the static deck. The cost to get out is adopting the orchestration layer instead of another point tool. MVP Mammoth is that orchestration layer, productized: the staged Hello-World-to-Hello-Exit journey grounded in the operational hierarchy, gated on real thresholds, wired to my workspace and computing real progress, with the spec engine underneath, so I get the journey and the path to revenue instead of another app or another document. :::animation p5 **ANIMATION p5: the thing in between, productized** - **What it shows:** a shelf holds a build tool that stops at a product and a plan tool that goes stale as a document; between them a glowing product appears, a staged venture-OS grounded in a framework, gated on real thresholds, wired to the buyer's workspace and computing live progress, the in-between thing the market never sold off the shelf - **Narrative role:** anchors persona 5's transformation, the productized orchestration layer - **What it teaches:** the buyer gets the journey-owning orchestration layer instead of another app or another document - **Intended impact:** the public buyer sees the missing in-between thing finally exist as a product ::: ## 5. The world model (run the PST framework) **Echolocate the world.** PST (Problem, Story, Transformation) starts by reading the whole world around the buyer. The substrate is the 2026 moment where AI made building trivial and exposed that building was never the bottleneck: the idea-to-MVP bottleneck is gone, the binding constraint is now idea-to-revenue, and founders are drowning in auto-generated MVPs that make no money (VERIFIED, Query 1 and Query 2). The institutional read finds three growing markets intersecting here (AI MVP builders, AI venture-planning, founder operating systems), real and monetized demand, and a gap: a tool that owns the whole journey from idea to exit, gates on profitability, and connects planning to execution. In the metagraph, the knowledge graph the whole ecosystem shares, MVP Mammoth is the venture-planning node, the place where an idea becomes a staged path to money, using PRD Master beneath and the app-builders as engines, so its customer is everyone with an idea or a built thing that doesn't yet make money, and the ecosystem itself, which stages its own brands through this layer. Echolocating the customer means seeing that the public story is "I'm working on my startup" and the private reality is a graveyard of dead projects, freemium hell, and a technical founder hiding in the code from the business they don't know how to do. :::animation 5a **ANIMATION 5a: the bottleneck moved** - **What it shows:** a pipeline where the old choke point, IDEA TO MVP, dissolves as AI makes building trivial, and the pressure surges downstream to a new binding choke point labeled IDEA TO REVENUE where founders pile up drowning in auto-generated MVPs that make no money - **Narrative role:** anchors the echolocation pass, the 2026 shift in the binding constraint - **What it teaches:** AI removed the build bottleneck and exposed idea-to-revenue as the real one - **Intended impact:** the reader sees exactly where the pressure and the opportunity now sit ::: **Locate the Problem.** Here the cycle of suffering is a loop of build into launch-to-crickets into self-doubt into avoidance, with a fresh AI-era cruelty. The pain is concrete: shipping something nobody wants, getting users who won't pay, hitting the now-what wall after an AI build, and freezing on the business work. The fear portfolio underneath is specific and existential: the maker's fear that "maybe I'll never build something people want," the stuck founder's fear that "the moment I charge I'll find out my product isn't valuable," the AI-tool user's fear that "if building was my advantage and AI took it, what do I bring now," the technical founder's fear of "gambling years of my life with nothing to show but GitHub repos," all under the cross-cutting fear of picking the wrong thing and wasting three years. The shame is the founder-identity shame: "real entrepreneurs get traction, I just make pretty things no one wants," "I'm running an expensive hobby," "I'm a developer trying to LARP as a founder," "I feel like a fanboy of real founders." The red line, where accountability lives, is the moment a person stops treating the failure as proof they aren't cut out to be a founder and recognizes it as a missing system: there's no staged path that forces validation, sequences the journey, and structures the business work. Most of this market lives below that line, which is why the brand's content speaks to the dead-project grief and the founder-shame directly. :::animation 5b **ANIMATION 5b: the red line of accountability** - **What it shows:** a founder stands treating each launch-to-crickets as proof he is not cut out for this; a red line on the floor separates that verdict from the truth on the other side, THERE IS NO STAGED PATH THAT FORCES VALIDATION AND STRUCTURES THE BUSINESS, and most of the market clusters on the self-blame side of the line - **Narrative role:** anchors the locate-the-problem station, the accountability move most will not make - **What it teaches:** the failure is a missing system, not proof the founder is not cut out for this - **Intended impact:** the reader recognizes the self-blame that keeps the loop closed ::: **Reconstruct the Story.** The belief structure that built this suffering starts from a true and load-bearing self-concept for the technical builder: "I am a capable maker, building is my superpower, if I build something good enough it will work." The build-it-and-they-will-come fantasy bent it: each launch-to-crickets registered as "I make things nobody wants" when the truer reading was "I built before I validated," and because building is the safe, competent, dopamine-rich activity, the maker retreated into more building rather than the exposing business work. The AI era added a brutal twist: the marketing said AI would make them unstoppable, so when the generated MVP made no money, the despair said "maybe I was never good enough to sell" instead of "building was never the bottleneck." The origin of the mess is the ease and the safety of building combined with the unfamiliarity and the exposure of the business, so each retreat into the code was a rational move toward competence and away from discomfort that became load-bearing on an unbuilt business. The uncomfortable identity layer: a person whose worth rests on being a capable maker is repeatedly producing things nobody pays for, is performing either I'm-working-on-my-startup confidence or I'm-still-building avoidance, and is privately afraid they're playing startup and gambling years. The story they tell is "real founders just know how to do this and I should too," and that's the trap, because the missing piece is a staged system and a structure for the business work, not an innate founder gene. :::animation 5c **ANIMATION 5c: retreat into the code hardens into identity** - **What it shows:** a chain forms, EXPERIENCE (launch to crickets) to BELIEF (I make things nobody wants) to BEHAVIOR (retreat into the safe dopamine of building) to RESULT (more corpses, no business) to IDENTITY (I am just a coder who likes toys, LARPing as a founder), with a mask of I'm-working-on-my-startup confidence over a private fear of playing startup - **Narrative role:** anchors the reconstruct-the-story pass, the belief chain and shame layer - **What it teaches:** each safe retreat into the code calcifies into a founder-identity shame masked by public confidence - **Intended impact:** the reader sees the story as a built structure that can be dismantled ::: **Design the Transformation.** The bridge has courage as its hinge, and the courageous act is two-fold and specific: validating before building (clearing Hello Users before pouring in the months), and facing the business work (the GTM, the pricing, the funnel) instead of retreating into the code. From courage flows truth: building was never the bottleneck, the dead projects came from skipping validation, the AI exposed that the business is the real work, and not knowing GTM or pricing is a missing skill, not a missing founder gene. From truth flows responsibility: adopting a staged path that gates on validation and revenue and structures the business work, instead of building another thing or hiding in the code. From responsibility flows healing: the maker validates before building and stops filling the graveyard, the stuck founder gets the roadmap from here to revenue and crosses the line, the AI-tool user gets the layer that turns the cheap build into a business, and the technical founder gets the business structure made concrete and navigable. From healing flows forgiveness of the earlier self who built before validating and hid in the code, who wasn't unfit for this, who was doing what a capable maker does when building is safe and the business is exposing. The transformation is crossable because MVP Mammoth makes the path concrete and gamified (the next stage and the next gate are always visible) and because it uses PRD Master and the build tools as engines so the founder isn't starting from a blank canvas. The brand proves to the stuck founder that it understands the dead-project grief and the founder-shame better than he says aloud, and that recognition, plus a navigable path, earns the bridge. :::animation 5d **ANIMATION 5d: courage, then the staged bridge** - **What it shows:** a founder on a near bank of dead projects and self-doubt takes one courageous step, VALIDATE BEFORE BUILDING and FACE THE BUSINESS WORK; a bridge extends plank by plank, the first reading BUILDING WAS NEVER THE BOTTLENECK, each further plank a cleared gate with PRD Master and the build tools as engines, until he reaches a far bank of a venture that makes money - **Narrative role:** anchors the design-the-transformation pass, courage as the hinge and the crossable bridge - **What it teaches:** the bridge opens with the courageous act and the truth that the missing piece was a system, not a founder gene - **Intended impact:** the reader feels the transformation as reachable and navigable, not a leap of talent ::: ## 6. Competitive and market read (the alpha / third door) The competitive field has three camps, and MVP Mammoth's position is defined by sitting above and orchestrating them. The AI app and MVP builders (Lovable, Bolt, v0, Replit Agent, Base44, Bubble) build the thing and celebrate code-shipping, and they don't own the business model, the validation gates, the make-money focus, or the journey to exit (VERIFIED, Query 1). The startup-planning and business-plan tools (LivePlan, PrometAI, Venturekit, BizPlanner, business-model-canvas tools, plus the education of Y Combinator's Startup School and the Mom Test) generate documents or teach concepts, and they don't impose staged validation gates, don't translate the plan into a concrete sequence of experiments and build tasks, and don't connect tightly to execution tools (VERIFIED, Query 1). The founder operating systems and stage-based templates either help with high-level strategy or focus on tactical execution, and very few enforce a rigorous, codified operational hierarchy that defines what done means at each stage and ladders up to monetization and exit (VERIFIED, Query 1). Across all three, the tools stop at app-built or plan-written, and the journey to revenue and exit is unsupported. :::animation 6a **ANIMATION 6a: three camps, all stopping short** - **What it shows:** three camps line up, APP AND MVP BUILDERS stopping at a shipped app, PLANNING AND BUSINESS-PLAN TOOLS stopping at a written document, FOUNDER OPERATING SYSTEMS covering only half the ladder, and past all three a dark stretch labeled THE JOURNEY TO REVENUE AND EXIT that none of them enters - **Narrative role:** anchors the competitive set, the three camps and the shared shortfall - **What it teaches:** every camp stops at app-built or plan-written, leaving the journey to revenue unsupported - **Intended impact:** the reader sees the gap is structural across all three camps ::: The alpha, in the spirit of Andy's third-door definition, is a tool that plans the whole journey from idea to exit in staged milestones, gated on profitability, grounded in a rigorous operational hierarchy, gamified, and wired directly into execution, using the app-builders as engines inside the plan and the spec engine underneath. The existing tools leave five specific openings, and together they're the alpha: treating anything short of Hello Revenue as incomplete and Hello Exit as the natural final boss (the make-money-and-exit focus the builders and plan-tools both skip); staged validation gates with real thresholds per stage (the must-have-user bar, the funnel and LTV:CAC and payback gates) that no tool imposes; a rigorous operational hierarchy as first-class structure that links vision to strategy to PRDs to tasks to metrics (which the strategy tools and the execution tools each cover only half of); a tight planning-to-execution link where moving a task in Notion or ClickUp or Linear moves the venture forward in a codified progression and progress is computed from real execution (which the static plan-generators lack); and a gamified world-map UX that turns the founder journey into navigable zones and quests (which almost no tool attempts) (VERIFIED, Query 1). The incumbents don't assemble this because a build tool's business is shipping code and a plan tool's business is generating a document, and owning the full staged journey from idea to exit, gated on profitability and wired to execution, is a different and harder business than either, which is the line between a commoditizing build-or-document category and an orchestration layer. :::animation 6b **ANIMATION 6b: five openings assemble into the alpha** - **What it shows:** five puzzle pieces snap together into one lit shape, MAKE-MONEY-AND-EXIT FOCUS, STAGED VALIDATION GATES, OPERATIONAL-HIERARCHY STRUCTURE, PLANNING-TO-EXECUTION LINK, GAMIFIED WORLD-MAP UX, the completed shape glowing as the third door no single incumbent assembles - **Narrative role:** anchors the alpha, the five specific openings the existing tools leave - **What it teaches:** the alpha is five openings assembled into one, which is a harder business than shipping code or a document - **Intended impact:** the reader sees the composite that no build tool or plan tool builds ::: On a Wardley map, which places each capability on an axis running from new (genesis) to commodity, the read is clear. App-building and business-plan-drafting are heading to commodity fast (AI generates an app in an hour and a plan in minutes), which is why MVP Mammoth uses the builders as engines and doesn't compete on the build or the document. The staged-milestone model and the validation gates sit at custom-built heading toward product. The operational-hierarchy-grounded, planning-to-execution-wired, gamified venture-OS sits in genesis: nobody owns the full staged journey as a living system that computes progress from real execution, and that's the lane to own hardest, because it's genesis-stage, it accumulates the staged-template and gate-definition and exit-path-model moat plus the cross-venture progress data, and it's the orchestration position above the commoditizing builders. So the strategy reads: use the commoditizing builders and the spec engine as engines, own the staged-milestone model and the validation gates and the operational-hierarchy grounding and the planning-to-execution wiring, and make owning the journey to revenue, not the build, the brand's signature. :::animation 6c **ANIMATION 6c: use the commodity as an engine, own the journey** - **What it shows:** a Wardley axis from genesis to commodity; app-building and business-plan-drafting slide fast toward the commodity end tagged USE AS ENGINE, the staged-milestone model and gates sit mid-axis heading toward product, and the operational-hierarchy-grounded, execution-wired, gamified venture-OS sits at the genesis end tagged OWN, glowing and load-bearing - **Narrative role:** anchors the Wardley read - **What it teaches:** building and plan-drafting are commoditizing, so the lane to own is the genesis-stage staged venture-OS - **Intended impact:** the reader holds the clean use-as-engine-versus-own line behind the position ::: The market is the three-market intersection with the idea-to-revenue bottleneck now binding because AI made building cheap, and the demand signal is unmistakable in both the market structure and the Lexicon of Pain (the graveyards, the freemium hell, the now-what wall) (VERIFIED, Query 1 and Query 2). The precise carve-out for the full-lifecycle staged-venture-OS niche isn't separately sized and is tagged OPEN, but the position is strong: a market full of founders drowning in builds that make no money has enormous latent demand for the layer that owns the path to revenue. :::animation 6d **ANIMATION 6d: three markets meet at the binding bottleneck** - **What it shows:** three market circles overlap, AI MVP BUILDERS, AI VENTURE-PLANNING, FOUNDER OPERATING SYSTEMS, and at their intersection a bright node pulses labeled THE PATH TO REVENUE, surrounded by a crowd of founders drowning in builds that make no money, the latent demand visible as pressure toward that node - **Narrative role:** anchors the market read, the three-market intersection with the binding idea-to-revenue bottleneck - **What it teaches:** three growing markets meet exactly where the binding bottleneck now sits, with enormous latent demand - **Intended impact:** the reader sees the market position as strong even with the niche TAM left open ::: ## 7. The build (what this brand needs, where Track R feeds Track P) MVP Mammoth's build composes existing pieces rather than building primitives: it uses PRD Master under the hood, the app-builders as engines, the project tools as the backbone, and the harness to run. The open-source research track (Track R) feeds this build through its reasoning and orchestration clusters: the patterns harvested for decision frameworks and workflows feed the staged-milestone logic and the planning-to-execution wiring. :::animation 7a **ANIMATION 7a: compose, do not build primitives** - **What it shows:** MVP Mammoth sits at the center and reaches out to four ready pieces it plugs in rather than rebuilds, PRD MASTER under the hood, THE APP-BUILDERS as engines, NOTION, CLICKUP, LINEAR as the backbone, THE HARNESS to run, with a big red circle-slash over a from-scratch rebuild of any of them - **Narrative role:** anchors the build approach, composing existing pieces rather than building primitives - **What it teaches:** the brand composes the spec engine, the builders, the workspace tools, and the harness rather than rebuilding them - **Intended impact:** the reader sees where the real value is and what the anti-pattern would be ::: The staged-milestone model is the brand's own core to build: the four milestones as first-class objects with stages and phases and validation gates encoding real thresholds, plus the per-category exit-path models. The operational-hierarchy grounding is adopted from the ecosystem's nine-rung model and its spec discipline. The spec generation is delegated to PRD Master under the hood `projects/prd-master.md`, which translates milestone goals into PRDs, task breakdowns, and validation experiments. The app-builders are integrated as engines (Lovable, Bolt, v0, Replit Agent and peers invoked inside the plan to produce the Hello-World artifact, with MVP Mammoth orchestrating rather than competing). The workspace integration is the planning-to-execution backbone (Notion, ClickUp, Linear, where each stage is expressed as tasks and docs and progress is computed from real execution). The interface is the gamified world-map UX (the video-game-engineer craft standard it shares with Agent Design Pro) plus the chatbot-plus-dynamic-forms interview-me interface (the ecosystem standard `projects/swarm-layer.md`). The deployment runs on the harness (Symphony AGI's Hermes `projects/symphony-agi.md`). The leverage is entirely in the orchestration and the staged model; building PRD Master, the app-builders, or the harness from scratch would be the anti-pattern. :::animation 7b **ANIMATION 7b: the brand's own core to build** - **What it shows:** amid the composed pieces, one module glows as the brand's own to build, THE STAGED-MILESTONE MODEL, four milestones with stages, phases, validation gates encoding real thresholds, and per-category exit-path models, while the rest are tagged ADOPTED or INTEGRATED around it - **Narrative role:** anchors the own-core distinction, the staged-milestone model as the brand's proprietary build - **What it teaches:** the milestone model with its gates and exit-path models is what the brand builds itself, the rest it composes - **Intended impact:** the reader sees exactly which piece is proprietary versus adopted ::: The data models come from Scatter Model's typed world-model layer (an entity-component system with Pydantic classes as the intermediate representation `projects/scatter-model.md`), which here types the venture, the milestone, the stage, the phase, the validation gate, the metric, and the exit-path model, and is what makes the venture state coherent and the progress computable. :::animation 7d **ANIMATION 7d: the entities of a venture** - **What it shows:** connected cards assemble on the Scatter Model genome, VENTURE, MILESTONE, STAGE, PHASE, VALIDATION GATE, METRIC, EXIT-PATH MODEL, each typed and linked so the venture state stays coherent and a completed workspace task can update the right card and recompute progress - **Narrative role:** anchors the data layer, the ECS genome that makes venture state coherent and progress computable - **What it teaches:** the venture is modeled as typed linked entities, which is what lets progress be computed from real execution - **Intended impact:** the reader sees the structured spine under the living-system claim ::: The medallion tiers (the bronze-silver-gold layering data engineers use, extended here to diamond) apply to the staged-journey-template library: a freshly composed journey template enters at bronze, a proven and reused template with validated outcomes rises through silver and gold, and the diamond tier is the canonical, repeatedly-successful staged journeys and gate definitions that anchor the product. :::animation 7c **ANIMATION 7c: journey templates refine into the diamond** - **What it shows:** four tiers brighten upward, BRONZE a freshly composed journey template, SILVER and GOLD a proven reused template with validated outcomes, DIAMOND the canonical repeatedly-successful staged journeys and gate definitions that anchor the product, each ascent driven by real outcomes across many ventures - **Narrative role:** anchors the medallion tiers, the staged-journey-template library as the accumulating asset - **What it teaches:** journey templates refine up into canonical staged journeys and gates a competitor cannot clone by building an app-generator - **Intended impact:** the reader sees the compounding template moat built by staging real ventures ::: The open-source harvests that serve it most sit in two clusters. In the reasoning cluster, the decision-framework and value-prioritization harvests feed the staging and gating logic `_synthesis-reasoning.md`; in the orchestration cluster, the workflow-and-coordination harvests feed the planning-to-execution wiring and the app-builder orchestration `_synthesis-orchestration.md`. The exact repo-by-repo harvest list still has to be reconciled against the cluster summaries as they land (INFERRED on the exact repos; the cluster-level fit is VERIFIED against the operation's Track-R structure). ## 8. Priority read (feeds the value rubric) MVP Mammoth sits on top of PRD Master (which it uses under the hood) and depends on the harness, the Scatter Model IR, and the app-builders it orchestrates, so its readiness is gated on PRD Master being usable first. Its leverage is real and of a particular kind: where other brands enable the building of agents or specs, MVP Mammoth enables the staging of any idea into a money-making venture, which makes it the brand most directly tied to the ecosystem's external customer growth and to the founder market. :::animation 8a **ANIMATION 8a: gated on PRD Master beneath it** - **What it shows:** MVP Mammoth sits atop a stack whose base rungs, PRD MASTER, THE HARNESS, THE SCATTER MODEL IR, must be usable before the top can stand; a readiness meter on the base fills, and only then does the top layer light up as ready to launch - **Narrative role:** anchors the dependency read, the gating on PRD Master and the substrate - **What it teaches:** the staged venture-OS cannot precede the spec engine and harness it stands on - **Intended impact:** the reader sees the gating constraint the priority read must weigh ::: The first-pass instinct is Next, sequenced after PRD Master and the harness. The full staged venture-OS depends on PRD Master generating the underlying specs and on the harness to run, so it can't precede them. But it has a distinctive property that pulls it forward in priority once the substrate lands: it's the brand that turns the ecosystem's own internal venture-creation (and its customers' ventures) into staged, gated, executable journeys, which is directly aligned with the external-growth and revenue mission. :::animation 8b **ANIMATION 8b: the brand tied to external growth** - **What it shows:** the ecosystem's own ventures and its customers' ventures both feed into MVP Mammoth, which turns each into a staged gated executable journey and sends money-making brands out the other side, a beam labeled EXTERNAL GROWTH AND REVENUE rising from the flow - **Narrative role:** anchors the strategic-value read, the external-growth alignment that pulls it forward in priority - **What it teaches:** the brand stages the ecosystem's and its customers' ventures into money-making journeys, directly serving the growth mission - **Intended impact:** the reader sees the strategic pull that raises its priority once the substrate lands ::: So the priority read is Next, sequenced in three steps: build the staged-milestone model on top of PRD Master first, then wire the planning-to-execution backbone and the app-builder orchestration, then layer the gamified world-map UX and open the productized version. The dependency on PRD Master is the gating constraint the value rubric should weigh; MVP Mammoth is the application layer that makes PRD Master's spec engine usable by non-technical founders, so it follows PRD Master closely. The final ranking comes from scoring every brand against the value rubric `VALUE_RUBRIC.md`, and this deck's input to it is that MVP Mammoth is a high-value Next-tier brand gated on PRD Master, with strong external-growth potential from the founder market and the gamified-engagement angle. Under the deck's seven-sins gate, a stress test of the read against seven named biases, the staged-model claim breaks into three findings: the staged-milestone model and the validation gates are buildable on top of PRD Master and documented patterns; the planning-to-execution wiring that computes real progress from the workspace is the hard, differentiating part; and the brand's external success depends on the gamified UX actually driving the engagement that the venture-OS retention requires. :::animation 8c **ANIMATION 8c: the call and the hard differentiating part** - **What it shows:** a dial reads NEXT, gated on PRD Master, and beside it a warning light stays lit marked THE PLANNING-TO-EXECUTION WIRING IS THE HARD PART, with a second smaller light reading THE GAMIFIED UX MUST DRIVE REAL ENGAGEMENT, the two conditions the external success rests on - **Narrative role:** anchors the Now/Next call and the differentiating-part caution - **What it teaches:** the desk instinct is Next after PRD Master, and the differentiating work is the execution-wiring and the engaging UX - **Intended impact:** the reader leaves with the priority verdict and the conditions that govern it ::: ## 9. The brand's own nine-rung position :::animation 9a **ANIMATION 9a: the brand's own chain** - **What it shows:** nine rungs climb from a PURPOSE rail that turns any idea into a money-making venture on a staged path, up through mission and objective, down to a single EVENT at the base, a milestone gate cleared, each rung lit in sequence as one aligned brand - **Narrative role:** anchors the brand's own nine-rung position - **What it teaches:** every rung ties back to staging an idea to revenue, ending in the concrete event of a gate cleared on a real threshold - **Intended impact:** the reader sees the brand as coherent from purpose down to captured event ::: - **Purpose (the rails):** turn any idea into a money-making venture on a staged, gated, navigable path, so founders and operators reach Hello Revenue and Hello Exit instead of filling a graveyard with dead projects, and so the ecosystem ships brands that actually make money. - **Mission (rung 1):** be the venture-planning engine that lays out the whole staged journey from idea to exit (Hello World, Hello Users, Hello Revenue, Hello Exit), grounded in the operational hierarchy, using PRD Master under the hood and wired to execution. - **Objective (rung 2):** a living, staged venture-OS that gates each milestone on real thresholds, generates the underlying specs and experiments, computes progress from the founder's workspace, and presents the journey as a gamified world map, sold as SaaS plus venture-planning service. - **Initiative (rung 3):** the platform build, sequenced after PRD Master and the harness, staged-model first then execution-wiring then gamified UX. - **Project (rung 4):** the staged-milestone model and validation gates, the operational-hierarchy grounding, the PRD Master integration, the app-builder orchestration, the workspace backbone, and the world-map UX. - **Task (rung 5):** one milestone definition, one validation gate, one exit-path model, one app-builder integration, or one workspace connector, owned by the relevant lane. - **Decision (rung 6/7):** the recurring judgment points: which milestone the venture is at and what gate promotes it (heuristic: the real thresholds, the would-be-devastated bar, the funnel and LTV:CAC and payback); whether to build more, get users, or charge next (heuristic: the staged sequence, not the founder's anxiety); how much rigor a stage needs (heuristic: delegated to PRD Master's complexity assessment); which exit path to design toward and which proof assets are missing (heuristic: the per-category exit models). - **Data (rung 8):** the ventures and their milestone and stage and phase state, the validation gates and metrics, the funnel and economics data, the exit-path models and proof-asset inventories, and the staged-journey templates, all modeled on the Scatter Model IR and computed from the workspace execution. - **Event (rung 9):** the real occurrences captured: a venture staged, a milestone gate cleared, a validation experiment run, a Hello-World artifact built, a paying stranger converted through a funnel, an exit proof-asset acquired, a journey template reused. If the milestone is not gated on a real threshold and the progress is not computed from real execution, it did not happen, which is the make-money-not-just-build discipline the brand sells. ## 10. Sources - **Recording transcript:** `looikos_andy_transcript.md` lines 643-685 (Andy's complete MVP Mammoth walkthrough: using PRD Master under the hood; planning what you're actually building at the venture level, not individual spec sheets; the four milestones Hello World / Hello Users / Hello Revenue / Hello Exit, each broken into stages and phases, with the rigorous definitions, the must-have / would-be-devastated user bar, the avoid-low-value-users warning, the strangers-paying-profitably-through-a-funnel bar, the exit strategy and the wow moment; grounding in the nine-rung operational hierarchy; PRD Master mass-producing the underlying pieces; the dependency line-up and the research and competitive intelligence; the Notion/ClickUp/Linear connection under the hood; the video-game-engineer UX for non-developers). - **Cross-referenced ecosystem docs (referenced, not duplicated):** `projects/prd-master.md` (the spec engine MVP Mammoth uses under the hood, and the shared valuation multiple ladder and open-source-wedge framing). `projects/agent-design-pro.md` (the shared video-game-engineer gamified-UX craft standard). `projects/swarm-layer.md` (the chatbot-plus-dynamic-forms interview-me interface standard). `projects/symphony-agi.md` (the Hermes harness it runs on, and the shared agent-infra valuation read). `projects/scatter-model.md` (the ECS/Pydantic-IR world-model layer). `THE_FLOOR.md` (the service-angle delivery model and economics). - **Perplexity Query 1 (venture-planning + app-builder market + alpha), verbatim:** "Researching the 2026 market for a brand called MVP Mammoth: an AI-powered venture-planning / idea-to-revenue staging tool... tracked through four high-level milestones (Hello World, Hello Users, Hello Revenue, Hello Exit)... uses a spec-engine (PRD Master) under the hood, grounded in a nine-rung operational hierarchy, connects to Notion/ClickUp/Linear, gamified video-game-quality UX... 1) market size and demand for AI startup/MVP builders and venture-building/founder-planning tools... 2) named competitors: AI app/MVP builders (Lovable, Bolt.new, v0, Replit Agent, Base44, Bubble), startup-planning tools (LivePlan, business-model-canvas, YC Startup School, Mom Test apps), founder operating systems... 3) where's the alpha / third door for a tool that plans the WHOLE journey from idea to exit in staged milestones, grounded in an operational hierarchy, gamified, connecting planning to execution?" Findings: the three-market intersection and sizing (AI MVP/agentic-workflow low-to-mid single-digit billions >20% YoY; AI business-planning $200-500M+; hyperautomation toward $249B by 2032); the per-competitor what-they-do/refuse table (builders celebrate code-shipping, plan-tools celebrate document-completion); the five-part third door (make-money-and-exit focus, staged validation gates, operational-hierarchy structure, planning-to-execution link, gamified world-map UX) plus the boss-per-milestone framing. Citations included simonkingsnorth ai-business-planning-tools-2026, ventureplanner best-business-plan-software-2026, bayone ai-powered-business-ventures-2026, helium42 best-ai-tools-for-business. - **Perplexity Query 2 (Lexicon of Pain / VoC), verbatim:** "I need the Voice of Customer / Lexicon of Pain in their actual words (Reddit r/Entrepreneur, r/startups, r/SaaS, r/indiehackers, Indie Hackers forum, r/SideProject, Hacker News, founder Discords) for people trying to go from idea to a money-making product in 2026, especially with AI build tools: 1) builders who shipped something nobody wants... 2) founders stuck at 'I have users but no money' or 'I have an idea but don't know the path'... 3) the AI-build-tool disillusionment ('built me an app in an hour and now what')... 4) the overwhelm and shame of solo founders who don't know business." Findings: the four pain clusters with quotable phrases ("I built it and nobody came," "a GitHub full of corpses," "I validated with upvotes, not dollars," "I have active users but $0 MRR," "stuck in freemium hell," "the idea-to-MVP bottleneck is gone, now the bottleneck is idea-to-revenue," "AI gave me a product, not a business," "I'm a developer trying to LARP as a founder," "I feel like a fanboy of real founders") plus the founder-identity-shame and waste-years-fear cross-cutting themes. Used directly in §4 personas and §5 PST. - **Perplexity valuation comps (reused from the same-category PRD Master run), referenced from `projects/prd-master.md` §10:** the document-generator (3-6x ARR) vs workflow-embedded (5-9x) vs execution-control-plane (8-12x) multiple ladder, the 2026 SaaS bands, and the open-source-wedge / orchestration-moat framing, applied here with the app-builder and venture-planning market figures from Query 1. Used in §3a. - **Build reality:** drawn primarily from Query 1 (the app-builder and planning-tool capabilities and the staged-lifecycle alpha) plus the first-party PRD Master repo (which MVP Mammoth uses under the hood; see `projects/prd-master.md`), so no separate build-reality Perplexity query was needed; the staged-milestone model and the planning-to-execution wiring are grounded in Query 1's explicit alpha analysis. - **VoC channels mined (via Query 2):** r/Entrepreneur, r/startups, r/SaaS, r/indiehackers, Indie Hackers forum, r/SideProject, Hacker News, founder Discords. Note: Perplexity reconstructed representative phrasing rather than live-scraping; the phrases are evidence-tagged as VoC-pattern (INFERRED-representative), consistent with the documented 2024-2026 indie-founder and idea-to-revenue discourse. - **Evidence tags:** the transcript seed, the three-market structure and figures, the named competitors and the staged-lifecycle alpha, and the PRD-Master-under-the-hood build are VERIFIED (first-party and Perplexity-cited). The precise full-lifecycle staged-venture-OS niche TAM is OPEN. The three-angle valuation figures for MVP Mammoth itself and the persona internal monologues are INFERRED (modeled from comps and the VoC lexicon). The exact Track-R repo harvest list is INFERRED-pending the cluster syntheses.