<?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[Vertex Ventures US - Medium]]></title>
        <description><![CDATA[The official blog of Vertex Ventures US, a venture capital firm investing in early-stage founders building infrastructure and SaaS companies. - Medium]]></description>
        <link>https://medium.com/vvus?source=rss----f6c6bc7f9eb2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Vertex Ventures US - Medium</title>
            <link>https://medium.com/vvus?source=rss----f6c6bc7f9eb2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:53:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/vvus" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reinventing SRE with AI: Our Investment in Cleric]]></title>
            <link>https://medium.com/vvus/reinventing-sre-with-ai-our-investment-in-cleric-6c2ced0b3f12?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/6c2ced0b3f12</guid>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[vc]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Megan Reynolds]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 18:30:29 GMT</pubDate>
            <atom:updated>2025-12-09T18:30:28.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqCPuADMlWsb-HgFjIrk_g.png" /></figure><p>We’re excited to share that <a href="http://vvus.com/">Vertex Ventures US</a> has led a new $5.5M seed round in <a href="https://cleric.ai/">Cleric</a>, bringing total funding to $9.8M alongside our friends at Zetta Venture Partners. You can find <a href="https://cleric.ai/blog/the-self-improving-ai-sre">Cleric’s own announcement here</a>, and <a href="https://siliconangle.com/2025/12/09/cleric-launches-ai-agent-uplevel-site-reliability-intelligent-automation/">go deeper on the news with SiliconAngle’s story here</a>.</p><p>Cleric is building an AI SRE that turns every investigation into operational memory — investigating like a senior engineer, giving teams SRE-level support, and reducing time to resolution and operational impact.</p><p>The net result: SREs spend less time constantly putting out fires and more time delivering real business value. In practice, mature teams like BlaBlaCar are already using Cleric to move from chasing one alert at a time to building intelligent coverage across services. Engineering leaders tell us Cleric surfaces the patterns behind recurring failures, which lets them eliminate entire classes of issues. That shift gives engineers meaningful time back, reduces repeat root causes, and, in early deployments, has reclaimed roughly 20–30% of total engineering capacity.</p><p>We met Shahram and Will, the founders of Cleric, early in their journey. They built and operated large-scale infrastructure at companies including Gojek, giving them an invaluable first-hand view into how AI-driven disruption necessitates change in the way that we monitor and manage the entire IT stack.</p><p>AI for production is fast becoming its own category. Over the last year, my colleagues at Vertex and I have dug into how AI is changing software not only in how it’s written but in how it runs. Across the IT stack, we’re moving from manual, human-paced workflows to systems that understand context and surface the next right action. Provisioning, CI/CD, security, observability and performance, and incident response are all being rethought for environments that are too complex and too dynamic to manage with dashboards and scripts alone.</p><p>That shift is happening because modern applications are no longer predictable. AI-generated code, agentic workloads and non-deterministic behavior introduce cascading changes, far more telemetry, and a whole new level of complexity. A single user action can trigger dozens of downstream processes, scale infrastructure in seconds and mutate environments in real time. Teams using traditional tools will struggle to keep up.</p><p>Observability is where this pressure shows up first. Most issues never become headline incidents, yet they still consume hours. An engineer is deep in a refactor, an alert fires, a Slack thread starts, logs and metrics are pulled, a deployment diff is checked, the immediate problem is fixed, and the context disappears. A few weeks later, it happens again. The investigation repeats. Anything learned rarely gets preserved, especially in the inevitable case of SRE staff turnover. Ultimately, time and velocity are lost.</p><p>This is where Cleric is different. It mirrors how experienced engineers actually investigate production issues. It asks what changed, correlates logs, metrics and deploys, explores multiple hypotheses in parallel and presents evidence-backed findings in Slack where engineers already work. Every new investigation makes Cleric smarter, as day-to-day triage becomes operational memory that compounds. The next time a similar issue appears, the organization doesn’t start from zero: Cleric already knows where to look.</p><p>Ultimately, we believe that complexity will keep rising faster than human attention can keep up. Systems like Cleric that capture and reuse investigative knowledge will become foundational to how modern software is run.</p><p>We are proud to partner with Shahram, Will and the team as they scale from strong product usage to broader adoption. If you are building or operating complex systems and want to compare notes, <a href="/service/mailto:megan@vvus.com">I’d love to talk</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c2ced0b3f12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/reinventing-sre-with-ai-our-investment-in-cleric-6c2ced0b3f12">Reinventing SRE with AI: Our Investment in Cleric</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to pivot your product for the AI era, according to the CEO of PromptQL and the head of…]]></title>
            <link>https://medium.com/vvus/how-to-pivot-your-product-for-the-ai-era-according-to-the-ceo-of-promptql-and-the-head-of-82a8966794b7?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/82a8966794b7</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 22:08:29 GMT</pubDate>
            <atom:updated>2025-11-03T22:08:28.202Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to pivot your product for the AI era, according to the CEO of PromptQL and the head of Microsoft Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a5CAT77D56QNs-u7" /></figure><p>Welcome back to Vertex Angles, the weekly newsletter from <a href="https://www.linkedin.com/company/vvus/">Vertex Ventures US</a>. We’re a boutique venture capital firm, investing in exciting companies across software infrastructure, developer tools, data, security, and vertical SaaS. If you prefer e-mail, you can <a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=7cf2345446&amp;e=dede606798">subscribe here to get Vertex Angles in your inbox every week</a>.</p><p>There’s much about the startup journey that’s the same as it’s ever been, even in the current age of AI progress. Focusing on your users, executing quickly, and hiring the right people remains some of the best advice that CEOs and founders can follow, no matter the circumstance.</p><p>As the SaaS market is undergoing a tumultuous sea change that presents a tremendous challenge — and opportunity — for every stripe of entrepreneur. Customers increasingly demand AI as a way to boost productivity and efficiency, even as the breakneck pace of AI development itself seems to unlock new business possibilities every day.</p><p>At Vertex Intersect, our recent invite-only gathering of founders and CEOs in Palo Alto, we invited Microsoft Teams Corporate VP <a href="https://www.linkedin.com/in/manikg/">Manik Gupta</a> and <a href="https://www.linkedin.com/company/promptql-io/">PromptQL</a> CEO <a href="https://www.linkedin.com/in/tanmaig/">Tanmai Gopal</a> to discuss how they’re meeting the moment and leading their product organizations to thrive in the AI-first era of enterprise software.</p><p>What both leaders have in common is that they had to pivot their product: Microsoft Teams, launched in 2017, has quickly reinvented itself with new LLM-powered features including automatic meeting transcription and dynamic agendas. That same year, Tanmai cofounded Hasura (a Vertex portfolio company) with Rajoshi Ghosh. This year, Hasura rebranded the entire company around PromptQL, its flagship product for AI developers.</p><h3>Here’s some of their advice on managing this kind of change:</h3><p>Enterprise AI is not consumer AI: The accuracy, security and privacy standards for consumer applications are simpler/lower in threshold. If you intend to sell into the enterprise, though, you have to keep enterprise-specific requirements in mind from day one, the leaders agreed. It doesn’t matter how slick your demo is or how clever your implementation of AI is — if it’s not reliable or compliant with security standards, it’ll never sell to enterprises at a scale that matters.</p><p>Learn to love the rapid pace of AI development: The frontier labs are making stunning progress on their AI models, with each new release smarter than the last. As Tanmai put it, however, this can be disorienting for product teams building on those foundation models: Every new model brings with it its own quirks that have to be accounted for in order to maintain a consistent customer experience.</p><p>This means that developers need to move beyond the traditional CI/CD metrics, and embrace a flow of constantly running evals on each model, and user-feedback from testing in production. Eventually, Manik suggests, you develop a kind of “intuition” on each new model, making you more sensitive to the changes and guiding you towards adjusting accordingly.</p><p>Sell intelligence, not software: It makes logical sense that a software company would consider itself in the business of selling, you know…software. In this brave new AI world, however, both leaders discussed how their perspectives have changed. Given that the ideal output of AI software is completed work, they say that you almost have to consider yourself in the consulting business. What you’re selling is a workforce to do things on the customer’s behalf.</p><p>There is, of course, a lot more to it, the leaders acknowledged. But what they agreed on is that in these still-early days of enterprise AI development and adoption, the ultimate burden of a leader is to stay nimble, listen to customer feedback, and expect the unexpected.</p><h3>More insights and startup lessons from Vertex Intersect 2025:</h3><ul><li><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=5a7dfad35a&amp;e=dede606798">Vertex Intersect 2025 recap: In a world of AI Agents, you need high-agency people</a></li><li><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=55ad50d283&amp;e=dede606798">Why you shouldn’t run your startup like a democracy, according to Facebook’s first VP of Engineering</a></li><li><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=d1046e3357&amp;e=dede606798">Storytelling should be part of the business school curriculum, says legendary investor Sir Michael Moritz</a></li><li><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=23c47f87c1&amp;e=dede606798">How to make sure your startup hires high-agency people, according to a 3X exited serial founder</a></li><li><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=327343a166&amp;e=dede606798">What your early-stage startup is getting wrong about GTM and sales, according to a founder who sold his startup to Workday</a></li></ul><h3>Vertex Portfolio Job of the Week: Chief of Staff at Tulip</h3><p><a href="https://www.linkedin.com/company/tulip-interfaces/">Tulip Interfaces</a>, the leader in frontline operations, is looking for an experienced Chief of Staff to help define and scale operational practices and drive efficiencies across the company. This role is based out of Tulip’s headquarters in Somerville, MA.</p><p><a href="https://vertexventures.us9.list-manage.com/track/click?u=6b638dad48d127373c520c8e7&amp;id=0117003526&amp;e=dede606798">Apply Here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82a8966794b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/how-to-pivot-your-product-for-the-ai-era-according-to-the-ceo-of-promptql-and-the-head-of-82a8966794b7">How to pivot your product for the AI era, according to the CEO of PromptQL and the head of…</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What your early-stage startup is getting wrong about GTM and sales, according to a founder who…]]></title>
            <link>https://medium.com/vvus/what-your-early-stage-startup-is-getting-wrong-about-gtm-and-sales-according-to-a-founder-who-ef53e9c8fc97?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef53e9c8fc97</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Tue, 28 Oct 2025 20:14:35 GMT</pubDate>
            <atom:updated>2025-10-28T20:26:58.175Z</atom:updated>
            <content:encoded><![CDATA[<h2>What your early-stage startup is getting wrong about GTM and sales, according to a founder who sold his startup to Workday</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c6y62T8_nZzlen2s4Rp-wA.jpeg" /><figcaption>Jerry Ting (right) and Megan Reynolds (right)</figcaption></figure><p>Congratulations, your startup just finished building its first product, and now it’s ready to ship.</p><p>But the end of one important leg of the journey marks the beginning of another, as you enter the wild world of go-to-market and actually getting what you made into the hands of customers. In most cases, a strong GTM motion is literally the only way your startup will generate the revenue it needs to survive.</p><p>This can be a difficult transition for many founders, particularly those with a more technical background. Up to that point, they likely spent the vast majority of their time on engineering and product leadership, or on fundraising. Now, they need to get out of their comfort zone and immerse themselves in the unfamiliar (and, for some, uncomfortable) business of sales and marketing.</p><p>In a roundtable discussion at <a href="https://www.linkedin.com/pulse/vertex-intersect-2025-recap-world-ai-agents-you-need-high-agency-pymsc/?trackingId=4TopoK3kRSOOMRBPgyH1RQ%3D%3D">Vertex Intersect 2025</a> — our recent invite-only gathering of founders and CEOs in Palo Alto — Jerry Ting shared with the gathered entrepreneurs his learned wisdom in mastering the art of GTM. Jerry is the co-founder of Evisort, acquired last year by Workday, where he now serves as VP and Head of Agentic AI.</p><p>Jerry’s message for startup leaders looking to learn the same is simple: Founders of early-stage companies should stop looking at sales as an unknowable and inscrutable discipline, and start thinking about GTM as a product and recruiting problem that can be solved.</p><p>“Early-stage sales is about finding partners and people that you have a relationship with,” he said. “As a founder, you can convince them to be part of a founding journey and a product journey. It’s not ‘Sales’ with a capital S. It’s lowercase ‘sales’ and I think getting that right is super important.”</p><p>His top bits of advice for entrepreneurs:</p><p><strong>Your sales problem is probably a product focus problem</strong>: Sometimes, founders get ahead of themselves when it comes to scaling sales and GTM. Before you spend a lot of money on fancy sales automation tools or hiring expensive leaders, make sure your product is something that your ideal customer actually wants to buy.</p><p>“I think it actually all starts with your product focus and doing really, really deep work on that before trying to scale your GTM,” Jerry said.</p><p>You can scale your commercial efforts as much as you’d like, but if you haven’t cracked product-market fit yet, those salespeople will mostly just be spinning their wheels.</p><p><strong>Your first sales hire shouldn’t be a shark</strong>: Along those same lines, a lot of startups make the mistake of hiring a traditional closer as their first salesperson — often an experienced salesperson, perhaps with experience at a big company in the same space. Jerry says that this doesn’t always work out well, as this kind of salesperson is “resource hungry and they’re not used to selling without a brand.”</p><p>It may seem logical to hire top sales execs from the leading incumbent in your space — after all, they must be doing something right — but that pedigree doesn’t tell you anything about how they’d operate under the constraints inherent in startup life. It’s usually better, Jerry says, to hire somebody scrappy and inventive from perhaps the second- or third-place players in your category.</p><p>Jerry instead says that you should instead treat that first sales hire as a kind of forward-deployed engineer. At the early stages, sales is fundamentally “deep product consulting,” where you have to spend a lot of time with the customer helping with un-sales-y activities like helping with deployment and asking smart questions to gather actionable product feedback.</p><p>That’s almost always the job of the founders at the time of the company’s inception. It works out because founders are also the best-equipped to communicate the vision for the product and company to prospective customers, while also helping them navigate any potential technical challenges and troubleshoot problems.</p><p>But beyond a certain scale, you need another smart, capable, low-ego technical generalist with experience in the market to carry the torch and work closely with customers while also evangelizing the mission. That’s the profile you should be looking for with your first hire.</p><p><strong>Avoid ”happy ears” and keep it real</strong>: Founders can sometimes put themselves in a reality distortion bubble, where they confuse customer interviews and product advisory meetings with actual sales conversations.</p><p>Jerry warns that if founders are too emotionally invested and desperate for success, they’ll fall victim to “happy ears,” where you “lie to yourselves to say that person is actually able to make a buying decision.” Too often, you end up wasting your time and confusing your pipeline.</p><p>He says that the antidote is being willing to ask clear, probing questions of anybody you’re talking to. He suggests making use of tools like the <a href="https://www.gartner.com/en/digital-markets/insights/bant-framework">BANT framework</a> for founders to frame customer calls.</p><p>He says that founders need to get accustomed to asking hard questions in a consultatory kind of way, and “have the discipline to say ‘hey, I love that you’re mentoring me as a founder and doing product advisory, but who owns the budget and how does the budget cycle actually work?”</p><p>This drive for clarity might feel “salesy” to founders who might not be used to it, but Jerry says that being clear about what you want is actually key to being a good partner.</p><p>On a final, related note, he says that founders <a href="https://www.linkedin.com/pulse/stop-making-enterprise-software-so-hard-buy-vvus-sijec?utm_source=share&amp;utm_medium=member_ios&amp;utm_campaign=share_via">shouldn’t be afraid to ask for payment if they’ve added significant value to a customer</a>. It’s the responsibility of the founder to initiate the commercial conversation with the customer and discuss both billing and their commitment level (e.g., pilot versus long-term). If you don’t, you’re being “irresponsible” to the customer, he says.</p><p>If you want to learn more about the secrets of GTM for early-stage technical startups, Vertex’s Megan Reynolds holds workshops for founders in New York City and San Francisco. You can <a href="https://forms.gle/feTW3WLk1NbmWhxk8">sign up to be notified about the next GTM event here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef53e9c8fc97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/what-your-early-stage-startup-is-getting-wrong-about-gtm-and-sales-according-to-a-founder-who-ef53e9c8fc97">What your early-stage startup is getting wrong about GTM and sales, according to a founder who…</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make sure your startup hires high-agency people, according to a 3X exited serial founder]]></title>
            <link>https://medium.com/vvus/how-to-make-sure-your-startup-hires-high-agency-people-according-to-a-3x-exited-serial-founder-eb8be69742d7?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb8be69742d7</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 17:20:09 GMT</pubDate>
            <atom:updated>2025-10-27T17:20:08.727Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQysnyaFM5hB1REvrh4TPA.jpeg" /><figcaption>David Politis (left) and Noah Carr (right) at Vertex Intersect 2025</figcaption></figure><p>It’s as trite as it is true: Your first hires as a founder are probably the single most important decision you’ll make in those early days. The right person will see around corners, jump every hurdle, and generally solve problems you didn’t even know you had. Bringing the wrong person onto the team, on the other hand, will slow your pace of progress and poison your culture, weighing you down before you’ve even gotten off the ground.</p><p>The key attribute you want to hire for, says serial entrepreneur David Politis, is a high level of agency. The only way to cut through the uncertainty and pace of the startup journey is to blaze your own trail forward, which is an ability as valuable as it is rare.</p><p>“You need the people going to run through walls for you,” David said, speaking at Vertex Intersect, our recent invite-only gathering of founders, operators, and technologists. “You need the people who are okay with the ambiguity of an early stage company that’s changing directions all the time.”</p><p>This is a lesson that David learned well from his own experiences as a founder and leader. He guided three companies to successful exits: Vocalocity (acquired by Vonage), Cloud Sherpas (acquired by Accenture), and BetterCloud (acquired by Vista Equity Partners). Now, he coaches leaders via his platform, <a href="https://notanotherceo.com/">Not Another CEO</a>.</p><p>When it comes to identifying those high-agency people in the recruiting process, David says there are certain traits you want to watch out for:</p><ul><li><strong>Proactivity: </strong>High-agency people are proactive, in a way that makes their manager’s life easier. At an early-stage startup, the right hire will take things off the founder’s plate, rather than add a bunch of new things for them to worry about. Managing this kind of person is conversational more than directional, with vibes that are more like collaboration than top-down management.</li><li><strong>Creation mindset: </strong>It’s enticing to prioritize recruiting people with a background at companies like Google, Meta, or Apple. This can sometimes be something of a red herring, though, warns David: People with that kind of pedigree are often more comfortable following an existing playbook than they are writing a new one on the fly. Impressive resumes are great, but only if it’s matched by a willingness to wear a lot of hats and learn by doing.</li><li><strong>Intrinsic motivation: </strong>The kinds of people who thrive in the startup setting tend to be those who aren’t motivated by money or prestige, but rather by a chip on their shoulder, in David’s telling. More than anything, they should be excited at the prospect of solving hard problems, and driven to work on building smart, sustainable solutions.</li></ul><p>Once you’ve hired those high-agency people, David says, the next big challenge for the CEO is keeping them. To that end, David says the trick is to create a high-performance culture that keeps your top talent engaged and challenged.</p><p>In practice, he says, that means:</p><ul><li><strong>Cut underperformers quickly: </strong>“A-players want to play with A-players,” David says. CEOs need to be willing to fire quickly in cases where people don’t live up to expectations, or else they can drag down the whole culture and impel your best talent to look elsewhere. He suggests that startups should try a 90-day probationary period for new hires.</li><li><strong>Giving top talent your time: </strong>A lot of your top performers probably came aboard because they wanted to work with <em>you</em>, personally. As hectic as your life as a leader can get, always make sure to allocate some face time with those high-flyers so they keep feeling seen, heard, and aligned with the mission.</li><li><strong>Consider incentives that don’t scale: </strong>Beyond cash and equity, CEOs should be looking for little, one-time ways to make their key peoples’ lives easier. When a star engineer was struggling with sleep because he and his girlfriend were sharing a twin mattress, he bought them a nice new queen-sized bed. Another time, a hotshot salesperson was struggling with credit card debt. So when the company passed an important milestone, David paid off the debt entirely as a one-time bonus, writing a check directly to the credit card issuer. These kinds of little things build loyalty, while also taking a burden off the shoulders of your best employees and theoretically making them more productive.</li></ul><p>Much of this is easier said than done, but the reward is a team that takes much of the burden of management off your shoulders, while helping propel your startup to new heights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb8be69742d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/how-to-make-sure-your-startup-hires-high-agency-people-according-to-a-3x-exited-serial-founder-eb8be69742d7">How to make sure your startup hires high-agency people, according to a 3X exited serial founder</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storytelling should be part of the business school curriculum, says legendary investor Sir Michael…]]></title>
            <link>https://medium.com/vvus/storytelling-should-be-part-of-the-business-school-curriculum-says-legendary-investor-sir-michael-ffb57d8cec39?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/ffb57d8cec39</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Thu, 09 Oct 2025 22:33:31 GMT</pubDate>
            <atom:updated>2025-10-09T23:31:22.475Z</atom:updated>
            <content:encoded><![CDATA[<h2>Storytelling should be part of the business school curriculum, says legendary investor Sir Michael Moritz</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCxd9p0eBhJsoO3aiCn5jA@2x.jpeg" /><figcaption>Sir Michael Moritz (left) and Vertex Ventures US General Partner Jonathan Heiliger</figcaption></figure><p>Sir Michael Moritz has one of the most interesting backgrounds in technology: A prolific and well-known journalist for many years (he <a href="https://en.wikipedia.org/wiki/The_Little_Kingdom">literally wrote the book on Apple</a>), he’d go on to become a legendary investor in companies like Yahoo, Google, Stripe, Klarna, and LinkedIn via his work at Sequoia Capital. Despite his legendary achievements, he prefers to stay out of the limelight that many investors today crave, and we’re fortunate he shared a day with us.</p><p>Speaking on stage at Vertex Intersect 2025, our annual invite-only gathering of founders, builders, and technologists, held recently in Palo Alto, Michael says that this vantage point has made him appreciate the power of storytelling in building a company all the more. The problem, he says, is that many young founders don’t know how to do it and don’t prioritize building this skill.</p><p>“I’ve always felt that at the top business schools, they’re missing one vital module in their curriculum, and that’s the art of storytelling,” Michael said. “As a venture person, as a founder, as a key senior member of a company, it is vital to be able to tell a story in a clear and eloquent fashion.”</p><p>For newly-formed startups, this is a particularly important skill to master, Michael said. In those early days, you’re trying to get potential hires, investors, and customers alike to take a chance on you before you have anything resembling a pedigree, money in the bank, or perhaps even a product itself. In their stead, he says, these young companies have to be able to tell a compelling story.</p><p>The foundational element of a good company story, Michael says, is defining the mission. The best ones, in his estimation, are short and sharp, almost to the point of glibness — but that belie a sense of the scale and scope of the founders’ ambition. Stripe, to use his example, has a mission to “increase the GDP of the Internet,” which is both succinct, and which indicates an aspiration much higher than merely facilitating credit card payments.</p><p>Then, Michael says, founders need to frame their mission as a mountain to climb. That mission sits at the peak, a goal towards which the entire company can slowly but surely make progress towards. Nailing this, he says, keeps employees engaged, and helps investors and recruits understand your journey more intimately. When it comes time to engage with the press, too, the mountain ascent framing will help journalists to understand what it is you’re trying to achieve and how you’re planning to get there.</p><p>The company should be aligned on the method of ascent, with plans to make base camp at certain milestones along the way. If you plan to attack the summit immediately out of the gate, you and your team will quickly get discouraged and burned out at the difficulty of the climb. It therefore falls on leadership to celebrate reaching each milestone as a major achievement unto itself, emphasizing that it’s brought them closer to their ultimate goal, he says.</p><p>Equally importantly, having a clear and well-defined path up that figurative mountain helps a startup keep its focus and not “fritter away time or money,” he says. Ultimately, a startup’s only true advantage is the ability to build and ship faster than the incumbents’ own bureaucracy allows.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffb57d8cec39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/storytelling-should-be-part-of-the-business-school-curriculum-says-legendary-investor-sir-michael-ffb57d8cec39">Storytelling should be part of the business school curriculum, says legendary investor Sir Michael…</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you shouldn’t run your startup like a democracy, according to Facebook’s first VP of…]]></title>
            <link>https://medium.com/vvus/why-you-shouldnt-run-your-startup-like-a-democracy-according-to-facebook-s-first-vp-of-4aff2423fdf6?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/4aff2423fdf6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Mon, 06 Oct 2025 18:44:39 GMT</pubDate>
            <atom:updated>2025-10-06T18:44:35.724Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Why you shouldn’t run your startup like a democracy, according to Facebook’s first VP of Engineering</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZMKskIhWbEKIzZaxuqK4fQ.jpeg" /><figcaption>Jeff Rothschild (right) in conversation with Vertex’s Insik Rhee at Vertex Intersect 2025.</figcaption></figure><p>A startup’s greatest advantage is its ability to move quickly. A small company can react to a new trend or add a customer-requested feature while your larger and more well-capitalized competitors are still holding a meeting to schedule a meeting to plan a meeting to make a slide deck to explore the possibility of shipping a point release.</p><p>But sometimes, startup CEOs themselves undermine that advantage, says <a href="https://www.linkedin.com/in/jeffrothschild/">Jeff Rothschild</a>, the entrepreneur and investor best known as Facebook’s first technology executive. Jeff spoke with <a href="http://www.vvus.com/">Vertex’s</a> <a href="https://www.linkedin.com/in/insikrhee/">Insik Rhee</a> in a keynote session at Vertex Intersect ’25 — our annual invite-only gathering of founders, builders, and technologists, held recently in Palo Alto.</p><p>The mistake those CEOs make, says Jeff, is to seek consensus when there’s a difficult decision to be made. It’s understandable, he says: Especially in the early days, you want your team to be fully on board with the plan, so you might wait to take action until everybody is bought in. In practice, however, it means you end up dragging your heels and wasting precious time.</p><p>“Trying to achieve consensus will slow you down forever, because people have the expectation that’s what you’re going to do in every decision,” Jeff said.</p><p>Instead, Jeff says, CEOs should remember that <strong>a startup is not a democracy</strong>. The buck stops with the CEO, who holds the ultimate responsibility for setting the vision and the direction for the company. When those forks in the road present themselves, it’s up to the CEO to chart the course.</p><p>Good leaders will solicit feedback from the team, take their perspectives into account, and generally make sure all viewpoints are heard and respected. They’ll make sure that they explain whatever decision is made clearly, thoroughly, and promptly. A CEO worth the title will value their thoughts and engage with their arguments in good faith, even if they disagree. What they won’t do is wait to make sure everybody who gave this feedback agrees with the final outcome.</p><p>“You’ll solicit input from your team,” Jeff said. “But you’re going to make this call, and you’re not going to pretend that it was a democracy.”</p><p>In fact, Jeff suggests that this kind of non-democratic conviction is also a benefit for CEOs when it comes to engaging with stakeholders like investors or board members. It’s vital that those interested outside parties feel heard and understood, and CEOs are well-served to solicit whatever advice and operational wisdom they have to offer.</p><p>At the same time, Jeff reminds CEOs that those very same board members first came aboard because they believed in their vision and ability to execute. It’s inevitable that the CEO and the board will disagree on something important, sooner rather than later in the company’s journey. In those instances, the board isn’t looking for the CEO to roll over and do exactly what they want, Jeff says — they want the CEO to demonstrate backbone, push back, and show that they have what it takes to meet the challenge.</p><p>“You want a CEO who has conviction, has substance behind that conviction, and backs it up, and sticks to their guns,” Jeff says.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aff2423fdf6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/why-you-shouldnt-run-your-startup-like-a-democracy-according-to-facebook-s-first-vp-of-4aff2423fdf6">Why you shouldn’t run your startup like a democracy, according to Facebook’s first VP of…</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vertex Ventures US Invests in Swarm Biotactics, Innovating Defense with Cyborg Insect Technology]]></title>
            <link>https://medium.com/vvus/vertex-ventures-us-invests-in-swarm-biotactics-innovating-defense-with-cyborg-insect-technology-430dca70ed2a?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/430dca70ed2a</guid>
            <category><![CDATA[defense]]></category>
            <category><![CDATA[wireless-communication]]></category>
            <category><![CDATA[swarm-intelligence]]></category>
            <category><![CDATA[military]]></category>
            <category><![CDATA[cyborg]]></category>
            <dc:creator><![CDATA[Sandeep Bhadra]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 16:17:28 GMT</pubDate>
            <atom:updated>2025-08-11T20:31:12.841Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*1LZ8zVIabj2uxNBP.jpg" /></figure><p>Today, Vertex Ventures US is proud to announce our investment in <a href="https://www.swarm-biotactics.com/"><strong>Swarm Biotactics</strong></a>, a pioneering biorobotics startup harnessing swarm intelligence for rapid, autonomous threat detection and response. This announcement comes at a pivotal moment: Europe is accelerating defense investment, primed for innovation in strategic deterrence.</p><p>In recent months, <a href="https://www.politico.eu/article/mark-rutte-nato-defense-spending-target-considerably-more-3-percent-munich-security-conference/">NATO</a> convened in The Hague to agree on a historic commitment to raise defense and security spending to<a href="https://en.wikipedia.org/wiki/Agreement_on_5%25_NATO_defence_spending_by_2035?utm_source=chatgpt.com"> 5 % of GDP by 2035</a> — comprising 3.5 % for core military capabilities and 1.5 % for resilience measures such as cyber, logistics, and innovation. <a href="https://www.politico.eu/article/friedrich-merz-germany-major-nato-defense-boost-donald-trump-us-eu-military-budget-ukraine-russia/?utm_source=chatgpt.com">Germany</a>, the largest defense spender in Europe, has committed to doubling its defense budget — from roughly €86 billion (2.4 % of GDP) in 2025 to over €153 billion (3.5 %) by 2029 — just one example of allied rearmament underway. Allies like France, the UK, Sweden, Poland, Denmark, and the Baltic states are also boosting military R&amp;D, industry capacity, and readiness.</p><p>This surge in defense funding highlights a generational opportunity for breakthrough technologies — and <strong>Swarm Biotactics</strong> is uniquely positioned to meet it by thinking radically about micromobility at scale. Leveraging decades of academic research, SWARM Biotactics has cracked the code on bio-robotics, creating cyborg madagascar hissing cockroaches controlled via miniature electrodes and equipped with custom sensor or actuator backpacks.</p><p>These aren’t your typical drones — they’re living, intelligent systems that can navigate cluttered, denied, and high-risk terrain where traditional machines simply can’t go. Their unique approach leverages biologically-inspired swarm algorithms, peer-to-peer networking, and high-throughput bioreceptors — enabling autonomous adaptation in contested environments. This technology offers distinct advantages over traditional unmanned ground vehicles (UGVs), effortlessly navigating complex terrain and providing enhanced capabilities for intelligence, surveillance, and reconnaissance (ISR).</p><p>The founding team brings decades of experience across military-grade autonomous systems, AI, and biotech platforms. I am thrilled to back, once again, co-founder and Chairman Joerg Lamprecht, whose previous venture, Dedrone, was successfully acquired by Axon (a defense tech public. CTO and co-founder Moritz Strube previously served as CTO of InspectifAI, a subsidiary of the $3 billion Körber AG group. Newly appointed CEO Stefan Wilhelm, a German native and U.S. citizen, brings extensive expertise in bridging European innovation with the U.S. defense market, reflecting Swarm’s ambition for transatlantic expansion.</p><p>It’s a testament to the team’s background and execution that in less than a year since founding, Swarm Biotactics has already secured Letters of Intent (LOIs) and is actively engaged in discussions with NATO defense primes, reflecting strong market interest and validation of their innovative approach.</p><p>Think about it: What if the most sophisticated robots weren’t built in factories, but evolved over millions of years? 🦗 🪳</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=430dca70ed2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/vertex-ventures-us-invests-in-swarm-biotactics-innovating-defense-with-cyborg-insect-technology-430dca70ed2a">Vertex Ventures US Invests in Swarm Biotactics, Innovating Defense with Cyborg Insect Technology</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI as a startup force multiplier: The CEO of SPRX explains how AI is showing the path to…]]></title>
            <link>https://medium.com/vvus/ai-as-a-startup-force-multiplier-the-ceo-of-sprx-explains-how-ai-is-showing-the-path-to-e2d63042da7c?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2d63042da7c</guid>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Matt Weinberger]]></dc:creator>
            <pubDate>Wed, 09 Apr 2025 18:56:25 GMT</pubDate>
            <atom:updated>2025-04-09T18:56:25.888Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>AI as a startup force multiplier: The CEO of SPRX explains how AI is showing the path to disrupting professional services</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiLjKjwdqH3ULT_rvdVVQA.jpeg" /><figcaption>Dominic Vitucci, CEO and founder of SPRX Tax</figcaption></figure><p><a href="https://www.linkedin.com/in/dominic-vitucci/">Dominic Vitucci</a> was almost certainly not the first tax accountant to get frustrated with doing, by hand, a task that he knew could be done better and faster by software.</p><p>Helping clients file for their R&amp;D tax credits at a major corporate accounting firm — his first real job out of college — Dominic was handed a checklist and told to follow it to the letter. The credit process was long and tedious, but straightforward enough that even a junior accountant, like Dominic was at the time, could sleepwalk through it.</p><p>The <a href="https://www.sprx.tax/features/rd">federal R&amp;D credit</a>, created in the ’80s, was designed as a way to incentivize American companies to invest in innovation. It’s since become a cornerstone of corporate tax accounting, with over 30 states offering their own similar credit.</p><p>It also hasn’t changed much in the intervening decades, and remains something of an infamous slog. But no software company ever cared enough about this very specific problem to solve it, and no accounting firm had the technical savvy to build a product to address it. Not to mention that success would mean cutting into their own billable hours.</p><p>This dynamic, Dominic saw, created an opportunity for entrepreneurship. In 2020, armed with his unique background in both computer science and accounting, his familiarity with linear regression, and developer access to an early version of OpenAI’s game-changing GPT 3.0 model, he left the tax industry behind, and <a href="http://sprx.tax/">SPRX </a>was born.</p><p>Five years later, SPRX has grown into a case study for the potential of AI-powered startups to disrupt the world of professional services. Last year, Vertex Ventures US was proud to lead SPRX’s Series A round, which came as the company saw early growth in revenue and customers. Since then, over 500 companies of all sizes have turned to SPRX’s automation platform to simplify their R&amp;D tax credit studies, speeding up what had been a months-long process so that it only takes a few weeks.</p><p>Importantly, Dominic says that SPRX would never have been possible in a pre-LLM world. With models like GPT handling the hard parts of reasoning and language processing, SPRX itself can stay laser-focused on solving its specific problem. That approach helped SPRX start up lean, as its core product was originally built by only 2 developers. SPRX kept that approach as it scaled: The company started 2024 with 7 employees, and ended the year with some 25, largely reflecting a new investment in enterprise sales.</p><p>“I think that’s where you see this force multiplier with AI being able to come in and say, hey, building with AI, building on AI, building with these platforms and making them capable to achieve the things that we need them to achieve is really only possible today,” Dominic says. “10 years ago, you couldn’t build this company.”</p><h3><strong>Firing its customers and starting again</strong></h3><p>The first lesson that SPRX learned in its journey is to be really thoughtful about who its customers should be.</p><p>When SPRX first incorporated, it prioritized selling into the same kind of big accounting firms where Dominic himself used to work. The idea was that SPRX’s AI would help them be more efficient, automating away the grunt work that Dominic and his entry-level peers would get stuck with in the R&amp;D tax credit process.</p><p>The good news was that Dominic was able to show that SPRX’s first product, built on a clumsy-but-functional foundation of early-access GPT and good old fashioned conditional statements, worked as intended. Dominic’s bet that software could automate tax work away started to pay off.</p><p>It did, however, lead to the harsh realization that most of these firms had no real interest in getting more efficient. First, there was the matter of pride: Few career accountants would accept that SPRX’s software could perform at their level. And second, even if they could, they were loath to invest in something that might make their own job moot.</p><p>“For two years I was just ripping my hair out, fighting with mid-level accountants: ‘I’m skeptical of AI, there’s no way AI could be as smart as I am,’” Dominic says. “Okay, well, respectfully, I disagree.”</p><p>A few forward-looking firms signed on as SPRX clients, but true product-market fit remained out of reach. On the other hand, it was becoming increasingly clear that the <em>clients </em>of those firms were hungry for a better way of applying for the R&amp;D credit.</p><p>“All these accounting firms are middlemen. There’s no point to them,” Dominic says. “The best way to compete, the best way to build a big, durable business is to take this technology to the people that actually benefit from it.”</p><p>In late 2022, SPRX fired all of its customers and rebuilt its product around this insight, even as it entered the Y Combinator startup accelerator program.</p><h3><strong>Building an AI-native startup for domain expertise</strong></h3><p>In the two short years between iterations of SPRX, the world of AI had changed a lot. In late 2022, right as Dominic was rethinking his own product, OpenAI released ChatGPT — sparking a Cambrian explosion in AI.</p><p>Dominic credits the wide availability and selection of foundational LLMs with making the new version of SPRX possible. The first time out, the SPRX team had to do a lot of hard engineering work just to mash together GPT-3 with its own homebrewed backend to get the desired results. This time, SPRX was able to spend more time focusing on the application logic and the vagaries of the tax code, letting a handful of models (including various versions of GPT, Anthropic’s Claude, and a few others) do the heavy lifting on the AI side.</p><p>This approach has helped SPRX grow and scale its customers and revenue with only a handful dedicated developers, plus himself, working on the core product. Let OpenAI and Anthropic and Google throw seven-figure salaries at Stanford PhDs, Dominic says; SPRX reaps the benefits when their models get better without his having to do anything.</p><p>”The secret is, having an OpenAI PhD as an engineer on our team makes no sense, right? We’re not building the forefront, bleeding-edge technology. We’re using it, certainly, to build a very domain-specific product,” Dominic says.</p><p>Instead, Dominic can afford to be slower and pickier when it comes to hiring. One engineer who knows (or can be taught) the tax code, and who’s excited to take on these problems, is worth a dozen generalists as far as Dominic’s concerned. It means SPRX can stay nice and lean even as it matures.</p><p>“So it’s more important for us to have engineers that we can train, that we can educate, that we can mint these hybrid CPA engineer/tax engineer kind of people who understand the context,” Dominic says. “Instead of hiring a team of 50 engineers and hoping 70% hit, we can hire five guys, make sure they’re all killers, and make sure they’re all in the right space to build this particular product.”</p><h3><strong>A sign of things to come</strong></h3><p>Dominic knows he can’t be the only person to have ever rued and lamented their employers’ backwards-thinking approach to solving very domain-specific problems. The issue was that unless that person happened to be technical themselves, or knew a willing co-founder who was, the tools didn’t exist for them to build a solution.</p><p>Now, the barrier for entry to building a product is getting lower by the day: When Dominic first built SPRX, he didn’t have access to AI code assistants like Windsurf, Lovable, Vercel, Cursor, or the rest of the usual suspects in so-called vibe coding.</p><p>As those products grow and mature, Dominic reckons that you’ll see a lot more founders who take advantage of these developments to build their own hyper-specific solutions to problems with which they’re painfully familiar. These kinds of products will only get easier and cheaper to build, which in turn means that it’ll become more viable to successfully start up a company to sell them.</p><p>The real differentiator, Dominic says, will be domain expertise. The founders that win will be the ones who best understand their respective industries — not those who are the most adept at coding or data science. In many cases, they might not even require a technical co-founder in the traditional sense. This changes the dynamic of product development and company-building in ways we have yet to see, Dominic says.</p><p>“There’s a sweet spot in there where you have to have some level of baseline, some level of ’I can build this myself, and I could have built this myself in the absence of AI, it just would’ve taken a lot longer and been a lot worse,’” he says. “But now, with this domain expertise, people like myself, people with the same type of background, are significantly more empowered to achieve some of these outcomes.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2d63042da7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/ai-as-a-startup-force-multiplier-the-ceo-of-sprx-explains-how-ai-is-showing-the-path-to-e2d63042da7c">AI as a startup force multiplier: The CEO of SPRX explains how AI is showing the path to…</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to find your next AI startup idea when everything seems possible]]></title>
            <link>https://medium.com/vvus/how-to-find-your-next-ai-startup-idea-when-everything-seems-possible-ae3784bdf9a2?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae3784bdf9a2</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Simon Tiu]]></dc:creator>
            <pubDate>Thu, 27 Mar 2025 23:55:55 GMT</pubDate>
            <atom:updated>2025-03-28T15:26:44.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3NNAjsexscXMNHmRFTvWug.png" /><figcaption>Generated with OpenAI</figcaption></figure><p>As an early-stage investor, friends often ask me something like, “Hey, I have this AI startup idea. Do you think it’s a good one?”</p><p>The ongoing AI revolution offers incredible possibilities, but also brings uncertainty. The stakes are high: choose well and shape the future; choose poorly and fall behind. With limitless possibilities, how do you decide what to build?</p><h3>A Simple Framework: the Critical Frequency Matrix</h3><p>To cut through complexity, here’s a simple mental model I’m calling the <strong>Critical Frequency Matrix</strong>. In physics, <em>critical frequency</em> often refers to a threshold at which a medium — like the ionosphere or a waveguide — changes its behavior by reflecting or blocking waves instead of letting them pass through. Similarly, I used the Critical Frequency Matrix to identify pivotal areas within an enterprise where startups can break through, drive transformation and capture new opportunities.</p><p>To start, think of any enterprise as a collection of tasks or “jobs to be done” (1). We can then visualize the profile of the business as the distribution of these tasks along two core dimensions: <strong>frequency</strong> and <strong>criticality</strong>.</p><p>Frequency is straightforward, tasks can happen constantly (e.g. processing orders) or very rarely (e.g. M&amp;A). Criticality is fuzzier — what’s vital for one business might be minor for another — but generally, criticality reflects the potential business consequences if a task goes wrong or is not executed to a high level of quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UFGxnT8RcwLDnRfU" /></figure><p>Every enterprise task can be mapped onto this grid, creating a simplified fingerprint of the business. While you might consider adding other dimensions like “technical complexity,” doing so actually weakens this framework’s effectiveness. The power of this approach lies in what it deliberately excludes.</p><p>This intentional simplification recognizes a core truth in our world of accelerating computing power: technical moats rarely endure (2). At best, technical complexity provides a temporary head start measured in months, not years. Yesterday’s PhD-level engineering challenge becomes tomorrow’s API call. The enterprises that win aren’t those with the most complex technology, but those that apply the right technology to the most valuable problems.</p><h3>Finding AI’s Sweet Spot</h3><p>Now that we have a framework, let’s return to the key question: <strong>Where exactly on this matrix can you find the most valuable AI opportunities?</strong></p><p>While every business has its unique dynamics (i.e. different dot profile), certain task categories will have similar commercial implications.</p><p><strong>Category 1: Humans excel at low-frequency, high-criticality tasks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0cg9322BAOfERCW8" /></figure><p>Infrequent but pivotal events, think major corporate pivots, crisis management, or annual strategic planning, are where AI automation is least valuable and where human leadership shines brightest. These tasks demand nuanced judgment, creativity, and rapid adaptability. While AI can offer data-driven insights or scenario modeling, it struggles with the intangible, context-rich decision-making that defines success in unpredictable moments.</p><p>For example, deciding whether to acquire a competitor or fundamentally realign product strategy requires balancing quantitative metrics with cultural considerations, ethical implications, and an opinionated vision of future markets — all areas where a human perspective is essential. Similarly, when a PR crisis erupts, the ability to negotiate, empathize, and communicate transparently cannot be reduced to lines of code. Because such events occur too rarely to justify extensive automation, and because they hinge so heavily on human feelings, AI will likely remain a supporting player here for the foreseeable future.</p><p><strong>Category 2: High-frequency, high-criticality tasks can be lucrative, but challenging for AI agents</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y7jhW2Mz6h_k3srK" /></figure><p>Tasks that occur frequently and hold high criticality offer immense market opportunities but also present significant challenges for agentic solutions. The key question is whether agentic solutions, with their non-deterministic reasoning, is better than Robotic Process Automation (RPA). Generally, automation in these areas must achieve near-perfect reliability and accuracy, making technical execution paramount. These attributes make this region a great place for simple, deterministic automation. AI agents can still contribute meaningfully here, but their agency, their ability to reason and independently think, must be constrained. For example, an agent may still determine which predefined workflow to execute based on a given context; however, once a workflow is selected, the individual steps are likely to remain rigidly structured to guarantee predictability and minimize risk.</p><p><strong>Category 3: Low-criticality, high-frequency tasks offer the broadest scalability</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sdmObgAGI6itptyF" /></figure><p>Tasks that have high frequency yet individually hold low criticality — such as routine customer support inquiries or basic bookkeeping — are ideally suited for automation through agentic systems. Their predictability and widespread presence across multiple industries create the opportunity for broad adoption, unlocking significant value previously trapped in these everyday processes.</p><p>For founders, there’s an additional layer of strategic potential: Within enterprises, there are clusters of related tasks which require the same set of underlying capabilities. Identifying one of these task clusters that extends across multiple industry verticals is exactly the kind of high-leverage, transformative opportunity that investors dream of.</p><p><strong>Category 4: Low-frequency, low-criticality tasks offer untapped value through generalized AI assistance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZwMpJDXDmf2PT7VP" /></figure><p>My intuition, though not yet fully validated, is that low-frequency, low-criticality tasks are typically fragmented, specialized, and disconnected. Said more plainly, I think the tasks in this category are relatively unrelated to one another. For example, executive assistants must execute a variety of tasks completely unrelated to one another: organizing occasional events, calendar coordination, even IT troubleshooting. Individually, these tasks do not justify dedicated automation and a solution that automates all of these tasks is challenging to develop due to their disparate nature.</p><p>Of course, a generalized agentic system capable of handling this diverse array of infrequent tasks would be immensely valuable–something close to AGI. Such a general system would require exceptional adaptability and intelligence to manage these unique, context-dependent activities that resist standardization. In short, building a big business here is possible but only with something resembling artificial general intelligence (AGI).</p><p><strong>Conjecture: Market value for individual tasks generally grows with frequency and criticality</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*NqlkS4pgDdpT91jT" /></figure><p>The market value of automating a job rises as you move “up and to the right” on our matrix — meaning tasks become more valuable when they are both more frequent (higher frequency) and more essential (higher criticality) to the business. Automating real-time fraud detection in banking, continuously monitoring patient vitals in hospitals, or running non-stop quality control checks in factories can yield significant returns precisely because these tasks are both critical and frequent. Conversely, occasional tasks with low criticality — like ordering office supplies quarterly or preparing annual internal memos — offer minimal benefit when automated.</p><p>Moreover, the market value of automating a task exhibits higher elasticity with respect to frequency than to business criticality, which is why the red curve is convex. Said more simply, my guess is that frequency is a greater contributor to market value than criticality. Why? Because the business value of solving a problem that causes constant pain is higher than solving episodic pain. Just look at the market capitalization of Uber versus automobile retailers.</p><h3>Using the Framework to Spot Hidden Opportunities</h3><p>As an investor, this framework helps me to focus on enterprise value and to highlight task areas with genuine potential for new AI-native ventures. Here’s a practical Charlie Munger-inspired checklist, to help apply this framework when thinking of your next AI-native startup (3,4).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*y03n1vBEvMTkz8lW4EZicQ.png" /></figure><h3>Common AI-Native Startup Patterns</h3><p>While evaluating individual tasks is important, building an AI-native business typically requires addressing a group of interconnected tasks. The sequence in which you tackle these tasks will significantly shape your business and go-to-market strategies. Here are a few common patterns in building an AI-native startup for the enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-a_ZhXvieuGXMnDIW6H13g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mReP937omMK4eDB74YbMxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUWDSVDjwgF_X0zKn_2drA.png" /></figure><h3>Remember, this is a tool, not a formula</h3><p>The Critical Frequency Matrix isn’t a magic wand — it’s a tool. Like a hammer that drives nails effectively but can’t cut wood, this framework is helpful within its intended use (AI-native, enterprise applications), but is limited outside of it. Apply it thoughtfully, not blindly.</p><p>To founders in this space: You’re building during an extraordinary moment. If you’re tackling these challenges, I’d love to hear about your journey. The world needs your ideas — now go build something amazing!</p><p><em>Footnotes:<br>(1) Clayton M. Christensen introduced the “Jobs to Be Done” theory, which proposes that customers purchase products or services to accomplish specific tasks or fulfill certain needs in their lives, highlighting the importance of understanding the underlying “job” driving consumer choice. See Clayton M. Christensen, Competing Against Luck: The Story of Innovation and Customer Choice (HarperBusiness, 2016).<br>(2) Richard S. Sutton’s “The Bitter Lesson” highlights how specialized, handcrafted technical advantages or moats in AI inevitably diminish over time, consistently displaced by simpler, general-purpose methods powered by increasing computational resources. This underscores that defensibility rooted in complexity or expert-crafted features is often temporary. See Richard S. Sutton, “The Bitter Lesson,” March 13, 2019, </em><a href="http://incompleteideas.net/IncIdeas/BitterLesson.html."><em>http://incompleteideas.net/IncIdeas/BitterLesson.html.</em></a><em><br>(3) Charlie Munger famously loved using checklists: “Checklist routines avoid a lot of errors. You should have all this elementary wisdom, and then you should go through a mental checklist in order to use it. There is no other procedure that will work as well.”<br>(4) Startups in enterprise B2B applications, this is not a framework for consumer-facing applications!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae3784bdf9a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/how-to-find-your-next-ai-startup-idea-when-everything-seems-possible-ae3784bdf9a2">How to find your next AI startup idea when everything seems possible</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From reactive to predictive: Entering the AI era of observability]]></title>
            <link>https://medium.com/vvus/from-reactive-to-predictive-entering-the-ai-era-of-observability-dd24a3cec94d?source=rss----f6c6bc7f9eb2---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd24a3cec94d</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Megan Reynolds]]></dc:creator>
            <pubDate>Thu, 13 Mar 2025 00:15:00 GMT</pubDate>
            <atom:updated>2025-05-08T01:30:07.559Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4sEQFExeELwh4wG34nzjA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mostafa_meraji?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">mostafa meraji</a> on <a href="https://unsplash.com/photos/person-holding-black-binoculars-cUxF-FcFwL4?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>The rise of AI presents a breaking point for the current model of observability: The confluence of AI-generated code, non-deterministic applications, and agentic workloads will bring with them an explosion in complexity and cardinality that today’s observability tools are not equipped to handle.</p><p>But as much as AI presents this problem, I’d propose that it brings with it the solution as well. Plenty of customers have already signalled that they’re ready for a seismic shift in this market; some are spending as much as 10% of their total cloud bill on the current generation of observability tools. AI brings with it the opportunity to rethink what observability software is and does, shifting from a reactive paradigm to a predictive one. In other words, AI brings the possibility of a generational leap in observability that goes beyond providing better dashboards, giving us new tools that are both smarter and more cost-efficient, stopping system problems before they start.</p><p>This article dives into how AI-native approaches are emerging, where incumbents are vulnerable, and why at <a href="http://vvus.com/">Vertex Ventures US</a> we’re excited about investing in the future of autonomous systems engineering.</p><h3>How the Cloud Era transformed observability</h3><p>In the beginning, developers relied on logs. You SSH’d into a machine, tailed a log file, and debugged. Your infrastructure team may have muttered about Ganglia and Nagios alerts, but most developers didn’t need to care. Then came the move to the cloud. Infrastructure became more complex, applications became distributed, it wasn’t enough just to debug, systems needed to be monitored and optimized. Ops teams and then developers needed dashboards, query interfaces, and visualizations… enter players like Datadog, and solutions like application custom metrics and Application Performance Monitoring (APM). By embedding itself into developer workflows and enabling cross collaboration with Ops teams, Datadog became the preferred player, winning adoption from the bottom up and redefining observability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FZr7RLd8CxPCbc_VvCjCQ.png" /><figcaption>Cloud Era observability architecture</figcaption></figure><h3>The AI Era: a new paradigm for observability</h3><p>Now, we’re entering a new era with AI and complexity is set to increase dramatically. It’s hard to understand any system that you didn’t develop yourself, harder still when those AI-generated AI apps don’t have consistent behaviours. With non-deterministic systems, visibility into how they acted is even more important. In today’s systems, a human performs an action that directly impacts a service but with AI-driven workflows and agents, a single human action can trigger a chain reaction of AI processes, scaling up and down dynamically.</p><p>This complexity is in turn triggering an explosion in cardinality — the number of unique combinations of metadata values in telemetry data being collected. It’s no longer practical to rely on dashboards alone. Debugging through a UI feels like searching for a needle in an ever-expanding haystack. One engineering manager from a Fortune 500 company told me “so often we see incidents where we are already emitting the correct metric to have caught it earlier, but we didn’t add it to the right dashboard” it’s a common frustration. Observability needs a new interface, and it’s becoming clear that the new interface will be driven by AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vW9rXTCnv3gAOjET" /><figcaption>AI Era observability architecture</figcaption></figure><h3>AI-driven root cause analysis: finding and fixing issues faster</h3><p>Just as AI-powered coding assistants are transforming how software is written, they will soon transform how systems are monitored and debugged. Today’s observability toil e.g. querying logs, correlating traces, sifting through dashboards will be automated. AI-enabled root cause analysis (RCA) tools are emerging, promising to surface issues faster and eliminate manual work in optimizing systems and debugging. <a href="https://cleric.ai/">Cleric</a> is one example. It mirrors the investigative flow of seasoned SREs, using the same log queries, metric checks, and deployment history they reach for, while continuously refining its approach with each investigation.</p><p>Incumbents like Datadog and New Relic were built for an era where humans handled debugging, so their platforms prioritize fast, interactive querying. AI-driven RCA systems, however, focus on reducing total response time by automatically identifying root causes, which doesn’t require sub-second query speeds but instead demands deep, long-term pattern analysis. Incumbents struggle to transition because their architecture, user experience, and customer expectations are all optimized for manual debugging, making it difficult to support both human- and AI-centric workflows. As a result, AI-native observability startups have an advantage by building automation-first systems without the constraints of legacy platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aXYdcCNqlj7Bzqw9" /><figcaption>Emerging early stage companies we’re tracking</figcaption></figure><p>We believe any early stage player that wins here will have the unique combination of deep customer empathy, experience running large scaled systems and enough expertise in cutting edge AI. The winning companies will start with battle tested and repeatable use cases e.g. analyzing logs for errors, metrics for uptime and availability issues, traces for performance issues while keeping a narrow focus defined by language, application type or even more vertical e.g. debugging Spark pipelines. This product focus needs to be combined with hands-on customer support to build on agent performance, fill any gaps and work towards a more generalisable product.</p><p>It will take time to build trust before any real, end-to-end automation is possible. One senior backend developer I spoke to said she would want the AI system correctly root causing and suggesting fixes for every incident over a 2-year timeline before trusting anything to run autonomously. How to build trust? Working collaboratively with early customers, proving accuracy, failing gracefully and investing heavily in a smooth UX that reduces friction in an already complex workflow. Early customers will be companies that feel the most pain — in the sweet spot of running complex infrastructure with strained SREs and likely for whom uptime = revenue, industries like software infrastructure, payments, analytics and e-commerce.</p><h3>Can incumbents adapt from human-centric to AI-centric RCA?</h3><p>Incumbents like Datadog and Chronosphere are starting to market their own AI products for automating on-call workflows and searching telemetry data using natural language. They have access to huge amounts of proprietary telemetry and incident data and this likely gives them a significant headstart in automating workflows. It’s unclear if these products are being used in production without customer case studies. As a public company, short term results are prioritized and there is a high bar for accuracy with any automation like this and so the roll-out and experimentation will likely be slow and steady. They are also already charging 10% of a company’s cloud bill and so customers may expect any AI products to be close to free. Plus, given the structure and breadth of the general purpose data that these platforms collect, avoiding false negatives and positives has historically been a challenge with e.g. Watchdog. This may burn early customer trust. The incumbents are a threat but there is an opportunity to move fast and build a better, AI-first leader in observability.</p><h3>Observability data lakes: decoupling storage from analysis</h3><p>At the same time, a deeper shift is happening in the infrastructure layer. The disaggregation of the modern data stack has revolutionized data engineering with standardisation across table, file and storage formats and is now playing out in observability. Traditionally, APM vendors provided an all-in-one solution — collect, store, analyze, visualize. Now, infrastructure teams, SREs, and IT Ops are rethinking how they handle observability data. With the rise of microservices and Kubernetes, telemetry cardinality has exploded by 10–15x in recent years. AI-driven, real-time applications are generating even more granular data. In the past, teams solved this by down-sampling — throwing away data to manage cost and performance. That approach is no longer enough.</p><p>Cribl was an early pioneer in observability cost reduction, making it easy for companies to filter, enrich and route telemetry data before storing and analysing. Honeycomb were the first to pioneer the idea of an observability tool that could handle the explosion of cardinality from microservices. These tools will continue to see growth in the AI era but observability analytics is now a discipline in itself. It’s no longer about just throwing up a dashboard with key metrics; teams need to slice, dice, and correlate observability data like they would with any other critical data they use to run their business.</p><p>Companies are realizing they need new ways to store and query high-cardinality telemetry, separate from the visualization and alerting layer. The key challenges here are 1) cross-correlating between metrics, logs, traces and events — typically stored and processed separately 2) fast queries across those data sources. For this analysis to be useful to a developer, it has to be real-time. We’re seeing the rise of observability data lakes and query engines built specifically for large-scale time-series analysis. Newer incumbents like Cribl are already working on their own observability data lake, to extend their pipeline products. The early-stage companies that will win here will drive greater standardisation (capitalizing on open standards like OpenTelemetry and Iceberg and formats like S3) and drive value in one of two ways — dramatically reduce cost with a tradeoff in performance or focus on high-performance but involving a new persona e.g. product teams with use cases like per customer analytics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4_6zL7edTQ17fBGx" /><figcaption>Emerging early stage companies we’re tracking</figcaption></figure><h3>Why enterprises are taking observability in-house</h3><p>There has been a growing trend among the largest tech companies to roll their own observability stack, often combining internal tooling focused on large scale data processing with a Datadog or Grafana UI. After FAANG, notable examples include Uber (OSS Jaeger), LinkedIn (Kafka-based), Dropbox, Airbnb, Pinterest, Shopify and more recently companies like Palo Alto Networks are applying their expertise in data infrastructure to observability, accelerated by the improvement in data tooling for observability and driven by exploding cardinality and the associated cost with an incumbent vendor.</p><h3>Incumbents are modernizing their data infrastructure but what are the limits?</h3><p>Datadog has invested heavily in its internal data infrastructure <a href="https://www.datadoghq.com/blog/engineering/introducing-husky/">releasing Husky as their event store in 2022</a> and more recently <a href="https://www.datadoghq.com/blog/datadog-acquires-quickwit/">acquiring Quickwit</a>, a sub-second query engine optimized for telemetry data. Datadog’s Husky is already a highly efficient storage engine and so it’s unlikely a new player will compete directly on performance. They are also positioning themselves to offer cross-correlation querying of any telemetry data and high cardinality but it’s an open question how this will collide with their existing business model, which is based on bulk, general purpose ingest and storage. The market rewards them for collecting and storing large amounts of data, forever, with rich UIs to query that are so loved by developers that they earn an 80% gross margin. Extracting meaningful insights from this bulk data using AI is an extremely hard problem to solve and with CFOs already pushing back on spend, Datadog will be unlikely to capture more high margin value without laser sharp messaging on the value these insights will drive.</p><p>Another open question is what role the data platforms e.g. Databricks and Snowflake will play in this market. They are already working with large enterprise customers incl. banks and telcos to enable custom observability data lakes for monitoring data workloads. It’s unclear yet whether this will become a more direct product strategy focused on IT operations and software engineering teams, tackling the observability vendors head-on.</p><h3>The next decade of observability</h3><p>The future of observability won’t be a better dashboard. Near-term it will be AI assistants that automate the toil, reason across fragmented telemetry sources, and give engineers superhuman abilities to debug and optimize their systems. Long-term, the model will flip from reactive incident response to preventative development, leveraging the universal context and memory capabilities of LLMs, reinforcement learning and related AI techniques to finally connect observability with code. It’s possible that AI agents will get to the point where fully-autonomous systems engineering is possible and both AI RCA and observability data lakes will be critical pillars. As autonomous software engineering advances, autonomous systems engineering will be its necessary counterpart, ensuring reliability, adaptability, and control.</p><p>Huge thank you to <a href="https://www.linkedin.com/in/inowland/">Ian Nowland</a>, <a href="https://www.linkedin.com/in/umachingunde/">Uma Chingunde</a>, <a href="https://www.linkedin.com/in/irabinovitch/">Ilan Rabinovitch</a>, <a href="https://www.linkedin.com/in/chrischolette/">Chris Cholette</a>, <a href="https://www.linkedin.com/in/andrewfong/">Andrew Fong</a>, <a href="https://www.linkedin.com/in/rkots/">Rakesh Kothari</a>, <a href="https://www.linkedin.com/in/mattjamesboyle/">🌍Matthew Boyle</a>, <a href="https://www.linkedin.com/in/anish-agarwal-io/">Anish Agarwal</a>, <a href="https://www.linkedin.com/in/richarddcrowley/">Richard Crowley</a>, <a href="https://www.linkedin.com/in/lalkaka/">Rustam X. Lalkaka</a>, <a href="https://www.linkedin.com/in/seshendranalla/">Sesh Nalla</a>, <a href="https://www.linkedin.com/in/yyemini/">Yotam Yemini</a> for sharing invaluable insights and the time spent helping me shape this article 🙏</p><p>If you’re working on something in this space, see the world differently or want to discuss any of the points above, I would love to continue the conversation. You can reach me at megan at vvus dot com and if you’re leading engineering teams or building at the frontier of software infrastructure and AI, <a href="https://forms.gle/voc6QjjkAhskXNuq9">sign up here to join the next</a> <a href="http://infra.community/">infra.community</a> <a href="https://forms.gle/voc6QjjkAhskXNuq9">meet-up</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd24a3cec94d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vvus/from-reactive-to-predictive-entering-the-ai-era-of-observability-dd24a3cec94d">From reactive to predictive: Entering the AI era of observability</a> was originally published in <a href="https://medium.com/vvus">Vertex Ventures US</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>