<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by DC on Medium]]></title>
        <description><![CDATA[Stories by DC on Medium]]></description>
        <link>https://medium.com/@dcirl?source=rss-17bcd27bce4d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1tgExKmlg3Q3FIzxlKa1iA.png</url>
            <title>Stories by DC on Medium</title>
            <link>https://medium.com/@dcirl?source=rss-17bcd27bce4d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:36:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dcirl/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Playbook: When Building Is the Easy Part]]></title>
            <link>https://medium.com/@dcirl/the-playbook-when-building-is-the-easy-part-92348d995548?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/92348d995548</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fundraising]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Tue, 12 May 2026 10:58:21 GMT</pubDate>
            <atom:updated>2026-05-12T10:58:21.164Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Just Because You Can Build It Doesn’t Mean It Should Exist</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*re_NX4p73RbTqSTpgIHATw.jpeg" /></figure><p>We are living through the most permissive build environment in software history. A motivated founder with a laptop, a coding assistant, and a weekend can ship something that would have required a six-person engineering team and a year of runway in 2018. The cost of building has fallen off a cliff, and the cost of looking competent has fallen with it. Polished landing pages, working prototypes, deployed apps — the entry-level signals of “real startup” are now available to anyone with curiosity and a credit card.</p><p>This is genuinely good. The friction that used to keep brilliant outsiders out of software has largely disappeared. People who would never have been able to raise a friends-and-family round to hire engineers can now test their ideas directly, in days, with their own hands. That is a gift to the ecosystem, and I have no interest in being the grumpy investor who pretends otherwise. The opportunity in front of founders right now is the most generous it has been in my career.</p><p>But there is a catch I keep running into in pitch meetings, and it is worth saying out loud: the friction that’s gone wasn’t only keeping outsiders out. It was also forcing insiders to think.</p><p>Pre-2023, if you wanted a real product in the world, you had to commit. You had to recruit a technical co-founder or write a real cheque. You had to convince another human being to spend months of their life on your idea. That conversation — the one where you had to make a case for why the thing should exist — was the first market test. It was crude, but it was a test. If you couldn’t articulate why the world needed this, you didn’t get the engineer, and you didn’t get the product. The system itself filtered out a certain volume of unconsidered ideas before they ever reached an investor’s desk.</p><p>That gate is gone. And I am watching the consequences walk into my appoitment diary most weeks.</p><h3>The pattern in the meeting room</h3><p>The founder has a deck. The founder has a working demo. The founder has, in many cases, a polished web app deployed to a clean domain with sign-ups already trickling in. What the founder does not have, when I start asking the obvious questions, is an answer to <strong>why this should exist.</strong></p><p>I ask how customers solve this problem today, and I get a vague gesture toward “Excel” or “manual processes” — phrases scraped from somebody else’s deck. I ask who they’ve spoken to about the pain, and the answer turns out to be friends, family, or a few people on Reddit. I ask what existing players in the space charge for similar tools, and the founder cheerfully tells me there are no direct competitors. I ask why those existing players — who have more capital, more distribution, and more domain expertise than this founder — haven’t already won the market, and the question lands like it has never been considered before.</p><p>What’s happened is straightforward. The easy work — building the thing — has been done before any of the hard work. The product exists, but the case for the product doesn’t. The founder has confused “I shipped something” with “I have a business,” and the gap between those two sentences is where the majority of startup money quietly dies.</p><h3>This isn’t really a vibe coding problem</h3><p>The discipline being skipped — earning the right to exist — has always been the discipline. What’s changed is that the world has stopped enforcing it for you. Every business that survives has, at some point, answered a small set of questions about why it deserves to exist. Not should it exist aesthetically. Not should it exist technically. Should it exist commercially — meaning, is there a real, painful, expensive problem that real people will spend real money to make go away, that nobody else is solving well enough, in a way that you can defensibly own?</p><p>That bar is the same as it was twenty years ago. The difference is that twenty years ago, you couldn’t reach a pitch meeting without crossing it. Today, you absolutely can. The signals of seriousness — domain, deck, demo, deployment — have been commoditised. The thinking has not. That asymmetry is the most important thing happening in early-stage right now, and most founders haven’t clocked it yet.</p><h3>You’re using the AI for the wrong half</h3><p>Here’s the part of this that should bother every founder reading it. The same tools that are enabling the vibe coding revolution — Claude, GPT, Perplexity, the whole stack — are equally capable of helping you do the upstream work. They are exceptional research partners. They will, if you ask them, produce a credible competitive landscape for your idea in fifteen minutes. They will run a SWOT analysis, draft a risk register, write the bear case against your thesis, and list the failure modes other companies in adjacent spaces have already hit. They will challenge the assumptions in your pitch deck more honestly than your friends and family ever will, because they have no social incentive to spare your feelings.</p><p>This is what makes the current pattern so frustrating to watch from the investor side. It isn’t that the work is harder than it used to be — it’s easier. It isn’t that founders lack the tools to think rigorously about their market — they have better tools than any prior generation. It’s that they’re using those tools for the half they enjoy (building) and not the half that actually decides whether the company will exist (interrogating the business). That isn’t a capability gap. It’s a discipline gap, and frankly, it’s lazy entrepreneurship in a way that simply wasn’t possible to accuse founders of two years ago.</p><p>You can ask any of the major models, right now, to do a competitive analysis for the idea you’re working on. Tell it the problem you think you’re solving, the customer you think you’re solving it for, and the solution you’re proposing. Ask it to identify the top ten companies operating in or adjacent to that space, what they charge, where they win, and where they lose. Ask it to write the most honest possible bear case against your idea. Ask it which of your assumptions are most likely to be wrong, and which would kill the business if they are. Ask it to list the five reasons a sceptical investor would pass on the round you’re about to raise. None of this is hard. None of it requires a budget. None of it requires you to find anyone willing to read your deck.</p><p>The friction has been removed from the thinking exactly as it has been removed from the building. The only question left is which half of the tool you choose to use. There is no excuse anymore for skipping the harder half — and the founders who skip it are simply handing the win to the ones who don’t.</p><p>So before you write another line of code, before you raise another euro, before you take another partner meeting, work through the six questions below. None of them is original. All of them are ancient. What’s changed is that nothing in your toolchain will force you to ask them — you have to choose to. If you can’t answer all six clearly and specifically, your idea hasn’t earned the right to exist yet. That doesn’t mean it never will. It means the work to get there hasn’t been done, and you’re confusing motion with momentum.</p><h3>1. Whose pain, and how badly?</h3><p>Not “what problem are you solving” — that’s the question that gets answered with platitudes. The real question is sharper: which specific human is in enough pain right now to pay you to make it stop?</p><p>A real problem has a face. You can name the role, the company size, the workflow they’re stuck in, and the specific moment in their week when the pain peaks. You know whether they currently complain about it openly, hide it from their boss, or have learned to tolerate it. You know what they’ve tried before, and you know what made those attempts fail. The detail matters because vague pain doesn’t open wallets. Specific, named, expensive pain does.</p><p>If your answer to “who feels this pain” is “everyone,” “small businesses,” or “creative professionals,” you don’t have an answer. You have an audience. Audiences don’t pay; people do. The test I ask founders to run on themselves: can you name three specific humans, by role and context, who would pay you cash today to make this problem disappear? Not “would be interested.” Not “would try a free version.” Would actually pay. If the answer is no, you’re upstream of where you think you are, and no amount of building will move you forward.</p><h3>2. How are they solving this today?</h3><p>Every problem worth solving is already being solved badly. The status quo is your real competitor — not the other startup with a similar landing page, not the giant incumbent on a billboard — the spreadsheet, the workaround, the manual process, the cobbled-together stack of three tools and an intern with a checklist. Until you can describe that current solution in unflattering, specific detail, you don’t understand the market you’re entering.</p><p>This is the work that vibe coding cannot do for you, and it’s the work founders most often skip. It requires conversations with strangers who have no incentive to be helpful. It requires patience with answers that don’t fit your thesis. It requires being willing to find out that the workaround is, for most people, fine — and that your beautifully-built product is solving a problem that doesn’t actually need solving badly enough to fund a company.</p><p>The founders who do this work develop something the others never get: pattern recognition for which complaints translate into purchases, and which are just complaints. People grumble about a lot of things they would never pay to fix. The skill of distinguishing the two is built only one way — by talking to enough humans about their actual workflows that the patterns become visible. There is no shortcut, and the tooling has not invented one.</p><h3>3. Why is your version ten times better, not ten percent better?</h3><p>Switching costs are real, even when they look small. People stay on bad spreadsheets for years. They keep using software that frustrates them daily. The bar for getting them to switch isn’t “marginally better than what they have” — it’s “obviously, dramatically, undeniably better than what they have, in a way that overcomes the inertia of their current habit and the friction of changing.”</p><p>If your honest answer to “why would they switch” is “it has more features,” “it’s better designed,” or “it uses AI,” you don’t have a switching argument. You have a feature list. Feature lists lose to inertia, every time. The customer doesn’t experience your features; they experience the cost of changing what they’re already doing, and they need a reason that’s big enough to make that cost feel worth it.</p><p>The ten times question is uncomfortable because most ideas, examined honestly, deliver about a one-and-a-half-times improvement on a dimension the customer doesn’t actually rank highly. That’s not a business. That’s a hobby that happens to compile. Better to find out now, when you’ve invested weeks, than after eighteen months of building toward a market that was never going to switch.</p><h3>4. Why now — and why hasn’t somebody already won this?</h3><p>If your idea is good and the market is real, the natural follow-up question is: why hasn’t somebody else already done this? Smart, well-funded people have been looking at the same market for years. They have more capital, more distribution, and more domain expertise than you currently do. What did they miss, or what has changed?</p><p>Acceptable answers exist. Maybe a regulation just changed and opened a window that wasn’t there before. Maybe a foundation model finally made something economically possible that wasn’t two years ago. Maybe a behavioural shift — remote work, declining trust in institutions, generational handover — has reshaped what customers will accept. Maybe the incumbents are structurally unable to cannibalise their own revenue, leaving a corridor open for an outsider.</p><p>Unacceptable answers also exist. “Nobody’s thought of it” is unacceptable; somebody almost certainly has. “AI exists now” is unacceptable, because AI exists for everyone, including every competitor in your space. “We’re more passionate” is unacceptable; passion is table stakes. If your why-now is something every other founder in your category could also claim, it isn’t a why-now. It’s a wish dressed up as a thesis. The real why-now should be specific enough that a sceptical investor can’t find five other companies riding the same wave.</p><h3>5. Why you?</h3><p>This is the question founders hate most, because it forces them to be honest about their actual edge. Domain expertise from years inside the problem. A distribution channel competitors don’t have. An asymmetric insight that came from a specific lived experience. A relationship with a difficult-to-reach customer set. Something — anything — that means you are the right team to win this race, and not just a team trying to enter it.</p><p>“I’m a great engineer” is not a why-you answer in 2026. Lots of people are great engineers, and most of them have access to the same coding assistants, the same cloud infrastructure, and the same off-the-shelf models you do. Your why-you has to survive a harder question: if I gave this idea to ten other competent founders tomorrow, why would you still win? If the honest answer is “I moved first,” that’s an advantage measured in weeks, not years.</p><p>If you can’t answer the why-you question, your idea isn’t really yours. It’s a market opportunity that happens to be in front of you, and markets like that get won by whoever combines the right edge with the right timing. Sometimes the best version of this answer is uncomfortable: the right move may be to find a co-founder whose edge complements yours, rather than insisting that your enthusiasm is sufficient.</p><h3>6. Will they pay — and will they keep paying?</h3><p>The final test, and the most ruthless. Words are cheap. Surveys are cheaper. Even early signups are mostly noise. The only signal that survives contact with reality is somebody opening their wallet — and then opening it again the following month.</p><p>The founders I trust most don’t wait until they’ve built the perfect product to test this. They test it embarrassingly early, before there’s anything real to sell. They have conversations where they ask for letters of intent, pre-orders, deposits, paid pilots — anything with friction higher than a free email signup. They get rejected, painfully and repeatedly, and they learn from each rejection what the real objection is. That’s the data the build cannot generate for you.</p><p>What they’re really testing isn’t just willingness to pay. It’s willingness to pay repeatedly. A one-time purchase tells you you’ve solved a one-time problem, which is a different and usually much smaller business than the one in your deck. Subscription revenue, retention, expansion — that’s how you know you’ve built a business and not a transaction. Revenue quality matters more than revenue quantity, and that test starts at the idea stage, not after you’ve booked your first invoice.</p><p>If you can’t get anyone to commit to paying repeatedly before you’ve finished building, the chances they’ll commit afterwards are vanishingly small. You’ll just have spent more money to find out the same answer.</p><h3>Build less. Think more.</h3><p>Here’s the trap of the current moment, stated as plainly as I can manage it: the lower the cost of building, the higher the cost of not thinking. When shipping a product was expensive, the act of building itself imposed a kind of forced discipline — you couldn’t afford to build the wrong thing, so you had to think first. Now that you can build cheaply, the temptation is to skip the thinking and let the building do the discovery for you.</p><p>It doesn’t work. The market doesn’t care how cheaply you built the wrong product. It cares whether the product solves a real problem for a real customer at a real price, and that question gets answered the same way it always was — by understanding the market before you build for it, not after. Vibe coding hasn’t changed the destination. It has only changed how easy it is to head off in the wrong direction. And the same AI tools that let you build the wrong product in a weekend will, if you ask them honestly, tell you it’s the wrong product before you start. The discipline gap is no longer about effort. It’s about choice.</p><p>The founders winning in this era aren’t the ones who ship fastest. They’re the ones who ship fastest toward something they’ve earned the right to build. Velocity without direction is just expensive motion. The compounding advantage — the kind that builds a company rather than a portfolio of half-finished prototypes — belongs to the founders who do the upstream work that the rest of the field is now free to skip.</p><p>So before you write another line of code, ask whether your idea has earned the right to exist. If the answer is no, the work isn’t another sprint. The work is the conversations, the research, the painful customer rejections, the honest market mapping you keep telling yourself you’ll do later. There is no later in 2026. The window has never been shorter, and the founders who catch it will be the ones who treated the thinking as a first-class deliverable, not a tax to avoid.</p><p>Build less. Think more. Earn the right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92348d995548" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Playbook: How Enterprise Software Gets Sold Now]]></title>
            <link>https://medium.com/@dcirl/the-playbook-how-enterprise-software-gets-sold-now-44a1a6274e11?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/44a1a6274e11</guid>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[selling]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 22:24:32 GMT</pubDate>
            <atom:updated>2026-04-14T22:24:32.542Z</atom:updated>
            <content:encoded><![CDATA[<p><em>AI didn’t just change what software can do. It broke how software gets priced, sold, and bought.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ucasrDoaw6J6GzpTCA49iQ.png" /></figure><p>The per-seat pricing model underpins a trillion-dollar industry. Every enterprise software company’s revenue model, every sales team’s compensation structure, every CIO’s budget line — all of it is anchored to a single unit of measurement: the human user.</p><p>That unit of measurement is now broken.</p><p>In the last two years, AI has not added a feature layer to enterprise software. It has attacked the foundational assumptions of the business model. What companies sell, how they sell it, who sells it, and how buyers evaluate it — all of these have changed simultaneously, and faster than most founders or investors have absorbed.</p><p>This is not a story about chatbots getting bolted onto dashboards. This is a structural rewrite of the largest software market in the world. And if you are building or investing in B2B software, the commercial model you learned no longer applies.</p><h3>The Buyer Arrived Before You Did</h3><p>Here is the most uncomfortable truth for anyone running a go-to-market function at a software company: your buyer no longer needs you for most of the buying process.</p><p>Forrester’s Buyers’ Journey Survey found that 89% of B2B buyers now use generative AI as a primary research tool across every phase of their purchasing journey. 6sense’s 2025 B2B Buyer Experience Report confirms it: 94% of enterprise buyers use LLMs to research solutions, 80% set their requirements before engaging with any vendor, and 83% of the buying journey now happens without a seller in the room.</p><p>Two years ago, the vendor’s sales team shaped the problem, defined the category, and curated the shortlist. That power has transferred to the buyer. When they do reach out, it is to validate a decision they have already made. The vendor that secures that first meaningful engagement still wins 77% of the time, but that engagement is happening later, is more demanding, and is far less tolerant of vague positioning.</p><blockquote><em>If your product story cannot be parsed accurately by an LLM, you are invisible to the majority of your prospective buyers.</em></blockquote><p>Enterprise software vendors now need to optimise their entire presence not just for Google, but for AI answer engines. Research from The Digital Bloom shows that 43% of buyers care more about getting a detailed, clear explanation of what a product does than about whether a brand appears first in an AI response. Ambiguity gets filtered out. Clarity gets surfaced.</p><p>This is something I see founders getting wrong constantly. They obsess over SEO and paid acquisition while their product descriptions read like word soup. In a world where an LLM is building the shortlist, your positioning needs to be machine-parseable — which, ironically, means it needs to be clearer and more specific than ever. No more “we leverage AI to transform workflows.” Say what you actually do, for whom, and what changes when someone uses it.</p><p>If you have read <a href="https://medium.com/@dcirl/the-user-reservoir-playbook-how-ai-native-startups-achieve-hypergrowth-919d78004c96">my URGE Playbook on how AI-native startups achieve hypergrowth</a>, you will recognise this dynamic. The bottom-up enterprise motion I described there — where individual users adopt before procurement ever gets involved — is accelerating precisely because buyers now self-educate through AI. The two trends are mutually reinforcing, and founders who understand both have a compounding advantage.</p><h3>The SDR Machine Is Being Disassembled</h3><p>The traditional enterprise go-to-market playbook ran on volume. Hire large SDR teams. Run thousands of sequences. Feed the top of the funnel. Let Account Executives close what falls through.</p><p>That model is in retreat. Emergence Capital’s 2025 survey of 560+ venture-backed B2B software companies found that 36% cut their SDR/BDR headcount over the previous twelve months — the sharpest reduction of any sales function. What is replacing it is smaller, more technical teams supported by AI agents that handle prospecting, qualification, and outreach at dramatically higher throughput.</p><p>Salesforce’s 2026 State of Sales report, surveying over 4,000 sales professionals globally, found that 87% of organisations now use some form of AI in their sales process and 54% have deployed AI agents across the sales cycle. High-performing teams are 1.7x more likely to use AI agents for prospecting than underperformers. Gartner predicts that by 2027, companies will begin replacing Revenue Operations roles with “Go-to-Market Engineers” — technical specialists who build and manage AI-driven sales workflows rather than executing them manually.</p><blockquote><em>You can build a credible enterprise sales motion with a fraction of the headcount required even two years ago. But the people you hire need to be fundamentally different.</em></blockquote><p>For founders building B2B companies, the implication is liberating and demanding in equal measure. The capital-intensive SDR army that used to gatekeep enterprise sales is dissolving. But the humans you do hire need to be more technical, more strategic, and more capable of handling the complex conversations that AI agents cannot. The bar for individual quality has gone up precisely because the need for volume has gone down.</p><h3>AI Has Graduated From Experiment to Budget Line</h3><p>On the buy side, the shift is equally dramatic. Andreessen Horowitz’s survey of 100 enterprise CIOs found that innovation budgets, which made up 25% of LLM spending a year ago, have collapsed to just 7%. AI spend has graduated into core IT and business unit budgets, with leaders expecting roughly 75% growth year-over-year.</p><p>Salesforce’s second annual CIO study confirmed the acceleration: full AI implementation across enterprises has increased 282% in a single year. CIOs are dedicating 30% of their AI budgets specifically to agentic AI. And 96% say their company either uses or plans to use agentic AI within the next two years.</p><p>Critically, the posture of procurement has changed. Model and AI app selection now follows the same disciplined evaluation frameworks that enterprises apply to any major software purchase. And there has been a decisive pivot from “build” to “buy.” Early in the cycle, enterprises built their own AI applications on top of foundation models. Now, with the AI app ecosystem maturing rapidly, organisations are purchasing off-the-shelf AI-native applications. In customer support, over 90% of CIOs surveyed by a16z were already testing third-party apps.</p><p>For AI-native startups, this is the window. Enterprise procurement is open, budgets are expanding, and incumbents are still fumbling their pricing transitions. But that window will not stay open indefinitely — and founders who mistake open procurement for permanent advantage will learn a painful lesson about timing.</p><h3>The Per-Seat Model Is Structurally Broken</h3><p>Per-seat pricing was built for a world where humans were the bottleneck. Every new hire meant a new licence. AI agents break this assumption entirely. They do not log in. They do not consume named-user licences. They do not map to headcount.</p><p>The data is stark. For every AI agent deployed, human software seat requirements drop at a ratio of roughly 1:5. Per-seat revenue share across SaaS has declined from 21% to 15% in twelve months. 40% of enterprise SaaS contracts now include outcome-based pricing elements, up from just 15% two years ago. And 83% of AI-native SaaS companies have already adopted usage-based pricing.</p><p>The market made this pricing crisis viscerally real in February 2026. In what the financial press dubbed the “SaaSpocalypse,” $285 billion was wiped from SaaS valuations in 48 hours. Atlassian reported its first-ever decline in enterprise seat counts. Intuit dropped 34%. The market was not correcting — it was reclassifying an entire sector. As Deloitte estimated, 40% of current per-seat SaaS revenue is at risk within 36 months.</p><h3>Where the Moat Actually Is Now</h3><p>This is where the structural change gets most consequential for builders and investors — and where most of the current analysis is getting it wrong.</p><p>AI agents do not care about dashboards. They do not care about user interfaces. They care about APIs, data access, permissions, and workflow execution rights. This shifts where power sits in the software stack in ways that the market has not yet fully priced.</p><p>I made the argument in the URGE Playbook that traditional SaaS is fundamentally a UI layer for databases — a translation layer between what databases can do and what humans can understand. When AI agents can interact with those databases directly, that entire premise weakens. What matters now is not whether you have the best interface, but whether you control the data and execution rights that agents need to function.</p><ul><li><strong>Systems of Record hold durable power.</strong> CRM databases, ERPs, core finance and clinical systems — these are embedded in governance, regulation, and institutional memory. AI agents can automate around them, but they still need to read from and write into them. These vendors retain leverage.</li><li><strong>Systems of Engagement are being hollowed out.</strong> Support desks, scheduling tools, lightweight collaboration, certain analytics layers — these can be wrapped by external AI agents. The customer keeps the tool but uses fewer seats, fewer features, and increasingly relies on automation outside the product. Churn stays low while Net Revenue Retention quietly deteriorates. That is the most dangerous scenario for a SaaS business: your customer stays, but your revenue shrinks.</li><li><strong>AI-native platforms are the new competitors.</strong> At least seven major tech firms now compete head-to-head across eight functional areas, all selling functionally similar AI agents. And behind them, a wave of startups building AI-native from scratch, unburdened by legacy pricing, legacy architectures, and legacy sales teams.</li></ul><blockquote><em>“API strategy” is no longer about developer relations. It is border control.</em></blockquote><p>Here is the pattern I keep seeing founders miss: they look at this landscape and see an opportunity to build better agents. But the real opportunity — the defensible one — is in owning the data layer that agents need to function. If an external agent can extract value while commoditising your UI, you either capture the agent layer or you get taxed by it. The founders who understand this distinction are building very different companies from the ones who do not.</p><h3>The Commercial Architecture Stack</h3><p>So what are software companies actually selling now? And more importantly, how should a founder think about where to position their own product?</p><p>I think of this as a five-layer commercial architecture. Each layer represents a fundamentally different product, a different pricing model, a different buyer relationship, and a different defensibility profile. Most of the confusion in the market right now comes from founders and investors conflating these layers — or worse, trying to straddle two of them without committing to either.</p><p><strong>Layer 1: Copilots.</strong> AI features bolted onto existing products. GitHub Copilot, Microsoft 365 Copilot, Salesforce Einstein. By 2026, this is table stakes. If this is all you offer, you are not an AI company — you are a legacy company with a feature update.</p><p>Pricing: bundled into existing subscriptions.</p><p>Defensibility: low. The buyer’s switching cost is the platform, not the AI.</p><p><strong>Layer 2: Credits and consumption.</strong> An interim model where AI capabilities are metered on top of existing subscriptions — tokens, credits, compute minutes. Credit-based pricing grew 126% year-over-year in 2025, with HubSpot, Figma, Adobe, and Salesforce all adopting it. Most people in the industry acknowledge this is transitional, not a destination.</p><p>Pricing: pay-as-you-go.</p><p>Defensibility: moderate, but only if consumption creates data that improves the product.</p><p><strong>Layer 3: Autonomous agents — “digital labour.”</strong> The defining new category. Software that performs work previously done by humans, not tools that assist them. ServiceNow has introduced “AI Specialists” that directly replace Level 1 help desk workers. Salesforce positions Agentforce as “digital labour.” Gartner predicts 40% of enterprise applications will include task-specific AI agents by end of 2026, up from less than 5% in 2025.</p><p>Pricing: per-agent or per-task.</p><p>Defensibility: moderate to high, depending on workflow complexity and data access.</p><p><strong>Layer 4: Outcome-as-a-Service.</strong> The logical end state. Zendesk pioneered this in late 2024, charging $1.50 per automated resolution rather than per human agent seat. Intercom charges $0.99 per AI-resolved conversation and generated tens of millions in revenue in its first year. For the first time in enterprise software history, the vendor’s incentive is fully aligned with the buyer’s: you pay for results, not for access.</p><p>Pricing: per-outcome.</p><p>Defensibility: high, because you own the performance benchmark.</p><p><strong>Layer 5: The data and orchestration layer.</strong> This is the layer most founders overlook and the one I think has the most durable value. If agents from Layer 3 and outcomes from Layer 4 all depend on access to proprietary data, workflow permissions, and system integrations, then whoever controls that connective tissue captures value from every layer above.</p><p>Pricing: platform fees, API access, data licensing.</p><p>Defensibility: very high — switching costs compound with every integration.</p><blockquote><em>The question is not “how do we add AI?” It is “what are we selling when humans are no longer the unit of work?”</em></blockquote><p>The decision for founders is not which layer is “best.” It is which layer matches your product architecture, your data advantages, and the buyer relationship you can credibly serve. If you are building at Layer 1 or 2, you are competing on features in a commoditising market. If you are building at Layer 4 or 5, you need to prove outcomes and own data — which is harder to start but vastly more defensible once established.</p><p>The founders I see making the biggest strategic error right now are the ones building Layer 3 products — autonomous agents — without a plan for how they reach Layer 4 or 5. An agent without proprietary data or measurable outcomes is a feature, not a company. And features get absorbed by platforms.</p><h3>Salesforce’s Pricing Odyssey: Why Nobody Has the Answer Yet</h3><p>If you want to understand the industry’s transition in miniature, look at Salesforce. In eighteen months, the company shipped three entirely different pricing models for Agentforce.</p><p>Late 2024 saw a launch at $2 per conversation. Adoption was tepid. May 2025 brought Flex Credits at $0.10 per action — more granular, more aligned with actual work done, but unpredictable for enterprise CFOs who need a budgetable number. Late 2025 introduced per-user licences at $125+/month, giving CFOs a contract shape they understood.</p><p>The result? All three models now run simultaneously. Agentforce hit $540M ARR by Q3 FY2026, growing 330% year-over-year. 18,500 deals closed, 9,500 paid. Only about 8% of Salesforce’s 150,000+ customer base has adopted Agentforce so far.</p><p>The broader lesson matters for every founder making pricing decisions right now: nobody has figured out the right model yet. The PricingSaaS 500 Index tracked over 1,800 pricing changes across the top 500 B2B and AI companies in 2025 alone — 3.6 pricing changes per company in a single year. The entire industry is experimenting in public.</p><p>But here is what Salesforce’s experience actually tells us, beyond the headline numbers. The multi-model approach is not a failure of strategy — it is the strategy. Different buyers need different commercial wrappers for the same underlying capability. The CFO needs a predictable line item. The department head needs a usage model that scales with adoption. The innovation team needs a low-commitment entry point. If you are a founder building an AI-native product and you think you need to pick one pricing model, you are solving the wrong problem. You need a commercial architecture that can flex across buyer types — and that means building the metering and billing infrastructure from day one, not bolting it on after you have locked yourself into per-seat contracts.</p><h3>So What Does This Mean?</h3><h4>For founders building enterprise software</h4><p>You are entering a market where the commercial model is being rebuilt in real time. You can build a credible enterprise go-to-market with a fraction of the headcount required two years ago. But you need to decide from day one where you sit on the Commercial Architecture Stack — and that decision will determine your product architecture, your pricing model, your sales motion, and ultimately your defensibility.</p><p>The build-vs-buy pendulum has swung decisively toward buy. Enterprise procurement teams are actively looking for AI-native applications that outperform what incumbents can offer. If you have a superior product in a well-defined vertical, this is the most receptive enterprise buying environment in years. Do not waste it by copying an incumbent’s pricing model. The founders who default to per-seat pricing because it “looks enterprise-ready” are importing a broken model into a company that has no reason to carry that baggage.</p><h4>For investors</h4><p>The SaaSpocalypse was not a correction. It was a reclassification. The per-seat model that generated predictable, high-margin recurring revenue for two decades is structurally compromised. The metrics that matter are shifting: watch Net Revenue Retention in companies where seat counts decline but revenue per customer grows through AI consumption. Watch for hybrid pricing adoption — projected to reach 61% of SaaS companies by end of 2026. And pay close attention to data moats — who owns the proprietary, non-replicable data that AI agents need to function.</p><p>There is also a CFO-level insight worth internalising: usage-based billing is not incremental cost for enterprise buyers. It is budget reclassified from headcount to technology. If AI agents replace two support roles, the consumption billing covers work that was previously a labour cost. This reframing — technology spend as labour replacement, not technology addition — is what makes the enterprise business case for AI-native products so much stronger than previous software categories.</p><p>The biggest opportunity is in AI-native companies that were never burdened by per-seat economics. The pattern is identical to the on-premise-to-cloud transition: new entrants that build natively for the new paradigm will capture outsized value, while incumbents fight painful model transitions in public markets.</p><h3>The Bottom Line</h3><p>Enterprise software selling is undergoing the most significant transformation since the shift from on-premise to cloud. But this time, the disruption is hitting both sides of the transaction simultaneously — what gets sold and how it gets sold are both changing at once.</p><p>The per-seat era is ending. The outcome era is beginning. And the most common mistake I see founders making right now is treating this transition as a pricing problem. It is not. It is a product architecture problem, a data strategy problem, and a commercial design problem — and the founders who solve it will not be the ones who bolt AI onto a traditional SaaS model and call it innovation. They will be the ones who looked at the Commercial Architecture Stack, picked a layer they could own, and built everything — product, pricing, and go-to-market — around that choice from day one.</p><p>The irony is that the enterprise software playbook everyone learned over the past two decades was itself a form of lock-in. The real unlock is not copying what worked before. It is recognising that “enterprise-ready” now means something entirely different — and building accordingly.</p><p>Good Luck</p><p><em>DC is a Venture Partner at </em><a href="http://www.svv.ai/"><em>SVV</em></a><em>, an AI-specialist VC firm, and author of upcoming book ‘We’re Doing it Wrong: How to Build Entrepreneur Ecosystems that actually work.’ He writes regularly about startup advice, AI-native startups, velocity-focused execution, and ecosystem architecture.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44a1a6274e11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Playbook: The Founder’s Operating System (FOS)]]></title>
            <link>https://medium.com/@dcirl/the-playbook-the-founders-operating-system-fos-d30802d9a3f4?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d30802d9a3f4</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 18:29:24 GMT</pubDate>
            <atom:updated>2026-04-07T18:29:24.921Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A practical guide to structuring your time, managing your decisions, and protecting the energy that actually moves the business forward.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2S9jxqXOyrBf0Hu-_cdBww.png" /></figure><p>I’ve backed dozens of founders, and I’ve been one myself multiple times over. So I’ve had a front-row seat — from both sides of the table — to the way founders actually spend their time. And here’s the uncomfortable pattern I keep seeing: the founders who work the longest hours are rarely the ones who build the most valuable companies.</p><p>This isn’t a wellness argument. I’m not going to tell you to meditate, take up journalling, or prioritise self-care. This is a performance argument. The founders who consistently outperform are the ones who treat their own time and cognitive capacity as a system to be designed, not a resource to be spent until it’s gone. They operate with what I’d call a founder’s operating system (FOS) mindset — a deliberate structure for how they spend their hours, make their decisions, and protect their capacity for the work that actually matters.</p><p>The founders who don’t have this system tend to look heroically busy. They’re in every meeting. They’re answering every Slack message. They’re context-switching between product, sales, hiring, and investor relations fifteen times a day. They eat at their desks or not at all. They haven’t exercised in weeks. They feel productive. They’re exhausted. And eighteen months later, they’re wondering why the company hasn’t moved as far as it should have — and why they feel like they’ve aged a decade.</p><blockquote><strong><em>Busyness is the founder’s most dangerous anaesthetic. It numbs you to the fact that you’re not making progress.</em></strong></blockquote><h3><strong>The Decision Fatigue Tax</strong></h3><p>Every founder knows about burn rate — the rate at which you spend cash. Far fewer think about their cognitive burn rate — the rate at which they deplete their capacity to make good decisions. And yet decision quality is arguably the single most important determinant of startup success. A company is nothing more than the accumulated consequence of its founder’s decisions. Product decisions, hiring decisions, pricing decisions, strategic decisions. When those decisions are sharp, the company compounds. When they’re muddy, the company drifts.</p><p>Decision fatigue is well documented in cognitive science. The quality of your decisions degrades measurably over the course of a day as you make more of them. This isn’t a theory — it’s observable in everything from judicial rulings to consumer purchasing behaviour. And yet most founders structure their days in a way that guarantees they’ll make their most important decisions when their cognitive capacity is at its lowest: at the end of a day filled with dozens of smaller decisions that have steadily eroded their judgment.</p><p>The practical implication is straightforward but counterintuitive. If you’re making fifty decisions a day, the quality of decisions forty through fifty is measurably worse than the quality of decisions one through ten. So the question becomes: which decisions are you making in slots one through ten, and which are getting the depleted, end-of-day version of you?</p><p>Most founders I observe get this backwards. They start their mornings in reactive mode — email, Slack, stand-ups, firefighting whatever’s landed overnight. By the time they get to the strategic work — the product direction, the pricing model, the hiring decision, the partnership negotiation — they’re operating on fumes. The decisions that shape the trajectory of the entire company are being made by someone who has already spent their best cognitive hours on things that could have waited.</p><h3><strong>The Three Types of Founder Work</strong></h3><p>Not all work is created equal, but most founders treat it as if it is. They move through their day responding to whatever feels most urgent, which almost never correlates with what’s most important. A useful framework is to think about founder work in three distinct categories, each with fundamentally different characteristics.</p><ol><li><strong>Direction-setting work</strong></li></ol><p>This is the work that determines where the company goes. Strategic decisions about market positioning, product direction, pricing architecture, which customers to pursue, what to build next, who to hire. Direction-setting work is high-stakes, cognitively demanding, and usually not urgent in the moment — which is precisely why it gets perpetually deferred in favour of things that feel more pressing. But every week you defer a direction-setting decision is a week your team is executing without clear guidance, which means they’re either guessing or waiting.</p><p><strong>2. Relationship work</strong></p><p>This is the work of building and maintaining the connections that make the business run. Investor conversations, customer calls, hiring interviews, partner meetings, team one-to-ones. Relationship work requires presence, emotional engagement, and genuine attention. It can’t be half-done. A distracted investor meeting is worse than no meeting at all, because you’ve spent the investor’s time without creating any value. Relationship work requires you to be fully switched on, which means it needs to be scheduled when you have the energy for it — not crammed into the gaps between everything else.</p><p><strong>3. Operational work</strong></p><p>This is the work of keeping the machine running. Answering emails, reviewing documents, approving expenses, dealing with administrative tasks, troubleshooting minor issues. Operational work is necessary, rarely urgent (despite feeling that way), and the least demanding on your cognitive capacity. It’s also the category that expands to fill all available time if you let it. Most founders spend sixty to seventy percent of their week on operational work, leaving a thin sliver for the direction-setting and relationship work that actually determines whether the company succeeds.</p><blockquote><strong><em>The work that feels most urgent is almost never the work that matters most. And the work that matters most almost never feels urgent.</em></strong></blockquote><h3><strong>Designing Your Week</strong></h3><p>The founders who perform best don’t just have good habits. They have structure. They design their week with the same intentionality they’d apply to designing a product. Here’s a practical framework that I’ve seen work across very different types of founders and companies.</p><ol><li><strong>Protect your first hours</strong></li></ol><p>The first two to three hours of your working day are when your cognitive capacity is highest. This isn’t productivity guru folklore — it’s consistent across the research on circadian rhythms and decision quality. These hours should be reserved exclusively for direction-setting work. No email, no Slack, no meetings. This is when you think about product strategy, evaluate a critical hire, model a pricing change, or work through a difficult strategic decision. If you do nothing else from this article, do this. The compound effect of making your most important decisions with your best available cognition is enormous over the course of a year.</p><p><strong>2. Batch your meetings</strong></p><p>Context-switching is extraordinarily expensive. Research suggests it takes an average of twenty-three minutes to fully re-engage with a task after an interruption. If you have six meetings scattered across your day with gaps of thirty to sixty minutes between them, those gaps aren’t usable for deep work — they’re recovery time dressed up as free time. The alternative is to batch your meetings into dedicated blocks. Mornings for deep work, afternoons for meetings. Or meeting-heavy days and meeting-free days. The specific pattern matters less than the principle: cluster your context switches so they don’t fragment the time you need for concentrated thought.</p><p><strong>3. Make your meetings move</strong></p><p>Not every conversation needs a conference room and a screen. Some of the sharpest founders I work with have made walking meetings their default for one-to-ones and informal catch-ups. There’s solid research behind this — walking increases creative output measurably compared to sitting — but the practical benefits go further. A thirty-minute walk with your co-founder or a team lead changes the dynamic of the conversation. People are more candid when they’re moving side by side than when they’re sitting across a table. The formality drops, the defensiveness drops, and you tend to get to the real issues faster.</p><p>One founder I work with does all his brainstorming sessions on his bike — he’ll take a long cycle with his technical co-founder when they need to work through a difficult product decision, and swears the combination of physical movement and unstructured time produces better thinking than any whiteboard session. Another uses solo runs as her dedicated time for working through the hardest strategic questions, returning with a clarity she never reaches at her desk. Whether it’s a walk around the block, thirty minutes on the bike, or time alone in the gym, building physical movement into your working pattern isn’t a break from work. It’s a different — and often better — format for it.</p><p><strong>4. Stack your meals with your meetings</strong></p><p>Here’s a simple arithmetic problem that most founders ignore. You need to eat three times a day. You also need to have conversations with investors, customers, advisors, potential hires, and your own team. If you treat meals and meetings as separate activities, you’ve just surrendered three to four hours of your day to eating alone at your desk or grabbing something forgettable between calls. If you stack them, you’ve recovered that time entirely.</p><p>A working breakfast with your co-founder to align on the week ahead. A lunch with the candidate you’re trying to close. A dinner with an investor you’re cultivating for your next round. These aren’t luxuries or indulgences — they’re efficient uses of time you were going to spend eating anyway. The informality of sharing a meal also produces better conversations, for the same reasons walking meetings do: lower formality, lower defensiveness, higher candour. Some of the most important decisions I’ve been part of — both as a founder and as an investor — happened over dinner, not in a boardroom.</p><p>And while you’re at it, normalise eating during internal meetings. The startup culture of back-to-back meetings that run through lunch, leaving founders and teams surviving on cold coffee and adrenaline, is not a badge of honour. It’s a system failure. If your team meeting runs at noon, bring lunch. If your stand-up is at nine, bring your breakfast. Tell your team explicitly that eating during meetings is not just acceptable but encouraged. The alternative — people sitting through an hour-long discussion with declining blood sugar, thinking about their empty stomach instead of the problem on the table — produces worse decisions and worse morale. A team that eats well thinks well. This is not complicated.</p><p><strong>5. Create a weekly decision log</strong></p><p>One of the most powerful practices I’ve seen effective founders adopt is keeping a simple log of the decisions they make each week. Not every trivial choice, but the ones that have strategic consequence. What was the decision, what were the alternatives, what was the reasoning, and what would need to be true for you to revisit it. This practice does three things simultaneously. It forces clarity of thought at the moment of decision. It creates an audit trail you can review to improve your pattern recognition over time. And it dramatically reduces the energy spent on revisiting decisions you’ve already made, which is one of the most insidious forms of cognitive waste in early-stage companies.</p><p><strong>6. Schedule your operational work</strong></p><p>Email, Slack, and administrative tasks should have designated time slots — not unlimited access to your attention. Two or three blocks per day of thirty to forty-five minutes each is sufficient for most founders. Outside those windows, these tools should be closed. Not minimised. Closed. The anxiety that something urgent will arrive while you’re not watching is almost always unfounded. Genuinely urgent situations find you regardless — someone will call, walk over, or send a text. The stream of Slack notifications is not urgency. It’s other people’s priorities competing for space in your head.</p><h3><strong>The Meeting Audit</strong></h3><p>Most founders have never looked critically at how they spend their meeting time, and when they do, they’re usually shocked. I’d encourage every founder to do a simple exercise: take your calendar from the last two weeks and categorise every meeting. Was it direction-setting, relationship, or operational? Was your presence genuinely necessary, or were you there out of habit or the desire to stay informed? Could the outcome have been achieved in a different format — an asynchronous update, a written memo, a five-minute walking conversation instead of a thirty-minute calendar slot?</p><p>When I’ve seen founders do this honestly, they typically discover that thirty to forty percent of their meetings are operational meetings where their presence adds marginal value. Stand-ups they attend but don’t contribute to. Status updates that could be written. Decision meetings where the decision was effectively already made. Reclaiming even half of those hours represents a transformative shift in how much capacity you have for the work that matters.</p><p>The instinct to attend everything comes from a good place — founders want to stay close to the business, they want their team to feel supported, they don’t want to miss important signals. But there’s a difference between staying informed and being physically present for every conversation. The most effective founders I’ve worked with are ruthless about which meetings require them and which require only their awareness. They read the notes. They ask questions asynchronously. They make themselves available for escalation. But they don’t sit through forty-five minutes of sprint planning when they could be working on the Series A strategy.</p><blockquote><strong><em>You cannot lead the company forward if you’re spending all your time watching it run.</em></strong></blockquote><h3><strong>Managing Energy, Not Just Time</strong></h3><p>Time management is only half the equation. You can have three hours blocked for strategic work, but if you spent the previous hour in a draining conversation about a team conflict, those three hours won’t produce the quality of thinking you need. Energy management — understanding which activities deplete you and which sustain you, and sequencing your day accordingly — is equally important and almost entirely ignored in startup culture.</p><p>This is where it gets personal, because energy patterns vary. Some founders find customer conversations energising and internal meetings draining. For others it’s the reverse. Some founders do their best strategic thinking early in the morning; others are sharper in the evening after the noise of the day has settled. The point isn’t to follow someone else’s prescription. It’s to observe your own patterns honestly and design around them.</p><p>What isn’t personal is the relationship between physical state and cognitive performance. You cannot make good decisions in a body you’re neglecting. The founder who skips meals, sits at a desk for twelve hours straight, and hasn’t raised their heart rate in weeks is not optimising for performance. They’re optimising for a crash. I’m not prescribing a specific regime — some founders run, some lift, some cycle, some swim. The modality is irrelevant. What matters is that physical movement is in your calendar, treated with the same non-negotiable status as a board meeting or a customer call. An hour in the gym at lunchtime doesn’t cost you an hour of work. It buys you two or three hours of higher-quality output in the afternoon. The maths favours it every time. The founders who understand this aren’t taking time off — they’re investing in the sharpness of every decision they’ll make for the rest of the day.</p><p>I know one founder who blocks ninety minutes every day at lunch for the gym and has done so since founding the company. His team knows that slot is untouchable. When I asked him about it, he didn’t frame it as self-care. He framed it as infrastructure. “Every important decision I’ve made well happened in the afternoon after training,” he told me. “Every bad decision I can trace back to a week where I skipped it.” That’s not anecdote as proof. But it’s a pattern I’ve seen repeated across enough founders that I’d call it a signal worth paying attention to.</p><blockquote><strong><em>You cannot outwork a body you’re running into the ground. Fitness isn’t a reward for when things calm down. Things never calm down.</em></strong></blockquote><p>One broader pattern I’ve observed consistently: the activities that create the most energy are usually the ones that generate visible progress. Shipping a feature, closing a customer, making a clear decision that unblocks the team. And the activities that drain the most energy are the ones that feel circular — meetings that don’t reach conclusions, decisions that get revisited, conflicts that simmer without resolution. If your weeks feel exhausting despite long hours, the problem is almost certainly an excess of circular activity and a deficit of progress. The fix isn’t to work more. It’s to restructure so more of your time produces visible forward movement.</p><h3><strong>The Stop Doing List</strong></h3><p>Most founders have a to-do list. Very few have a stop-doing list. And yet the stop-doing list is almost always more valuable, because the constraint on your effectiveness isn’t a shortage of good things to do — it’s the accumulation of things you shouldn’t be doing that consume the time and energy you need for the things you should.</p><p>Here are the patterns I see most often that founders need to deliberately quit.</p><ul><li><strong>Attending meetings for visibility rather than contribution.</strong> If you’re there to be seen rather than to decide or contribute, you shouldn’t be there.</li><li><strong>Making decisions that someone else could make.</strong> Every decision you make that a team member could have made is a decision you’ve taken from them and a tax on your own capacity.</li><li><strong>Personally responding to every inbound email.</strong> You are not a customer service channel. Build the systems and delegate.</li><li><strong>Reviewing work that doesn’t require your specific expertise.</strong> If your feedback is mostly “looks good”, you’re a bottleneck disguised as a quality gate.</li><li><strong>Saying yes to coffee meetings with no clear purpose.</strong> Your calendar is not a charity. Every hour you give to a vague networking conversation is an hour you’ve taken from the company.</li><li><strong>Eating at your desk as a point of pride.</strong> If you’re too busy to eat a proper meal, you’re not disciplined — you’re disorganised. Stack the meal with a conversation that needs to happen anyway, or sit down for twenty minutes and refuel properly.</li></ul><p>The difficulty with the stop-doing list is that every item on it felt like a good idea when you started doing it. Attending stand-ups felt like staying connected. Reviewing every document felt like maintaining quality. Saying yes to every meeting felt like being accessible. Skipping lunch felt like commitment. The operating system requires recognising that what made sense when you were a three-person team actively harms you at fifteen people. Your job evolves faster than your habits, and if you don’t deliberately prune the old habits, they accumulate until they’ve consumed the space where the new, more important work should live.</p><h3><strong>The System Is the Strategy</strong></h3><p>I’ve written previously about the <a href="https://medium.com/@dcirl/youre-confusing-motion-for-progress-and-it-s-killing-your-startup-369f599d2d9c">distinction between motion and momentum</a> — the difference between being busy and actually making progress. The founder’s operating system is the infrastructure that converts one into the other. Without it, you’re relying on willpower and instinct to make good decisions about where to spend your most finite resource. And willpower, as any founder who’s tried to “just be more disciplined” about their calendar can tell you, is not a sustainable strategy.</p><p>The best founders I’ve backed don’t just build systems for their products, their teams, and their operations. They build systems for themselves. They know when they think best. They know which decisions matter most. They protect the time and energy for those decisions with the same intensity they’d protect their runway or their key customers. They schedule their gym sessions and their walking meetings with the same rigour they schedule their board meetings, because they understand that the quality of the latter depends on the discipline of the former. They stack meals with conversations. They move their bodies because it sharpens their minds. They eat properly, not as self-care, but because a founder running on caffeine and cortisol is a founder making progressively worse decisions and calling it dedication.</p><p>Your company is a reflection of your decisions, and your decisions are a reflection of the conditions under which you make them. Design those conditions deliberately — your time, your energy, your body, your week — and the quality of everything downstream improves. Leave them to chance, and you’ll work harder than anyone you know and wonder why the results don’t match the effort.</p><p>Build your operating system. The company will follow.</p><p><strong>About the Author</strong></p><p><em>DC is a Venture Partner at SVV, an AI-specialist VC firm, and author of upcoming book ‘We’re Doing it Wrong: How to Build Entrepreneur Ecosystems that actually work.’ He writes regularly about startup advice, AI-native startups, velocity-focused execution, and ecosystem architecture.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d30802d9a3f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Playbook: The Investor Update That Actually Works]]></title>
            <link>https://medium.com/@dcirl/the-playbook-the-investor-update-that-actually-works-1d0b24dff1a5?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d0b24dff1a5</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[investors]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Fri, 03 Apr 2026 18:58:27 GMT</pubDate>
            <atom:updated>2026-04-03T18:58:27.466Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why the best founder-investor relationships are built on what’s broken, not what’s polished.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mROxv7OfxsTNvg5phOZ66Q.png" /></figure><p>I receive a lot of investor updates every month. Not just from companies I’ve invested in — many come from founders who keep me on their distribution list after a meeting, or from portfolio companies of other funds who cross-share with our syndicate. Two hundred updates. Every month.</p><p>I read about forty of them properly. The rest get skimmed in under ten seconds. And the ones I skim aren’t the ones with bad news. They’re the ones that say nothing at all.</p><p>Here’s the pattern I see over and over again: a founder closes a round, sends a jubilant first update, then settles into a rhythm of monthly or quarterly emails that read like a press release written by someone who’s been media-trained within an inch of their life. Revenue is “growing.” The pipeline is “healthy.” The team is “executing well.” Everything is bathed in the warm glow of vague positivity. And none of it is useful to anyone — least of all the founder sending it.</p><p><strong><em>The investor update isn’t a report card. It’s a lever. And most founders are leaving it on the table.</em></strong></p><p><strong>The Performance Theatre Problem</strong></p><p>Most investor updates are performance theatre. I don’t say this to be harsh — I say it because I’ve watched the pattern play out dozens of times, and I understand why it happens. After spending months convincing investors that you’re the right founder to back, the last thing you want to do is send an email admitting that things aren’t going to plan. It feels like an admission of failure. It feels like you’re undermining the very confidence that got you funded.</p><p>So founders default to polish. They curate. They emphasise the wins and bury the problems in euphemism. “We’re iterating on our go-to-market approach” means sales aren’t working. “We’re exploring strategic options for our enterprise segment” means the big customer deal fell through. “We’re being thoughtful about hiring” means you can’t find anyone who wants to join.</p><p>The irony is that this approach achieves the exact opposite of what founders intend. Polished updates don’t build investor confidence. They erode it. Because here’s what investors are actually thinking when they read a relentlessly positive update: either this founder has no problems — which is impossible — or this founder has problems they’re not willing to discuss. Neither interpretation builds trust. Both create distance.</p><p><strong>What Investors Actually Do With Your Update</strong></p><p>To understand why honest updates produce better outcomes, you need to understand what happens on the investor side when your email lands. At a typical early-stage fund, your update enters a workflow. It gets read by the partner who led your deal. It might get forwarded to an associate for tracking. Key metrics get entered into a portfolio monitoring system. And critically, it informs a conversation at the next partners’ meeting about which portfolio companies need attention, resources, or introductions.</p><p>This is where the dynamics shift in ways most founders don’t appreciate. At our fund, and at most funds I know, the portfolio companies that get the most active support aren’t the ones doing best. They’re the ones that are clear about what they need. When a founder writes “we’re struggling to close enterprise deals because procurement cycles are longer than we modelled”, that’s actionable. The partner reading it might know someone who can help navigate enterprise procurement. They might have a portfolio company that solved exactly this problem. They might have operational experience they can bring to bear. But they can only activate that help if they know it’s needed.</p><p>When a founder writes “sales are progressing well across all segments”, there is nothing for anyone to do except nod and move on to the next company. You’ve successfully communicated nothing. Congratulations.</p><p><strong><em>Investors can’t help you with problems they don’t know exist. And they definitely can’t help you with problems you’ve disguised as strengths.</em></strong></p><p><strong>The Vulnerability Paradox</strong></p><p>There’s a counterintuitive dynamic at work here that I think about a lot. The founders who are most transparent about their challenges are, almost universally, the ones investors trust most. Not because vulnerability is admirable in the abstract, but because it signals something specific: this founder has a clear-eyed understanding of their situation. They know what’s working and what isn’t. They’re not hiding behind narrative. They’re operating in reality.</p><p>That signal is incredibly valuable in early-stage investing, where the single greatest risk isn’t that a market won’t exist or a product won’t work — it’s that a founder will run out of runway while refusing to acknowledge that their original assumptions were wrong. Founders who can’t be honest with their investors about problems are usually founders who can’t be honest with themselves. And founders who can’t be honest with themselves don’t pivot in time, don’t cut costs in time, and don’t ask for help in time.</p><p>I’ve seen this play out in both directions. Founders who sent raw, honest updates about struggling sales ultimately got introductions that unlocked their pipeline. Founders who maintained a facade of smooth progress until the cash was nearly gone found themselves trying to raise a bridge round with investors who felt blindsided — and justifiably so. The polished updates didn’t protect those founders. They prevented anyone from helping them.</p><h3><strong>The Anatomy of an Update That Works</strong></h3><p>An effective investor update does three things simultaneously: it keeps investors informed, it builds trust, and it activates your investor network on your behalf. Here’s a structure that achieves all three without consuming your entire week.</p><p><strong>Open with the headline</strong></p><p>Two sentences maximum. What is the single most important thing that happened since the last update, and what is the single biggest challenge you’re facing right now? Not five things. Not a balanced summary. The one thing that matters most in each direction. This forces clarity of thought and signals to investors that you know what’s important. If you can’t identify the one thing, that’s diagnostic in itself.</p><p><strong>Key metrics, presented consistently</strong></p><p>Pick four to six metrics that you’ll report every single time. Revenue or ARR. Burn rate and runway. Customer count or key pipeline metric. One product metric that matters for your business. Present them the same way every update so investors can see the trajectory over time. Don’t change the metrics you report depending on which ones look good this month — that’s the fastest way to destroy credibility.</p><p>Show the numbers with brief, honest context. If ARR dropped, say so and explain why. If burn rate increased, explain what you’re investing in. Investors are adults. They can handle reality. What they can’t handle is discovering reality for themselves three months later.</p><p><strong>What’s working</strong></p><p>A short section on genuine wins. Not spin, not exaggeration — actual progress. A customer signed, a feature shipped that moved a meaningful metric, a hire you’re genuinely excited about. Keep this tight and specific. “We closed Company X on a £30K annual contract after a two-week trial, which validates our enterprise pricing model” is infinitely more useful than “sales momentum continues to build.”</p><p><strong>What’s not working</strong></p><p>This is where most founders fail, and it’s where the real value of the update lives. Be specific about what’s broken. Describe the problem clearly enough that someone reading it could potentially help. “Our conversion rate from free trial to paid dropped from 8% to 4% after we changed the onboarding flow, and we’re not sure why” gives your investors something to work with. Maybe one of them has seen this pattern before. Maybe they know a growth expert who specialises in exactly this. But “we’re optimising our conversion funnel” gives them nothing.</p><p>The founders who do this well tend to frame problems as diagnostic observations rather than confessions. You’re not apologising. You’re demonstrating that you see the problem clearly and are working on it. That’s what competence looks like in practice.</p><p><strong>The specific ask</strong></p><p>End with one to three concrete things your investors can do to help you right now. Not vague requests like “introductions to potential customers would be great.” Specific, actionable asks: “We’re trying to reach the VP of Engineering at Company Y — does anyone in the syndicate have a connection?” or “We need a fractional CFO for three months to sort out our financial model before Series A — any recommendations?”</p><p>Most investors want to help. They’ve committed capital and they’re motivated to see you succeed. But they’re also busy and they operate across dozens of portfolio companies simultaneously. The more specific your ask, the more likely someone will act on it. Vague asks get vague intentions. Specific asks get specific introductions.</p><p><strong><em>The update that gets an investor to pick up the phone isn’t the one that says everything is fine. It’s the one that says: here’s exactly where we need help.</em></strong></p><h3><strong>Getting the Mechanics Right</strong></h3><p>Frequency matters. Monthly is the standard for early-stage companies, and I’d argue it’s the right cadence for anything from pre-seed through Series A. Quarterly is too infrequent — too much changes between updates, and the gaps invite investor anxiety. Weekly is too much for most investors to process across a full portfolio. Monthly is the sweet spot: frequent enough to maintain the relationship, infrequent enough that each update carries weight.</p><p>Length matters more than most founders think. The ideal investor update is something someone can read in three to five minutes. That’s roughly five hundred to eight hundred words. If you’re writing two thousand words, you’re writing a memo, not an update. Nobody reads two-thousand-word emails from twenty different portfolio companies. They skim them, which means your carefully buried ask in paragraph fourteen gets missed entirely.</p><p>Format matters too. Send it as the body of the email, not as an attachment. Not as a link to Notion. Not as a PDF. The body of the email. Every additional click between your investor and your content is a friction point that reduces the chance they’ll read it. As someone who processes hundreds of these, I can tell you that attached updates get opened roughly half as often as embedded ones.</p><p>Subject line matters. Make it consistent and scannable. Something like “[Company Name] — Investor Update — April 2026” works because it’s immediately identifiable and searchable later. Investors often need to go back and find a specific update months later — don’t make that harder than it needs to be with clever or inconsistent subject lines.</p><h3><strong>The Mistakes That Cost Founders</strong></h3><p>Beyond the core performance theatre problem, there are a handful of specific mistakes I see repeatedly that undermine otherwise decent updates.</p><p><strong>Changing the metrics.</strong> The moment you stop reporting a metric you’ve previously included, every investor on your list assumes that metric went in the wrong direction. This is worse than reporting a bad number, because it invites speculation. If you committed to reporting churn rate, report it every time — even when it’s embarrassing. Especially when it’s embarrassing.</p><p><strong>Burying the bad news.</strong> Some founders technically include challenges but sandwich them between so much positive framing that the signal gets lost. If your biggest challenge is buried in paragraph six and surrounded by qualifiers, it’s invisible. Lead with it. The founders I respect most put their biggest problem in the first paragraph.</p><p><strong>Making excuses instead of observations.</strong> There’s a meaningful difference between “sales were slow because the market is seasonal” and “sales were slower than projected. We think seasonality is a factor, but we’re also questioning whether our pricing is right for this segment.” The first is defensive. The second is diagnostic. Investors back founders who diagnose, not founders who defend.</p><p><strong>Not sending them at all.</strong> This is the worst signal of all. When investor updates stop arriving, every investor on the list assumes the worst. And they’re usually right. The companies that go quiet are almost always the companies that are struggling. Silence doesn’t protect you — it tells your investors that either things have gone very wrong, or you’ve given up. Neither interpretation helps you if you ever need to go back to those investors for support, a bridge round, or an introduction.</p><p><strong>The Update as Relationship Architecture</strong></p><p>The investor update is one of the most underused tools in a founder’s arsenal. Not because founders don’t send them — most do, at least initially — but because they treat the update as an obligation rather than an opportunity. An obligation to prove things are going well. An opportunity to demonstrate clarity of thought, activate a network of people who are financially motivated to help you, and build the kind of trust that pays dividends when you really need it.</p><p>The founders who build the strongest investor relationships aren’t the ones whose companies never struggle. They’re the ones who are honest about the struggles in real time, specific about what help looks like, and consistent in keeping their investors close to the reality of the business. That honesty doesn’t just make for better investor relations. It makes for better companies, because a founder who can articulate what’s broken is a founder who’s already halfway to fixing it.</p><p>Your investor update isn’t a performance. It’s a conversation. And the best conversations start with the truth.</p><p><strong>About the Author</strong></p><p><em>DC is a Venture Partner at SVV, an AI-specialist VC firm, and author of upcoming book ‘We’re Doing it Wrong: How to Build Entrepreneur Ecosystems that actually work.’ He writes regularly about startup advice, AI-native startups, velocity-focused execution, and ecosystem architecture.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d0b24dff1a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Acceleration Gap]]></title>
            <link>https://medium.com/@dcirl/the-acceleration-gap-7b4c5cfa7173?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b4c5cfa7173</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[startup-ecosystem]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 12:42:08 GMT</pubDate>
            <atom:updated>2026-03-18T12:42:08.824Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why the Two-Speed Startup Economy Is Creating a Moat Nobody Can Cross</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W4kao3STc46vL1SYg-D-8g.png" /></figure><p>Last quarter, I sat through two pitch sessions back to back. The first was an AI-native team of three, eleven months old, already at €840K ARR with a product that had been through fourteen major iterations since launch. Their customer feedback loop was measured in hours. They knew, down to the feature level, exactly what drove retention in each of their three core segments.</p><p>The second was a team of nine, eighteen months in, with a polished deck, a respectable prototype, and approximately €40K in pilot revenue. They were smart, experienced, well-funded. They were also, by any honest measure, already dead. They just didn’t know it yet.</p><p>What separated them wasn’t talent. It wasn’t funding. It wasn’t even the quality of the underlying idea. It was that the first team had been operating in a fundamentally different competitive reality for nearly a year, and the distance between these two realities was no longer something the second team could close. Not by hiring. Not by pivoting. Not by adopting new tools.</p><p>I’m seeing this pattern everywhere now. Not occasionally. Not in edge cases. In the majority of the deal flow that crosses my desk, the single clearest signal of whether a startup will succeed or fail is which side of the acceleration gap it sits on. And that gap is no longer narrowing. It’s compounding.</p><h3>The Compound Interest Nobody’s Calculating</h3><p>Most people think about the advantage of AI-native teams in linear terms. They’re faster, so they get more done. Twice the speed, twice the output. That framing fundamentally misunderstands what’s happening.</p><p>The advantage is exponential, not linear, because each improvement cycle feeds into the next one. An AI-native team that ships a feature in three days instead of three weeks doesn’t just gain eighteen saved days. They gain the customer feedback from that feature eighteen days earlier. They gain the insight from that feedback eighteen days earlier. They gain the next iteration built on that insight eighteen days earlier. And that next iteration generates its own feedback, its own insight, its own iteration — all of which are also accelerated.</p><p>Run the numbers and it gets uncomfortable. If an AI-native team improves its product by even 5% per week and a traditional team improves by 1.5% per week, after twelve months the AI-native team hasn’t achieved a 3x advantage. It has achieved roughly a 12x advantage. After eighteen months, it’s closer to 30x. The maths is merciless. Compounding always is.</p><p>This isn’t theoretical. I’m watching it play out in real portfolios, across real markets. The AI-native companies in our pipeline aren’t just outpacing their traditional competitors. They’re lapping them. They’re answering market questions their competitors haven’t even formulated yet, because they’ve already run the experiments, gathered the data, and moved on to the next hypothesis.</p><p>And here’s the part that should keep every founder awake at night: the gap accelerates. It doesn’t just grow — it grows faster over time. The AI-native team at month twelve is improving faster than the AI-native team at month three, because it’s compounding on a larger base of institutional knowledge, customer insight, and operational capability. The divergence curve isn’t a straight line pulling apart. It’s a hockey stick.</p><h3>The Catch-Up Fantasy</h3><p>The most dangerous piece of conventional wisdom in the startup world right now is this: “We can catch up. We just need to adopt the right tools.”</p><p>This is roughly equivalent to saying you can become a concert pianist by buying a Steinway. The instrument is the least interesting part of the equation.</p><p>When people talk about the AI advantage, they almost always talk about tools. Which LLM are you using? What’s your AI development stack? Have you integrated copilot into your workflow? These are reasonable questions, but they’re the wrong questions. They focus on the visible, purchasable layer and completely miss the invisible, earned layer underneath.</p><p>The real advantage of an AI-native team that’s been operating at AI speed for twelve months isn’t the tools. It’s the hundreds of micro-decisions they’ve already made about how to use those tools. It’s the workflow adaptations that emerged through trial and error. It’s the intuitive understanding of when to trust AI output and when to override it. It’s the organisational habits — the meeting cadences, the decision thresholds, the communication patterns — that have been reshaped around a fundamentally faster operating tempo.</p><p>None of this transfers through a software subscription. None of it can be acquired in a workshop or an accelerator programme. It’s institutional muscle memory, and like all muscle memory, it’s built through repetition over time.</p><p>I recently spoke with a founder who’d been running an AI-native operation for fourteen months. I asked him what would happen if a well-funded competitor adopted identical tools tomorrow. He didn’t hesitate: “They’d be faster than they were. They still wouldn’t be fast. It took us four months just to learn how to think at AI speed. The tools were the easy part.”</p><p>That phrase — learning to think at AI speed — captures something important. The transformation isn’t technical. It’s cognitive and organisational. It’s a rewiring of how decisions get made, how information flows, how teams coordinate, and how fast the organisation can absorb and act on new information. You don’t install that. You cultivate it. And you can’t cultivate twelve months of adaptation in a quarter by throwing money at the problem.</p><h3>A View from the Other Side of the Table</h3><p>As an investor, I’m watching this divergence reshape deal evaluation in real time. The benchmarks for what “good” looks like at seed stage have shifted so dramatically in the past eighteen months that the metrics we used in 2023 are essentially useless.</p><p>When an AI-native team can get to €500K ARR in six months with a three-person team and €200K in capital, the startup next door with nine people, €1.2M raised, and €80K in annual revenue isn’t just behind. It’s competing in a different sport. Same pitch event, same investor audience, wildly different operating realities. And investors are adjusting their expectations accordingly — which creates a secondary problem for the slower teams.</p><p>Capital follows performance. When LPs and partners see AI-native companies hitting milestones at three to five times the rate of traditional startups, capital allocation shifts. It has to. Fund economics depend on backing winners, and the winners are increasingly clustered on one side of the acceleration gap. This means non-AI-native startups aren’t just losing the product race. They’re losing the funding race, because the bar for what constitutes an investable pace of progress has been reset by teams operating in a different gear.</p><p>The same dynamic is playing out in talent acquisition. The best engineers, designers, and operators want to work where things move. They want to see their work ship, get feedback, iterate, and ship again — on a cycle measured in days, not quarters. AI-native teams offer that cadence. Traditional startups, even well-intentioned ones, often can’t. Which means the faster teams attract better talent, which makes them faster still. Another compounding loop. Another widening gap.</p><p>I want to be clear: this isn’t a judgement about the people on either side of this divide. I’ve met brilliant founders running traditional-speed operations. The issue isn’t intelligence or ambition. It’s that the competitive environment has shifted beneath their feet, and the adjustment required isn’t incremental. It’s structural.</p><h3>The Ecosystem Problem Nobody’s Talking About</h3><p>If the acceleration gap were purely a company-level phenomenon, it would be concerning enough. But its implications extend well beyond individual startups, into the support structures, institutions, and policy frameworks that surround them.</p><p>Consider the typical accelerator programme. Twelve weeks. A cohort of ten to fifteen startups. Weekly check-ins. A demo day at the end. This cadence was designed for a world where meaningful progress took months and a twelve-week programme could materially shift a company’s trajectory. In the two-speed economy, an AI-native startup can go through the equivalent of an entire accelerator’s worth of learning in the first fortnight — and then spend the remaining ten weeks waiting for the programme to catch up.</p><p>The same misalignment shows up in public support bodies, grant processes, and government-backed entrepreneurship programmes. Application cycles measured in months. Decision timelines that assume founders can wait. Reporting requirements designed for annual review cadences. Progress metrics built around milestones that AI-native companies blow past in their first quarter.</p><p>This isn’t just inefficient. It’s actively harmful. When a support programme operates at the slower speed, it implicitly trains founders to operate at that speed too. It normalises a pace of progress that is no longer competitive. It creates an environment where founders feel validated for hitting milestones that the market has already moved past. The programme becomes a comfortable waiting room for companies that should be sprinting.</p><p>For ecosystem builders, policy makers, and anyone running support programmes, the uncomfortable question is this: are you preparing founders for the race that exists today, or the race that existed three years ago? Because if your programme timeline, your milestone expectations, and your feedback cadence haven’t fundamentally changed since 2023, you’re training athletes for an event that’s already been run.</p><h3>What Founders Should Actually Do About This</h3><p>If you’ve read this far and recognised your own startup on the wrong side of the gap, the temptation is to panic-adopt a stack of AI tools and declare yourself transformed. Don’t. That’s motion, not momentum, and it will waste the time you don’t have.</p><p>The shift that matters isn’t technological. It’s operational and it starts with decision-making cadence. Look honestly at how long it takes your organisation to go from “we have a hypothesis” to “we’ve tested that hypothesis with real users.” If the answer is measured in weeks, you have a structural problem that no tool can fix. The goal is to compress that cycle to days — not by cutting corners on quality, but by eliminating the organisational friction that sits between insight and action. Most of that friction is human: approval layers, meeting dependencies, consensus requirements, documentation overhead. AI tools can help, but only after the organisational architecture is redesigned to move at a fundamentally different speed.</p><p>Second, build learning loops that compound. Every customer interaction, every feature release, every failed experiment should feed directly and immediately into the next decision. Not through a quarterly review. Not through a strategy offsite. Through systems — automated or otherwise — that capture signal and route it to decision-makers in real time. The AI-native teams winning right now aren’t just fast. They’re learning fast, and they’re structuring their operations so that each thing they learn makes the next thing they learn more valuable.</p><p>Third, be ruthlessly honest about whether the gap is closable for your specific business. This is the advice nobody wants to give and nobody wants to hear. Some businesses, because of their market, their regulatory environment, their customer base, or their team composition, simply cannot operate at AI-native speed. That doesn’t make them bad businesses. It might make them bad venture-backed businesses. There’s an important difference. If your honest assessment is that you cannot close the acceleration gap in your market, the strategically intelligent move might be to redefine your competitive frame entirely — pursue a market where the gap is less relevant, adjust your funding model, or find the niche where depth and trust matter more than speed. That’s not failure. That’s clarity. And clarity, in a two-speed economy, is worth more than denial.</p><p>Finally, stop benchmarking against your calendar. Start benchmarking against your market. The question isn’t “Are we making progress?” The question is “Are we making progress at the rate our competitive environment demands?” In the AI-native economy, absolute progress is meaningless. Relative velocity is everything.</p><h3>The Moat That Builds Itself</h3><p>There’s a deep irony in the acceleration gap. The companies that least need a competitive moat — the ones already moving fastest — are the ones building the most durable one. Their advantage compounds without conscious effort, because every day of operation at AI speed adds another layer of institutional capability that their slower competitors can’t replicate.</p><p>The startups on the other side of the gap face the inverse: every day of operation at the slower speed doesn’t just leave them further behind. It makes catching up harder, because the distance they need to cover tomorrow is greater than the distance they needed to cover today.</p><p>This is the new competitive reality. Not a gap that opens and then stabilises. A gap that opens and then accelerates. The founders who understand this — who build their organisations, their operations, and their strategies around this fact — won’t just win their markets. They’ll make those markets unreachable for anyone who starts the race late.</p><p><em>The best time to cross the acceleration gap was twelve months ago. The second best time is today. There won’t be a third.</em></p><p><em>DC is a Venture Partner at Sure Valley Ventures, an AI-specialist VC firm investing across the UK and Ireland. He writes about entrepreneurship, AI, and the realities of building companies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b4c5cfa7173" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Ecosystem Recycling Problem: Why Exits Are Actually Infrastructure, Not Just Exits]]></title>
            <link>https://medium.com/@dcirl/the-ecosystem-recycling-problem-why-exits-are-actually-infrastructure-not-just-exits-de80eb536ce1?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de80eb536ce1</guid>
            <category><![CDATA[economic-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-ecosystem]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 12:29:38 GMT</pubDate>
            <atom:updated>2026-03-18T12:29:38.344Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Healthy ecosystems don’t need more programmes. They need more exits. Not because exits are the goal — but because exits are the fuel that powers everything else.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVCRtF_8yEjjIQtYh2NAbg.png" /></figure><h3>The Flywheel Nobody Talks About</h3><p>Every conversation about startup ecosystems eventually lands on the same topics: access to capital, quality of talent, strength of support programmes, density of mentorship networks. These are the visible inputs — the things governments fund, conferences celebrate, and strategy documents dissect. They’re important. They’re also not the thing that separates ecosystems that compound from ecosystems that stall.</p><p>The thing that separates them is recycling.</p><p>Specifically: what happens when a startup reaches its conclusion — whether through acquisition, IPO, or even a well-managed failure. In healthy ecosystems, every exit triggers a cascade of resources that flows back into the system: capital from founders and early employees who now have liquidity, talent from experienced operators who join or start early-stage companies, pattern recognition from people who’ve navigated the journey and can now compress timelines for others, and cultural permission — the visible proof that building a company in this ecosystem can actually lead somewhere.</p><p>This is the <strong>Ecosystem Flywheel</strong>. Startups are created, some succeed, their success generates resources, those resources feed the next generation of startups, some of which succeed, generating more resources. Each turn of the flywheel produces more capital, more experienced talent, more institutional knowledge, and more cultural confidence than the last. The system compounds.</p><p>When the flywheel is spinning, it looks effortless. Silicon Valley didn’t become Silicon Valley because of superior government programmes. It became Silicon Valley because six decades of exits created a self-reinforcing cycle where every generation of successful companies funded, mentored, and staffed the next generation. Israel’s ecosystem runs on the same fuel: exits that recycle founders, capital, and knowledge back into formation-stage companies at extraordinary velocity.</p><p>When the flywheel is stuck, nothing else compensates. You can pour capital into formation programmes. You can build world-class incubators. You can design elegant tax incentives. But if exits don’t happen — or don’t happen at sufficient scale and frequency — the recycling mechanism never kicks in, and the ecosystem remains permanently dependent on external inputs rather than generating its own momentum.</p><p>This is the ecosystem recycling problem. And it’s hiding in plain sight in most of the world’s aspiring startup ecosystems.</p><h3>The Four Things an Exit Actually Produces</h3><p>To understand why the recycling problem matters so much, you need to understand what an exit actually generates for an ecosystem. It’s not one thing. It’s four distinct resources, each of which is irreplaceable and none of which can be manufactured through policy alone.</p><p><strong>1. Angel capital with pattern recognition attached. </strong>When a founder exits a company for €20 million, the most valuable thing that happens for the ecosystem is not the €20 million itself. It’s that a meaningful portion of it gets reinvested into early-stage companies by someone who understands — from visceral personal experience — what those companies actually need. A founder who has built and sold a B2B SaaS company evaluates early-stage B2B SaaS companies fundamentally differently from a professional fund manager who has only seen them from the outside. They spot different risks. They ask different questions. They add different value post-investment. This is not a knock on institutional investors. It’s an observation that founder-angels bring a qualitatively different type of capital that ecosystems cannot replicate through any other mechanism. When exits don’t happen, this capital doesn’t exist.</p><p><strong>2. Experienced operators who de-risk early-stage teams. </strong>After an exit, a predictable pattern emerges: some founders start new companies, some join early-stage companies as senior operators, and some do both sequentially. Each of these paths dramatically improves the success rate of the companies they touch. A CTO who has scaled a product from zero to ten million users brings institutional knowledge that a first-time technical founder simply cannot have. A VP of Sales who has built an enterprise sales motion from scratch at one company can compress that learning curve from two years to six months at the next one. This experienced talent is the single most underappreciated asset in ecosystem development. Every exit that doesn’t happen is experienced talent that remains locked inside a company — often a company that is no longer growing — rather than being redistributed to where it could generate the most value.</p><p><strong>3. Pattern recognition and scar tissue that compresses timelines. </strong>Founders who’ve been through the full lifecycle — formation, growth, scaling, exit — possess pattern recognition that cannot be taught. They’ve made specific mistakes in specific contexts and understand not just what went wrong but why, and what they would do differently. When they mentor the next generation, they don’t offer generic advice. They offer calibrated judgment forged from lived experience. This is what I’ve described elsewhere as “scar tissue” — the hard-won knowledge that only comes from having been through it. An ecosystem without exits is an ecosystem where this scar tissue doesn’t accumulate. Every generation of founders makes the same mistakes as the previous one, because nobody who’s completed the journey is available to warn them.</p><p><strong>4. Cultural permission and proof of possibility. </strong>This is the most intangible resource, and possibly the most important. When a company exits successfully in a given ecosystem, it sends a signal to every potential founder in that market: it can be done here. This is not motivational poster nonsense. It’s a practical calculation that aspiring founders make when deciding whether to leave a comfortable job and take the risk. If no company in their ecosystem has achieved a meaningful exit in the last five years, the rational conclusion is that the ecosystem doesn’t support outcomes at that level. The talented engineer at the multinational stays at the multinational. The senior product manager considers starting a company but decides the risk-reward ratio doesn’t justify it. Each missing exit is a signal that suppresses the next hundred potential founders.</p><h3>Where the Flywheel Gets Stuck</h3><p>If exits are the fuel, the obvious question is: why aren’t they happening at sufficient scale in most ecosystems? The answer is not one thing — it’s a series of interconnected structural failures, any one of which can stall the flywheel.</p><p><strong>The acquisition gap. </strong>Most startup exits globally happen through acquisition, not IPO. For acquisitions to happen at scale, an ecosystem needs a layer of mature technology companies large enough to be acquirers. Silicon Valley has thousands of them. Israel has cultivated deep relationships with US acquirers and multinational R&amp;D centres that function as acquisition pipelines. Most developing ecosystems have almost no domestic acquirers and weak institutional relationships with international ones. The result is that even when a startup builds something genuinely valuable, there’s nobody positioned to buy it. The company either relocates to a market with acquirers — taking the exit and its recycling effects with it — or it lingers, growing slowly, consuming resources, never reaching the liquidity event that would release its value back into the ecosystem.</p><p>This acquirer gap is structural, not incidental. It’s a direct consequence of ecosystem immaturity: you need successful companies to create the conditions for more successful companies, and the first generation has no predecessors to sell to. Breaking this chicken-and-egg problem requires deliberate policy intervention — attracting multinational R&amp;D operations, creating incentives for corporate development activity, building relationships with international acquirers — that most ecosystem strategies completely ignore because they’re focused on the creation of startups rather than their conclusion.</p><p><strong>The IPO infrastructure deficit. </strong>For the small percentage of companies that reach IPO scale, many ecosystems lack the institutional infrastructure to support a public listing. Local stock exchanges may not have technology-focused indices. Institutional investors may lack experience valuing high-growth technology companies. Analyst coverage may be nonexistent. The practical result is that companies large enough to go public often list elsewhere — on NASDAQ, the London Stock Exchange, or Euronext — which dilutes the local ecosystem’s claim on the recycling benefits. The founders may stay local, but the institutional knowledge, capital market expertise, and public market infrastructure don’t develop domestically.</p><p><strong>The zombie trap. </strong>I’ve written extensively about zombie startups — companies that are technically alive but lack the growth trajectory to reach a meaningful exit. They shuffle through the ecosystem, consuming capital and talent without generating the liquidity events that would recycle those resources. But here’s the ecosystem-level insight that gets missed: every zombie company is a recycling failure. It’s capital that could be angel investment locked in a company going nowhere. It’s experienced talent trapped in a role that utilises a fraction of their capability. It’s a cautionary tale that discourages the next generation of founders instead of an inspiring example that encourages them. Healthy ecosystems need mechanisms for graceful failure — orderly wind-downs that release talent and capital quickly rather than letting them decay slowly inside companies that will never reach escape velocity.</p><p><strong>Capital gains taxation as a recycling blocker. </strong>In many ecosystems, the tax treatment of startup exits actively discourages the recycling behaviour that ecosystems need most. When founders face punitive capital gains taxes on exit proceeds, two things happen: they delay exits to defer the tax event, locking up resources that the ecosystem needs, and they’re less likely to reinvest the post-tax proceeds in high-risk early-stage companies because the risk-adjusted return no longer justifies it. The countries that understand this — the UK with its Entrepreneurs’ Relief and EIS structure, Israel with its incentives for founder reinvestment, Singapore with its absence of capital gains tax entirely — are the countries where exits recycle most efficiently. The countries that don’t understand it are the countries where founders exit and emigrate, taking the recycling benefits with them.</p><h3>The Recycling Velocity Gap</h3><p>Even in ecosystems where exits do happen, there’s a second-order problem that most people miss: the speed at which exit proceeds recycle back into the ecosystem determines the compounding rate of the flywheel.</p><p>In Silicon Valley, the recycling velocity is extraordinary. A founder exits, and within months they’re writing angel cheques, advising early-stage companies, or starting their next venture. The cultural expectation is that you stay in the game. The infrastructure supports it: cap table management tools make distributions fast, tax treatment is favourable, and the social norm is to reinvest rather than retire. The recycling half-life — the time it takes for half of an exit’s resources to re-enter the ecosystem — is measured in months.</p><p>In most other ecosystems, the recycling velocity is glacial. A founder exits, pays taxes, takes a year off, considers their options, maybe buys some property, slowly gets involved in angel investing, and might start another company three to five years later. The cultural norm is to “take a break.” The tax system doesn’t reward fast reinvestment. There’s no institutional infrastructure that channels exit proceeds back into the ecosystem quickly. The recycling half-life is measured in years, not months.</p><p>This velocity gap compounds devastatingly over time. An ecosystem where exits recycle in six months gets twice as many turns of the flywheel per decade as an ecosystem where exits recycle in five years. Over twenty years — roughly the time it takes for an ecosystem to mature — that difference in compounding rate produces a chasm in outcomes that no amount of government funding can bridge.</p><p>The implications for ecosystem design are profound. It’s not enough to create the conditions for exits. You have to create the conditions for <em>fast</em> recycling. That means tax incentives that reward reinvestment within specific timeframes. It means cultural infrastructure — founder communities, angel networks, venture studios — that immediately re-engage successful founders rather than letting them drift out of the ecosystem. It means making the path from exit to re-engagement frictionless, attractive, and socially expected.</p><h3>What Healthy Recycling Looks Like</h3><p>The ecosystems that get recycling right share specific characteristics that aspiring ecosystems consistently fail to study — partly because these characteristics are invisible to visiting delegations, and partly because they’re boring compared to shiny innovation campuses and impressive demo days.</p><p><strong>Israel: The Compounding Machine. </strong>Israel’s ecosystem is the world’s most efficient recycling system. With over 100 exits per year in a country of nine million people, the recycling rate is extraordinary by any measure. But what makes Israel exceptional isn’t just the volume of exits — it’s the cultural expectation of what happens after. Israeli founders who exit are expected to reinvest, mentor, and build again. The military culture of service and contribution transfers directly into entrepreneurial culture: you succeed, and then you help others succeed. The result is that Israeli angel investors are overwhelmingly former founders. Israeli startup boards are populated by people with operational scar tissue. Israeli accelerators are run by people who’ve actually built companies. This isn’t an accident. It’s the compound interest of sixty years of recycling.</p><p><strong>Silicon Valley: The Talent Redistribution Engine. </strong>When a Silicon Valley startup gets acquired, the most important thing that happens isn’t the financial transaction — it’s the talent redistribution. The experienced team scatters across the ecosystem: some start new companies, some join other startups at senior levels, some become investors. The acquirer, meanwhile, has integrated the technology and team it needed, making it a stronger potential acquirer or partner for the next wave. This constant redistribution of experienced talent is the primary mechanism through which Silicon Valley’s knowledge base compounds. It’s why a Series A company in San Francisco can hire a VP of Engineering who has already scaled a team from ten to two hundred — because that person exists in the talent pool, released by a previous exit. In ecosystems without exits, that person doesn’t exist. The Series A company hires someone doing it for the first time and makes all the predictable mistakes.</p><p><strong>The UK: Incentive Architecture for Recycling. </strong>The UK’s approach to ecosystem recycling is less culturally organic than Israel’s or Silicon Valley’s, but it demonstrates something important: recycling behaviour can be engineered through policy. The Seed Enterprise Investment Scheme and Enterprise Investment Scheme don’t just encourage investment in startups — they specifically create a tax-efficient pathway for recycling exit proceeds back into the ecosystem. An entrepreneur who exits, pays capital gains tax with Entrepreneurs’ Relief, and then invests in SEIS-eligible companies receives significant tax relief on those investments. The system is explicitly designed to accelerate the recycling loop. The cumulative result — £34 billion invested into 59,000 businesses — demonstrates that incentive architecture can substitute for cultural norms when those norms haven’t yet developed.</p><h3>The Recycling Failures Nobody Diagnoses</h3><p>If healthy recycling is the engine of ecosystem compounding, then recycling failures are the silent killers of ecosystem potential. And they’re almost never diagnosed correctly because people look at the wrong symptoms.</p><p>When an ecosystem struggles to produce successful startups, the standard diagnosis is always about inputs: not enough capital, not enough talent, not enough programmes, not enough mentorship. The standard prescription is always more of these inputs: more funding, more accelerators, more government support. But in many cases, the actual problem is downstream. The inputs exist. What’s missing is the recycling mechanism that turns those inputs into compounding returns.</p><p>Consider a mature ecosystem that has been investing in startup support for fifteen years. It has produced a reasonable number of startups. Some have grown to meaningful scale. But very few have exited, and those that did often relocated to another jurisdiction before the exit happened. The ecosystem looks at its results, concludes it needs more investment in formation-stage support, and doubles down on programmes.</p><p>This is the wrong diagnosis. The problem isn’t formation. The problem is that the companies formed ten years ago haven’t exited yet, which means the capital, talent, and knowledge from that generation hasn’t recycled, which means the current generation is starting from the same base rather than from a compounded one. Adding more formation programmes to an ecosystem without recycling is like pouring water into a bucket with a hole in it. The water level never rises because the recycling loop that should be returning resources to the top of the funnel doesn’t exist.</p><p>This misdiagnosis is epidemic. I’ve watched ecosystems across Europe, the Middle East, Southeast Asia, and Latin America pour resources into startup creation while completely ignoring the question of what happens to those startups once they’re created. The implicit assumption seems to be that exits will take care of themselves — that if you create enough startups, some will inevitably exit, and the flywheel will start spinning on its own.</p><p>It won’t. Exits don’t happen by accident. They happen because specific structural conditions exist: acquirers who are present and active, capital markets that support liquidity events, tax regimes that don’t punish founders for succeeding, and cultural norms that encourage recycling rather than extraction. In the absence of these conditions, even a vibrant startup creation ecosystem will produce disappointing long-term results — because the flywheel never engages.</p><h3>Building the Recycling Infrastructure</h3><p>If exits are ecosystem infrastructure, then building the conditions for exits should be a first-order priority for any serious ecosystem strategy. Here’s what that looks like in practice.</p><p><strong>Design for the full lifecycle, not just formation. </strong>Most ecosystem strategies are obsessively focused on startup creation: incubators, accelerators, seed funding, formation-stage support. These matter. But they’re only the first third of the lifecycle. An ecosystem strategy that doesn’t address scaling support, exit pathways, and post-exit recycling is an ecosystem strategy that’s designed to produce startups but not outcomes. Every serious ecosystem strategy should include explicit goals for exit volume, exit value, and recycling velocity alongside the usual metrics for company formation and early-stage investment.</p><p><strong>Build the acquirer layer deliberately. </strong>This is the most structurally important and most consistently ignored piece of ecosystem architecture. Ecosystems need domestic or domestically-connected acquirers. That means attracting multinational corporate development teams, incentivising R&amp;D centre establishment by large technology companies, creating deal-flow infrastructure that connects mature startups with potential acquirers, and fostering the growth of indigenous companies to a scale where they themselves become acquirers. The UK’s technology ecosystem improved dramatically when its first generation of successful companies — companies like Autonomy, ARM, and DeepMind — demonstrated that valuable exits were possible on British soil. Each of those exits, whatever their individual controversies, expanded the acquirer map and made the next generation of exits more likely.</p><p><strong>Fix the tax recycling loop. </strong>Capital gains tax policy should be explicitly designed to accelerate ecosystem recycling, not just to generate revenue. This means favourable treatment for founders who reinvest exit proceeds in early-stage companies within a defined timeframe. It means angel investment tax relief that makes the risk-adjusted return on recycled capital attractive. It means ensuring that the tax treatment of employee equity — the mechanism through which experienced talent gets created — doesn’t penalise the very behaviour the ecosystem needs. Countries that tax founder exits heavily and offer no incentive for reinvestment are countries that export their ecosystem’s recycling benefits to jurisdictions with better policy design.</p><p><strong>Create graceful failure infrastructure. </strong>Not every startup will achieve a successful exit. Many will fail. The question for ecosystem architecture is: how quickly and humanely does that failure release resources back into the system? Ecosystems need streamlined wind-down processes that don’t trap founders in legal limbo for years. They need cultural mechanisms — founder communities, peer support, reintegration pathways — that make failure a step in the journey rather than the end of it. They need investors who understand that a fast, clean failure followed by a founder’s next venture is vastly preferable to a slow zombie death that consumes five years of everyone’s time. Every month a zombie company stumbles on is a month its founders, employees, and investors aren’t recycling into something better.</p><p><strong>Engineer the cultural expectation of recycling. </strong>In the strongest ecosystems, recycling is not just incentivised — it’s expected. Founders who exit and disappear are the exception, not the norm. The cultural infrastructure that creates this expectation includes visible founder-angel networks, alumni communities from successful companies that stay connected, public celebration of founders who start their second and third companies, and explicit mentorship programmes that create social obligations to give back. None of this happens organically in young ecosystems. It has to be designed, funded, and cultivated until it becomes self-sustaining.</p><h3>The Uncomfortable Arithmetic</h3><p>Let me make the recycling problem concrete with some rough arithmetic.</p><p>An ecosystem that produces fifty funded startups per year, with a ten-year average time to exit and a fifteen percent exit rate, generates approximately seven to eight exits per year once the pipeline matures. If those exits average €30 million in value and founders reinvest twenty percent, that’s roughly €40–50 million in recycled angel capital per year, plus perhaps a hundred experienced operators released back into the talent pool. That’s meaningful — enough to start the flywheel turning.</p><p>Now consider the same ecosystem with a five percent exit rate because the structural conditions for exits don’t exist. That’s two to three exits per year, generating perhaps €10–15 million in recycled capital and a handful of experienced operators. Not enough to sustain a flywheel. The ecosystem remains permanently dependent on external capital, imported talent, and government programmes to fund each new generation. It never compounds. It never becomes self-sustaining. It’s a garden that needs watering every day because it never develops roots.</p><p>The difference between these two scenarios isn’t the quality of startups being produced. It’s the exit rate — which is a function of structural conditions that are entirely within the power of policymakers and ecosystem builders to influence. The acquisition gap, the tax treatment, the failure infrastructure, the cultural expectation of recycling — these are design choices, not laws of physics.</p><p>Every ecosystem strategy I’ve seen in the last five years has a section on company creation. Almost none have a section on company conclusion. This asymmetry reveals a fundamental misunderstanding of how ecosystems actually work. Creation without recycling is a one-way street. You pour resources in at the top, and they flow through the system and disappear at the bottom. Creation <em>with</em> recycling is a loop. Resources flow through the system, generate returns, and flow back to the top to fund the next generation.</p><p>The ecosystems that understand this are the ecosystems that compound. The ecosystems that don’t are the ecosystems that wonder why, after twenty years of investment in startup programmes, they still haven’t produced a self-sustaining entrepreneurial economy.</p><p>Exits aren’t the finish line. They’re the starting gun for everything that comes next.</p><p><em>DC Cahalane is a Venture Partner at Sure Valley Ventures, an AI-specialist early-stage VC firm investing across the UK and Ireland.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de80eb536ce1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation Theatre]]></title>
            <link>https://medium.com/@dcirl/innovation-theatre-15ff551b329e?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/15ff551b329e</guid>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[corporate-innovation]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 19:56:58 GMT</pubDate>
            <atom:updated>2026-03-06T19:56:58.556Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Busy Being Innovative, Building Nothing</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Km3VMtf0RiUAEzl0G6ovQ.png" /></figure><p>Picture the scene. A major corporation has just unveiled its new innovation hub. The ribbon is cut in a gleaming glass-fronted space in the city’s tech quarter. There are bean bags. There is exposed brick. There is, inevitably, a wall with the word ‘FAIL’ on it, stylised in brushed steel — because nothing says ‘we embrace failure’ quite like a several-thousand-euro piece of custom signage.</p><p>The press release goes out. The LinkedIn posts follow. Senior executives are photographed alongside young founders, everyone beaming. The launch event features a panel discussion about ‘the future of innovation’, moderated by someone whose title includes the word ‘evangelist’. There is a pitch competition with a prize fund. There is a hashtag.</p><p>The founders who win the pitch competition get a cheque, a press mention, and a meeting with a ‘senior stakeholder’ that takes eleven weeks to schedule and produces no commercial outcome. The corporate gets a year’s worth of social media content and a line in its ESG report.</p><p>Six months later, the hub is used primarily for client entertaining and internal offsites.</p><p>This is <strong>Innovation Theatre</strong>. And it is everywhere.</p><h3>Defining the Performance</h3><p>Innovation Theatre is the systematic performance of innovation activity without the substance of innovation outcomes. It is what organisations — corporations, governments, universities, and increasingly, accelerators — do when they want to be associated with innovation without doing the hard, expensive, uncertain work that innovation actually requires.</p><p>It is not a new phenomenon. But it has industrialised. And it has found, in the startup ecosystem, the perfect stage.</p><p>The cast is large and the performances are diverse. Corporate innovation labs that produce no commercial products. Government startup competitions where the grand prize is a desk in a government building and some ‘mentoring’. Hackathons where the winning idea disappears the moment the weekend ends. Accelerator programmes that cycle cohorts through the same generic curriculum regardless of their actual stage or needs. Corporate venture arms that make small, exploratory investments designed to generate optics rather than returns. ‘Open innovation’ initiatives structured as beauty pageants, where startups perform their pitch, the corporate takes notes on their technology approach, and nothing happens next.</p><p>What all of these have in common is a fundamental misalignment between what is being measured and what actually matters. The organisation measures activity — events held, startups engaged, press mentions generated, boxes ticked in the innovation programme checklist. Founders measure outcomes — customers acquired, contracts signed, revenue earned, genuine partnerships formed.</p><p>These are not the same thing. And the gap between them is where founder time, energy, and capital goes to die.</p><h3>Who Performs It, and Why</h3><p>Before naming the harm, it is worth understanding the incentive structures that produce Innovation Theatre — because most of it is not malicious. It is structural.</p><p>For large corporations, genuine innovation is threatening. It challenges existing revenue streams, requires patience with uncertain outcomes, and demands that senior leaders champion projects that might fail publicly. Innovation Theatre offers a superior deal: all the external signalling of an innovative culture, with none of the internal disruption. The innovation team gets budget and visibility. The CEO gets a compelling narrative for the annual report. Nobody’s P&amp;L is at risk.</p><p>For governments and economic development agencies, the calculus is similar. Innovation ecosystems are complex adaptive systems that take years to show measurable results. Politicians operate on electoral cycles of four to five years. Programmes that generate visible, photographable, press-release-ready activity are far more attractive than the patient infrastructure investment that actually builds ecosystems. Nobody cuts a ribbon on a ten-year tax incentive reform.</p><p>For universities, innovation theatre serves the rankings and the alumni narrative. For accelerators, it fills cohorts and justifies management fees. For ecosystem organisations, it fills event calendars and membership value propositions.</p><p>The incentive to perform innovation is, in most institutional contexts, considerably stronger than the incentive to produce it.</p><p>And founders are the ones who bear the cost.</p><h3>The Specific Harm to Founders</h3><p>Here is what Innovation Theatre actually costs founders, and why it is more dangerous than most of them realise.</p><p>Time is a startup’s only non-renewable resource. Every week spent in a pitch competition that will not lead to a commercial outcome, every meeting with a corporate ‘innovation champion’ who has no budget authority, every accelerator cohort that provides community but not customers — these are not neutral. They are weeks not spent on the work that determines whether a startup survives.</p><p>The more insidious cost is psychological. Innovation Theatre is designed, consciously or not, to feel like progress. The pitch competition provides the dopamine hit of winning. The corporate meeting provides the sense of being taken seriously. The accelerator cohort provides structure, community, and the feeling of forward motion. Founders emerge from these experiences feeling validated, when the only validation that matters is revenue.</p><blockquote><em>The startup ecosystem has built an extraordinarily sophisticated infrastructure for making founders feel like they’re building businesses while they’re actually performing them.</em></blockquote><p>I have watched talented founders spend eighteen months cycling through pitch competitions, corporate innovation programmes, and accelerator cohorts, accumulating a LinkedIn feed full of badges and trophies, while their actual metrics barely moved. They were not lazy. They were not stupid. They were responding rationally to an environment that rewarded performance over progress.</p><p>There is also the strategic distraction cost. Engaging with corporate innovation programmes typically means dedicating significant founder time to understanding the corporate’s processes, navigating their stakeholder landscape, and tailoring your proposition to their internal needs — all before you know whether there is any genuine commercial intent. This is not relationship-building. This is unpaid consulting.</p><p>And then there is the opportunity cost of misplaced optimism. A founder who has been told by a corporate that they are ‘really excited about exploring a partnership’ will, entirely rationally, hold back from approaching the corporate’s competitors. They will decline inbound from potential customers in the same sector, not wanting to compromise the relationship. They will build their pipeline assumptions around a deal that was never real. By the time it becomes clear that the corporate’s enthusiasm was performative, months have been lost.</p><h3>How to Spot It Before It Costs You</h3><p>Innovation Theatre is not always obvious in the moment — that is what makes it effective. But there are reliable signals, and experienced founders learn to read them quickly.</p><p>The first signal is the absence of commercial specificity. Genuine innovation engagement starts early with questions about commercial terms, procurement processes, and integration requirements. Performative engagement stays permanently at the level of the exciting, the interesting, and the potential. If nobody has mentioned a budget, a procurement timeline, or a specific use case after two or three meetings, you are almost certainly in a theatre.</p><p>The second is stakeholder distance. Corporate innovation teams are frequently structurally disconnected from business units with actual budgets. They exist to identify and engage startups — not to buy from them. If your champion cannot get you into a room with someone who controls a budget, your champion cannot help you.</p><p>The third is the engagement model itself. Programmes that ask founders to spend significant time and energy on activities with no clear commercial pathway — pitch competitions with prize funds but no procurement commitment, hackathons, demo days that are not investor days — are almost always theatrical. The corporate or institution is extracting value (ideas, technology intelligence, brand association, content) without offering equivalent value in return.</p><p>The fourth is urgency asymmetry. You need this to move quickly. They need nothing. Urgency is a reliable signal of genuine intent. Its absence tells you something important about how seriously the other party is taking the relationship.</p><ul><li>No budget authority in the room? You’re in a theatre.</li><li>Three meetings and still no commercial specifics? You’re in a theatre.</li><li>They’re more interested in your pitch deck than your product? You’re in a theatre.</li><li>The programme’s success metrics are about reach and engagement, not founder outcomes? You’re in a theatre.</li><li>The ‘prize’ is mentoring, visibility, or a desk? You’re almost certainly in a theatre.</li></ul><h3>What Genuine Innovation Engagement Looks Like</h3><p>The antidote to Innovation Theatre is not cynicism — it is clarity. And to be clear: genuine corporate-startup collaboration exists, creates real value, and can be transformational for both parties. The problem is not that large organisations engage with startups. The problem is the performance of engagement without its substance.</p><p>Genuine engagement has a commercial pathway visible from the first conversation. The corporate knows what problem they are trying to solve and is willing to discuss what a real solution is worth to them. They bring people with budget authority into the room early. They move at a pace that acknowledges the founder’s constraints, not just their own.</p><p>Genuine government support does not look like pitch competitions and innovation hubs. It looks like Estonia’s e-Residency programme — infrastructure that removes friction and then gets out of the way. It looks like the UK’s SEIS and EIS — tax incentive architecture that shapes private investment behaviour rather than substituting for it. It produces systemic, compounding returns rather than press releases.</p><p>Genuine accelerator support is not curriculum delivery to a cohort of twenty companies with fundamentally different challenges. It is one-to-one engagement with the specific, heterogeneous obstacles a founder faces right now — because no two growth-stage companies are failing in exactly the same way, and the pretence that they are is what produces generic advice that serves no one.</p><p>The test I would apply to any innovation programme or engagement opportunity is simple: can you draw a straight line from participating in this to a specific, measurable commercial outcome within a defined timeframe? If the line requires you to pass through more than two ‘exploration meetings’ or ‘relationship-building sessions’ before any commercial discussion can happen, you have your answer.</p><h3>A Note to the Performers</h3><p>To the corporations, governments, and institutions running Innovation Theatre programmes — a direct word.</p><p>You are not fooling anyone who has been in the ecosystem long enough. The founders who engage with your programmes are not naive; they are optimistic, and they are rationally testing whether the engagement is genuine. When they discover it is not, they tell each other. Ecosystems are small. Reputations for performative engagement spread faster than reputations for genuine partnership.</p><p>More importantly: you are wasting money. The investment required to run a credible-looking innovation programme — the staff, the events, the hub, the prizes — is substantial. The return, measured against actual innovation outcomes or genuine startup partnerships, is typically negligible. You would generate more real value by identifying two or three startups solving genuine problems you have, and buying from them at market rates.</p><p>But the deepest cost is to the founders you engage and disappoint. They trusted the signal. They invested their time, adjusted their strategy, and told their investors about the potential partnership. When the engagement collapses into nothing, it is not a neutral outcome for them. For some, it is genuinely damaging.</p><p>If you are not prepared to create genuine commercial pathways for the startups you engage, the most honest and valuable thing you can do is not engage them at all.</p><h3>The Curtain Call</h3><p>Innovation Theatre persists because it serves the institutional interests of the organisations that perform it. It will not be reformed from the inside. The pressure has to come from founders who become better at identifying it early, from investors who stop treating accelerator logos and corporate LOIs as validation signals, and from the broader ecosystem stopping its applause.</p><p>The scene I described at the opening — the gleaming hub, the exposed brick, the ‘FAIL’ signage — is not the exception. It is standard operating procedure across dozens of cities and hundreds of organisations. And every founder who spends six months navigating it before realising the show was never for them is six months further from building something real.</p><p>The performance will continue as long as there is an audience.</p><p>Stop watching.</p><p>—</p><p><em>DC Cahalane is a Venture Partner and Head of Ecosystem at </em><a href="http://www.svv.ai/"><em>SVV </em></a><em>(Sure Valley Ventures) and a four-time startup founder. He writes about venture capital, startup ecosystems, and the gap between what the ecosystem says and what it does.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15ff551b329e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[90 Days to €10K MRR: The Founder’s Playbook for Building Revenue Momentum]]></title>
            <link>https://medium.com/@dcirl/90-days-to-10k-mrr-the-founders-playbook-for-building-revenue-momentum-68505847a09f?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/68505847a09f</guid>
            <category><![CDATA[revenue]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 20:52:06 GMT</pubDate>
            <atom:updated>2026-03-02T20:52:06.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_r5lQNJfg9BKo9r16QMXFg.png" /></figure><p><em>The best founders I’ve backed all share the same origin story. Not a lightbulb moment. Not a brilliant pivot. A disciplined 90-day sprint that turned an idea into evidence.</em></p><p>Last year, I watched a founder go from her first customer conversation to €12,000 in monthly recurring revenue in exactly 87 days. She didn’t have a revolutionary product. She didn’t have a famous co-founder. She didn’t have a warm introduction to a single investor. What she had was a system.</p><p>Not a complicated system. Not a proprietary framework she’d learned at business school. A simple, repeatable rhythm of focused 30-day sprints, each one building on the last, each one moving her closer to the milestone that changes everything for an early-stage company: €10,000 in monthly recurring revenue.</p><p>I’ve been on both sides of the table — four times as a founder, now as a venture partner at an AI-specialist VC firm. Across hundreds of companies, I’ve seen enough patterns to know what works. And the founders who reach meaningful revenue fastest aren’t the ones with the most elaborate strategies or the biggest seed rounds. They’re the ones who understand that momentum is built in 30-day increments, and that revenue is the most honest signal the market can give you.</p><p>This is the playbook.</p><h3>Why €10K MRR Is the Milestone That Changes Everything</h3><p>Let me be specific about why this number matters.</p><p>€10K MRR isn’t a vanity milestone. It’s a proof point. It tells you — and eventually, investors — three things simultaneously. First, that you’ve found a problem painful enough that people will pay to solve it. Second, that you can acquire customers through a process that’s at least partially repeatable. Third, that you’re building recurring relationships, not collecting one-off transactions.</p><p>In the AI era, where companies are reaching €1M ARR in months rather than years, €10K MRR might sound modest. But every one of those hypergrowth companies had the same unglamorous starting point. The magic of €10K MRR isn’t the revenue itself — it’s what it unlocks.</p><p>For you as a founder, it transforms your confidence from hope into evidence. Every conversation you have — with co-founders, with advisors, with potential hires — shifts from speculative to grounded. You’re no longer asking people to believe in a vision. You’re showing them a business that’s working.</p><p>For investors, it changes the entire nature of the conversation. I sit through hundreds of pitches. The difference between a founder who says “we believe customers will pay for this” and one who says “we have twelve customers paying us €800 a month and our pipeline has thirty more” is the difference between a polite coffee and a serious diligence process.</p><p>And perhaps most importantly, €10K MRR is where compounding begins. Each customer you’ve acquired teaches you something about how to acquire the next one. Each subscription renewal proves your product is delivering ongoing value. Each month of growth makes the following month’s growth easier. This is the engine of momentum — each win making the next win more likely.</p><h3>The System: Three 30-Day Sprints</h3><p>The framework behind this playbook is one I’ve encouraged dozens of founders to adopt: 30/60/90 day planning. The concept is simple. You should have absolute clarity on the next 30 days. Reasonable visibility on days 31–60. And a directional view of days 61–90.</p><p>Most founders instinctively resist this. They want to plan twelve months out. They want to map every milestone, build elaborate roadmaps, set annual OKRs. That feels strategic. It feels serious. It also, in most cases, is fiction writing. The startup world moves too fast for twelve-month plans to survive contact with reality. What matters — what actually drives outcomes — is what you’re doing in the next 30 days.</p><p>The beauty of 30-day sprints is that they force honesty. When the deadline is the end of this month rather than the end of next year, you can’t hide behind aspirational language. You either shipped it or you didn’t. You either closed the customer or you didn’t. You either hit the milestone or you missed it.</p><p>Here’s how the three sprints build on each other to take you from zero to €10K MRR.</p><h4>Sprint 1 (Days 1–30): Find the Pain, Price the Solution</h4><p>The entire purpose of your first 30 days is to answer two questions. Is the problem you’re solving painful enough that someone will pay for a solution? And if so, what will they pay?</p><p>Notice I didn’t say “build the product.” This is where many founders start, and it’s the wrong starting point. Building is comfortable. It’s controllable. You’re in your element, writing code or designing interfaces, and you can tell yourself that success is just around the corner once you finish that next feature. But the market doesn’t care about your comfort. It cares about value.</p><p>The founders who reach €10K MRR fastest start with conversations, not code.</p><p><strong>Week 1–2: Deep customer discovery. </strong>Schedule 15–20 conversations with potential customers in your target segment. Not casual coffees. Structured conversations where you’re exploring the depth of the pain you’ve identified. How are they currently solving this problem? What does it cost them — in money, time, frustration? What have they already tried? What would a perfect solution look like?</p><p>The specificity matters here. “Everyone we talk to loves the idea” is worthless. “We spoke to 18 procurement managers at mid-market retailers, and 12 told us they’re spending more than 15 hours a week on manual inventory reconciliation” — that’s a signal you can build on.</p><p><strong>Week 2–3: Pricing validation. </strong>Start testing willingness to pay before you’ve built anything. This terrifies most founders, but it’s the fastest way to learn what actually matters. Describe the solution you’re building. Put a price on it. Watch how people react. The goal isn’t to close deals yet — it’s to understand whether you’re in the right ballpark and what the customer values most.</p><p><strong>Week 3–4: Secure commitments. </strong>By the end of Sprint 1, you want tangible evidence of demand. Signed letters of intent. Waitlist deposits. Design partner agreements. These aren’t revenue yet, but they represent something far more valuable than theoretical interest: commitment. Someone put their name, their reputation, or even a small amount of money behind the statement “I want this.”</p><p><strong>Sprint 1 deliverables: </strong>15+ deep customer conversations completed. A validated pricing hypothesis. At least 3 signed commitments (LOIs, design partner agreements, or waitlist deposits). A clear definition of your ideal customer profile — not a broad market, but a specific segment you can serve brilliantly.</p><h4>The Six-Pillar Check-In</h4><p>One of the patterns I see in the most effective founders is that they think about their business across six interconnected dimensions, even from day one: technology, product, commercials, people, finance, and operations. At the end of each sprint, take thirty minutes to audit your progress across all six.</p><p>For Sprint 1, this means asking: Are we building the right technology to serve the customers we’ve spoken to (technology)? Is our product vision aligned with the actual pain we’ve discovered (product)? Do we have a commercial pipeline forming (commercials)? Do we have the right people to execute the next sprint (people)? Do we understand our unit economics at a basic level (finance)? Can we actually onboard and serve a customer if one says yes tomorrow (operations)?</p><p>These dimensions need to advance together, not sequentially. You don’t perfect your technology, then build your product, then figure out sales. You make coordinated progress across the board. The 30-day horizon makes any imbalances visible — and addressable — before they become serious.</p><h4>Sprint 2 (Days 31–60): First Customers, First Revenue</h4><p>Sprint 2 is where money changes hands. This is the sprint that separates founders who are building businesses from those who are building projects.</p><p>You’ve spent 30 days understanding the pain and validating willingness to pay. Now it’s time to convert those commitments into actual recurring revenue. The emphasis on “recurring” is deliberate and important.</p><p><strong>Week 5–6: Convert design partners to paying customers. </strong>If you did Sprint 1 well, you have at least three people who’ve committed interest. Now you’re building (or finishing) the minimum viable product and putting it in their hands — for money. Not free trials. Not extended pilots. Paid engagements from day one, even if the price is introductory.</p><p>Why charge from the start? Because free users give you feedback. Paying customers give you validation. There’s a fundamental difference between someone who says “this is interesting” and someone who opens their budget. The act of paying forces a customer to assess your value honestly. And it forces you to deliver value honestly.</p><p><strong>Week 6–7: Set up recurring billing from day one. </strong>This is a small operational detail that has enormous strategic implications. Structure your very first contracts as subscriptions — monthly or annual, depending on your market. The founders who start with project-based pricing or one-off fees create a habit that’s incredibly difficult to break later. And when you eventually sit down with investors, the difference between genuine Annual Recurring Revenue and a creative repackaging of one-off deals is something every experienced VC will spot instantly.</p><p><strong>Week 7–8: Tighten the feedback loop. </strong>Your first paying customers are the most valuable source of intelligence your company will ever have. They’re telling you, through their behaviour and their words, exactly what your product needs to become. Build a tight rhythm of weekly check-ins. Understand what’s delighting them and what’s frustrating them. Ship improvements in days, not months. This rapid iteration cycle is what transforms an early product into something customers genuinely rely on.</p><p><strong>Sprint 2 deliverables: </strong>First paying customers on recurring contracts. Billing infrastructure operational. Weekly customer feedback rhythm established. A clear understanding of your early unit economics — what does it cost to acquire and serve each customer, and what are they paying you?</p><h4>The Revenue Quality Question</h4><p>As you start generating revenue, pay attention to its quality from the very beginning. Revenue is the market’s way of telling you that you’re onto something real — but not all revenue tells the same story.</p><p>Recurring revenue from a defined customer segment, on structured contracts, with clear terms — that’s the foundation of a scalable business. One-off project fees, customisation charges, or services revenue dressed up as product income — that’s a different story entirely. Both put money in the bank, but they signal very different futures.</p><p>At this stage, don’t worry about optimising revenue. Worry about understanding it. Where is the money coming from? Will it recur? Are these the kinds of customers you want a hundred more of? The answers to these questions will shape everything you do in Sprint 3.</p><h4>Sprint 3 (Days 61–90): From Customers to Engine</h4><p>Sprint 3 is where individual customer wins become a repeatable process. This is the sprint where you cross the €10K MRR threshold — and more importantly, where you prove that you can keep growing beyond it.</p><p>The difference between a company with a few customers and a company with a growth engine is systems. In Sprint 3, you’re building the systems that turn early success into compounding momentum.</p><p><strong>Week 9–10: Turn customer success into acquisition fuel. </strong>Your first customers are now your most powerful sales tool. Work with them to create case studies, testimonials, or reference stories that you can use in your next ten sales conversations. The best early-stage growth often comes not from clever marketing but from genuinely delighted customers who become advocates.</p><p>This is the compounding effect in action. A startup with five happy customers who actively refer others has more genuine momentum than one with a thousand free trial users who signed up and forgot. Mass is about how deeply you’ve embedded yourself with a specific customer segment, how essential you’ve become to their operations. Velocity is about directed progress — moving consistently towards product-market fit rather than sprinting in circles. Momentum is what happens when those two forces multiply.</p><p><strong>Week 10–11: Refine your messaging based on evidence. </strong>After two months of real customer conversations and actual sales, you now know what resonates and what doesn’t. You know which problem descriptions make prospects lean forward and which ones get polite nods. Rebuild your outreach, your website copy, and your pitch around the language your customers actually use to describe their pain and your value. This isn’t marketing theory — it’s marketing built on commercial evidence.</p><p><strong>Week 11–12: Systematise your sales process. </strong>By now you’ve closed enough deals to see patterns. How did prospects find you? What questions did they ask? What objections came up? How long was the typical sales cycle? Document this. Build a simple, repeatable process that someone other than you could follow. You’re not trying to build a complete sales machine yet — you’re trying to prove that the process can work without depending entirely on the founder’s personal network and charisma.</p><p><strong>Sprint 3 deliverables: </strong>€10K+ MRR achieved. At least 2 customer case studies or reference stories. A documented sales process with clear stages. Refined messaging grounded in real customer language. A pipeline of qualified prospects for month four and beyond.</p><h3>The Sprint Review Template</h3><p>At the end of each 30-day sprint, sit down with your co-founder or your team and complete this exercise. It takes thirty minutes and it’s worth more than any two-day strategy offsite.</p><p>Create a simple one-page document with six rows — one for each pillar of your business. For each pillar, answer three questions: What did we accomplish this sprint? What is the single most important milestone for the next sprint? And what does “done” look like?</p><ul><li><strong>Technology: </strong>What did we ship? What’s the most important thing to ship next? What does done look like?</li><li><strong>Product: </strong>What customer problems did we solve? What’s the biggest gap between what customers need and what we deliver? What does closing that gap look like?</li><li><strong>Commercials: </strong>How many customers did we acquire? What’s our revenue? What’s the pipeline for next month?</li><li><strong>People: </strong>Do we have the right capabilities? What’s the most critical hire or skill gap? When do we need it filled?</li><li><strong>Finance: </strong>What’s our burn rate? What’s our runway? Are our unit economics improving?</li><li><strong>Operations: </strong>What processes supported us well? What broke? What do we need in place before we double in size?</li></ul><p>Look at the balance across all six. Are three pillars charging ahead while three are stagnant? If so, your next sprint’s priorities need to shift. The goal isn’t to be world-class in one area. It’s to make steady, coordinated progress across all the areas that matter.</p><p>Be honest about capacity. If you’ve listed six ambitious milestones but only have three people, something has to give. Better to hit four milestones than miss six.</p><h3>What €10K MRR Unlocks</h3><p>When you cross this threshold, several things shift simultaneously.</p><p><strong>Your investor conversations transform.</strong> You’re no longer pitching a hypothesis; you’re presenting a business with paying customers, a documented sales process, and evidence of repeatable demand. The best investors I know — the ones you actually want on your cap table — get excited by clean, honest revenue metrics that demonstrate a repeatable model. €10K MRR gives you exactly that.</p><p><strong>Your own decision-making improves. </strong>With real revenue comes real data. You know your customer acquisition cost. You know your sales cycle. You know which segments convert and which don’t. Every strategic decision from here forward is grounded in evidence rather than intuition. That’s an enormous competitive advantage.</p><p><strong>And the compounding accelerates.</strong> The systems you built in Sprint 3 — the case studies, the refined messaging, the documented process — they continue to work for you. Each month’s growth builds on the previous month’s infrastructure. This is what momentum feels like: the compound effect of positioning and directed progress, where each win makes the next win easier.</p><p>The founders who reach €10K MRR in 90 days don’t then slow down. They speed up. Because they’ve built something more valuable than revenue — they’ve built the engine that generates it.</p><h3>The 90-Day Choice</h3><p>Every founder reading this is somewhere on this journey. Maybe you’re pre-revenue, still building in isolation, telling yourself that success is just around the corner once you finish that next feature. Maybe you’ve had a few customer conversations but haven’t yet mustered the courage to put a price on your solution. Maybe you have some revenue but it’s project-based, inconsistent, and you know it doesn’t tell the story you need it to.</p><p>Wherever you are, the next 90 days can change your trajectory.</p><p>Not because this playbook contains secret knowledge. There’s nothing here that the best founders don’t already know instinctively. The power is in the structure — the discipline of 30-day sprints, the honesty of concrete deliverables, the compounding effect of focused execution across every dimension of your business.</p><p>The founders I most want to back aren’t the ones with the most impressive strategies or the most elaborate plans. They’re the ones who can tell me exactly what they’re shipping on Tuesday. Who know their numbers cold. Who’ve talked to more customers this week than they’ve attended networking events.</p><p>Ninety days. Three sprints. €10K MRR. The system is simple. The execution is hard. And the results are worth every uncomfortable conversation, every imperfect product launch, and every moment of doubt along the way.</p><p>The market is waiting to tell you whether you’re onto something real. All you have to do is ask — and be ready to listen.</p><p><em>DC is a Venture Partner at </em><a href="http://www.svv.ai/"><em>SVV (Sure Valley Ventures)</em></a><em>, an AI-specialist VC firm, and a four-time founder. He writes regularly about the patterns that separate the companies that make it from those that don’t.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68505847a09f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Premature Acceleration: What Breaks Inside a Startup That Scales Before It’s Ready]]></title>
            <link>https://medium.com/@dcirl/premature-acceleration-what-breaks-inside-a-startup-that-scales-before-its-ready-cbea82cb7206?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbea82cb7206</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[accelerator]]></category>
            <category><![CDATA[incubator]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 21:43:04 GMT</pubDate>
            <atom:updated>2026-02-23T21:43:04.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*JD86PmBldqwy5_BEE57Vgg.png" /></figure><p><em>Acceleration is an amplifier. When you amplify a startup that hasn’t validated its foundations, you don’t waste time — you create compounding damage across every dimension of the business.</em></p><p>Last year, I watched a founder make what looked like the smartest decision of her startup journey. She’d built a promising product, secured a handful of early customers, and landed a place on a well-known ‘accelerator’ programme. Within weeks, she’d hired three engineers, committed to a demo day pitch, expanded her roadmap to target enterprise customers, and started preparing investor materials for a seed round.</p><p>Six months later, she was laying off the engineers, pivoting back to her original market, and scrambling to explain to her early customers why features they’d been promised had never materialised. The runway she’d burned couldn’t be recovered. The credibility she’d damaged with investors would take years to rebuild. And the worst part? The programme she’d joined wasn’t actually an accelerator at all. It was an incubator wearing an accelerator’s clothing — a programme designed for a company at a completely different stage, pushing her to scale before she’d validated the foundations that scaling depends on.</p><p>She’s not an outlier. Across Europe, I’m seeing this pattern with alarming regularity: startups that enter acceleration mode — either through a formal programme or self-imposed ambition — before the underlying business is ready for it. And the damage isn’t just wasted time. It’s structural. It breaks things inside the company that are extraordinarily difficult to repair.</p><p>Here’s the thesis I want to explore: <strong>acceleration is an amplifier, not a fixer.</strong> It takes whatever exists inside your startup and makes it louder. If your product-market fit is strong, acceleration makes it stronger. If your unit economics work, acceleration scales them. But if your foundations are cracked — if you haven’t validated your assumptions, haven’t found real customers, haven’t understood your own economics — acceleration doesn’t fix those cracks. It turns them into fault lines.</p><h3>The Programme Problem: When ‘Accelerator’ Doesn’t Mean What You Think</h3><p>Before we get into the internal mechanics of what breaks, we need to talk about one of the primary causes of premature acceleration: the wholesale mislabelling of startup support programmes.</p><p>I’ve written extensively about this in <a href="https://medium.com/@dcirl/stop-calling-it-an-accelerator-f7cd2c491028"><em>Stop Calling It an Accelerator</em>,</a> and the problem has only intensified since. The word ‘accelerator’ has become a catch-all term for any startup programme. University enterprise schemes call themselves accelerators. Government grant programmes brand themselves as accelerators. Corporate innovation initiatives, co-working spaces with occasional workshops, six-month mentoring circles — accelerators, all of them, apparently.</p><p>This isn’t semantic pedantry. It’s a structural problem in our ecosystem that directly causes the damage I’m about to describe. Because the distinction between incubation and acceleration isn’t just about programme design — it’s about what stage of company the programme is engineered for, and what it expects you to arrive with.</p><p>A true accelerator exists to do one thing: accelerate traction. Revenue. Customers. Growth. It assumes you arrive with a validated product and a customer base. The 12–16 week timeline, the demo day pressure, the intensive one-on-one mentorship — all of it is engineered around the premise that you know what works and need help doing more of it faster.</p><p>An incubator, by contrast, exists to help you figure out what works in the first place. It provides protected time for exploration, group learning for foundational skills, and mentorship designed to navigate early-stage uncertainty. Both are valuable. Neither should pretend to be the other.</p><p>The danger emerges when a founder who is still exploring problem-solution fit — still working out who their customer is, still iterating on their value proposition — joins a programme that operates on accelerator timelines and expectations. They face pressure to build roadmaps when they should be running experiments. They’re encouraged to hire when they should be doing customer discovery. They’re pushed towards a demo day pitch when they don’t yet have anything validated to demonstrate.</p><p>And here’s the cruelest part: the founder experiences all the <em>pressure</em> of acceleration without receiving any of the actual <em>acceleration</em>. They burn runway at an accelerated rate. They make commitments at an accelerated pace. They accumulate what I call <strong>‘acceleration debt’</strong> — a compound interest of premature decisions that becomes progressively harder to unwind. But their underlying business doesn’t actually accelerate, because you can’t accelerate something that doesn’t yet have direction.</p><p>This connects directly to a distinction I’ve explored before: the difference between motion and momentum. Acceleration without validated foundations doesn’t create momentum. It creates faster motion. And as any physicist will tell you, motion without direction is just vibration.</p><h3>Two Paths to Premature Acceleration</h3><p>Startups don’t end up accelerating prematurely by accident. They get there through one of two paths — and understanding which path you’re on matters, because the remedies are different.</p><h4>Path One: The Ecosystem Push</h4><p>This is the programme-induced version I’ve just described. A founder joins what they believe is an accelerator, and the programme’s structure — its timelines, its expectations, its demo day culmination — pushes them into scaling mode before they’re ready. The programme itself becomes the forcing function for premature acceleration.</p><p>The tragedy is that these founders often made a perfectly rational decision. The programme had a good reputation. The brand looked impressive. The application process was competitive. Everything signalled legitimacy. What the founder couldn’t see — because the ecosystem’s labelling is so broken — was that the programme was designed for companies at a fundamentally different stage.</p><p>Having helped design and deliver more than a dozen accelerator and incubator programmes globally, I can tell you that the mismatch is often invisible until you’re inside it. The same buzzwords appear in every programme’s marketing. The same vague promises about ‘mentorship’ and ‘networks’ and ‘growth support’ adorn every website. Without specific, probing questions about programme structure, mentor experience, and stage-appropriate design, founders are essentially making one of the most consequential decisions of their startup’s life based on marketing copy.</p><h4>Path Two: The Founder’s Ambition</h4><p>The second path is self-imposed, and it’s driven by one of the most admirable qualities a founder can have: ambition. The founder sees what successful startups look like at scale — the team sizes, the revenue numbers, the market positioning — and begins mimicking those behaviours before the business justifies them.</p><p>They hire a VP of Sales before they’ve personally closed ten deals. They build an engineering team before they’ve validated what to build. They expand into new markets before dominating one. They raise a large seed round because they can, not because their milestones require it.</p><p>This path is more insidious because it feels like ambition. It looks like confidence. From the outside, it <em>appears</em> like a founder who’s thinking big. But there’s a critical difference between thinking big and acting big. Thinking big means having a vision for where you’re going. Acting big before you’ve earned it means spending resources you haven’t validated, on a trajectory you haven’t confirmed, at a pace your foundations can’t support.</p><p>Both paths lead to the same destination: a startup operating in acceleration mode without the validated foundations that acceleration depends on. And the internal damage follows a depressingly predictable pattern.</p><h3>The Five Internal Fractures</h3><p>When a startup accelerates before it’s ready, the damage doesn’t appear in one dramatic failure. It manifests as a series of internal fractures — each one weakening the structure, each one making the others worse. Here’s what breaks, and why.</p><h4>Fracture 1: Product — Scaling Unvalidated Assumptions</h4><p>The first thing that breaks is the product itself. When you accelerate before achieving genuine product-market fit, you don’t just build the wrong features — you <em>cement</em> the wrong features into your architecture, your roadmap, and your customer expectations.</p><p>In incubation mode, building the wrong thing is cheap. You’re running experiments. You’re testing hypotheses. You can pivot quickly because your commitments are small. But in acceleration mode, building the wrong thing is catastrophic. You’ve hired engineers to build out a roadmap based on unvalidated assumptions. You’ve made promises to customers based on a product vision that hasn’t been tested. You’ve invested months of development time in features that were designed for a customer you haven’t properly understood.</p><p>I’ve seen this play out in programmes that push founders to build investor-ready roadmaps and hire engineering teams during a 12-week programme. The founder arrives still exploring which customer segment to target, and leaves with a fully staffed engineering team building towards a roadmap that was created under demo day pressure rather than customer insight. Six months later, they’re rebuilding from scratch — but now with payroll obligations and technical debt they didn’t have before.</p><h4>Fracture 2: Revenue — The Junk Metrics Trap</h4><p>Premature acceleration creates intense pressure to show revenue growth. And when that pressure meets an unvalidated business, it produces what I call ‘junk revenue’ — income that looks impressive on a pitch deck but signals nothing about sustainable commercial viability.</p><p>I’ve written before about founders who conflate Annual Recurring Revenue with Annual Run Rate, or who include project revenue, pilot charges, and services income in their ARR projections. Premature acceleration turbocharges this problem. The demo day timeline creates pressure to show numbers. Any numbers. Founders start closing deals they shouldn’t close — customers who aren’t in their target market, pricing that isn’t sustainable, contracts that require bespoke work rather than scalable product delivery.</p><p>The result is revenue that actually makes the business <em>harder</em> to scale, not easier. Each non-standard customer becomes a support burden. Each custom deal fragments the product. Each pilot that converts at a discounted rate establishes a pricing precedent that’s difficult to undo. International investors now focus intensely on revenue composition, and they can spot junk revenue from across a boardroom table. The very metrics you created under acceleration pressure become the red flags that keep serious investors away.</p><h4>Fracture 3: Team — Building the Wrong Organisation</h4><p>Perhaps the most painful fracture is organisational. When you hire for scale before you’ve found fit, you build the wrong team — and unwinding that is both expensive and emotionally devastating.</p><p>Pre-product-market-fit, you need generalists who can wear multiple hats, tolerate ambiguity, and pivot without existential crisis. Post-product-market-fit, you need specialists who can execute with precision in well-defined roles. These are fundamentally different people with fundamentally different skills and motivations.</p><p>A startup that accelerates prematurely typically hires specialists too early. They recruit a Head of Enterprise Sales when they haven’t validated their SMB playbook. They hire dedicated product managers when the founders should still be the ones talking to every customer. They bring on marketing specialists when the messaging hasn’t been tested.</p><p>The specialists aren’t the problem — they’re often excellent at what they do. The problem is that what they do isn’t what the company needs yet. And when the inevitable course correction comes, you’re not just changing strategy. You’re making people redundant. You’re damaging the culture you’ve built. You’re burning through the trust that early employees placed in your vision.</p><h4>Fracture 4: Economics — The Death Spiral</h4><p>Unit economics are the vital signs of a startup. And premature acceleration is like running a marathon before your doctor has cleared you — you’ll get data, but it will tell you more about the damage you’re doing than about your actual fitness.</p><p>When you start spending to acquire customers before you understand your customer acquisition cost, lifetime value, and the ratio between them, you don’t learn what works — you learn what you can buy. The difference matters enormously. Organic traction tells you something real about product-market fit. Paid traction at an unvalidated stage tells you only that you can exchange money for attention.</p><p>The death spiral works like this: premature acceleration increases burn rate. Higher burn rate creates pressure to show growth to justify the burn. The fastest way to show growth is to spend on acquisition. Acquisition spending without validated economics produces customers with negative unit economics. Negative unit economics require more funding to sustain. More funding creates more pressure to show growth. And the cycle continues until the money runs out.</p><p>I’ve seen this pattern destroy companies that had genuinely good products. The product wasn’t the problem. The timing of the investment in growth was.</p><h4>Fracture 5: Founder Psychology — The Identity Trap</h4><p>This is the fracture nobody talks about, but it might be the most damaging of all.</p><p>Building a startup requires two fundamentally different psychological modes. In exploration mode, you’re comfortable with uncertainty. You’re hypothesis-driven. You’re willing to be wrong, to kill ideas, to pivot based on evidence. In scaling mode, you’re committed. You’re execution-driven. You’re rallying a team around a clear direction and executing with conviction.</p><p>Premature acceleration forces founders to shift from explorer to scaler before the exploration is complete. And once you’ve made that identity shift — once you’ve hired a team, committed to a roadmap, pitched investors on a specific vision — it becomes psychologically excruciating to go back.</p><p>Going back to exploration mode means admitting that the direction you committed to was premature. It means telling your team that the plan has changed. It means facing investors with a story about course correction rather than progress. Most founders would rather double down on a failing direction than endure that conversation. And that’s how premature acceleration becomes permanent misdirection.</p><p>The ecosystem reinforces this trap. Accelerator programmes celebrate conviction. Demo days reward polished narratives, not honest uncertainty. The founder who stands up and says ‘we’re still figuring this out’ doesn’t win the pitch competition. So founders perform certainty they don’t feel, and eventually the performance becomes indistinguishable from actual belief — including to themselves.</p><h3>The Compounding Cascade</h3><p>These five fractures don’t exist in isolation. They feed each other in a cascading failure that accelerates the very damage it creates.</p><p>Bad revenue masks a bad product. When you’re closing deals through sheer founder hustle and custom promises, you never get the clean signal about whether your product actually works at scale. The wrong team can’t course-correct, because the specialists you hired are executing the original plan — that’s exactly what specialists do. Broken economics justify more fundraising, which increases the pressure to scale, which deepens every other fracture.</p><p>And sitting at the centre of this cascade is the founder, trapped in a scaling identity that makes it impossible to do what the business actually needs: stop, reassess, and potentially go backwards before going forwards.</p><p>I’ve written before about zombie startups — companies that are technically alive but creating no real value, shuffling through the ecosystem consuming resources without generating meaningful outcomes. Many zombie startups didn’t start as zombies. They started as promising companies with real potential. What turned them into the walking dead was premature acceleration that damaged their internal mechanics so thoroughly that recovery became nearly impossible.</p><p>The cascade creates a company that’s too committed to pivot, too damaged to scale, and too funded to die gracefully. It’s the worst possible outcome — worse than failure, because at least failure frees up the founder’s time and the investor’s capital for something that might actually work.</p><h3>The Readiness Diagnostic: Before You Accelerate</h3><p>If you’re a founder considering entering acceleration mode — whether through a formal programme or your own strategic decision to scale — you owe it to yourself and your business to answer these questions with brutal honesty.</p><h3>Questions About Your Business</h3><p><strong>Do you have paying customers?</strong> Not pilots. Not letters of intent. Not ‘strong interest.’ Actual revenue from customers who chose to pay you money for your product or service. If the answer is no, you need incubation, not acceleration.</p><p><strong>Do you know your unit economics from real data?</strong> Can you tell me your customer acquisition cost, lifetime value, and the ratio between them — calculated from actual transactions rather than projections? If these numbers are hypothetical, acceleration will turn hypothetical economics into real losses.</p><p><strong>Is your primary challenge discovery or scaling?</strong> Are you still figuring out exactly what to build and for whom? That’s incubation territory. Do you know what works and need help doing more of it faster? That’s genuine acceleration.</p><p><strong>Can you describe your ideal customer with painful specificity?</strong> Not a broad market segment. A specific person with a specific problem who buys your specific solution for a specific reason. If your customer description still uses words like ‘various’ or ‘multiple segments,’ you’re not ready to accelerate.</p><p><strong>Have you personally sold to at least ten customers?</strong> Not your co-founder. Not a salesperson. You. If you can’t sell your product yourself, you don’t yet understand your market well enough to build a scalable sales process.</p><h3>Questions About the Programme</h3><p>If you’re considering joining a programme that calls itself an accelerator, these questions will help you determine whether it actually is one — and whether it’s designed for a company at your stage.</p><p><strong>1.What stage are the other companies in the cohort?</strong> If the cohort includes both pre-idea explorers and companies with established revenue, the programme hasn’t thought carefully about stage-appropriate support. You want a cohort of peers facing similar challenges — not similar exploration challenges, but similar <em>scaling</em> challenges.</p><p><strong>2.How much time is spent in group sessions versus one-on-one work?</strong> If the schedule is primarily filled with group workshops, cohort sessions, and standardised curriculum, you’re looking at an incubator regardless of what it calls itself. True acceleration requires intensive one-on-one engagement because every scaling company faces unique challenges.</p><p><strong>3.How many of the mentors have founded and scaled companies themselves?</strong> This matters enormously. At the scaling stage, you need mentors with scar tissue from building companies, not consultants or academics with theoretical knowledge. If the answer is ‘few’ or ‘none,’ you’re in an incubator.</p><p><strong>4.What does the programme measure as success?</strong> Accelerators should measure revenue growth, customer acquisition, and market traction. If the programme celebrates completing workshops, attending events, or ‘engaging with the ecosystem,’ the metrics don’t match the acceleration promise.</p><p><strong>5.What equity are they taking, and what are you getting for it?</strong> Programmes taking accelerator-level equity (5–10%) should deliver accelerator-level value. If they’re taking that equity for incubator-level support — classroom sessions, generic mentorship, and a logo for your pitch deck — you’re overpaying dramatically.</p><p><strong>6.Can you speak to alumni at a similar stage to yours?</strong> This is the single most revealing question. Talk to founders who entered the programme at roughly your stage and ask them directly: did your traction meaningfully change during the programme? If they talk about the community, the network, and the experience but can’t point to concrete commercial progress, you have your answer.</p><h3>The Counterintuitive Truth</h3><p>Here’s what I wish more founders understood: the fastest path to sustainable growth is almost never the most direct one. Slowing down to validate your foundations — to truly understand your customer, prove your economics, confirm your product-market fit — isn’t cautious. It’s strategic. It’s the difference between building on bedrock and building on sand.</p><p>I’ve watched companies that took eighteen months to incubate properly and then accelerated to €1M ARR in three months. I’ve also watched companies that jumped straight to acceleration and spent two years going nowhere — or worse, going somewhere they couldn’t sustain.</p><p>The best acceleration is the one you’ve earned. You earn it by doing the unglamorous work of exploration, validation, and honest self-assessment. You earn it by being ruthlessly clear about what stage you’re actually at — not what stage you wish you were at, or what stage a programme’s marketing material assumes you’re at.</p><p>And you earn it by understanding that acceleration and incubation are both essential phases of building a company. Neither is superior. Neither is a shortcut. But confusing them — or having them confused for you by a mislabelled programme — can inflict damage that takes years to repair.</p><p>Joining a prestigious programme won’t make you ready for acceleration any more than entering a marathon will make you a runner. Get ready first. Then accelerate. The difference between the two approaches isn’t speed — it’s survival.</p><p><em>DC is a venture partner at </em><a href="http://www.svv.ai/"><em>SVV</em></a><em>, an AI-specialist VC firm investing in early-stage AI companies across the UK &amp; Ireland. He writes about entrepreneurship, AI, and the realities of building companies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbea82cb7206" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orphaned Startups: The Saddest Crisis in Venture Capital That Nobody’s Solving]]></title>
            <link>https://medium.com/@dcirl/orphaned-startups-the-saddest-crisis-in-venture-capital-that-nobodys-solving-0971fb4cae2d?source=rss-17bcd27bce4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0971fb4cae2d</guid>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[DC]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 21:17:53 GMT</pubDate>
            <atom:updated>2026-02-19T21:17:53.040Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Thousands of startups are stranded between Seed and Series A with great products, real revenue, and absolutely nowhere to go. Here’s what’s actually happening — and what founders can do about it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*GWCwUfW-lEEBCrlnSr6ztA@2x.png" /></figure><p><em>Inspired by a brilliant post from Judie Alvarez, whose take on “Orphaned Startups” sparked a conversation the entire ecosystem needs to have.</em></p><p><a href="https://www.linkedin.com/in/juditalvarez/">Judie Alvarez </a>recently posted something on LinkedIn that stopped me mid-scroll. She highlighted a growing phenomenon called “<a href="https://www.linkedin.com/posts/juditalvarez_there-is-a-new-term-that-is-getting-popular-share-7428847434149310464-oKs0?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAO83kAB3d3gSx__ow3seaPWDWwAuAnPIjQ">Orphaned Startups</a>” — companies stuck between Seed and Series A with nowhere to go. Great products. €500K to €1M in revenue. Founders who still have some passion left, but are watching it drain away week by week.</p><p>She described founders throwing company hoodies in the river in Berlin. Burning them in Copenhagen. Crying over them in London on their last day out. If you’ve been in this ecosystem long enough, you don’t just recognise these stories — you can name the founders.</p><p>What Judie identified isn’t just a catchy term. It’s the defining crisis of the current venture landscape. And having sat on both sides of the table — as a founder who built four companies and as a VC partner who now reviews hundreds of startups a year — I want to unpack why this is happening, why it’s getting worse, and what founders can actually do about it.</p><h3>The Series A Market Has Fundamentally Changed</h3><p>Before we get into the orphan crisis, we need to talk about why the Seed-to-Series A gap has become a chasm. Because too many founders are still operating with a mental model of Series A that hasn’t existed for three years.</p><p><strong>The minimum revenue bar has moved — dramatically.</strong> The €1M ARR threshold that used to unlock Series A doors? That’s now the absolute floor, not the ceiling, and even at €1M you’ll really be fighting for attention. The real competitive threshold for a strong Series A in 2025 sits between €2M and €5M ARR. Companies are raising at 2–3x higher ARR levels than during the boom years. And it’s not just top-line revenue that matters — investors now demand proof of a repeatable sales motion, net revenue retention above 100%, CAC payback under 12 months, and a burn multiple below 2.5x. The “raise on a great deck and a compelling narrative” era is over. Series A investors invest in traction and metrics, not vision and potential.</p><p><strong>The quality bar has risen alongside the revenue bar.</strong> It’s no longer enough to show growth. Investors now scrutinise the <em>quality</em> of your growth. A company growing at 15% monthly with 120% net revenue retention now beats one growing at 25% monthly with 90% NRR. Churn kills Series A rounds faster than low revenue. Unit economics are a deal-breaker if they’re poor. By the time you sit down with a Series A investor, they expect to see 40–80+ paying customers, a proven sales playbook, and a clear path to €10M+ ARR within 18–24 months. That’s a fundamentally different ask than what most seed-stage founders planned for when they raised their first round.</p><h3>The Yellow Brick Road to America Doesn’t Exist</h3><p>Here’s a fantasy I encounter with alarming regularity from European founders: “We’ll just go raise in the US. The money’s bigger, the valuations are better, and American VCs understand scale.”</p><p>Let me be blunt: this is a myth, and a dangerous one. The mythical Yellow Brick Road to American funding doesn’t lead to a pot of gold. It leads to months of wasted time, burned cash, and a bruised ego.</p><p>Yes, US startups consistently raise 2–3x more than European counterparts across all stages. Yes, 70% of US venture capital now flows to megarounds of $100M+. But here’s what European founders don’t hear: that money isn’t flowing to foreign companies who fly into San Francisco for two weeks of meetings. It’s flowing to US-based companies with US customers, US traction, and US-based teams. The Silicon Valley venture capital market is as competitive as it is deep. Getting visibility as a European startup is extremely difficult, and you face a fundamental unasked question that every American VC is thinking: “Why aren’t you raising this round in your home market?”</p><p>The honest answer — that you couldn’t get it done at home — is the worst possible signal you can send to an investor anywhere in the world. If your home market’s investors, the ones who can most easily verify your claims and meet your customers, won’t fund you, why should someone 5,000 miles away take the risk?</p><p>The data backs this up. According to McKinsey’s analysis, European startups are 30% less likely to progress from seed to a successful outcome compared to US startups. But the solution isn’t to pretend you’re an American company. The companies that successfully raise from US investors do so because they’ve already built significant traction in their home market first. They cross the Atlantic from a position of strength, not desperation.</p><p>If you’re an orphaned European startup thinking America is your escape hatch, I’d urge you to reconsider. The Series A bar in the US is even higher than in Europe. The competition for attention is fiercer. And you’ll be burning through precious runway — flights, accommodation, legal fees for US entity setup, local hire costs — while your European competitors are using that same time and money to acquire customers. Fix the problem at home first. The US can wait. Your runway can’t.</p><h3>The Numbers Are Brutal — And Getting Worse</h3><p>Let’s start with the data, because the scale of this problem is staggering.</p><p>Series A shutdowns jumped 2.5x in 2025, moving from roughly 6% to 14% of all startup closures. These aren’t failed experiments or weekend projects. These are companies that made it through early validation, secured institutional investment, built real product — and still hit a wall. The SimpleClosure State of Startup Shutdowns report paints a picture of a correction that has moved unmistakably up-market. The companies dying now aren’t the ones that never got started. They’re the ones that got started, gained traction, and then ran out of road.</p><p>The seed-to-Series A pipeline has become a bottleneck of historic proportions. According to Crunchbase, for the 2022 cohort, only 20% of seed-funded companies have graduated beyond seed. Compare that with earlier vintages where graduation rates sat between 51% and 61%. The 2021 cohort — the companies that benefited from the peak of cheap capital — has seen only 36% progress to the next stage. More than 1,000 startups are getting orphaned each year, stranded between seed and Series A with nowhere to go.</p><p>And here’s the detail that should terrify every early-stage founder: Carta’s Q1 2025 data shows that bridge rounds now account for 46% of seed-stage financings. Nearly half. That’s not a bridge to somewhere — for most of these companies, it’s a bridge to nowhere. The data on bridge round outcomes is devastating: 70% of VC-backed exits in 2023 were below the total capital invested, often because companies that had previously raised bridge rounds had to accept lower valuations just to get acquired at all.</p><h3>How Orphaned Startups Are Created</h3><p>Here’s what most people get wrong about orphaned startups: they assume these are bad companies with bad founders. They’re not. Many of them are good companies with capable teams who made predictable mistakes that the ecosystem actively encouraged them to make.</p><h3>The Oversized Seed Trap</h3><p>The median seed raise in 2025 is €4M, with the top end stretching to €80M+ post-money valuations. But bigger rounds create bigger expectations. When you raise €5M at a €25M valuation, you’re implicitly promising a Series A story that justifies a €60–80M valuation. That means you need to show the kind of explosive, repeatable growth that very few seed-stage companies can deliver in 18–24 months.</p><p>I’ve watched companies raise €5M seeds and make modest progress, then struggle to attract Series A interest regardless of how much they’ve accomplished in absolute terms. Meanwhile, companies that raised €1.5M seeds and achieved strong product-market fit have gone on to raise €10M+ Series A rounds at excellent valuations. The difference isn’t just capital efficiency — it’s that smaller rounds force the kind of focus and discipline that produces the metrics Series A investors actually care about.</p><h3>The Product Perfection Trap</h3><p>The pattern that terrifies me most: founders who disappear into a cave for six, nine, twelve months to build the “perfect” product. They obsess over features, user experience, technical architecture — all important things. But they treat go-to-market as an afterthought, something you bolt on at the end. Then launch day arrives, they flip the switch, wait for customers to flood in, and… crickets.</p><p>You can’t expect to wake up one morning, decide “now it’s time for revenue,” and magically flip on a go-to-market engine. Building revenue capabilities — understanding your customer acquisition channels, refining your value proposition, learning to sell, iterating on pricing — is a muscle that takes time to develop. You can’t start exercising it on demo day and expect to run a marathon.</p><h3>The Motion-Not-Momentum Trap</h3><p>Many orphaned startups didn’t sit still. They were busy. They attended accelerators. They went to conferences. They took meetings. They “built relationships.” They measured success in meetings taken rather than revenue generated. They confused activity with progress and motion with momentum.</p><p>There’s a critical distinction between motion and momentum that most founders miss until it’s too late. Motion is mere activity and busyness. Momentum is directional, compounding progress. The Activity Theatre Trap — collecting accelerator logos, attending conferences, building advisory boards — is one of the most seductive forms of motion masquerading as momentum. Every hour spent in this theatre is an hour not spent acquiring customers.</p><h3>What the Orphanage Actually Looks Like</h3><p>As Judie rightly pointed out, investors aren’t the bad guys here. They have downside protection built into the terms. Liquidation preferences. Participating preferred stock. Board control. That’s how the game is structured. They’re protected. Founders, unfortunately, are not.</p><p>Here’s what actually happens when an orphaned startup reaches the end of its runway:</p><p><strong>The acquihire scenario.</strong> The most common outcome. A larger company — often a Series C or D startup that raised heavily during the ZIRP era — buys the assets and takes one to three people from the founding team. The purchase price is typically just enough to cover investor liquidation preferences. The founder? Walks away with basically nothing. The technology they spent years building gets absorbed into someone else’s product roadmap. Their vision dies in a corporate integration meeting.</p><p><strong>The zombie scenario.</strong> Some orphaned startups don’t die cleanly. They become what I call zombie startups — technically alive, but lacking any real life force or purpose. They shuffle through the ecosystem, consuming resources but creating no real value. They attend the same conferences year after year with the same pitch deck (just with updated dates). They have enough runway to survive but not enough drive to thrive. From an investor perspective, zombie startups are a special kind of hell. They tie up capital that could be deployed elsewhere and rarely deliver the returns that justify the investment.</p><p><strong>The quiet shutdown.</strong> The founder simply runs out of energy, money, or both. SimpleClosure’s data tells us that 60% of startups that fail don’t have enough capital left to return anything to investors. They just… stop. The Slack channels get archived. The domain expires. Another dream dissolves quietly while the ecosystem moves on to the next cohort of hopefuls.</p><h3>What Judie Got Absolutely Right</h3><p>Judie’s conclusion was as direct as it gets: <strong><em>customers are the only thing that saves you.</em></strong></p><p>Not a better deck. Not a warmer intro. Not another bridge round. Revenue.</p><p>She’s right. And having been on both sides of this conversation — sweating through my own fundraises as a founder, and now dissecting revenue quality as a VC — I want to add some texture to why this is true and what it means in practice.</p><p><strong>Revenue isn’t just money. It’s proof.</strong> When a customer pays you, they’re not being nice. They’re making a calculated decision that your solution is worth more than the money in their pocket. That’s the signal you need. Not vanity metrics, not social media buzz, not even user growth. Revenue tells you that you’ve crossed the chasm from “interesting idea” to “valuable business.”</p><p><strong>Revenue is leverage.</strong> As Judie said, it’s the only leverage you have against bad terms, bad timing, or bad luck. When you have customers paying you recurring, predictable revenue, you’re not entirely dependent on the next funding round. You can weather market downturns. You can make decisions based on what’s right for your business, not just what impresses investors. Startups with early revenue have options. Orphaned startups without revenue have none.</p><p><strong>Revenue attracts better investors.</strong> VCs don’t just want to see revenue because it proves your business model. We want to see it because it proves you understand how to create and capture value. It shows you’re a founder who can execute, not just envision. And when that revenue is clean, recurring, and high-quality? That’s when we get genuinely excited.</p><h3>But Here’s What Judie Didn’t Say: Not All Revenue Will Save You</h3><p>This is where I want to build on Judie’s argument, because it’s a nuance that trips up even the most revenue-focused founders.</p><p>International investors have developed a laser focus on revenue quality. Not just revenue — but what it’s actually made up of. Gone are the days when you could pad your numbers with project revenue, pilot charges, services revenue, integration fees, and one-off consultancy work. Most VCs worth their salt now strip all of that out.</p><p>I sat through a pitch recently where the founder proudly announced “€2.4 million in revenue.” Impressive, right? Then I asked three questions: How much of that is recurring? How much is project-based? How much came from a single customer? The answers — €340,000 recurring, €1.6 million from integration projects, and €460,000 from a pilot that hadn’t renewed — didn’t just deflate the number. They fundamentally changed what the company was worth. In about ninety seconds, a “€2.4 million revenue company” became a “€340,000 ARR company with some project work.”</p><p>If you’re an orphaned startup with €500K–€1M in revenue, the first question you need to ask yourself isn’t “how do I raise my Series A?” It’s “what is my revenue actually worth in the eyes of the investors I’m trying to reach?”</p><h3>The Orphan’s Survival Playbook</h3><p>If you recognise your startup in this piece — stuck between Seed and Series A, revenue that’s real but not quite enough, runway that’s measured in months not years — here’s what I’d tell you if you were sitting across the table from me.</p><p><strong>1. Stop everything that isn’t directly generating or protecting revenue.</strong> That conference you’re planning to attend? Unless you have five confirmed meetings with potential customers who have budget authority and a pain point you solve, don’t go. That feature your engineering team wants to build? Unless a paying customer has asked for it and will expand their contract when it ships, don’t build it. Every hour and every euro needs to be ruthlessly allocated to activities that drive revenue. This isn’t forever. This is survival mode.</p><p><strong>2. Audit your revenue quality immediately.</strong> Break your revenue into categories: recurring subscription revenue, project-based revenue, services revenue, and one-off payments. Be honest about what each category represents. Then focus all your energy on growing the recurring bucket. That’s the only number that matters for your Series A story.</p><p><strong>3. Narrow your focus, don’t widen it.</strong> When startups feel the squeeze, the instinct is to chase every possible customer segment and revenue stream. This is exactly backwards. The magic happens when you streamline every decision around a single, crystal-clear target: one specific customer with one specific pain point that you’re going to solve better than anyone else. Dominate a niche before you try to expand.</p><p><strong>4. Read your damn terms.</strong> Judie was right to emphasise this. If you don’t understand your liquidation preferences, your anti-dilution provisions, and your board control provisions, you need to understand them now. Not when you’re negotiating an acquihire from a position of zero leverage. Right now. Know exactly where you stand so you can make informed decisions about your company’s future.</p><p><strong>5. Consider whether a bridge round is really the answer.</strong> With 46% of seed financings now being bridge rounds, the temptation is obvious. But the data is clear: most bridge rounds delay the inevitable rather than changing the outcome. Before you raise a bridge, ask yourself honestly: what will be fundamentally different in 6–12 months? If the answer is “more of the same but with more time,” the bridge won’t save you. If the answer is “We’ll have 3x the recurring revenue because we’ve identified a repeatable sales motion,” then it might be worth it.</p><p><strong>6. Move faster than you think is possible.</strong> In the AI era, the window for establishing dominance has compressed dramatically. Companies are reaching €1M ARR in 6–9 months. If you’re an orphaned startup that’s been operating for two or three years, the market isn’t going to wait for you to figure things out. Velocity isn’t just a nice-to-have — it’s the pre-revenue and early-revenue founder’s best friend because it signals to investors that you can execute.</p><h3>What the Ecosystem Needs to Change</h3><p>The orphaned startup crisis isn’t just a founder problem. It’s a systemic failure that the ecosystem needs to address.</p><p>The explosion of micro-VCs, accelerators, and “spray and pray” seed investing created thousands more funded startups, but the number of legitimate Series A investors hasn’t grown proportionally. We funded companies before they were ready, encouraged them to raise more than they needed, and then expressed surprise when they couldn’t clear a Series A bar that has risen significantly since 2021.</p><p>Meanwhile, 70% of venture capital now flows to megarounds of €100M+, mostly into AI companies. Seed deals are declining in number. The market has become a barbell — either you’re commanding premium terms with AI positioning and explosive traction, or you’re fighting for scraps. There is precious little in between, and that’s exactly where orphaned startups live.</p><p>We need better stage-appropriate support. Too many startup programmes are mislabelled — calling themselves accelerators when they’re actually incubators, offering standardised curriculum to companies that need personalised scaling support. Orphaned startups don’t need another pitch deck workshop. They need intensive, hands-on help with go-to-market execution, revenue quality improvement, and honest assessments of whether their business model can actually scale.</p><p>We need more honest conversations between investors and founders about what Series A readiness actually requires. The old €1M ARR threshold that used to unlock Series A doors? It’s necessary but no longer sufficient. Investors now want to see capital efficiency, clean unit economics, low churn, and a repeatable sales motion. Founders deserve to know this before they spend 18 months optimising for the wrong metrics.</p><h3>The Uncomfortable Truth</h3><p>Judie ended her post with a challenge: “Get customers like your life depends on it. Because it does at every level.”</p><p>She’s right. And I’d add this: the era of easy money has ended. The era of earned credibility has begun. Pre-revenue fundraising hasn’t just gotten harder — for many companies, it’s become nearly impossible outside of exceptional circumstances. The founders who succeed are the ones who treat their revenue not as an afterthought but as the central proof point their entire business is built around.</p><p>If you’re an orphaned startup reading this, I know the situation feels hopeless. It’s not. But the path forward isn’t another bridge round, another accelerator programme, or another redesigned pitch deck. The path forward is customers. Real ones. Paying ones. Ones who renew.</p><p>Because as Judie so perfectly put it: revenue is the only thing that protects you when everything else falls apart.</p><p><strong>And right now, a lot is falling apart.</strong></p><p>— — —</p><p><em>DC is a Venture Partner at </em><a href="http://www.svv.ai/"><em>SVV,</em></a><em> an AI-specialist VC firm investing in early-stage companies across the UK &amp; Ireland. A former startup founder who built four companies, he writes about startup velocity, fundraising strategy, and ecosystem architecture.</em></p><p><em>Full credit to Judie Alvarez for bringing the “Orphaned Startups” conversation to the forefront and for saying what the ecosystem needs to hear. Follow her for more unflinching takes on the realities of startup life.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0971fb4cae2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>