Metrics That Matter: Proving Value to Technical VCs

Transcript

SPEAKER_1: Last time we landed on mission criticality as the core positioning move. Now I want to push into the numbers—what does a founder actually bring into a partner meeting? SPEAKER_2: Right, and this is where technical founders often trip up. They assume strong ARR carries the room. But technical VCs want to see whether the product is changing how engineering teams actually perform. SPEAKER_1: So what's the first metric an investor reaches for in this space? SPEAKER_2: The DORA metrics. Deployment frequency, lead time for changes, change failure rate, and mean time to recovery. Research has directly linked improvements in those four measures to better profitability and market share. When a founder shows their tool moved a customer from weekly deploys to daily, that's a business outcome—not a feature claim. SPEAKER_1: What does the benchmark actually look like? 'More frequent deployments' is vague without a reference point. SPEAKER_2: Top-performing DevOps organizations deploy multiple times per day. Lead times—from code commit to production—are measured in hours, not weeks. The gap between elite and low performers is enormous. If a startup's tool can move a customer from the bottom quartile toward the top, the business case writes itself. SPEAKER_1: But here's what I'd push back on—can't a founder just show strong ARR growth and call it a day? SPEAKER_2: ARR tells you what happened. It doesn't tell you whether the product survives a budget cut. Technical VCs want net dollar retention above 120%, which signals existing customers are expanding—adding more services, more environments, more data. That expansion pattern separates a sticky infrastructure tool from a line item that gets rationalized away. SPEAKER_1: So the expansion story matters as much as acquisition. Think of Datadog—textbook land-and-expand, right? SPEAKER_2: Exactly. Investors track cohort expansion over time, not just total ARR. A customer who started monitoring ten hosts and now monitors five hundred—that trajectory is the real signal. It also connects to usage-based pricing: when revenue scales with data ingested or compute minutes consumed, growth becomes almost automatic as customers' own businesses grow. SPEAKER_1: Now, what about pre-revenue founders? A founder who's early-stage, without meaningful ARR—can they even get a serious meeting? SPEAKER_2: Some technical VCs will back pre-revenue DevOps tools if developer adoption is exceptionally strong. GitHub stars, downloads, active open-source contributors—these become proxies for future monetization. The key idea is that community engagement signals organic traction paid marketing can't replicate. But investors also discount vanity metrics. Raw star counts without conversion data don't move the needle. SPEAKER_1: So what does community depth actually mean beyond stars? Give me something concrete. SPEAKER_2: Think of it as the difference between passive interest and active dependency. Investors want free users converting to paid, contributors opening pull requests, self-serve signups growing week over week. Platform extensibility matters too—the number of integrations or partners building on top of the tool tells investors whether a startup is becoming a platform or staying a point solution. SPEAKER_1: There's also the Rule of 40—VCs keep referencing it. What's the actual definition? SPEAKER_2: It combines revenue growth rate and profit margin. If those two numbers add up to 40% or more, investors read that as a healthy balance between growth and efficiency. For cloud infrastructure and DevOps businesses, gross margin is a critical metric; successful software and cloud platforms typically exhibit gross margins in the 70–80% range. If margins are compressing, it raises immediate questions about infrastructure cost discipline. SPEAKER_1: And revenue quality matters too, not just the headline number. SPEAKER_2: Absolutely. Investors scrutinize the mix of subscription versus services, multi-year contracts versus pilots, broad-based growth versus spikes from one or two large accounts. A sudden usage spike from a single customer looks like risk, not traction. For observability tools specifically, very high data volumes not normalized against revenue can actually signal poor cost discipline rather than product success. SPEAKER_1: So the takeaway for everyone building in this space: don't just collect metrics—connect them to outcomes. SPEAKER_2: That's exactly it. That maps directly to ROI for the buyer and de-risks the thesis for the VC. Remember, a relatively small improvement in recovery time can have outsized economic impact in high-stakes industries. Metrics without that business translation are just numbers on a slide.