# CloudNative Co > **A note on sources:** the external documents this report refers to were copied into `canon/` on 2026-07-05. The report's citations record what it read when it was written and are left verbatim; to follow one to the live document, open the copy under `canon/`. :::animation HERO **HERO: The black-box bill made into a per-model P&L** - **What it shows:** a towering, opaque cloud-bill invoice (twenty pages of incomprehensible line items, a six-figure total pulsing red) on the left; CloudNative Co's lens passes over it and the opacity resolves into a clear, attributed breakdown where a glowing red wedge labeled "GPU inference / training waste" separates out from the legitimate spend; an engineer-and-finance pair, previously turned away from each other, now both read the same clear per-model cost-and-margin picture and shake hands. - **Narrative role:** sets the scene; this is the share/card thumbnail. It frames CloudNative Co as the brand that turns an out-of-control, unreadable AI cloud bill into an attributed, fixable, margin-aware picture both engineering and finance can act on. - **What it teaches:** the one idea is that the AI cloud bill is not an unavoidable tax, it is a black box full of attributable waste that a specialist can find, fix, and turn into a per-model profit-and-loss. - **Intended impact:** the realization that the terrifying, opaque GPU bill can become legible, accountable, and materially smaller without breaking production. ::: | Field | Value | |---|---| | Project | CloudNative Co | | Looikos cluster | Infrastructure & Agent Platforms (the cloud-economics layer: cloud FinOps specializing in AI/GPU cost) | | One-line | A cloud FinOps service-plus-platform that finds the bottlenecks and the waste in a company's cloud bill, fixes them, and finds where they can make more money, specializing specifically in AI cloud costs (GPU training and inference) | | Status | Concept (a service-led brand; the platform layer builds on the ecosystem's harness and data tooling) | | Existing code | None as a standalone product yet; the service is delivered by Andy and the agent fleet, with the platform layer built on the harness (Symphony AGI), the data/IR (Scatter Model), and the metagraph knowledge (WikiDesignCo) | | Desk | desk-infra (written by desk-brands-finish) | | Coverage | VERIFIED-heavy on the seed (Andy's transcript) and on the cloud-spend and FinOps market, the AI/GPU cost reality, the competitor set, and the comps (Perplexity, cited, with real figures and real acquisitions). INFERRED on the persona PST depth (tagged inline). Named acquisitions are primary-source-verifiable (IBM-Apptio, VMware-CloudHealth, NetApp-Spot.io) or retagged OPEN | | Date | 2026-06-21 | --- ## Nine-rung frame (this research task) - **Purpose (the rails):** give the ecosystem the depth to build and run CloudNative Co with agents, not headcount. CloudNative Co is the brand that makes the ecosystem's own AI compute affordable and that sells cost discipline as a high-trust service, so its depth determines whether the ecosystem runs its agents and the clients run theirs without the GPU bill eating the margin. - **Mission (rung 1):** convert Andy's recorded CloudNative Co breakdown into a research-grounded ~10k brand deck, so the cloud-FinOps brand is built and sold from understanding the cloud-bill-shock and AI-cost pain, not from a dashboard-vendor's-eye view. - **Objective (rung 2):** a finished deck at `symphony/stack-recon/projects/cloudnative-co.md`, ~10k words, three-angle valuation modeled, 5+ PST personas to world-experience depth, build section grounded in the FinOps and AI/GPU-cost reality, graded CLEAN by desk-qc-final and the lead. - **Initiative (rung 3):** the symphony-recon Track-P run; the final deck in the desk-brands-finish set. - **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 (input: transcript lines 198-203; output: the brand's shape; failure: seeding from stale docs). A2 skeleton (output: section stubs; failure: prose before skeleton). A3 Perplexity (output: market/VoC/comp grounding; failure: fabricated queries). A4 PST on five personas (output: world-experience personas; failure: demographics not PST). A5 incremental writing (failure: single-pass dump). A6 self-check (failure: declaring done without the probe). A7 hand to the lead (failure: marking done before CLEAN). - **Decision (rung 7):** the evolution stage of the cloud-cost capability (generic visibility-and-tagging FinOps is heading to commodity; AI-workload-aware optimization-as-a-service that takes a savings outcome is the genesis-stage own-it lane; heuristic: Wardley genesis-to-commodity from reception evidence; authority: within-desk). Which personas carry the deck (the five whose cloud-bill-shock and AI-cost and org-dysfunction pain drive the brand; authority: within-desk). The valuation framing (heuristic: FinOps-SaaS comps plus the service-and-savings-share blend plus the AI/GPU premium; authority: desk proposes, lead decides). When a comp cannot be verified (heuristic: retag OPEN; any named acquisition must be primary-source-verifiable; authority: within-desk). - **Data (rung 8):** the deck is the ECS artifact. Entity: BrandDeck:CloudNativeCo. Components: the_template_sections, evidence_tags, word_count, sources, animation_briefs. System: the desk writes it; the lead grades it; it later seeds the metagraph with edges to Symphony AGI, Scatter Model, WikiDesignCo, and the AI-infra brands whose compute it optimizes. - **Event (rung 9):** the real occurrences captured: deck written to disk, animation briefs placed, progress posted, grade recorded, live on the hub. If it is not on disk and live, it did not happen. ## 1. What it is (the one-paragraph truth) CloudNative Co is the cloud-economics brand of the Looikos ecosystem of brands: a cloud FinOps service and platform (FinOps is the practice of managing what a company spends on cloud) that finds the bottlenecks and the waste in a company's cloud bill, fixes them, and finds where they can make more money, with a deliberate specialization in AI cloud costs, the GPU training and inference spend that is now the fastest-growing and most-painful line item in software. In Andy's framing it's all about understanding cloud operations and cloud FinOps, on the premise that cloud is really expensive and one of the biggest bills in software, so what he does is make things cheaper: figure out the bottlenecks and the things people are doing wrong that cost them money, show them how to fix it, and find where they can make more money, especially in AI, in the cloud infrastructure and the training and the inference. The market this serves is enormous and wasteful: public cloud spending is approaching the high hundreds of billions toward 2026, roughly a fifth to a third of it is wasted (the devops-and-FinOps platform Harness alone estimates $44.5B of unused resources in 2025), and AI is now the top future FinOps priority because GPU training runs cost fortunes and inference scales linearly with usage and eats margins. CloudNative Co's answer is to be the AI-workload-aware FinOps layer that the generic visibility tools and the project-based consultancies aren't: it goes past the dashboard and the tagging recommendation into the GPU and the inference architecture, takes a savings outcome, and turns the black-box bill into a per-model profit-and-loss. For the people it serves, CloudNative Co is the answer to a sharp and shameful set of miseries: the surprise six-figure bill nobody can explain, the inference cost that is eating the margins, the org dysfunction where engineering doesn't care about cost and finance can't read the bill, and the helplessness of not knowing where to start cutting without breaking production. :::animation 1 **ANIMATION 1: The find-fix-grow loop** - **What it shows:** a three-beat cycle animated over a client's cloud infrastructure: FIND (a scanner sweeps the infra and lights up the bottlenecks and waste, idle GPUs glowing red), FIX (those red zones are right-sized, scheduled, and re-architected, the red cooling to green without any "production down" alarm firing), GROW (the freed budget and the per-model margin view reveal where the client can invest to make more money); the loop repeats, each pass tighter. - **Narrative role:** opens §1 by making Andy's verbatim "find the bottlenecks, fix them, find where they can make more money" the brand's core mechanism. - **What it teaches:** that the brand is not just cost-cutting, it is a continuous find-fix-grow loop that also surfaces revenue opportunity. - **Intended impact:** the viewer sees cost discipline as a growth lever, not just a defensive cut. ::: :::animation 1a **ANIMATION 1a: past the dashboard, into the GPU** - **What it shows:** a generic FinOps tool stops at a DASHBOARD and a tagging recommendation, a wall it will not cross; CloudNative Co steps through the wall into the GPU and the inference architecture itself, takes a SAVINGS OUTCOME stamped on the contract, and the black-box bill reforms into a per-model PROFIT AND LOSS the buyer can read line by line - **Narrative role:** anchors the §1 differentiation claim, the AI-workload-aware layer the generic tools are not - **What it teaches:** the brand goes past visibility into the model-level architecture and prices on the outcome - **Intended impact:** the reader sees the line between a dashboard vendor and an outcome-owning specialist ::: :::animation 1b **ANIMATION 1b: four miseries the opaque bill breeds** - **What it shows:** four figures cluster around one unreadable invoice, a SURPRISE SIX-FIGURE BILL nobody can explain, an INFERENCE COST eating visible margin, an ENGINEER and a FINANCE lead turned away from each other unable to read the same page, and a fifth frozen at a START-CUTTING switch afraid of breaking production, all bred by the same black box - **Narrative role:** anchors the closing claim of §1, the set of miseries the opaque AI bill leaves - **What it teaches:** the brand answers four concrete pains at once, the surprise bill, the margin drain, the org war, and the paralysis - **Intended impact:** the reader holds the four buyers the brand rescues before meeting them as personas ::: ## 2. Andy's seed, expanded **Andy's words (verbatim from the recording):** "Cloud native co so this is all about understanding cloud operations and cloud finops is what they call it. So the idea here is that cloud is really expensive. It's one of the biggest bills when it comes to software. And so what I do is I help make things a little bit cheaper. I make it to where they have I can figure out the bottlenecks and the things that people are doing wrong that's costing them money and then I show them how to fix it anywhere they can make more money. So cloud native code we especially specialize in AI in cloud info and training and inference and stuff like that." (From the transcript, lines 198-203.) **Reading between the lines:** Andy's seed compresses three claims, each load-bearing. First, "cloud operations and cloud FinOps, cloud is really expensive, one of the biggest bills when it comes to software" is the foundational market claim, and it's precisely correct and quantified. Public cloud end-user spending was roughly $595.7B in 2024 and $723.4B in 2025, with analysts anchoring 2026 in the $800-900B range, and nearly a quarter of businesses spend over $12M a year on public cloud while the vast majority are above $1.2M a year (VERIFIED, Query 1). The waste is real and large: multiple 2024-2026 sources converge on roughly 20-30% of cloud budgets wasted, with Harness estimating $44.5B of unused or underused resources in 2025, which on the full market translates to $160-270B a year of addressable waste (VERIFIED, Query 1). FinOps is now a CTO-and-CIO-level discipline (78% of FinOps practices report into that org, up 18% from 2023), and optimization and waste reduction are still the number-one current priority (VERIFIED, Query 1). The market Andy describes is this: a near-trillion-dollar spend with a hundreds-of-billions waste pool that buyers are increasingly accountable for at the executive level. :::animation 2 **ANIMATION 2: The trillion-dollar bill and the waste pool** - **What it shows:** a giant cloud-spend bar growing year over year ($595.7B in 2024, $723.4B in 2025, toward $800-900B in 2026), with a red sub-band (~20-30%) separating out as "waste," labeled with the $44.5B Harness unused-resource figure and the $160-270B total addressable waste; a counter shows the share of that waste now driven by AI/GPU. - **Narrative role:** grounds §2's first claim in the real market figures. - **What it teaches:** that the opportunity is sized in hundreds of billions of addressable waste, with AI the fastest-growing slice. - **Intended impact:** the viewer grasps the scale of the money on the table. ::: Second, "I can figure out the bottlenecks and the things people are doing wrong that's costing them money and then I show them how to fix it anywhere they can make more money" is the service mechanism, and it's the find-fix-grow loop that differentiates CloudNative Co from the dashboard tools. The market's pain confirms the need: practitioners describe surprise bills nobody can explain, the easy wins being gone (teams have tackled the big obvious waste and now face many harder, smaller optimizations), and a fear of touching anything for risk of breaking production (VERIFIED, Query 1). Andy's loop answers all three: he finds the non-obvious bottlenecks, fixes them safely, and goes past cost-cutting to find where the client can make more money. The "make more money" half is the part most FinOps players ignore, and it's the part that turns a cost-center engagement into a value-center one, which is why the loop includes growth, not just savings. :::animation 3 **ANIMATION 3: The easy wins are gone, the hard ones remain** - **What it shows:** a cloud-waste iceberg; the small visible tip labeled "obvious waste (zombies, orphaned storage), already cut" sits above water, while the large submerged mass labeled "hard, entangled, AI/GPU optimizations" remains, with a nervous engineer at the waterline afraid to dive because "I might break prod"; CloudNative Co descends with the right tools and surfaces the deep savings safely. - **Narrative role:** illustrates §2's second claim, the find-and-fix-the-hard-waste mechanism, and the fear that blocks it. - **What it teaches:** that the remaining waste is the hard, risky, AI-heavy kind that needs a specialist who can cut it without breaking production. - **Intended impact:** the viewer understands why generic advice ("just right-size") is not enough. ::: Third, "we especially specialize in AI in cloud info and training and inference" is the strategic specialization, and it's precisely where the market is moving and where the differentiation is sharpest. AI is now the top future FinOps priority, with 98% of surveyed organizations managing AI costs in FinOps scope, and the pressure is to fund AI initiatives by finding savings elsewhere rather than adding budget (VERIFIED, Query 1). The economics are brutal: frontier training runs cost tens to hundreds of millions, even modest enterprise models cost hundreds of thousands to millions per cycle, and inference is the bigger long-term cost because it scales with every request and latency SLOs push teams to over-provision expensive GPUs, so GPU inference at scale becomes multi-million-dollar annual line items per model (VERIFIED, Query 1). The generic FinOps tools treat GPUs as a resource class, not as AI-domain objects; almost nobody owns the model-level optimization (batching, right-sizing, quantization, workload placement, the per-model unit economics) (VERIFIED, Query 1). CloudNative Co's AI specialization is the third door. Its promise is to "make inference economically sustainable without compromising latency or quality" and to turn the GPU bill from a black box into a per-model P&L, not to "cut cloud 20%." This brand optimizes the compute the AI-infra brands run on, and those sibling brands have separate decks that this one points to without repeating: Symphony AGI for the agent harness `projects/symphony-agi.md`, Solana Brain `projects/solana-brain.md` and the quant brands for the AI-heavy workloads, and Scatter Model for the data and IR layer `projects/scatter-model.md`. :::animation 2a **ANIMATION 2a: GPUs as AI objects, not a resource class** - **What it shows:** a generic tool renders a client's GPUs as gray identical RESOURCE-CLASS blocks it cannot reason about, while CloudNative Co relabels each one an AI-DOMAIN OBJECT, a training run, an inference cluster, a warm latency buffer, and prices each on its own model-level unit economics, batching and quantization and placement levers appearing on each object - **Narrative role:** anchors the third claim of §2, the AI specialization that is the sharpest differentiation - **What it teaches:** the generic tools see GPUs as a resource class while the specialist sees them as AI-domain objects with model-level economics - **Intended impact:** the reader grasps why the AI specialization is the third door, not a feature checkbox ::: ## 3. The three-angle valuation (the core of a self-standing brand) CloudNative Co has a distinctive valuation shape because it's a service-plus-platform with an outcome-based pricing option, in a category with rich, real M&A comps and a documented AI-specialization premium. Its service angle is the near-term cash engine (the find-fix-grow consulting with a savings share), its software angle is the AI-FinOps platform, and its finance angle benefits from both the strategic-acquisition comps and the savings-share-as-quasi-recurring-revenue logic. ### 3a. Finance (credit and capital access) The corporate-finance read has unusually strong real comparable deals (comps) for this category. The strategic-acquisition ceiling is well-established: IBM acquired Apptio (which had earlier bought Cloudability) for $4.6B cash in June 2023, VMware acquired CloudHealth for roughly $500M in 2018, NetApp acquired Spot.io for roughly $450M plus earn-outs in 2020, and IBM acquired Kubecost in 2024 for an undisclosed amount widely placed in the low-to-mid hundreds of millions (VERIFIED, valuation query; the IBM-Apptio, VMware-CloudHealth, and NetApp-Spot.io figures are primary-source-reported, the Kubecost figure is undisclosed and tagged OPEN). Harness, the broader devops-plus-FinOps platform, was last valued around $3.7B (VERIFIED, valuation query). These show that strategic buyers (IBM, NetApp, the hyperscalers, observability vendors) pay premium multiples for category-defining cloud-cost assets, above the SaaS median, because they attach into large installed bases and close capability gaps. The market is large and growing: the cloud-FinOps market is in the mid-teens of billions around 2025-2026 (roughly $15-16B per the Mordor, MarketsandMarkets, and Precedence estimates) growing at high-single-to-mid-teens CAGR (VERIFIED, valuation query; the estimates vary by scope, stated honestly). :::animation 4 **ANIMATION 4: The strategic-acquisition ceiling** - **What it shows:** a tier of real acquisitions stacked as building blocks with their verified prices (IBM-Apptio $4.6B, VMware-CloudHealth ~$500M, NetApp-Spot.io ~$450M, Harness ~$3.7B valuation, IBM-Kubecost undisclosed/OPEN), each labeled with the strategic logic (attach into installed base, close the AI-cost gap); a CloudNative Co marker sits below, positioned as the AI-specialized version strategic buyers would pay a premium for. - **Narrative role:** grounds §3a's comp ceiling in real, primary-source M&A. - **What it teaches:** that cloud-cost assets command real strategic premiums, and the AI-specialized version commands more. - **Intended impact:** the viewer sees the proven exit logic of the category. ::: The valuation logic for CloudNative Co specifically turns on its three revenue streams, which bankers value separately and blend. The pure-platform ARR (the AI-FinOps software) earns the full SaaS multiple (good infra and devops FinOps SaaS trades at roughly 5-8x NTM ARR, category leaders at 8-12x-plus; the 2026 private-SaaS median is 3.8-5.3x revenue). The recurring managed-FinOps-service retainers earn a lower multiple (roughly 3-5x if sticky and standardized, because services are labor-intensive at 30-50% gross margin). The savings-share or outcome-based revenue (taking a percentage of verified cloud savings) earns a middle tier (roughly 5-8x) that rises toward the SaaS multiple the more it can be shown as multi-year, predictable, auditable, and embedded, so it behaves like usage-based SaaS (VERIFIED, valuation query). The decisive premium is the AI/GPU specialization: a product that directly optimizes AI and GPU spend and exposes model-level unit economics can underwrite a premium of roughly one-to-three turns on the ARR multiple above generic FinOps peers, if a meaningful share (say over 25-30%) of managed spend is GPU and AI and the platform demonstrates net-new AI budgets unlocked by its ROI (VERIFIED, valuation query). So CloudNative Co's blended valuation reads as a base case of roughly 5-7x run-rate revenue and a bull case of 8-12x-plus if it shows strong AI/GPU specialization, a majority of revenue in high-quality recurring streams, and deep embedment in clients' FinOps practices. :::animation 5 **ANIMATION 5: Three revenue streams, three multiples, one premium** - **What it shows:** three revenue pipes (platform ARR at 5-8x+, recurring service retainers at 3-5x, savings-share at 5-8x) feeding a blended-multiple meter; an "AI/GPU specialization" booster then adds 1-3 turns to the blend, the meter ticking from a base of 5-7x to a bull of 8-12x+. - **Narrative role:** makes §3a's blended-multiple-plus-AI-premium logic legible. - **What it teaches:** that the valuation is a weighted blend of three differently-priced revenue types, lifted by the AI specialization. - **Intended impact:** the viewer understands how the service-plus-platform-plus-savings-share model is actually valued. ::: For credit and capital access, the savings-share model is the distinctive lever: if 70-80% of accounts renew their savings programs annually and the savings volumes are stable or growing (tied to recurring production GPU usage rather than one-off clean-ups, with minimum commitments or floors in multi-year MSAs), the savings-share behaves like usage-based subscription revenue, and lenders will advance more debt against it, treating the baseline savings as collateralizable cash flow, while equity investors apply near-SaaS multiples (VERIFIED, valuation query). The constraint is measurement and verification: anything hard to audit (disputes over what counts as savings) or exposed to rapid erosion (the customer internalizes the optimization and the revenue collapses) gets discounted, so the more CloudNative Co standardizes the savings definitions, the automated reporting, and the contract terms, the more its revenue is priced like high-quality SaaS (VERIFIED, valuation query). The accumulated proprietary state an acquirer pays the premium for is the AI-workload optimization methodology, the model-level cost-and-margin data across many clients, and the embedded position in clients' FinOps practices, which a generic-visibility competitor can't replicate. :::animation 3a1 **ANIMATION 3a1: savings-share priced like a subscription** - **What it shows:** a stream of verified cloud savings, once treated as one-off clean-up coins that vanish, gets tied to recurring production GPU usage with a floor written into a multi-year contract, and a lender re-reads the stream as collateralizable cash flow, advancing debt against the stable baseline while a disputed or easily-internalized slice stays discounted and dark - **Narrative role:** anchors the §3a credit-conversion claim, the savings-share as quasi-recurring revenue - **What it teaches:** standardized, auditable, floored savings-share borrows like usage-based subscription revenue, unverifiable savings does not - **Intended impact:** the reader sees contract discipline reprice an outcome fee into real credit capacity ::: The tri-level market-maker read looks at fundamentals, technicals and sentiment. On fundamentals, the brand has a large, growing, executive-level-accountable market with a hundreds-of-billions waste pool, an AI specialization that's exactly where the demand is moving, and rich strategic-acquisition comps. On technicals, the FinOps tooling market is crowded with visibility-and-tagging tools and project-based consultancies, but the AI-workload-aware optimization-as-a-service-that-takes-a-savings-outcome position is thinly occupied, which is a favorable order book. On sentiment, AI cost management is the consensus top 2026 FinOps priority. The named risk is that a hyperscaler or an incumbent (IBM, an observability vendor) builds or buys the AI-FinOps capability, and the hedge is the service-led, outcome-based, deeply-embedded position that a tool alone can't replicate. :::animation 3a2 **ANIMATION 3a2: fundamentals, technicals, sentiment** - **What it shows:** a market-maker reads the target on three stacked panels, FUNDAMENTALS showing a hundreds-of-billions waste pool with AI the fastest slice, TECHNICALS showing a crowded visibility-tool field but a thinly-occupied outcome-based-AI lane, SENTIMENT showing AI cost as the consensus 2026 priority with a hyperscaler-builds-it risk flagged and a service-led hedge beside it - **Narrative role:** anchors the §3a tri-level read, the fundamentals-technicals-sentiment framing - **What it teaches:** the position reads well on all three levels, a large waste pool, a thin order book, and consensus demand with a named hedge - **Intended impact:** the reader holds the full market-maker read of the brand in one frame ::: ### 3b. Software (the interface stack) CloudNative Co's software is the AI-FinOps platform that sits above the existing tools and the cloud-provider telemetry, and its architecture is the layer the market lacks (VERIFIED, Query 1). The platform is an AI-workload-aware cost-and-value layer: it integrates the telemetry from the MLOps platforms (the SageMaker, Run:AI, Vertex, Azure ML scheduling and utilization data), the inference hosts, and the model-optimization compilers into one cost-plus-value picture, and exposes the thing none of the generic tools expose: model-level unit economics, the cost per inference, the margin per model, the cost per experiment that leads to a launch (VERIFIED, Query 1). That model-level view is the difference between the CloudZero-class unit-economics tools (which do cost-per-feature attribution but not AI-specific optimization) and the Kubecost-class Kubernetes-cost tools (which treat GPUs as a resource class, not an AI-domain object). The platform's detection finds the AI-specific waste (idle GPUs at 5-20% utilization, over-provisioned inference clusters kept warm for latency SLOs, training runs that blow a quarterly budget), and its safe-optimization levers (right-sizing, scheduling, batching, quantization, spot and preemptible GPU placement, workload locality) give engineering automated ways to cut GPU waste without breaking production (VERIFIED, Query 1). :::animation 6 **ANIMATION 6: The AI-FinOps layer above the stack** - **What it shows:** a stack diagram; at the bottom the cloud providers and the MLOps tools (SageMaker, Run:AI, inference hosts, compilers) each with their own narrow cost view; CloudNative Co's platform sits as a single layer above them, ingesting all their telemetry and resolving it into one unified panel showing cost-per-inference, margin-per-model, and cost-per-experiment, with safe-optimization levers exposed to engineering. - **Narrative role:** grounds §3b's software-architecture claim, the layer-above-the-tools position. - **What it teaches:** that the platform's value is unifying the fragmented AI-cost telemetry into model-level economics the tools below cannot. - **Intended impact:** the viewer sees the distinct software position above the existing FinOps and MLOps tools. ::: Each product surface is priced differently. The platform is the SaaS (subscription by managed cloud spend and by AI-workload coverage), the savings-share is the outcome-priced surface (a percentage of the verified savings the find-fix loop produces), and the managed-FinOps service is the retainer. The platform runs on the ecosystem's stack: the agent fleet that runs the find-fix loop is built on the ecosystem's agent harness (Symphony AGI's Hermes `projects/symphony-agi.md`), the cost-and-model data is typed on the Scatter Model IR `projects/scatter-model.md`, and the FinOps and AI-cost knowledge is held in the metagraph, the ecosystem's shared knowledge graph (WikiDesignCo `projects/wikidesignco.md`). The architectural signature is the revenue-linked view the generic tools refuse to build: "cost per inference, margin per model, cost per experiment that leads to a launch," not "GPU spend by tag." That view is the language that lets engineering and finance finally talk to each other. :::animation 3b1 **ANIMATION 3b1: the language that lets two teams talk** - **What it shows:** an engineer speaking GPU SPEND BY TAG and a finance lead speaking IT COSTS stand on opposite sides of a silence, unable to meet; the platform emits a third language between them, COST PER INFERENCE, MARGIN PER MODEL, COST PER EXPERIMENT THAT LEADS TO A LAUNCH, and both turn toward it and finally speak, the same words legible to each - **Narrative role:** anchors the §3b architectural signature, the revenue-linked view the generic tools refuse to build - **What it teaches:** the platform's real product is a shared language of model-level economics that engineering and finance can both read - **Intended impact:** the reader sees the software value as translation between two teams, not just cost charts ::: ### 3c. Service (premium-at-accessible boutique delivery) The service angle is the near-term cash engine and the brand's defining shape, because cloud FinOps with an AI specialization is a high-trust, high-value service where the buyer can verify the savings. The target operator is the mid-market SaaS company, the AI-native startup, or the digital enterprise running seven-to-nine-figure annual cloud bills with a fast-growing AI/GPU component, where the easy waste is already cut and the remaining savings are hard, entangled, and AI-heavy. The premium-quality-at-accessible-pricing model is delivered through the AI specialization and the savings-share alignment: instead of a project-based consultancy that delivers a six-to-twelve-week assessment and leaves the client to implement (and takes no risk on performance), CloudNative Co is the team that keeps optimizing the AI infrastructure every sprint, takes a savings outcome, and embeds with the ML teams to tune the training pipelines and the inference architecture, which the generic consultancies won't do. The retainer and savings-share economics combine the ecosystem standard with the outcome model: $1-2k accessible at entry, $2-12k+ for the real engagements, plus the savings-share (a percentage of the verified cloud savings, which on a seven-or-eight-figure cloud bill with 20-30% waste is a large absolute number), structured as multi-year MSAs with floors so the revenue is predictable (VERIFIED, `THE_FLOOR.md` and the valuation query). The 100-250-customer target puts the broader service angle's floor around $1M/month, with room to scale well above it, and the savings-share makes the per-client revenue scale with the client's spend (VERIFIED, `THE_FLOOR.md`). The trust differentiator is the answer to the deepest fears the Lexicon of Pain, the words buyers use for the problem among themselves, surfaces: the bill-shock dread ("our AWS bill is insane and nobody knows why"), the margin-erosion fear ("inference is eating our margins," "our GPU bill is bigger than our payroll"), the org-dysfunction exhaustion ("engineering doesn't care about cost, finance can't read the bill, and I'm stuck in the middle"), and the break-prod paralysis ("I'm terrified of breaking prod if I change anything"). CloudNative Co's promises speak that language directly: find where AI is eating your margins and fix it without breaking prod, turn the GPU bill from a black box into a per-model P&L, and give engineering safe automated levers and finance a language they can understand (VERIFIED, Query 1). The ongoing FinOps operation and the implementation are partnered to the sister affiliate network and run on the shared-floor model, with emerging-market senior cloud and MLOps engineers working through the platform and the harness (VERIFIED, `THE_FLOOR.md`). The vertical doesn't matter; any company with a large and AI-heavy cloud bill qualifies, and the service angle is also the proving ground that makes the ecosystem's own AI compute affordable. :::animation 3c1 **ANIMATION 3c1: the consultancy leaves, the partner stays** - **What it shows:** a project-based consultancy hands over a six-to-twelve-week ASSESSMENT BINDER, takes no performance risk, and walks out the door leaving the client to implement alone; beside it CloudNative Co stays embedded with the ML team sprint after sprint, tuning the training pipelines and the inference architecture, its fee tied to a SAVINGS OUTCOME it keeps earning - **Narrative role:** anchors the §3c delivery claim, the continuous embedded model versus the leave-behind assessment - **What it teaches:** the service keeps optimizing every sprint and carries the risk, where the generic consultancy assesses once and departs - **Intended impact:** the reader sees why the embedded, outcome-aligned model is the defining service shape ::: ## 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 is the bill-shock dread, the AI-margin-erosion fear, the engineering-versus-finance org dysfunction, and the break-prod paralysis, braided with the specific shame of senior engineers who can't speak the language of money. :::animation p0 **ANIMATION p0: five people, one opaque bill** - **What it shows:** five figures stand around a single twenty-page invoice glowing at the center, each gripped by a different pain, an ENGINEER who cannot explain it, a FOUNDER watching inference eat margin, a FINOPS LEAD yelled at from both sides, an ENGINEER frozen at a change switch, an AI-NATIVE LEADER whose whole model economics ride on it, all circling the same black box - **Narrative role:** frames the whole persona section, the five pains bred by one opaque AI-heavy bill - **What it teaches:** the five personas differ on the surface but all orbit the same unreadable, unfixable-feeling bill - **Intended impact:** the reader reads the personas as one structure with five entry points rather than five unrelated buyers ::: ### Persona 1: The engineer staring at an unexplainable bill I'm a senior engineer who can't explain our own cloud bill. "Our AWS bill is insane and nobody can tell me where it's coming from." "Every month we get this six-figure bill and I feel like I'm just paying ransom. I have no idea what's actually driving it." "We launched a feature and our cloud bill literally doubled. Finance asked what happened and all we had was a hand-wavy answer about increased usage." "Cloud costs feel like a black box. The invoice is 20 pages of services nobody understands." It hits me where my competence is supposed to live. The fear is "I'll be blamed for negligence." The shame is "as a senior engineer I can't speak the language of money." The resentment is "the bill is my responsibility, but the tools are built for cloud providers and finance, not me." I got here because the cloud bill is opaque (twenty pages of services, no attribution) and nobody on the team owns making it legible. To get out, I need the bill turned from a black box into an attributed, explainable picture where I can answer finance's "what happened" with a real, specific answer. Most engineers in my seat fail because the native billing tools are overwhelming and built for someone else. Staying stuck costs me the ransom feeling and the blame risk. The price of getting out is bringing in a specialist who makes the bill legible. CloudNative Co makes the black box legible: it resolves the twenty-page invoice into an attributed, per-service, per-model breakdown, so I can answer exactly what doubled the bill and why, and I stop paying what feels like ransom for a bill I can't read. :::animation 7 **ANIMATION 7: The twenty-page invoice resolves** - **What it shows:** a chaotic twenty-page invoice of incomprehensible line items flips through rapidly, then collapses into a single clean attributed view where the spike is traced to a specific feature and a specific model, a clear "this is what doubled your bill" arrow pointing at the culprit; the engineer, previously slumped, sits up with an answer for finance. - **Narrative role:** dramatizes persona 1's transformation from black-box ransom to legible attribution. - **What it teaches:** that the first value is making the bill explainable so the engineer can speak to it. - **Intended impact:** the viewer feels the relief of the opaque bill becoming readable. ::: ### Persona 2: The founder watching inference eat the margins I'm a founder whose AI feature is popular and unprofitable. "Inference is eating our margins." "Our LLM feature is popular, but now our GPU bill is bigger than our payroll." "We're paying thousands a day to keep GPUs warm so we don't miss our latency SLOs." "One training run cost more than my house. And the model still wasn't good enough." "Every new model we ship adds another permanent tax to our margin." "We have a cluster of A100s sitting idle most of the time because nobody remembers who asked for them." :::animation p2v **ANIMATION p2v: the GPU bill bigger than payroll** - **What it shows:** a founder watches a popular LLM feature light up with users while, beside it, a GPU bill towers over the payroll line; a cluster of A100s sits idle most of the day because nobody remembers who asked for them, thousands a day burn keeping GPUs warm for latency SLOs, and each new model shipped stacks another permanent tax onto the margin - **Narrative role:** carries persona 2's first-person voice, the raw texture of inference eating the business - **What it teaches:** the pain is a beloved feature that is quietly unprofitable, its GPU cost scaling past payroll - **Intended impact:** the reader feels the specific dread of success that loses money on every request ::: It lands on me as a direct threat to the business. The anxiety is "I'll be told to turn the feature off because it's too expensive." The conflict is "product wants the best newest model, finance wants the cheapest." The helplessness is "GPUs are expensive, what can we do." I got here because the AI feature scaled with usage and the inference cost scaled linearly with it, while the latency SLOs pushed us to over-provision expensive GPUs. To get out, I need someone who specializes in AI cost, who can make inference economically sustainable without compromising latency or quality (batching, right-sizing, quantization, spot placement), and who turns the GPU bill into a per-model P&L so I know which models are actually profitable. Most founders in my seat fail because they either eat the margin erosion or kill the feature. The cost to stay stuck is the GPU bill bigger than payroll and the permanent margin tax. The cost to get out is bringing in an AI-FinOps specialist. CloudNative Co makes inference sustainable, so my popular feature stops being a permanent tax on my margin. :::animation 8 **ANIMATION 8: GPU bill bigger than payroll, then not** - **What it shows:** two bars side by side, "payroll" and "GPU bill," the GPU bar towering over payroll and glowing red with idle-GPU and over-provisioned-inference segments; CloudNative Co's optimization (batching, right-sizing, quantization, spot) shrinks the red segments and the GPU bar drops below payroll, while a small "latency SLO" gauge stays green throughout to show nothing broke. - **Narrative role:** visualizes persona 2's transformation, inference cost brought under control without breaking SLOs. - **What it teaches:** that AI cost can be cut materially while preserving the latency and quality that matter. - **Intended impact:** the viewer feels the margin threat lift without a quality sacrifice. ::: ### Persona 3: The FinOps person stuck between engineering and finance I'm the person caught in the middle of the cost war. "Engineering doesn't care about cost, finance doesn't understand the tech, and I'm stuck in the middle getting yelled at by both." "Finance just tells us to reduce AWS by 30% without any idea what that means for uptime or performance." "We have no real chargeback. It's one giant bill that gets dumped on the CTO, so nobody feels responsible." "I can't tie cloud spend to revenue. It's just this giant bucket of IT costs." "Our tags are a mess; half the resources are misc or untagged, so we literally can't see who owns what." :::animation p3v **ANIMATION p3v: caught in the cost war** - **What it shows:** a FinOps lead stands in a crossfire, ENGINEERING on one side holding uptime is my OKR not cost, FINANCE on the other holding cut AWS by 30 percent, and between them one giant untagged bill dumped on the CTO that nobody feels responsible for; half the resources read misc or untagged, so no arrow of ownership can be drawn - **Narrative role:** carries persona 3's first-person voice, the raw texture of the org dysfunction - **What it teaches:** the pain is structural, budget owned by finance and architecture by engineering with no one holding both and nothing attributable - **Intended impact:** the reader feels the exhaustion of a role with responsibility but no authority or information ::: It makes mine a thankless, exhausting role. The shame is "I don't want to admit we don't know where 30% of our spend is going." The defensiveness from engineering is "uptime is my OKR, cost isn't, don't blame me." The exhaustion is "FinOps becomes another job and nobody takes anything off my plate." I got here because the org has the budget owned by finance and the architecture owned by engineering and no one with both the authority and the information to decide, and the tags are a mess so nothing is attributable. To get out, I need cost attribution that actually works (cost per team, per product, per customer, per model), a showback and chargeback that makes teams own their spend, and a language (cost per feature, margin per model) that lets engineering and finance finally talk. Most FinOps people in my seat fail because the org dysfunction is structural and they have no leverage to fix it alone. Staying stuck means being yelled at by both sides forever. The price of getting out is bringing in a specialist who installs the attribution and the shared language. CloudNative Co gives me the shared language and the working attribution, with cost tied to revenue as well as to model and team, so I stop being yelled at from both sides and the org finally has one accountable picture instead of a giant untagged bucket. :::animation 9 **ANIMATION 9: The bridge between engineering and finance** - **What it shows:** an engineer and a finance lead on opposite cliffs, shouting past each other (engineer holds "uptime is my OKR," finance holds "cut AWS 30%"), the gap between them full of untagged "misc" resources; CloudNative Co installs a bridge of attribution (cost per model, margin per feature, showback by team), the untagged resources resolving into owned ones, and the two meet in the middle reading the same picture. - **Narrative role:** visualizes persona 3's transformation, the org dysfunction resolved by a shared language and attribution. - **What it teaches:** that the value is organizational, giving engineering and finance one accountable picture to act on together. - **Intended impact:** the viewer feels the cross-functional war defuse. ::: ### Persona 4: The engineer paralyzed by the fear of breaking prod I'm an engineer who knows there's waste and is too scared to touch it. "Every article says just right-size your instances, but I'm terrified of breaking prod if I change anything." "I open the billing dashboard and it's overwhelming. Where do you even start?" "We ran a cost-cutting sprint; nobody touched the GPU workloads because they're mission-critical and nobody wants to break them." "We tried downgrading some instances and immediately got paged. Now nobody wants to risk it again." "I'm scared that if I push for aggressive savings and something goes wrong, I'll be the one blamed." For me it's a paralysis that keeps the waste in place. The fear is "if I touch this, I might take down production." The bias is "it's safer to over-spend than under-provision." The frustration is "we know there's waste, but everything is so entangled we can't safely change it." I got here because the easy waste is already cut and the remaining savings are in the entangled, mission-critical, GPU-heavy workloads where one wrong change pages the whole team, so the rational move is to leave the waste alone. To get out, I need a specialist who can make the changes safely (who has done this on AI workloads before, who takes the performance risk, who has the safe levers and the rollback paths), so the deep savings get captured without me being the one who breaks prod. Most engineers in my seat fail because the risk of breaking production outweighs the reward of cutting cost, so the waste persists. The cost to stay stuck is the entangled waste nobody dares touch. The cost to get out is bringing in someone who can cut it safely and take the risk. CloudNative Co is that specialist, so the waste I was too scared to touch gets cut without my name on an incident. :::animation 10 **ANIMATION 10: Safe levers on entangled workloads** - **What it shows:** a tangle of mission-critical GPU workloads wired together, with an engineer's hand hovering nervously over a "right-size" switch and a "PROD" warning light flickering; CloudNative Co's specialist takes over, applying changes through a safe-lever console with visible rollback paths and a green canary check before each change, the tangle untangling and the savings appearing while the PROD light stays steady green. - **Narrative role:** visualizes persona 4's transformation, the deep waste cut safely. - **What it teaches:** that the value is the safe-execution capability and the owned risk, not just the recommendation. - **Intended impact:** the viewer feels the break-prod paralysis lift. ::: ### Persona 5: The AI-native company whose whole model economics are at risk I'm leading an AI-native company where the cloud bill is the business model. Our entire product is GPU-heavy (training cycles plus production inference at scale), our cloud bill is approaching eight figures and growing faster than revenue, and our unit economics depend entirely on the cost per inference. The generic FinOps tools treat our GPUs as a resource class and give us tagging recommendations, the project-based consultancies do a one-time assessment and leave, and neither goes into the model-level optimization that actually moves our economics. Inference is the bigger long-term cost and it scales with every user, so without aggressive, continuous, AI-aware optimization our margins erode as we grow. It falls on me as the person accountable for whether the company is economically viable at scale. The fear is concrete: growing into bankruptcy because each new user adds inference cost faster than revenue, or being forced to compromise model quality or latency to survive. I got here because we built an AI-native product where compute is the dominant cost and the optimization is hard and specialized. To get out, I need a partner who continuously optimizes the AI infrastructure at the model level (the batching, the quantization, the right-sizing, the workload placement, the per-model unit economics), who takes a savings outcome aligned with my margins, and who turns the GPU bill into the per-model P&L that runs my business. Most AI-native companies in my seat fail because the AI cost optimization is too specialized to do in-house and the generic tools don't go deep enough. Staying stuck means growing into negative margins. The price of getting out is adopting a continuous AI-FinOps partner. CloudNative Co is the continuous AI-cost partner my model economics need, so I grow into healthy unit economics instead of growing into bankruptcy. :::animation 11 **ANIMATION 11: Growing into margin, not bankruptcy** - **What it shows:** two divergent trajectories for an AI-native company; the "no optimization" path shows revenue and inference-cost lines crossing as cost overtakes revenue (growing into bankruptcy), while the "CloudNative Co" path shows continuous optimization keeping the inference-cost line below revenue as both grow, the per-model P&L panel staying green. - **Narrative role:** visualizes persona 5's transformation, the model economics made viable at scale. - **What it teaches:** that for AI-native companies, continuous AI-FinOps is the difference between scaling into margin and scaling into loss. - **Intended impact:** the viewer sees the existential stakes and the path through. ::: ## 5. The world model (run the PST framework) **Echolocate the world.** The PST framework (Problem, Story, Transformation, Andy's method for reading a buyer) starts by modeling the buyer's world. Here the substrate is the 2026 cloud-economics reality: a near-trillion-dollar public-cloud spend with a hundreds-of-billions waste pool, FinOps now a CTO-and-CIO-level discipline with optimization as the top priority, and AI cost the top future priority because GPU training and inference are exploding faster than the tooling and the org practices to control them (VERIFIED, Query 1). The institutional read is that the easy waste is cut, the remaining waste is hard and AI-heavy and risky, the generic tools stop at visibility and tagging, and the consultancies do one-time assessments, so the AI-workload-aware, outcome-based, continuous optimization position is open. In the metagraph, CloudNative Co is the cloud-economics node, optimizing the compute that the ecosystem's own AI-infra brands and the clients run on, so its customer is the company drowning in an opaque, AI-heavy cloud bill, and the ecosystem itself, whose AI compute it makes affordable. Echolocating the customer means seeing that the public story is "AI is transforming our product" and the private reality is inference eating the margins, a GPU bill bigger than payroll, an org war between engineering and finance, and a paralysis of not daring to touch the waste. :::animation 12 **ANIMATION 12: The squeeze between AI ambition and AI cost** - **What it shows:** a company stretched between two forces, an upward pull labeled "ship more AI, best models, lowest latency" and a downward drag labeled "GPU cost, inference scaling, margin erosion"; the tension holds it in place, growing strained; CloudNative Co inserts as a release valve on the cost side, letting the company keep its AI ambition without the cost crushing it. - **Narrative role:** opens §5 by grounding the world model in the AI-ambition-versus-AI-cost squeeze. - **What it teaches:** that the customer is not failing, they are caught between a real ambition and a real cost they cannot control alone. - **Intended impact:** the viewer feels the specific tension of wanting AI and fearing its bill. ::: **Locate the Problem.** The station where these buyers are stuck in the cycle of suffering is a loop of bill-shock into blame into paralysis, with a margin-erosion fear running through it. The pain is concrete: the unexplainable surprise bill, the inference eating the margins, the engineering-versus-finance dysfunction, and the break-prod paralysis. The fear portfolio underneath is specific: the engineer's fear of being blamed for negligence and not being able to speak the language of money, the founder's fear of being told to kill the popular feature, the FinOps person's fear of being yelled at by both sides, the cautious engineer's fear of taking down production, the AI-native leader's fear of growing into bankruptcy. The shame is the competence-shame of senior people who can't explain or control their own bill: "I don't want to admit we don't know where 30% of our spend is going," "as a senior engineer I can't speak the language of money." The red line, where accountability lives, is the moment a team stops treating the bill as an unavoidable tax or a personal failing and recognizes it as a black box full of attributable, fixable waste that a specialist can address without breaking production. Most of this market lives below that line, in the loop, which is why the content speaks to the bill-shock dread and the margin fear directly. :::animation 5a **ANIMATION 5a: the red line where accountability lives** - **What it shows:** a horizontal line crosses the frame; below it teams call the bill an UNAVOIDABLE TAX or a personal failing and stay stuck in a loop of bill-shock into blame into paralysis, while a few cross above and rename it a BLACK BOX FULL OF ATTRIBUTABLE, FIXABLE WASTE a specialist can cut without breaking production, the crossing point glowing - **Narrative role:** anchors the Locate-the-Problem movement of §5, the red line between resigned tax and fixable waste - **What it teaches:** the turn happens when a team stops accepting the bill as unavoidable and names it as attributable, addressable waste - **Intended impact:** the reader locates the exact moment a resigned buyer becomes reachable ::: **Reconstruct the Story.** The belief structure that built this suffering starts from a reasonable engineering self-concept: "I build systems, I keep them up, uptime is my job." Cost was finance's problem, so each rising bill registered as "the cloud is just expensive, what can we do," when the truer reading was "we have no cost attribution or optimization discipline," and the AI explosion made it worse because GPU cost scaled with usage faster than anyone modeled. The org structure deepened it: engineering owned the architecture but not the budget, finance owned the budget but couldn't read the bill, so no one had both the authority and the information, and the waste persisted because touching it risked production. The origin of the mess is the combination of cloud's genuine opacity, the AI cost explosion, and the structural split between who owns the architecture and who owns the budget, so each decision to over-provision for safety or to leave the entangled waste alone was rational and became the persistent waste. The identity layer underneath is uncomfortable: senior engineers and leaders whose worth rests on competence and control are repeatedly unable to explain or control their own largest software bill, are performing either AI-ambition confidence or quiet dread about it, and privately fear the bill will force a feature cut or a margin collapse. The story they tell is "the cloud is just expensive and AI is just expensive," and that's the trap, because it accepts the hundreds-of-billions of waste as unavoidable when it's attributable and fixable. :::animation 5b **ANIMATION 5b: the story that keeps the waste in place** - **What it shows:** a belief hardens into a wall reading THE CLOUD IS JUST EXPENSIVE AND AI IS JUST EXPENSIVE, and behind it sit the reasonable steps that built it, engineering owning uptime but not budget, finance owning budget but unable to read the bill, each over-provision-for-safety choice rational and load-bearing; the wall accepts hundreds of billions of waste as if it were fixed - **Narrative role:** anchors the Reconstruct-the-Story movement of §5, the belief structure underneath the suffering - **What it teaches:** the trap is accepting the bill as inherently expensive when the waste is attributable and fixable - **Intended impact:** the reader sees the resigned story as the thing that must be dismantled first ::: **Design the Transformation.** The bridge has courage as its hinge, and the courageous act is admitting that the bill isn't an unavoidable tax to accept, and that bringing in a specialist who can make it legible and cut it safely is the move, not a confession of failure. From courage flows truth: the bill is a black box full of attributable waste, the AI cost is optimizable, the org dysfunction is a missing shared language, and needing a specialist isn't weakness. From truth flows responsibility: installing the attribution, adopting the AI-aware optimization, and aligning on the per-model P&L instead of accepting the opaque bill. From responsibility flows healing: the bill becomes legible, the inference becomes sustainable, the engineering-and-finance war defuses into a shared picture, the entangled waste gets cut safely, and the AI-native company grows into margin instead of loss. From healing flows forgiveness of the earlier self who couldn't speak the language of money, who wasn't incompetent, who was facing a genuinely opaque bill, an exploding AI cost, and a structural org split with no specialist. The transformation is crossable because CloudNative Co takes the savings outcome (aligned incentives, verifiable results) and cuts safely (the owned performance risk, the rollback paths), so the first step is low-risk and the value is provable. For the cloud-cost sufferer, the brand proves it understands the bill-shock dread and the competence-shame better than the customer says aloud, and that recognition, plus a provable, aligned, safe service, earns the bridge. :::animation 13 **ANIMATION 13: The bridge from black box to per-model P&L** - **What it shows:** the courage-to-forgiveness PST bridge over the opaque bill from the hero; a team steps from the "the cloud is just expensive" side onto a bridge whose planks read courage (bring in a specialist), truth (the waste is attributable), responsibility (install attribution and optimization), healing (sustainable inference, defused org war), forgiveness (you were never the problem), arriving at a clear per-model P&L on the far side. - **Narrative role:** the §5 transformation made visual. - **What it teaches:** that the path out reframes the bill as fixable and adopts an aligned, safe specialist. - **Intended impact:** the viewer feels the crossing is low-risk and provable. ::: ## 6. Competitive and market read (the alpha / third door) The competitive field splits into three camps that each stop short of the AI-workload-aware, outcome-based, continuous position. The FinOps platforms (CloudHealth, Apptio Cloudability, Harness, Kubecost, Vantage, Finout, CloudZero, nOps, ProsperOps) deliver visibility, allocation, forecasting, anomaly detection, commitment management, and unit economics, but they generally don't do deep workload-level or model-level optimization for AI and GPU, don't take a savings outcome with owned performance risk, and treat GPUs as a resource class rather than an AI-domain object (VERIFIED, Query 1). The AI and GPU cost tools (the MLOps platforms with cost controls like Run:AI and SageMaker scheduling, the inference hosts like Modal and Replicate and Anyscale whose incentive is to host more workloads, not reduce your compute, the model-optimization compilers like TensorRT and ONNX Runtime, which are developer tools, not FinOps solutions) optimize one slice but don't own the end-to-end cost-and-value story or commit to P&L-relevant outcomes (VERIFIED, Query 1). The cloud-cost consultancies do governance, tagging, assessment, and capability-building, but their work is project-based (a six-to-twelve-week assessment), they don't embed continuously with the ML teams to tune the pipelines, and they recommend rather than implement and take no performance risk (VERIFIED, Query 1). Across all three, the AI-workload-aware optimization-as-a-service that takes a savings outcome and embeds continuously is the gap. The alpha, in the spirit of Andy's third-door definition, is that combination the field declines to assemble: the AI-FinOps layer above all the tools (SageMaker, Run:AI, the inference hosts, the compilers) that integrates their telemetry into one cost-and-value picture, goes into the model-level optimization, takes a savings outcome with owned performance risk, embeds continuously with the ML teams, and provides the revenue-linked views (cost per inference, margin per model, cost per experiment that leads to a launch) that none of the generic tools provide (VERIFIED, Query 1). The reasons the incumbents don't assemble it are structural: the FinOps platforms' business is the tool and the visibility, and committing to P&L outcomes and taking performance risk turns a tool into a heavy service; the AI-cost tools' business is one slice (scheduling, hosting, or compilation) and they have no incentive to reduce your total compute; the consultancies' business is the project-based assessment, and continuous embedded optimization with owned risk is a different model. The differentiation lives where they abstain: the AI-workload specialization (model-level, not resource-class), the outcome-based savings-share alignment, the continuous embedded delivery, the safe-execution-with-owned-risk, and the revenue-linked per-model P&L. :::animation 14 **ANIMATION 14: The unoccupied AI-FinOps position** - **What it shows:** a two-axis map; one axis "AI-workload depth (resource-class to model-level)" and the other "engagement model (one-time tool/assessment to continuous outcome-based service)"; the FinOps tools cluster at resource-class/tool, the consultancies at generic/one-time, the AI-cost tools at one-slice; the upper-right quadrant (model-level depth PLUS continuous outcome-based service) is empty until CloudNative Co lands there. - **Narrative role:** the §6 third-door argument made spatial. - **What it teaches:** that the alpha is the unoccupied quadrant combining model-level AI depth with continuous outcome-based service. - **Intended impact:** the viewer locates the brand's open position clearly. ::: :::animation 6a **ANIMATION 6a: why each camp abstains** - **What it shows:** three camps each stand at the edge of the missing position and turn away for a structural reason, the FINOPS PLATFORM whose business is the tool not owned outcomes, the AI-COST TOOL whose business is one slice with no incentive to shrink total compute, the CONSULTANCY whose business is the one-time assessment not continuous embedded risk, each refusal rational and each leaving the AI-outcome lane open - **Narrative role:** anchors the §6 alpha argument, the structural reasons the incumbents will not assemble the whole - **What it teaches:** each camp declines the AI-workload outcome-based position because building it runs against its own model - **Intended impact:** the reader sees the opening is durable, held open by the incumbents' own economics ::: The Wardley read places each capability on a Wardley map's evolution axis, which runs from genesis (new and custom) to commodity. Generic cloud-cost visibility and tagging is heading to commodity fast (the cloud providers' native tools and the established platforms cover it), which is why CloudNative Co doesn't compete on the dashboard. The AI-workload-aware optimization sits at custom-built heading toward product. The outcome-based, continuously-embedded, model-level AI-FinOps service with the per-model P&L sits in genesis: nobody owns the AI-workload optimization-as-a-service that takes a savings outcome and embeds continuously, and that's the lane to own hardest, because it's genesis-stage, it accumulates the AI-optimization methodology and the cross-client model-cost data moat, and it has the strategic-acquisition appeal that the IBM and NetApp comps prove. So the strategy reads: treat generic visibility as the commoditized baseline, own the AI-workload optimization-as-a-service with the savings-share and the per-model P&L, and signature the brand on making AI economically sustainable, turning the GPU black box into a per-model profit-and-loss. :::animation 6b **ANIMATION 6b: three Wardley stages, three moves** - **What it shows:** an evolution axis runs left to right with three pieces placed on it, GENERIC VISIBILITY AND TAGGING sliding into commodity and marked baseline, AI-WORKLOAD OPTIMIZATION at custom-built heading to product and marked own, the OUTCOME-BASED EMBEDDED AI-FINOPS SERVICE with a per-model P&L sitting far left in genesis and marked own hardest, each piece labeled with its stage and strategy - **Narrative role:** anchors the §6 Wardley read, where each capability sits and what to do about it - **What it teaches:** treat visibility as commodity baseline, own the AI-workload optimization, own the genesis-stage outcome service hardest - **Intended impact:** the reader sees the build-versus-adopt call mapped cleanly onto evolution stage ::: The market is the near-trillion-dollar cloud spend with the hundreds-of-billions waste pool and AI cost the top priority, and the demand signal is unmistakable in both the figures and the Lexicon of Pain (VERIFIED, Query 1). The cloud-FinOps tooling market itself is in the mid-teens of billions and growing at high-single-to-mid-teens CAGR (VERIFIED, valuation query); the precise carve-out for the AI-workload-optimization-as-a-service niche isn't separately sized and is tagged OPEN, but with $160-270B of addressable waste and AI the fastest-growing slice, the latent demand for the specialist who makes AI affordable is enormous. ## 7. The build (what this brand needs, where Track R feeds Track P) CloudNative Co is a service-led brand whose platform layer composes the ecosystem's stack plus the FinOps and AI-cost tooling. Track R, the research into open-source repositories, feeds this project plan (Track P) through the tooling and reasoning clusters: the observability and cost-data harvests feed the platform, and the optimization-decision harvests feed the find-fix loop. The service is delivered by the agent fleet running the find-fix-grow loop, built on the harness (Symphony AGI's Hermes `projects/symphony-agi.md`), with the FinOps and AI-cost knowledge held in the metagraph (WikiDesignCo `projects/wikidesignco.md`) so the agents resolve the current optimization patterns. The platform integrates the existing telemetry (the cloud-provider billing, the MLOps platforms' utilization data, the inference hosts, the compilers) and adds the layer the market lacks: the model-level unit economics, the AI-specific waste detection, the safe-optimization levers, and the per-model P&L. The build leverage is in the AI-workload optimization methodology and the integration-and-attribution layer, not in rebuilding the underlying cloud-cost telemetry or the MLOps schedulers, which are adopted. CloudNative Co is concept-stage as a brand and service-led, so the platform is a forward build and the savings-share model is a real business decision; the market, the comps, and the AI-cost reality are VERIFIED, and the brand's own build is a forward projection. :::animation 15 **ANIMATION 15: The service-led build, agents on the harness** - **What it shows:** the find-fix-grow agent fleet (built on the harness) running over a client's infrastructure, pulling telemetry from the integrated tools below and the FinOps knowledge from the metagraph above, producing the attribution, the safe optimizations, and the per-model P&L; the human FinOps specialists supervise and own the performance risk, the agents doing the continuous detection and the analysis. - **Narrative role:** grounds §7's service-led, agent-powered build. - **What it teaches:** that the brand runs on the ecosystem's harness and metagraph, with agents doing the continuous find-fix work under human supervision. - **Intended impact:** the viewer sees how the service scales without a large human FinOps department. ::: The data models are the ECS / Pydantic-IR genome (Scatter Model's shared data model, an entity-component system with Pydantic classes as its intermediate representation `projects/scatter-model.md`), which here types the cloud-resource, the cost record, the model, the inference-workload, the optimization, and the savings-verification, and is what makes the per-model P&L and the auditable savings-share possible. The ecosystem's medallion asset tiers apply to the optimization library: a freshly identified optimization enters at bronze, a verified-and-safely-applied optimization rises through silver and gold, and the diamond tier is the proven, repeatedly-successful AI-workload optimization patterns that anchor the service and the methodology moat. CloudNative Co optimizes the compute the ecosystem's AI-infra brands run on (the harness fleet, the Solana Brain pipelines, the quant brands' training and inference), which is the internal proving ground. The open-source harvests that serve it most sit in two clusters: in the tooling cluster, the observability and cost-data harvests feed the platform's telemetry integration `_synthesis-tooling.md`; in the reasoning cluster, the optimization-and-decision harvests feed the find-fix loop's optimization decisions `_synthesis-reasoning.md`. The exact repo-by-repo harvest list should be reconciled against the summaries of that research's clusters as they land (INFERRED on the exact repos; the cluster-level fit is VERIFIED against the operation's Track-R structure). :::animation 7a **ANIMATION 7a: the optimization climbs the medallion tiers** - **What it shows:** a freshly identified optimization enters the library at a BRONZE tier, then as it is verified and safely applied it rises through SILVER and GOLD, and a proven, repeatedly-successful AI-workload pattern reaches DIAMOND at the top where it anchors the methodology moat, the whole climb driven by verified, safely-applied savings - **Narrative role:** anchors the §7 data-model claim, the medallion tiers applied to the optimization library - **What it teaches:** an optimization earns its way up the tiers on verified safe application, and the top tier is the methodology moat - **Intended impact:** the reader sees the accumulated method as an earned, auditable ladder rather than a static playbook ::: ## 8. Priority read (feeds the value rubric) CloudNative Co is a service-led brand with a distinctive priority profile: it's both an external revenue engine (a high-trust, high-value, verifiable cloud-FinOps service) and an internal enabler (it makes the ecosystem's own AI compute affordable, which matters as the ecosystem runs more agents and more AI workloads). It depends on the harness, the metagraph, and the Scatter Model IR for its platform layer, but the service can begin with the agent fleet and the methodology before the full platform is built, because cloud FinOps is a service the market buys today. :::animation 8a **ANIMATION 8a: service first, platform second** - **What it shows:** a sequenced path lights up in order, the SERVICE-LED ENGAGEMENT starting first as the find-fix loop with a savings-share delivered by the agent fleet, proving the methodology and earning revenue while also optimizing the ecosystem's own compute, and only then the AI-FINOPS PLATFORM layer building out as the substrate matures, the integration and attribution and per-model P&L assembling behind the proven service - **Narrative role:** anchors the §8 priority call, the Next-with-a-service-led-sequence read - **What it teaches:** the service can start today because the market buys it, and the platform follows once the method is proven - **Intended impact:** the reader understands the disciplined sequencing that de-risks the forward platform build ::: The first-pass instinct is Next, with a strong service-led near-term case. The full AI-FinOps platform is a forward build that depends on the substrate, but the service (the find-fix-grow consulting with the savings-share, delivered by the agent fleet plus human supervision) can start earlier because it's a service the market already pays for and the savings are verifiable. The internal use is load-bearing and immediate: as the ecosystem runs AI workloads (the harness fleet, Solana Brain, the quant brands), CloudNative Co's discipline keeps that compute affordable, which is a real internal need. So the priority read is Next, in two steps: start the service-led engagement first (the find-fix loop with the savings-share, delivered by the agent fleet, proving the methodology and generating revenue, while also optimizing the ecosystem's own compute), then build out the AI-FinOps platform layer (the integration, the attribution, the per-model P&L) as the substrate matures and the methodology proves. A separate strategist reconciles every brand against the shared value rubric `VALUE_RUBRIC.md`, and this deck's grounded input is that CloudNative Co is a Next with a strong service-led near-term path and a real internal-enabler role. The seven-sins gate, a check of the read against seven named ways an analysis fools itself, applies to the savings-share claim. The market and the AI-cost pain and the comps are real, but the savings-share-as-quasi-recurring-revenue requires the standardized, auditable, multi-year-MSA structure to be built, and the AI-workload optimization methodology must be proven on real workloads, starting with the ecosystem's own, before the premium valuation is asserted. ## 9. The brand's own nine-rung position :::animation 9a **ANIMATION 9a: the black box becomes a P&L** - **What it shows:** the brand's purpose renders as one transformation held in frame, an opaque BLACK-BOX BILL on one side and a clear PER-MODEL PROFIT AND LOSS on the other, the find-fix-grow loop running between them safely, no production-down alarm firing, so AI runs at scale without eating the margin - **Narrative role:** anchors the top of §9, the brand's own purpose rail restated as its nine-rung position opens - **What it teaches:** the whole brand reduces to one move, turning an opaque bill into a legible per-model P&L without breaking production - **Intended impact:** the reader carries the brand's purpose in a single image into its formal position ::: - **Purpose (the rails):** make cloud and especially AI compute economically sustainable, by finding and fixing the waste safely and turning the black-box bill into a per-model profit-and-loss, so companies (and the ecosystem itself) can run AI at scale without it eating the margin. - **Mission (rung 1):** be the AI-workload-aware cloud-FinOps service and platform that finds the bottlenecks and waste, fixes them without breaking production, takes a savings outcome, and finds where clients can make more money. - **Objective (rung 2):** a continuous, outcome-based AI-FinOps engagement (the find-fix-grow loop with a savings-share) plus a platform exposing model-level unit economics and safe-optimization levers, sold as service retainers, savings-share, and platform SaaS, with the AI/GPU specialization as the premium. - **Initiative (rung 3):** the build, service-led first then the platform layer, starting with the ecosystem's own compute as the proving ground. - **Project (rung 4):** the find-fix-grow agent fleet and methodology, the telemetry-integration-and-attribution platform, the safe-optimization levers, the per-model P&L, and the savings-verification machinery. - **Task (rung 5):** one client engagement, one optimization identified and safely applied, one telemetry integration, one savings verification, or one platform feature, owned by the relevant lane. - **Decision (rung 6/7):** the recurring judgment points, each with a heuristic and an authority: which waste to cut first (heuristic: highest savings at lowest production risk; authority: within-desk, human-supervised); whether an optimization is safe to apply (heuristic: the rollback path exists and the canary check passes; authority: the human FinOps lead, who owns the performance risk); what counts as verified savings (heuristic: the standardized, auditable definition against the baseline; authority: within-desk, contractually defined); whether a model is profitable (heuristic: the per-model P&L against its revenue contribution; authority: within-desk, surfaced to the client). - **Data (rung 8):** the cloud-resource and cost records, the model and inference-workload data, the optimizations and their verified savings, and the per-model P&L, all modeled on the Scatter Model IR and integrated from the underlying tools. - **Event (rung 9):** the real occurrences captured: a bottleneck found, an optimization safely applied, a saving verified, a per-model P&L produced, a growth opportunity surfaced, a client's AI compute made affordable. If the optimization is not safely applied and the saving is not auditably verified, it did not happen, which is the verifiable-outcome discipline the brand sells. ## 10. Sources - **Recording transcript:** `looikos_andy_transcript.md` lines 198-203 (Andy's complete CloudNative Co walkthrough: cloud operations and cloud FinOps; cloud is really expensive and one of the biggest bills in software; finding the bottlenecks and the things people are doing wrong that cost them money, showing them how to fix it, and finding where they can make more money; the special AI specialization in cloud infrastructure, training, and inference). - **Cross-referenced ecosystem docs (referenced, not duplicated):** `projects/symphony-agi.md` (the harness the find-fix agent fleet runs on, and the compute it optimizes). `projects/wikidesignco.md` (the metagraph holding the FinOps and AI-cost knowledge). `projects/scatter-model.md` (the ECS/Pydantic-IR world-model layer). `projects/solana-brain.md` and the quant brands (the AI-heavy workloads CloudNative Co's discipline keeps affordable). `THE_FLOOR.md` (the service-angle delivery model and economics). - **Perplexity Query 1 (cloud-FinOps + AI-cost market + players + Lexicon of Pain), verbatim:** "Researching the 2026 market and customer pain for a brand called CloudNative Co: a cloud FinOps / cloud cost-optimization service+platform that finds the bottlenecks and waste in a company's cloud bill, fixes them, and finds where they can make more money, specializing specifically in AI cloud costs (GPU training and inference). 1) MARKET: the 2026 cloud spend + cloud waste + FinOps market... named players in (a) FinOps platforms (CloudHealth, Apptio Cloudability, Harness, Kubecost, Vantage, Finout, CloudZero, nOps, ProsperOps), (b) AI/GPU cost optimization, (c) cloud cost consultancies... 2) VOICE OF CUSTOMER / LEXICON OF PAIN in their actual words (Reddit r/devops, r/aws, r/FinOps, r/kubernetes, r/mlops, Hacker News) for engineers and finance teams dealing with out-of-control cloud bills, especially AI/GPU costs: the surprise bill, the GPU/AI cost explosion, the org dysfunction, the helplessness of not knowing where to start." Findings: the market figures (public cloud $595.7B 2024 / $723.4B 2025 / $800-900B 2026; 20-30% waste / $44.5B Harness unused / $160-270B addressable; 78% of FinOps reporting to CTO/CIO; AI the top future priority, 98% manage AI costs in FinOps scope); the inference-bigger-than-training and GPU-inference-at-scale economics; the three-camp competitor set with per-player what-they-do/refuse; the four pain clusters with quotable phrases ("our AWS bill is insane and nobody knows why," "inference is eating our margins," "our GPU bill is bigger than our payroll," "one training run cost more than my house," "engineering doesn't care about cost and finance can't read the bill," "I'm terrified of breaking prod if I change anything"). Citations included nops state-of-finops-2026, softjourn finops-stats, finops.org data, cloudzero cloud-finops, marketsandmarkets/mordor/precedence cloud-finops-market. - **Perplexity Query 2 (cloud-FinOps valuation comps + savings-share model), verbatim:** "Real 2023-2026 valuation/M&A comps for cloud FinOps / cloud-cost-management companies, for a corporate-finance read on a brand (CloudNative Co)... 1) FinOps company valuations/acquisitions: Apptio (IBM), CloudHealth (VMware), Cloudability, Spot.io (NetApp), CloudCheckr, Vantage, CloudZero, Finout, nOps, ProsperOps, Harness, Kubecost (IBM)... 2) the cloud-cost-management software market size 2026 and ARR multiples... 3) how would a cloud-FinOps brand that is BOTH a service (savings cut) AND a platform be valued, the savings-share/outcome-based pricing model, how recurring savings-share converts to credit/capital access, plus the AI/GPU specialization premium." Findings: the real acquisitions (IBM-Apptio $4.6B June 2023, VMware-CloudHealth ~$500M 2018, NetApp-Spot.io ~$450M 2020, IBM-Kubecost 2024 undisclosed/OPEN, Harness ~$3.7B valuation); the cloud-FinOps market (~$15-16B 2025-26, high-single-to-mid-teens CAGR, estimates varying by scope); the SaaS multiple bands (5-8x for good infra/devops FinOps SaaS, 8-12x+ for leaders, 3.8-5.3x 2026 private median); the three-revenue-stream blend (platform ARR high, service retainers 3-5x, savings-share 5-8x rising toward SaaS if predictable) and the AI/GPU premium (+1-3 turns); the savings-share-as-quasi-recurring underwriting and the verification constraint. Citations included saasrise private-SaaS-M&A-Q1-2026, marketsandmarkets/mordor/insightace/precedence cloud-finops-market, finops.org, prnewswire state-of-finops-2026. - **VoC channels mined (via Query 1):** r/devops, r/aws, r/FinOps, r/kubernetes, r/mlops, Hacker News, engineering blogs. Note: Perplexity drew on the documented FinOps and cloud-cost discourse plus the cited 2026 FinOps reports; the phrases are evidence-tagged as VoC-pattern (representative), with the market and waste and AI-cost figures VERIFIED from the cited reports. Used in §4 personas and §5 PST. - **Evidence tags:** the transcript seed, the cloud-spend and waste figures, the FinOps market data, the AI/GPU cost reality, the competitor set, and the comps (including the real IBM-Apptio, VMware-CloudHealth, NetApp-Spot.io acquisitions) are VERIFIED (Perplexity-cited; the named acquisitions are primary-source-reported). The IBM-Kubecost price is undisclosed and tagged OPEN. The precise AI-workload-optimization-as-a-service niche TAM is OPEN. The brand's own platform build and the savings-share structure are the forward read (the brand is concept-stage). The three-angle valuation figures for CloudNative Co 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.