Ben Werther

Reading Metronome’s Monetization Operating Model, I kept coming back to one idea: pricing has become product. Software now delivers outcomes, not access. Yet most companies still charge as if they’re selling seats or licenses. That disconnect creates friction: for customers, unpredictability; for companies, stalled growth. The paper’s argument is simple but sharp—monetization isn’t a late-stage decision. It’s strategic infrastructure. Pricing needs the same ownership and iteration as any feature. Treat it like a surface that customers touch, not a spreadsheet buried in finance. If value is continuous and dynamic, pricing must be as well. That means product, GTM, finance, and engineering working from one system of truth. How many of us still treat pricing as an afterthought—when it should be a growth engine? https://lnkd.in/gnH7WzYf #Monetization #ProductStrategy #AI

8

Thrilled to announce that Together Fund is investing in Sentra, alongside a16z speedrun! You track results in Jira. Decisions in Notion. Conversations in Slack. But the reasoning, the debates, trade-offs, and context behind why you chose A over B, disappears into what we call "Dark Matter." A decision made in March looks insane by July because no one remembers the constraints that made it smart. I lived this firsthand at Twitter scaling from 800 to 8,000 employees, and at Google while launching AI Overviews to billions at planet scale. The problem isn't process. Process is compensation for something deeper: organizational amnesia. An organization’s "Systems of Record" doesn’t solve this, they encode it. They store what happened, never why. That's why we are investing in Sentra. Sentra is the always-on collective memory that eliminates organizational amnesia by maintaining accurate context for all members and agents, functioning as an operational nervous system. It connects to every channel where work happens, meetings, Slack, email, code commits, docs, calendars, and treats them not as artifacts to search, but as living signals to synthesize. The fleeting and the permanent, unified into a memory that understands. The founding team is built for this: - Jae Gwan Park (CEO): Product-first founder, memory systems research at UofT and MIT - Ashwin Gopinath (CSO): Former MIT professor, created "Reflexion" (NeurIPS 2023), agents that learn from mistakes, 2x founder - Andrey Starenky (CTO): Early Vapi engineer, ex-IBM, built to process enterprise-scale data firehose Together is an operator-led fund. We invest in problems we've lived. This is one of them. Many congrats Jae, Ashwin and Andrey, we are so excited to partner with you! Read the full thesis: https://lnkd.in/gixj9cE4 Book a demo: https://www.sentra.app/ #OrganizationalMemory #AI #Sentra #TogetherFund #a16z #ContextGraphs

71

3 Comments

The hottest role in AI startups right now isn’t Forward Deployed Engineers. It isn't GTM Engineers. It’s Deployment Strategists. Decagon calls it an “Agent Product Manager.” Harvey calls it a “Solutions Architect.” Palantir Technologies has had versions of this role for years. And the salaries are climbing fast: - Decagon: $200k–$285k - Palantir Technologies: $120k–$200k - Figma: $150k–$260k - Ramp: $100k–$180k - Harvey: $190k–$260k So who are these people? They are usually pseudo-technical -- CS or engineering majors, or folks with technical work experience. Many come from 2 years in consulting, IB, or PE, then jump into startups to get their hands dirty. They are young, hungry, polished, and comfortable being in front of customers. What do they actually do? They make sure enterprise AI deployments succeed. A $100k+ deal does not survive on a nice pitch or a self-serve onboarding flow. It survives if the customer sees value in the pilot. That means: - Embedding directly with the customer - Designing prompt logic for specific workflows - Working with engineering to align integrations and data flow - Helping exec teams define their AI roadmap - Running feedback loops into product and GTM Why does this role matter so much? Because enterprise AI is messy. Integrations, data transfer, and adoption make or break a deal. Most buyers are using AI for the first time, and each has unique workflows. Deployment Strategists bridge that gap. They own the outcome. They are accountable for making pilots successful, which often means millions in revenue down the line. At Conversion, Sam Bochner has been leading this work for us. We are now thinking about scaling it into a full team. Because a few successful pilots can fund an entire department, and the cost of failed deployments is too high to ignore. Is this just a rebrand of customer success? Not really. Success is about answering tickets and renewals. Deployment Strategy is about going deep with a few enterprise accounts, extracting maximum value, and ensuring the pilot closes into a multi-year contract. Call it Agent PM, Solutions Architect, or Deployment Strategist. Whatever the title, this is becoming one of the most important roles in AI SaaS.

657

92 Comments

I had a great time chatting with Patrick O'Shaughnessy on Invest Like The Best. I've known Patrick since college, and this is the first time we've talked markets and investing at this much depth. The fundamentals of company building haven’t changed: people, products, and markets matter. But obviously, private markets have evolved substantially over my career: there are now ~6x more private unicorns than public companies with a $1b+ market cap. And at the end of 2010, just 2 public technology companies were among the top 10 in market cap; today it’s 8 of 10. AI (alongside software eating everything more generally) is clearly driving a lot of this. But it’s instructive to look at everything from the steam engine, to the early days of Facebook and Google user monetization, to real-time success stories like Databricks, Anduril, OpenAI and Waymo, to get a clear picture of where the opportunities lie. It was a pleasure to go deep on all this and more!

131

9 Comments

CRV Security: Request for Startups I never know if this actually works for our friends over at YC but figured we'd try. Here's what we want to fund in 2026! 1. Golden Artifacts: Think Chainguard but more broad. Artifact attestation exists for open source. Almost nothing exists for internal software — especially the vibe-coded tooling now running in production. We want the company building cryptographic proof of secure software delivered from secure artifacts: who built it, how, and whether it was reviewed. If more things are being yeeted into the world via Claude Code (myself included), this feels like an issue. 2. MCP & Agentic Security: Agents are getting real credentials and taking real actions. The security posture of most orgs around this is basically zero. That changes fast. You'd never give an employee hardcoded API keys or write access to your email without supervision/trust. Why give it to agents? 3. AI Governance: Boards are asking CISOs to account for AI risk. CISOs have no good answer other than "Palo has a module" 4. Next-Gen Endpoint: CrowdStrike was built for a world of static binaries and human operators. AI workloads, cloud-native infra, and AI-assisted attackers need a new architecture. The category is ready to be reinvented. 5. Networking in the AI Era: Zero trust was designed for humans. What does network security look like when the entity requesting access is an agent? Nobody's really solved this. 6. Email Security + Next-Gen Phishing: LLMs have made spear phishing infinitely scalable. I've never truly understood why Abnormal and KnowBe4 aren't one company. Maybe this time it's different. 7. Frontier Security Lab: We'd back a credible, well-staffed lab focused entirely on red-teaming models and setting the evidentiary standard the industry needs as LLM built apps become the norm. 8. Dependency Security: That Actually Remediates Malicious and vulnerable dependencies are a top attack vector. The tooling is mostly noise — scanners that don't close the loop. The winner here ships fixes, not just alerts. 9. Critical Infrastructure Cyber: Data centers, satellites, power grids, undersea cables. The physical backbone of the internet is increasingly exposed and wildly under-defended. We have data centers in space, for God's sake. Surely we need better cyber for critical infrastructure? 10. PAM for the Modern Era Legacy: PAM was built for static roles, human users, on-prem directories. Cyberark was founded in 1999.....Agents, ephemeral workloads, and cloud-native infra have broken all of those assumptions. Is anyone rebuilding this from scratch? If you're building in any of these areas — or something we haven't thought of — reach out. james@crv.com

451

49 Comments

Ontologies remain one of the most effective ways to ground AI memory, keeping extracted knowledge anchored to existing structures and adaptable through feedback. As memory systems evolve, their role remains essential, and a core focus at Cognee.

47

4 Comments

Cloud cost uncertainty isn’t a fluke; it’s by design. Cloud providers profit from complexity: 💸 Granular billing 💸 Shifting discount programs 💸 Opaque pricing for AI workloads 💸 Exploding SaaS and shadow IT The result? Engineering and FinOps leaders are left scrambling to explain unpredictable cloud bills while innovation can’t slow down. Traditional dashboards and static budgets won’t save you. You need adaptive cloud cost management that embeds cost awareness into engineering workflows, detects anomalies early, and drives shared accountability. We break it all down in our latest post, including 5 steps to start leading through the chaos. Read it here: https://lnkd.in/ge4jadxr #FinOps #CloudCost #EngineeringLeadership #CloudComputing #AI #SaaS #Ternary

35

1 Comment

Marcus built his tech company from a garage startup to a $50 million enterprise. His board celebrated record growth. His employees admired his vision. His investors praised his strategic brilliance. Yet in the quiet moments between meetings, he struggled with something he couldn't discuss with anyone: a persistent sense that he was failing at everything that mattered. His marriage was strained. His sleep was fragmented. His confidence in major decisions had eroded to the point where he'd spend hours second-guessing himself. When his CFO mentioned therapy, Marcus dismissed it immediately. CEOs don't have time for that, he thought. More importantly, what would happen if word got out? The research tells a different story: → 55% of CEOs experienced a mental health issue in the past year (up 24 points from previous year) → 50% report feeling lonely in their roles → 61% believe this isolation negatively impacts their performance → 81% believe organizations view mental health issues as weakness → 70% of C-suite leaders seriously considered quitting for roles that better support their wellbeing Here's what most people miss: the very traits that propel someone to the CEO role—relentless drive, high standards, comfort with risk, the ability to compartmentalize—can become liabilities when psychological strain reaches a critical point. The isolation of leadership creates a perfect storm: immense pressure combined with virtually no safe outlet for processing it. Addressing these challenges doesn't compromise your leadership. It enhances it. https://lnkd.in/gJdyKVJd #CEOMentalHealth #Leadership #ExecutiveWellbeing

1

Key takeaways: - The core shift is economic, not hype. LLMs turn “AI” into a recurring operating cost, so pilots quickly become capacity planning, governance, and ownership. - Power and timelines show up because production inference needs sustained compute capacity. When usage increases across the org, you run into procurement, security review, integration work, and infrastructure readiness challenges. - The winners are not the teams with the flashiest demos. The winners are the teams that convert compute into measurable outcomes inside a workflow with traceability and controls. - In 2026, “AI strategy” that is not tied to a specific workflow, KPI, and operating model is mostly theater. If you are building the application layer on top of the datacenter buildout, execution systems, workflow automation, data-layer tooling, compliance automation, I want to see what you are shipping. Founder intro: www.axion.ventures

6

It’s time to be real about what HTAP actually means and how to implement it in a way that supports agents and other similar workloads…

11

This section on how dbt Labs transitioned from a purely PLG motion to layering on enterprise is a fascinating one. Two instructive passages that I have bolded (below from First Round Review's path to PMF series featuring dbt Labs) TLDR: GTM comprises your ICP, channel, and message. When you transition from PLG / bottom up to Enterprise / top down motion, naturally your ICP and channel also changes, but your messaging / proposition needs to change too, e.g., the enterprise may be multiple personas and are buying assurance as much as solution. --- "Handy found product-market fit organically for dbt as an open-source tool mostly used by data practitioners and developers. But a few years into running a commercial business, he realized he had to build a growth curve all over again with C-suite data leaders. “Even though we had an unbelievable amount of market pull, as we initially commercialized, it wasn’t easy for us to transform this open-source command line tool into a product that enterprises would pay a million dollars for,” says Handy. “When you have enough product-market fit, sometimes it allows you to get away with not being super tight on product marketing or sales motions. So around 2022, we went from this gigantic acceleration curve and overnight we realized, we have to sit at the adults’ table and figure things out real fast,” says Handy. After the PLG flame started to fizzle, Handy turned his attention to layering on a sales-led motion for the cloud platform. “We had to focus our efforts on telling cohesive stories to senior data leaders. We had to have a very clear, explainable answer to the question, ‘Why should I use the commercial product and not the open-source product? And it had to be digestible by someone with a C in their title,” he says. Handy’s answer: dbt Cloud can handle complex data for companies of every size. “The longer people used dbt, the more complex their code became,” he says. “It was a problem for the most sophisticated dbt users, who were often at the largest companies. So there was a real opportunity for us to step in and solve that for them with dbt Cloud.” To tell that story to enterprise customers, Handy relied on data, naturally. “At a user conference we presented a chart that showed the number of dbt projects that had a certain number of models in them — over 100, over 1,000, et cetera,” he says. “We watched that number climb and we knew as users ourselves, ‘Oh my God, trying to work in a dbt project with 5,000 models in it is challenging.’ So we started with that quantitative data point and asked folks in our community about their experiences with these very large, complex dbt projects, and validated that this was a pain in the ass without a cloud platform.”

23

4 Comments

AI is reshaping every industry — and VC is no exception. great catching up with Nathaniel Barling, operating partner at Andreessen Horowitz, who leads a 10-person engineering team building internal AI tools to supercharge their VC workflows. 🚀 at Creandum, we’re right there on the same journey. Over the past year, we’ve rolled out multiple AI-enabled apps (some built with Lovable ofc 😎) that now power everything from sourcing + dealflow analysis to portfolio management. the productivity impact is real — and we’re only just getting started. in VC (like everywhere else): adapt and embrace…or get run over. ⚡️

204

11 Comments

JFrog’s Earnings Leap: Hopping Past Wall Street’s Cloud Rev Forecasts (and Competitors) – ( $FROG $SPY ) https://lnkd.in/gE_hMhKQ JFrog showcased impressive growth in Q3 2025, combining software innovation, cloud momentum, and AI advancements #JFrog #EarningsLeap #FROG #CloudGrowth #DevOps #DevSecOps #AI #SoftwareSecurity #RevenueSurge #MarketLeaders #TechnologyStocks #InvestorConfidence #FinancialResults #QuarterlyEarnings #GrowthStock #SoftwareSupplyChain #Innovation #WallStreet 

1

Worth paying attention to... Anthropic vs. Cursor. While Cursor was paying Anthropic hundreds of millions in API fees to power its AI code editor, Anthropic seems to have studied exactly what developers wanted, then launched Claude Code to "eat" their biggest distribution partner. The result. Claude Code hit $1B ARR in just six months and has already surged past $2.5B, proving that when you're a "wrapper" startup, you're often just paying your provider to learn how to replace you. Keep an eye on Cursor layoffs...

89

13 Comments