<?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  Aaron Cort on Medium]]></title>
        <description><![CDATA[Stories by  Aaron Cort on Medium]]></description>
        <link>https://medium.com/@aaronjcort?source=rss-6165c6fc194d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-sBhzZyCB7ZnBfFYMrRYCw.jpeg</url>
            <title>Stories by  Aaron Cort on Medium</title>
            <link>https://medium.com/@aaronjcort?source=rss-6165c6fc194d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:52:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aaronjcort/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[Inside Un_prompted: Seven Lessons on Marketing & Growth When Agents Are the Customer]]></title>
            <link>https://medium.com/@aaronjcort/inside-un-prompted-seven-lessons-on-marketing-growth-when-agents-are-the-customer-9e2e2609dab1?source=rss-6165c6fc194d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e2e2609dab1</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[ Aaron Cort]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 12:28:17 GMT</pubDate>
            <atom:updated>2026-10-21T12:28:17.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zT3k7qNWtRa8mRPNmIVMA.png" /><figcaption><em>Un_prompted by Craft Ventures: seven lessons on marketing and growth when agents are the customer.</em></figcaption></figure><p>By <a href="https://www.craftventures.com/team/aaron-cort">Aaron Cort</a> and <a href="https://www.craftventures.com/team/caroline-brayson">Caroline Brayson</a></p><p><em>Originally published on the </em><a href="https://www.craftventures.com/articles/inside-un-prompted-seven-lessons-on-marketing-growth-when-agents-are-the-customer"><strong><em>Craft Ventures blog</em></strong></a><strong><em>.</em></strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpSXMH6HaA78%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpSXMH6HaA78&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpSXMH6HaA78%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c958b3a2a91df564422396b56e04ab8b/href">https://medium.com/media/c958b3a2a91df564422396b56e04ab8b/href</a></iframe><h3>Why we built Un_prompted</h3><p>At Craft, we spend a lot of our time inside our portfolio companies, working next to the teams doing the growth work. Over the last year, founders, marketers and growth leaders have all been asking the same question:</p><p><strong>How do you grow a company when you’re marketing to agents and humans at the same time?</strong></p><p>Agents now research, compare, shortlist, sign up for, and run products on someone’s behalf. People still decide, still own the relationships, and still set the bar for what’s good. The playbooks we’ve been building for the last decade assumed a human on the other side of every touchpoint. That’s no longer true, and the new playbooks are being written right now and are evolving in real time.</p><p>So Craft identified the people and products at the forefront — the founders and executives rewriting the playbooks and building the foundational tools in today’s stack — and brought the conversation to life at Shack15 in San Francisco. We brought together 19 founders and operators from Supabase, LinkedIn, ClickHouse, ElevenLabs, Anthropic, Apostra, ClickUp, Clay, WorkOS, HubSpot, Vercel, AWS, Braintrust, SpaceXAI, and Replit. Two keynotes, three panels, and two rounds of lightning talks.</p><p>We had more than 200 people in the room, and every attendee was intentionally selected. We created a forum where leaders and operators would share what’s actually working, not postulate or present repurposed slides. That’s what we got.</p><p>David Sacks, Partner at Craft Ventures, said it perfectly: “This AI boom has completely changed what we think is possible.”</p><h3>The day in seven takeaways</h3><p>We’ve written this up the way the day ran: one takeaway per session, in order, from the opening keynote to the final session. Over the next few weeks, we’ll release each full session plus an in-depth analysis — stay tuned to <a href="https://unprompted.craftventures.com/">unprompted.craftventures.com</a>.</p><p>1. <strong>Agents follow your best builders.</strong> Opening keynote: Ant Wilson with Michael Robinson.</p><p>2. <strong>Earn attention twice.</strong> The Execution panel, presented by LinkedIn.</p><p>3. <strong>Codify your taste.</strong> Lightning talks: performance marketing.</p><p>4. <strong>Lead by doing.</strong> The Workflows panel, powered by Clay.</p><p>5. <strong>Treat agents as a customer.</strong> The Systems panel, powered by HubSpot for Startups.</p><p>6. <strong>Give agents a front door.</strong> Lightning talks: developer marketing.</p><p>7. <strong>The math hasn’t changed.</strong> Closing keynote: Amjad Masad with David Sacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOkJ26jvE9ptwf00BusLgQ.png" /></figure><p><em>Alt text: The seven takeaways from Un_prompted in the order of the day, each with its session and speaker company logos.</em></p><h3>1. Agents follow your best builders</h3><p><em>Keynote 1: Ant Wilson (Co-Founder &amp; CTO, Supabase) with Michael Robinson (Partner, Craft Ventures)</em></p><p>The day opened with Supabase’s Ant Wilson and Craft Partner Michael Robinson, who led our Series C and subsequent investments in Supabase. Supabase never set out to market to agents, and that turned out to be the lesson. “All the work we did making Supabase easy for developers translated super well to agents,” said Ant. Years of tutorials and community content became training data: “the models just slurped it up.”</p><p>Ant’s framing was simple:</p><p><em>“If you just think of an agent as an elite-level software engineer, they look for the same things.”</em></p><p>Great docs. An API that can do anything the dashboard can. A fast path to the first “wow.” The team timed onboarding with a stopwatch: roughly 25 minutes to a first query on legacy cloud, about 40 seconds on Supabase, and now around three seconds with an agent.</p><p>Then came the best story of the morning. “Lovable integrated Supabase but didn’t tell us.” Thousands of databases a minute showed up, and the security team thought it was an attack. It was the moment the funnel changed, as Ant put it: “From signup to activation just disappeared. The agent comes in, signs up and immediately activates.”</p><p>The other lesson was about choosing the hard path. Early on, nobody would hand two founders in Singapore their production data, so Supabase hosted the databases itself. Ant’s advice: “do the hard thing because that’s eventually going to be your moat.” When anyone can generate a feature in an afternoon, the hard parts are the ones that last.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqNnFhsBYTI-1f2_ONEP0g.png" /><figcaption><em>Takeaway 1 from Keynote 1 (Supabase, Craft Ventures): time to first query is about 25 minutes on legacy cloud, versus 40 seconds on Supabase or 3 seconds with an agent.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Run the stopwatch test this week.</strong> Time your signup to first value twice: once yourself, once by handing it to an agent. Every place the agent gets stuck goes on the roadmap.</p><p>2. <strong>Close the API gap.</strong> List everything the dashboard can do that the API can’t. If an agent can’t do it programmatically, it can’t do it.</p><p>3. <strong>Treat community content as training data.</strong> Tutorials, examples, and answers written by real users are how models learn your product. Make them easy to read and easy to find.</p><p>4. <strong>Keep talking to users yourself.</strong> As Ant put it, “it’s really easy to build the wrong thing really quickly.”</p><h3>2. Earn attention twice</h3><p><em>Execution panel: Earning attention from agents · Presented by LinkedIn</em></p><p><em>Hilary Batsel (VP, Marketing, LinkedIn, moderator), Tanya Bragin (VP, Product &amp; Marketing, ClickHouse), Bridget Ferris (Partnerships, ElevenLabs)</em></p><p>If the first session was about how agents pick tools, the Execution panel was about how they pick vendors. Search used to give you a broad shelf. Now you get an answer, and it’s a lot shorter.</p><p>Hilary Batsel laid out the stakes: 94% of B2B buying groups now use LLMs in their research, and the “digital shelf” has shrunk from about 40 organic listings to around five recommendations. If you’re not in the agent’s five, you don’t exist for that buyer.</p><p>What gets you into the five mostly isn’t on your website. Tanya Bragin put it plainly:</p><p><em>“That third-party evidence ranks actually higher than anything you would put out on your domain.”</em></p><p>Which is why your homepage is now the least trusted page about your company, by LLM standards. Hilary shared one of the most useful numbers of the day: on LinkedIn, about 75% of a company’s citations in LLM answers come from its employees, and only 7–10% from the CEO and founders. Small teams have the edge here, because you can get 40 people posting faster than 40,000. Bridget Ferris described how ElevenLabs does it: an ambassador program publishing weekly use-case videos and contests that leave hundreds of real projects on other people’s sites. Creators “train the audience, but they also train the LLMs.”</p><p>But the agent only gets you onto the shortlist. As agents recommend ClickHouse more, its branded search goes up, and Tanya shared that “humans still close the loop.” Hilary added that models can tell when you’re making it up. If a claim isn’t credible, it won’t get cited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BPMYkDp0ReRMidiYy-dKZw.png" /><figcaption><em>Takeaway 2 from the Execution panel (LinkedIn, ClickHouse, ElevenLabs): the agent builds the shortlist, then a human makes the call.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Pick the one question you most want to be the answer to.</strong> Point every channel at it.</p><p>2. <strong>Track it like you used to track keywords.</strong> Run the same task-based prompts across the major AI assistants every week and log who gets recommended.</p><p>3. <strong>Make it easy for employees to post.</strong> Give them an opt-in way to share every launch in their own voice.</p><p>4. <strong>Fund many small creators over one big one,</strong> each answering your one question with a real project.</p><p>5. <strong>Only claim what the product backs up.</strong> Unbelievable claims don’t get cited.</p><h3>3. Codify your taste</h3><p><em>Lightning talks: Performance marketing</em></p><p><em>Nino Medina (Growth &amp; Demand, Anthropic), Brian O’Kelley (Founder, Apostra), Chris Cunningham (Head of Social, ClickUp)</em></p><p>Three performance marketing lightning talks addressed the next question: when everyone has the same models, what makes your marketing yours?</p><p>Nino Medina, who leads growth and demand at Anthropic, had the line of the session:</p><p><em>“Marketing will have its Claude Code moment.”</em></p><p>His point: Claude Code changed how engineers work. They describe what they want, an agent writes the code, and they spend their time reviewing it. Marketing is next. At Anthropic, a single command turns a product doc into a multi-channel campaign that’s about 90% ready to ship. The work moves from making every asset to defining what good looks like and judging the output. The tool for that is an eval: what good looks like, written down precisely enough to score against, with examples of your best work, clear criteria, and checks for what went wrong.</p><p>Brian O’Kelley, who built AppNexus and now leads Apostra, walked through how agents are starting to plan and buy media across channels. His caveat mattered more than the tech: agents only scale what you give them. The idea still has to be great.</p><p>Chris Cunningham, who runs social at ClickUp, brought it back to attention. People still spend far more time on social than in AI assistants, and launches only buy you a moment. “People need to think of you before they go search.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*benRCNOPSlyikBTDI3yc2w.png" /><figcaption><em>Takeaway 3 from the performance marketing lightning talks (Anthropic, Apostra, ClickUp): your taste becomes examples of your best work and criteria, then an eval that scores agent output before human review.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Write your first eval.</strong> Take one past campaign that worked. Write down why, with three examples of your best work and clear criteria.</p><p>2. <strong>Score before you review.</strong> Run new agent output against that eval before a person ever looks at it.</p><p>3. <strong>Put your brand and voice rules in a form a model can follow.</strong> If you can’t define good, an agent can’t produce it.</p><p>4. <strong>Plan the weeks between launches,</strong> not just the launch. Decide what keeps you in people’s feeds so they think of you before they search.</p><h3>4. Lead by doing</h3><p><em>Workflows panel: AI productivity &amp; connectivity · Powered by Clay</em></p><p><em>Bruno Estrella (Head of Marketing, Clay, moderator), Zeb Evans (Founder &amp; CEO, ClickUp), Michael Grinich (Founder, WorkOS)</em></p><p>The Workflows panel took the question inside the company. Adding a chat box to every tool isn’t the same as changing how work gets done. So how does a team actually become AI-native?</p><p>Zeb Evans and Michael Grinich gave the same answer: leaders go first. Zeb’s view is that “the best thing that AI has done is democratized opportunity and knowledge,” which means every team has the same tools and the edge comes from how you lead. Michael showed what that looks like at WorkOS. Once a month they run “Claude Days,” where non-engineers drive and engineers coach, and 40 to 50 things ship in a day. The mantra: “Just try it.”</p><p>Michael also turned the lens outward. He put his own spin on YC’s classic motto: “Make something agents want,” and made the case on stage:</p><p><em>“Not having a way for agents to sign up and use your product will be kind of like not having a website.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCtraPVdK2WHNNcUTAviQA.png" /><figcaption><em>Takeaway 4 from the Workflows panel (Clay, ClickUp, WorkOS): leaders go first, run a monthly build day where non-engineers drive and engineers coach, then ship and repeat. “Just try it.”</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Put a build day on the calendar this month.</strong> Non-engineers drive, engineers coach, and the goal is to ship something by the end of the day.</p><p>2. <strong>Go first.</strong> Each leader ships one real workflow with AI this month and shows the team how they did it.</p><p>3. <strong>Make trying safe.</strong> Judge the output, not the attempt. “Just try it” only works if nobody gets punished for a miss.</p><p>4. <strong>Then test the outside.</strong> Can an agent sign up for and use your product today? If not, that’s the next build day.</p><h3>5. Treat agents as a customer</h3><p><em>Systems panel: Agentic systems of record · Powered by HubSpot for Startups</em></p><p><em>Sarika Garg (GM, HubSpot, moderator), Jeanne DeWitt Grosser (COO, Vercel), Nate Slater (Head of Startup Solution Architecture, AWS)</em></p><p>The content so far has assumed agents have accurate information and permission to act. Sarika Garg opened the Systems panel with the line that framed the afternoon: “For the last several decades, all our enterprise systems were built with basically one fundamental assumption… that the user is a person.”</p><p>Jeanne DeWitt Grosser gave the room a name for what replaces PLG and SLG:</p><p><em>“We also now talk about ALG at Vercel, so Agent Led Growth… think of agents actually as a customer.”</em></p><p>Agent Led Growth is a go-to-market motion where AI agents, not just people, discover, evaluate, sign up for, and use your product. Vercel builds for it by making the CLI and MCP first-class and exposing every capability through both the UI and MCP. Underneath sits a semantic layer over the warehouse that “increasingly has become our system of record,” and an AI support agent that handles 91% of cases, with every miss turned into new documentation. Jeanne’s rule for outbound: don’t let a model draft it. Write the template the way you want it and let the model fill in the blanks. As she put it, “company building is agent building.”</p><p>Nate Slater added the rule nobody gets to break: agent permissions “have to be deterministic. You can’t let the LLM read the policy.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rq0aDgTG6HFhMFtyvRx66A.png" /><figcaption><em>Takeaway 5 from the Systems panel (HubSpot, Vercel, AWS): Agent Led Growth (ALG) is a go-to-market motion where AI agents, not just people, discover, evaluate, sign up for, and use your product, alongside PLG, PLS, and SLG.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Expose every capability twice,</strong> once in the UI and once through an API or MCP server, and make your CLI first-class.</p><p>2. <strong>Name one source of truth per function</strong> that agents can read and write, with people reviewing bulk changes.</p><p>3. <strong>Template anything deterministic.</strong> Outbound, follow-ups, and reports get templates. The model fills in the blanks.</p><p>4. <strong>Hard-code permissions.</strong> Put a human checkpoint on anything that spends money, sends an external message or changes a system of record.</p><p>5. <strong>Turn every support miss into documentation</strong> that people and agents can both read.</p><h3>6. Give agents a front door</h3><p><em>Lightning talks: Developer marketing</em></p><p><em>Morgane Palomares (VP, Marketing, Braintrust), Martin “Gonto” Gontovnikas (Growth Advisor, Supabase), Shub Gaur (GrokBot Advocate, SpaceXSI)</em></p><p>The developer marketing lightning talks were the most tactical 15 minutes of the day. Gonto’s opening point stuck with a lot of people:</p><p><em>Your website “is already used and seen more by agents than by humans.”</em></p><p>So build it for them. Publish an <a href="https://llmstxt.org/">llms.txt</a>, serve a clean Markdown version of every page, add agent-only guidance to your docs, and swap “Sign up” for “Build with agents”: a prompt someone can paste straight into their agent.</p><p>Morgane Palomares, who led marketing through hypergrowth at Vercel and GitHub and now leads it at Braintrust, covered what happens once you’re open for business. For years most marketing work was planned. “The ratio has completely flipped.” When a model drops, the team should decide that day whether to act, to say something or stay quiet. Shub Gaur from SpaceXAI pointed to where it goes next, persistent agents that own outcomes instead of tasks: “Instead of having your company staffed, you will actually have outcomes staffed.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPNI0PiuwAPy0G_npUBxiA.png" /><figcaption><em>Takeaway 6 from the developer marketing lightning talks (Braintrust, Supabase, SpaceXAI): an agent-ready checklist with llms.txt, Markdown pages, agent-only doc rules, a “Build with agents” prompt, and an MCP server.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Publish an llms.txt</strong> that maps your most important pages for agents.</p><p>2. <strong>Serve Markdown.</strong> Give agents a clean Markdown version of every page at the same URL people visit.</p><p>3. <strong>Add a “Build with agents” prompt</strong> next to your sign-up button.</p><p>4. <strong>Write a same-day response plan</strong> for model drops and competitor moves: who decides, by when and on which channels.</p><p>5. <strong>Staff one outcome, not a task.</strong> Pick one recurring result and give an agent the volume work, with a named person who owns it.</p><h3>7. The math hasn’t changed</h3><p><em>Keynote 2: Amjad Masad (Co-founder &amp; CEO, Replit) with David Sacks (Partner, Craft Ventures)</em></p><p>The day closed with Amjad and David, and they brought everything back to fundamentals. Replit went from a $2M to a $500M run rate in under two years, and Amjad is already looking past “everyone can ship.” The most interesting new thing he’s seeing is “collaboration across agents,” or agents handing work to other agents.</p><p>David brought it back to the numbers every founder with a hit consumer or prosumer product eventually runs into. The best consumer products lose about 5% of their customers a month. Good team and enterprise products start each year above 100% net dollar retention. Companies adopt for the product, and they stay for collaboration, trust, security, and infrastructure.</p><p><em>“Whenever I’ve met a founder who’s built a great consumer or prosumer product, they always end up at the same place.”</em></p><p>Agents change who finds you, who signs up and who does the work. They don’t change what keeps a customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9dyRttnSHpgAjnvTMfYCQ.png" /><figcaption><em>Takeaway 7 from Keynote 2 (Replit, Craft Ventures): the best consumer products lose about 5% of customers a month, while good team and enterprise products start each year above 100% net dollar retention.</em></figcaption></figure><p><strong>What to do</strong></p><p>1. <strong>Find your teams early.</strong> Count how many of your accounts already have several people from the same company. That’s your enterprise pipeline.</p><p>2. <strong>Build the team features before you need them:</strong> sharing, admin, security, and billing that a company can sign off on.</p><p>3. <strong>Measure retention next to signups.</strong> Put net dollar retention on the same dashboard as growth, so a viral month doesn’t hide a leaky bucket.</p><p>4. <strong>Plan the team motion now</strong> if you have a prosumer hit, not after the first big customer asks for it.</p><h3>Thank you</h3><p>Thank you to every speaker for being so candid about what’s working (and what isn’t). And thank you to the partners who made Un_prompted possible: LinkedIn, Clay, Goodwin, Amazon Web Services (AWS), HubSpot for Startups, 3FORTY3 and Brickell Digital. See you at the next one.</p><p><em>Originally published on the </em><a href="https://www.craftventures.com/articles/inside-un-prompted-seven-lessons-on-marketing-growth-when-agents-are-the-customer"><strong><em>Craft Ventures blog</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e2e2609dab1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside Supabase’s Breakout Growth: Lessons Scaling to 4.5M+ Devs, Powering AI & Vibe Coding]]></title>
            <link>https://medium.com/@aaronjcort/inside-supabases-breakout-growth-lessons-scaling-to-4-5m-devs-powering-ai-vibe-coding-dc574acfafaa?source=rss-6165c6fc194d------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc574acfafaa</guid>
            <category><![CDATA[supabase]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[ Aaron Cort]]></dc:creator>
            <pubDate>Wed, 08 Oct 2025 15:39:23 GMT</pubDate>
            <atom:updated>2025-10-08T18:14:52.495Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKoX87m3o-9H5Sj3MuxE3g.jpeg" /></figure><p>Supabase is one of the most explosive, beloved developer products we’ve seen at Craft. When I say explosive, I mean Supabase rocketed from <strong>1M to over 4.5M developers in less than a year</strong> — that kind of scale is unprecedented in developer products and reflects the precision, discipline, and authenticity of a product and community built by developers, for developers. At Craft I’ve embedded into a number of portfolio companies as an interim Marketing &amp; Growth executive as Operator-in-Residence (OIR). Most recently, I did this at <a href="http://supabase.com/">Supabase</a>.</p><p>When I met <a href="https://x.com/kiwicopple">Paul</a> back in May 2024 (Co-Founder and CEO at Supabase), I was blown away. His clarity of vision and relentless focus came from an innate desire to help developers. A developer himself, Paul and the entire team combine technical depth with a genuine commitment to open-source and community — values that are the foundation of Supabase’s breakout growth. Since Craft’s initial investment, I’ve supported Paul and the team on growth experiments, lifecycle design, and marketing foundations. This year, we decided I’d go deeper, embedding full-time for four months to help codify their viral growth.</p><p>I partnered with <a href="https://x.com/CraigCannon">Craig</a> (Head of Marketing &amp; DevRel), <a href="https://x.com/AntWilson">Ant</a> (Co-Founder &amp; CTO) and <a href="https://x.com/Rorstro">Rory</a> (CCO/COO) to create a sharp-shooting organic growth machine. Supabase powers <strong>millions of databases worldwide, with tens of thousands created every day</strong>, making it one of the fastest-growing open-source developer platforms ever built. For more on Supabase’s growth through a <a href="https://www.craftventures.com/articles/inside-supabases-product-community-led-growth">strategic finance lens</a>, read Craft investor Zao Chen’s deep dive after serving as interim VP Finance at the company.</p><p>As for my time at Supabase, here are my top three takeaways:</p><ol><li><strong>Devs have a high bar for community.</strong> Supabase proved that authenticity, open-source ethos, and developer-first culture aren’t just nice-to-haves, they’re moats.</li><li><strong>There’s always one event that matters.</strong> For Supabase, focusing on initialization — getting a database created — is the unlock that drives activation and downstream growth.</li><li><strong>Bifurcating your core ICP groups is essential.</strong> Supabase’s lifecycle hinged on serving two distinct groups differently: Postgres-familiar developers and those brand new to databases.</li></ol><p>I joined at a pivotal moment: the company had just launched General Availability, which transformed it from a beloved Firebase alternative to the go-to Postgres platform at scale. Now we had to codify Supabase’s growth systems: lifecycle funnels, cohort-based monetization frameworks, and community distribution loops.</p><p>Last week, <a href="https://fortune.com/2025/10/03/exclusive-supabase-raises-100-million-at-5-billion-valuation-as-vibe-coding-soars/">Supabase announced its $5 billion Series E</a> — a milestone that reflects not only the strength of its product and community, but also the scalable growth engine now in place. Here’s how we helped turn developer love and viral adoption into a repeatable growth system:</p><h3>Takeaway 1: Developers Have a High Bar for Community</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_92hdAU3T0VBwHIG-P1xA.jpeg" /><figcaption><em>Framework for structuring out your growth-oriented community</em></figcaption></figure><p><strong>“Evergreen” PLG takeaway</strong>: Winning in GEO/SEO, Community and Lifecycle requires a multi-threaded effort between each respective function, both at the program and tactical level.</p><p>From day one, Supabase was built on community trust. It grew into one of the most starred open-source projects on GitHub, scaling from early Hacker News buzz to powering millions of databases. By summer 2025, it had become both the default backend for serious Postgres developers (many using Supabase alongside Cursor and Claude Code and other AI coding products) and the infrastructure behind the vibe coding boom (i.e. Bolt, Figma Make, Lovable, v0). The takeaway is clear: authenticity and open-source ethos aren’t marketing fluff in developer markets — they are the moat.</p><h3>What We Did</h3><ul><li>Established Supabase’s brand voice guide across docs, lifecycle emails, and YouTube — maintaining the authenticity that the community expected.</li><li>Built frameworks to transform tutorials, docs, and videos into distribution loops, turning education into content-led growth.</li><li>Designed lifecycle journeys that converted open-source contributors and signups into long-term users without breaking community trust.</li><li>Mapped Supabase’s role in the “vibe coding” wave, speaking to both core Postgres developers as well as AI-native builders using Supabase alongside vibe coding.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TKNKGoL6k5jjrE1CtixYdw.png" /><figcaption><em>How to develop a community foundation in action in four steps</em></figcaption></figure><h3>Why We Did It</h3><p>Supabase had the opportunity to lean into its open-source transparency and grassroots adoption, giving them an advantage.</p><p>At the same time, the developer landscape was shifting. Vibe coding was no longer a fringe movement; it was becoming a mainstream pathway for new builders. Supabase was uniquely positioned to straddle both worlds: a trusted, Postgres-first platform for technical teams coding with AI, and a creative, AI-powered backend for the new generation of vibe coders.</p><h3>Impact</h3><ul><li>Supabase’s community scaled to millions of developers and more than a million active databases — cementing its position as one of the fastest-growing developer platforms.</li><li>55% of the most recent YC batch and more than 1,000 YC companies total use Supabase for their backend, validating its “default choice” status.</li><li>Supabase became the backend behind many of the top vibe coding platforms.</li><li>The company proved that community isn’t just engagement — it’s a distribution system that drives credibility with enterprises and virality with startups.</li></ul><h3>Takeaway 2: There’s Always One Event That Matters Most</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iu6Nw1aWurgnRNvKzpHLg.jpeg" /><figcaption><em>The “one key event” enters middle-of-funnel after initial onboarding</em></figcaption></figure><p><strong>“Evergreen” PLG takeaway</strong>: The “pillar” activation event is the one that makes all others possible. This will either <em>be</em> or <em>lead</em> to the industry standard “aha” moment. Simplify your focus.</p><p>For Supabase, the single most important event was <strong>initialization</strong>, or creating a database. Everything downstream depended on it. Once a developer spun up a database, the odds of them exploring Auth, Storage, Realtime, or Postgres extensions rose dramatically. Focusing on this action turned a broad funnel into a sharp point of leverage.</p><h3>What We Did</h3><ul><li>Re-oriented all funnel metrics around database creation as activation milestone</li><li>Simplified onboarding to reduce friction and guide users to “create your first database” as quickly as possible.</li><li>Designed lifecycle campaigns that celebrated initialization, then nudged users into next steps like enabling Auth or connecting APIs.</li><li>Built activation benchmarks where success was measured by the percentage of users reaching initialization.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjUbt-_qMqj4sztrOEvUMw.png" /><figcaption><em>How to apply the “one key event” focus in action in four steps</em></figcaption></figure><h3>Why We Did It</h3><p>Launches drive attention, but sustainable growth comes from activation. By locking onto database creation as the true north, we turned product adoption into a repeatable system. Initialization wasn’t just an onboarding step, it was the gateway into Postgres and the full Supabase ecosystem.</p><h3>Impact</h3><ul><li>Establishing this keystone event provided a durable framework where retention, expansion, and revenue scale predictably.</li><li>Initialization served as the gateway event that pulled developers into Auth, Storage, and Realtime adoption. Anchoring around this keystone event created a durable framework that connected activation to retention, expansion, and revenue.</li><li>Improved onboarding engagement by guiding users straight to database creation.</li><li>Tracking initialization rates instead of raw signups gave Supabase a reliable leading indicator for growth.</li></ul><h3>Takeaway 3: Use “Rule of Two” for Your Core ICP Groups</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z78OKlWVuRG1BONXJMGrHw.jpeg" /><figcaption><em>The “rule of two” starts at the top-of-funnel experience for users</em></figcaption></figure><p><strong>“Evergreen” PLG takeaway</strong>: Split out your funnel by starting with Beginners (B) and Advanced (A) users. Follow a two-way split for every segmentation after to avoid getting complicated.</p><p>Supabase users fell into two distinct camps: developers already familiar with Postgres, who needed confidence in product readiness, and those new to databases altogether, who needed reassurance that they could succeed quickly. Both loved Supabase, but they engaged in different ways and required different support. Success depended on building systems that treated them separately, rather than forcing a one-size-fits-all path.</p><h3>What We Did</h3><ul><li>Built ICP + use case frameworks mapping the needs, pain points, and upgrade paths.</li><li>Designed lifecycle campaigns and onboarding flows tailored to each audience: advanced prompts for Postgres pros versus step-by-step tutorials for newcomers.</li><li>Layered growth experiments (e.g., Free → Pro conversions, Teams upgrades) differently across each ICP cohort.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3XJl_7nVVZ4X7AE_uW40Q.png" /><figcaption><em>How to apply the “rule of two” user journey in action in three steps</em></figcaption></figure><h3>Why We Did It</h3><p>By splitting ICP groups, Supabase could meet each on their own terms. For Postgres-familiar devs, messaging emphasized scale, reliability, and advanced Postgres features. For newcomers, campaigns leaned on simplicity, community support, and “get started in minutes.” The result was a growth engine that could serve both audiences with precision and without compromise.</p><h3>Impact</h3><ul><li>Targeted journeys for each ICP improved activation and conversion.</li><li>Monetization exercises revealed clear ARR upside across distinct segments.</li><li>Established a scalable model where Supabase could serve both enterprise-grade developers and first-time builders without diluting its brand.</li></ul><h3>Takeaways for Founders</h3><h3>1. Community is a moat, not a channel.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fbBWN4a9St4JWM7HT3b0hQ.png" /><figcaption><em>Being open-source, GitHub stars are a great “dev love” measure</em></figcaption></figure><p>At Supabase, community wasn’t an accessory to growth — it <em>was</em> the growth engine itself. From GitHub stars and core developer community around its open-source software (OSS), to many of the top vibe coding platforms (i.e. Bolt, Figma Make, Lovable, v0), the company’s ability to build authentic trust created distribution, credibility, and virality. Founders take note: communities– especially developer communities–have a high bar for authenticity that no paid marketing campaign can ever deliver.</p><h3>2. Focus on your unique keystone event.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUV5yDPJzN9itqsQqGFxRw.png" /><figcaption><em>Example of an initialized database table in Supabase</em></figcaption></figure><p>Supabase’s entire funnel became sharper when we aligned around initialization (aka creating a database) as the single activation event. Founders often get focused on a myriad of metrics like signups, traffic, or vanity metrics, but the reality is that every business has one keystone event that drives compounding growth. Find it, orient around it, and measure success against it.</p><h3>3. Don’t force one-size-fits-all ICPs.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_OfKUCixZF_pabW9GzJ9gA.png" /><figcaption><em>AI-coding &amp; “vibe coding” products have different user types</em></figcaption></figure><p>Supabase saw success with splitting its lifecycle between Postgres developers and those new to databases. Each group engaged differently, needed different onboarding, and converted along separate paths. Treating them the same would have slowed growth. Founders should identify their own “rule of two” — the natural split in their customer base — and design tailored experiences. This precision will help you scale more quickly.</p><h3>Takeaways for Marketers</h3><h3>1. Codify brand voice early.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIpFEf_BrsKdh0iw0lZCdw.png" /><figcaption><em>Actual Supabase meme — this is one of hundreds of “bangers”</em></figcaption></figure><p>At Supabase, one of the first moves was codifying its brand voice early and making it consistent. For developers especially, tone is everything: too salesy and you lose credibility, too dry and you lose attention. Supbase differentiated itself from the start by making their internal meme obsession central to their brand. It was authentic and natural, which made it easier to execute. A similar tone followed, which was also familiar and unforced: since most people on the team are developers, former developers, or technical operators, it came naturally.</p><h3>2. Lifecycle is where community gets operationalized.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFI79-LYwzzDs_Z4hb6QuA.png" /><figcaption><em>Community video for Supabase walkthrough (includes key event)</em></figcaption></figure><p>Supabase’s community wasn’t just on GitHub or Discord — it was reflected in content and lifecycle campaigns across all channels that met developers where they were. Initialization prompts, reactivation nudges, and referral loops were written in the same authentic voice that the community had come to trust. Marketers should view lifecycle as the bridge between community energy and product adoption: it’s how you take the goodwill of an open-source movement and turn it into sustained usage and retention.</p><h3>3. DevRel is how you scale community credibility.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_5n2ymeKAV1WL0ROaZ6HA.png" /><figcaption><em>Supabase dominates owned + community YouTube content for devs</em></figcaption></figure><p>For Supabase, DevRel wasn’t just about SEO rankings or tutorials. Each blog, YouTube video, and doc became proof of community-led, technical expertise — showing developers that Supabase understood their workflows and pain points. This made content both an educational resource and a credibility signal that fueled word-of-mouth from external sources.</p><p><strong>In summary</strong>, Supabase’s spectacular rise to a <a href="https://fortune.com/2025/10/03/exclusive-supabase-raises-100-million-at-5-billion-valuation-as-vibe-coding-soars/">$5B Series E</a> wasn’t the result of chance. It was the convergence of three forces: a community that scaled to millions worldwide, a sharp focus on the one event that mattered (initialization), and a disciplined approach to ICP journeys. Together, those things turned developer love into durable growth.</p><p><strong>My biggest takeaway</strong>: in developer-first companies, the product and DevRel catalyze the movement — but it’s the systems around community, lifecycle, and ICP precision that turn that ignition into a growth engine</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc574acfafaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside Replit’s Breakout Growth: Lessons from $2.8M to $150M ARR]]></title>
            <link>https://medium.com/@aaronjcort/inside-replits-breakout-growth-lessons-from-2-8m-to-150m-arr-d2820d28552f?source=rss-6165c6fc194d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2820d28552f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[ Aaron Cort]]></dc:creator>
            <pubDate>Fri, 12 Sep 2025 18:00:28 GMT</pubDate>
            <atom:updated>2025-09-12T18:10:20.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_VrDvxAbfBY3i9mB9r2RRQ.png" /></figure><p>By: <a href="https://www.linkedin.com/in/aaroncort/">Aaron Cort</a>, Operating Partner, Marketing &amp; Growth at Craft Ventures</p><p>At Craft, we often take a hands-on approach to supporting our portfolio companies where they need it most. Unlike boardroom advisory roles, these stints as Operators-in-Residence (OIR) are when we embed deeply at a company, roll up our sleeves, and use tried-and-true playbooks to accelerate progress.</p><p>Last fall I embedded at <a href="https://medium.com/craft-ventures/why-we-invested-in-replit-81d297364742">Replit</a> as its interim Marketing &amp; Growth executive. Replit already had all the right signals for breakout potential — viral top-of-funnel momentum, a deeply engaged community, and a category-shaping product vision. These were a lot of the same indicators that I saw in my four-year journey at <a href="https://medium.com/craft-ventures/why-we-invested-in-clickup-9732c81d3dfa">ClickUp</a>, helping the company grow from $4M to $150M+ ARR as the first Head of Marketing and VP of Operations. The ClickUp journey taught me two things that became foundational to my work at <a href="https://replit.com/">Replit</a>:</p><ol><li><strong>Product-led growth is the unlock</strong> — if your product resonates, the right systems compound it.</li><li><strong>Speed without systems leaks value</strong> — launches and campaigns must be codified to sustain scale.</li></ol><p>When I joined Replit as an OIR in September 2024, they had just launched the <a href="https://blog.replit.com/introducing-replit-agent">Replit Agent</a>, a full-stack product for AI coding that pioneered vibe coding and created a brand new category. It was the perfect moment to install the marketing and growth systems that ultimately turned a launch spike into compounding growth.</p><p>This week, <a href="https://blog.replit.com/introducing-agent-3-our-most-autonomous-agent-yet">Replit announced their Agent 3 release</a>, alongside <a href="https://www.bloomberg.com/news/articles/2025-09-10/ai-coding-startup-replit-valued-at-3-billion-with-new-funding?srnd=phx-technology">a $3 billion valuation and insane growth numbers</a> — in less than one year, they went from $2.8M to $150M ARR. Lessons learned at ClickUp applied to Replit’s electric product-led growth helped this. Here’s what we did:</p><h3>Product-Led Marketing is The Unlock</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSmoVnTPy2i--f7nF_8UCg.png" /><figcaption>How to cohort user journeys and associate key metrics / unit economics</figcaption></figure><p>At ClickUp, I learned that marketing only works when it amplifies what people are already doing in the product. Our turning point came when we shifted from promoting features to focusing on jobs to be done — guiding users toward outcomes they already wanted. I applied that same philosophy to Replit.</p><p>The Agent wasn’t just another launch; it was a new entry point into the product’s value. Every marketing motion that worked best started with Agent or Assistant inside the product, and then rippled outward — into lifecycle email, website framing, and DevRel distribution. Launches weren’t announcements; they became activation engines.</p><p><strong>What we did</strong></p><ul><li>Created usage narratives across Agent, Assistant, Teams, and solo developers; then built segmented email tracks, content flows, and launch comms around them.</li><li>Audited lifecycle and onboarding, producing a dozen quick wins including Agent-specific flows for the first 24 hours, 7 days, and 30 days.</li><li>Launched dedicated journeys for Free and Core users, segmented by ICP — solo, Teams, and classroom — so messaging matched context.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9YikLN5q3lnNCdg6xu2Ug.png" /><figcaption>3 steps to start email / lifecycle initiatives to validate and simplify</figcaption></figure><p><strong>Why we did it<br></strong>At ClickUp, the growth model was built on a free-forever product that let people experience value without friction and then naturally expand into paid plans as usage deepened. Marketing’s role wasn’t to convince — it was to amplify those usage patterns. That philosophy is what led us to invest heavily in attribution and business intelligence, so we could identify the signals that predicted conversion and focus every campaign on guiding users toward them.</p><p>I saw the same opportunity at Replit. The Agent was not just a feature, but a new entry point where developers could move from curiosity to habit. To capture that moment, we gave it its own GTM muscle: lifecycle journeys tied to product states, onboarding flows that reinforced early wins, and campaigns designed to accelerate the moment when users realized the product had become indispensable.</p><p><strong>Impact on the business</strong></p><ul><li>Segmented lifecycle programs consistently outperformed general nurtures.</li><li>Agent-specific onboarding drove stronger early retention, especially in Week 1.</li><li>Resurrection campaigns re-engaged lapsed prosumer cohorts and funneled them back into new value paths.</li></ul><h3>Shipping Velocity and Timing = Viral Growth</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTCYGXQrB23s252KhXZFlw.png" /><figcaption>Web traffic growth broken out by channel over the last 12 months</figcaption></figure><p>ClickUp scaled on the back of relentless shipping velocity — we were launching weekly, sometimes daily. But speed alone doesn’t translate into ARR. Without discipline, launches spike and fade. The unlock was connecting every release into lifecycle, monetization, and retention. That’s how we made shipping velocity a driver of unit economics, not just product momentum.</p><p>At Replit, the Agent launch in September 2024 was lightning in a bottle: the right product at the right time, paired with a community ready to embrace “vibe coding.” The challenge was to make sure every launch after that wasn’t just an announcement, but a repeatable growth loop that improved activation, retention, and payback.</p><p><strong>What we did</strong></p><ul><li>Built a launch framework (product release + comms + email/lifecycle) with narrative templates, asset briefs, QA, and post-launch follow-through.</li><li>Coordinated homepage revamps, ideal customer persona (ICP) landing pages, and lifecycle email campaigns to align launches with activation nudges.</li><li>Wired launches directly into product signals, ensuring we could measure not just sign-ups but downstream monetization and retention.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dIIhjyfbCDo0laz7Gjuk0Q.png" /><figcaption>4 step framework to amplify a consistent release cycle</figcaption></figure><p><strong>Why we did it<br></strong>At ClickUp, the lesson was clear: launches only matter if they connect into lifecycle and monetization. Investors and boards don’t care about vanity spikes — they care about revenue growth, net dollar retention, and CAC payback. Lifecycle is the lever that ties shipping velocity to those unit economics. We applied that same discipline at Replit, treating every launch as both a marketing moment and a lifecycle milestone.</p><p>Velocity without lifecycle discipline actually works against you. When you’re releasing daily, user attention fragments and messaging becomes noise unless there’s a system to capture, educate, and convert. Lifecycle makes velocity coherent: it ensures every launch reactivates existing users, accelerates new ones to “aha” moments, and nudges the right cohorts toward monetization. At ClickUp, that discipline was the difference between short-term usage spikes and the sustained run from $4M to $150M+ ARR. At Replit, we used that same lens to transform the Agent launch into a template for every release that followed.</p><p><strong>Impact on the business</strong></p><ul><li>Coordinated launches consistently drove higher activation and conversion to paid.</li><li>Agent-specific lifecycle campaigns extended launch impact beyond the announcement window.</li><li>The cadence established during this period set the foundation for repeatable growth loops that scale with shipping velocity.</li></ul><h3>Community and Brand are Amplifiers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fipXKWYSY-KDRVLNqh1vvQ.png" /><figcaption>360 degree DevRel &amp; Community assessment across similar products</figcaption></figure><p>At ClickUp, we leaned heavily on organic engines — founder-led thought leadership, relentless product buzz, and a content/SEO strategy that scaled organic revenue by over 1000% year-over-year. Paid campaigns and billboards came later, but the foundation was already built. The core lesson was clear: organic growth is the backbone, and marketing only compounds once there’s a system around it.</p><p>Replit already had that founder-led presence through <a href="https://x.com/amasad">Amjad</a>, with <a href="https://x.com/pirroh">Michele</a> and <a href="https://x.com/mattppal">Matt</a>, amplifying the message on X, YouTube, and across DevRel. My job was to build scaffolding around that energy and turn individual sparks into a repeatable engine that could scale. That meant aligning Replit’s strengths with the same three growth buckets that drove ClickUp’s trajectory:</p><ul><li><strong>User-led growth</strong> through a passionate developer community.</li><li><strong>Product-led growth</strong> fueled by constant innovation around the Agent and Assistant.</li><li><strong>Content-led growth</strong> built on SEO, tutorials, and review proof.</li></ul><p><strong>What we did</strong></p><ul><li>Partnered with DevRel (<a href="https://x.com/mattppal">Matt</a>) to audit YouTube, benchmark against Vercel/LangChain, and double down on creator walkthroughs.</li><li>Ran G2 review campaigns synced with launches, growing reviews from 17 → 116 and placing Replit #4 in the AI Code Generation category.</li><li>Overhauled SEO from “viral” to “educational long-tail,” focusing on tutorials and rebuilding the blog taxonomy around intent-driven topics.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NOtjFWFSz5u6QFHH1W8wQ.png" /><figcaption>Replit’s placement on the AI Code Generation G2 grid as of September 2025</figcaption></figure><p><strong>Why we did it<br></strong>At ClickUp, community buzz was powerful, but it only converted once tied to structured programs like SEO, lifecycle, and review campaigns. The same principle applied here: organic energy needs infrastructure. Without it, momentum fizzles; with it, every founder post, DevRel video, or user shoutout compounds into authority, search visibility, and activation.</p><p>Beyond momentum, this is also about unit economics and control. Community reach is unpredictable unless it is converted into measurable, intent-driven surfaces — searchable tutorials, review proof, and lifecycle paths tied to product signals. That’s why we paired founder/DevRel distribution with attribution-backed SEO and G2 social proof: it turns spikes from X or YouTube into durable traffic, qualified signups, and activation cohorts we can actually forecast. It’s the same playbook I ran at ClickUp — organic first, then structure — where paid and performance become multipliers instead of crutches, and every post or video compounds into retention and revenue over time.</p><p><strong>Impact on the business</strong></p><ul><li>Amplified launch reach and brand authority in a crowded AI devtools market.</li><li>Solidified Replit’s future category leadership execution to come in “vibe coding.”</li><li>SEO and educational content laid the foundation for scalable, compounding inbound.</li></ul><h3>Takeaways for Founders</h3><h4>1. Build your own founder-led buzz</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GL2iSzuFamh5pwaH6PAxpw.png" /><figcaption>Operating cadence for announcing &amp; amplifying major features</figcaption></figure><p>Amjad’s authentic presence on X, backed by Michele and Matt, became one of Replit’s strongest channels. Turn launches into simple stories leaders tell in public; tie those posts to landing pages that advance and link to activation campaigns across lifecycle marketing.</p><h4>2. Focus on organic PMF above all</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qC_MIqo4sDStbxNLJyEZ1Q.png" /><figcaption>3 steps to follow for harvesting / expanding organic demand + awareness</figcaption></figure><p>Replit already had 11.5M+ organic visitors/month before launching the Agent. Marketing worked because the product had deep organic pull via the IDE; we channeled it to Agent/Assistant use cases with content that answers real searches and onboards straight into product tasks.</p><h4>3. Layer marketing on top of product growth</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRqZpf84SwMsFbKGtw_D7Q.png" /><figcaption>Framework for multi-functional ownership for amplifying product releases</figcaption></figure><p>Lifecycle and content programs were effective because they layered on top of strong usage patterns, not before. Lifecycle is the operating system; content/DevRel are the apps; founder/brand is the distribution. Ship quickly and let data decide where to lean in.</p><h3>Takeaways for Marketers</h3><h4>1. Lifecycle marketing is foundational</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G-S_Xd9qFSsc40QeazDySw.png" /><figcaption>Groupings for initial cohorts of users to target and timeframe windows</figcaption></figure><p>Segmentation by persona/use-case immediately improves performance. Retention lifts come from building infrastructure around first-week value. For Replit, Agent/Assistant education, reactivation of inactive/churned users, and quickstarts for personal vs. business use — all triggered off product truth. Start with cohorts that mirror product states; enrich via Reverse ETL. Make “launch → lifecycle” a standard path, not a one-off.</p><h4>2. Content is the organic backbone</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W8cR8x0f-epWxDPkKF8I7w.png" /><figcaption>Framework for Homepage testing and prioritization feeding other initiatives</figcaption></figure><p>Homepage revamps, ICP landing pages, and long-tail SEO captured demand and clarified positioning. At ClickUp, as we hit hypergrowth, organic content drove 65% of new ARR (much more in early growth stages when I first joined). I applied the same lens here for Replit: the journey flows from homepage/primary value prop to Agent/Assistant to ICP/use-case pages; a content plan that targets gaps where competitors rank.</p><h4>3. Community makes marketing better</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSGksIF7Rpjur9zc94AAgA.png" /><figcaption>Breakdown of YouTube channel analysis alongside core website structure</figcaption></figure><p>Campaigns (email, web, SEO) performed better when amplified by DevRel, reviews, and creators. At ClickUp, this meant organic buzz and review programs; at Replit, it meant DevRel channels (YouTube + X) and G2. Plug DevRel into search + lifecycle. When a video matches a high-intent query and an in-product task, shared compounded brand moments become durable traffic and activation. This can also very easily translate to social.</p><p>In summary, Replit’s jump from $2.8M to $150M ARR in less than one year wasn’t an accident. It was the convergence of product timing (Agent), community energy, and support by product-led marketing systems. For me, it felt like déjà vu from my ClickUp days — except this time, I could apply the lessons learned to help Replit accelerate even faster. My biggest learning: <strong>in PLG, the product gives you the spark, but systems turn sparks into fire.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2820d28552f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>