What VCs Look for
in Developer Tools.
VCs evaluating a DevTools company are reading the same artifacts the developer audience reads — just with different questions. The signals that matter for fundraising and the signals that matter for product-market fit are mostly the same signals, observed twice. A practitioner walkthrough for founders preparing rounds and VCs sourcing in the category.
By Daria Dovzhikova · Updated May 2026
TL;DR
- The signals VCs weigh in DevTools deals are the same signals product-market fit produces: organic top-of-funnel, measured activation, cohort retention, founder-led growth, frictionless pricing.
- The pitch fails on positioning roughly as often as it fails on numbers. A team that cannot name the honest competitive alternative (usually OSS or a hand-rolled tool) has not done the customer work.
- DevTools companies are not slow-motion B2B SaaS. The evaluation surface, retention metric, and channel mix differ enough that mispricing a DevTools deal as a SaaS deal is a common diligence error.
Why DevTools diligence diverges from SaaS diligence
A B2B SaaS deal is diligenced through pipeline coverage, logo concentration, ACV trends, and net retention. A DevTools deal has those numbers too, but the signal-to-noise is different. Most DevTools companies at Series A still have lumpy revenue concentrated in a few enterprise contracts; the leading indicator of where the company will be at Series B is the self-serve activation curve, not the named-account list.
That changes what diligence weights. The product evaluation surface — docs, free tier, OSS adjacency, sample code — is the actual sales surface, so it gets read carefully. The activation cohort is the company's product-market-fit measurement. The retention curve on weekly active developers (not logos) is the rough north-star metric the board will steer to. Most DevTools companies that look weak on traditional SaaS metrics are strong on these; companies that look strong on SaaS metrics but weak on these are usually overvalued.
David Skok's SaaS Metrics 2.0 is the canonical reference for the underlying math. The OpenView SaaS Benchmarks give a year-on-year benchmark for the absolute numbers (gross retention, CAC payback, ARR growth). What this page adds is the DevTools-specific overlay that adjusts those benchmarks for the bottoms-up motion.
Five signals VCs actually weight
Not the only signals — there are dozens, and stage-dependent. These are the five that almost every DevTools-focused fund checks early, before the deeper diligence opens.
Signal 01: Top-of-funnel that breathes without paid
VCs at seed and Series A want to see organic signups arriving from docs SEO, OSS adjacency, conference talks, or community presence. Paid acquisition is fine as a top-up; as the primary engine of top-of-funnel at Series A, it is a yellow flag. The underlying question: when you take the marketing budget to zero next month, does the funnel still produce signups?
Signal 02: Activation rate measured and improving
Activation in DevTools is usually defined as the developer completing the quickstart and the product doing something useful. The exact rate varies by category; the existence of the measurement and a trend line is the signal. A team that cannot tell you their 7-day activation rate has not yet treated the funnel as a product surface.
Signal 03: Retention on a cohort basis
Weekly-active-developer retention at 30, 60, 90 days, cut by signup cohort. Pricing-page conversions and revenue retention come downstream. The cohort retention curve is the highest-information artifact a DevTools company can show — it captures product-market fit more accurately than topline revenue.
Signal 04: Founder-led growth proof
A founder who has built audience in the category — meaningful following in the relevant developer community, a published OSS project, a talk track that gets accepted at the right conferences, a blog that ranks for category queries. At seed this is sometimes the entire bet. Founder distribution compounds; teams that lack it usually have to pay for distribution they cannot afford.
Signal 05: Pricing that does not gate evaluation
Public pricing page. A free tier that lets a developer evaluate without contacting sales. Tiers that map to usage primitives the developer audience already understands. Pricing decisions made by people who have priced developer tools before — not pricing decisions copy-pasted from a generic SaaS playbook.
How DevTools diligence differs from B2B SaaS diligence
Same job title on the partner's LinkedIn; different artifact set on the diligence checklist. Five axes where the two motions diverge — the right column is what a DevTools-aware VC actually weighs.
| Axis | Standard B2B SaaS lens | DevTools lens |
|---|---|---|
| North-star metric | ARR growth, net retention | Weekly active developers, activation cohort, paid retention |
| Top-of-funnel | Pipeline coverage, marketing-sourced leads | Organic signups, GitHub trending, docs SEO, OSS pulls |
| Proof artifact | Logo slide, analyst report, ROI deck | Working code, public docs, dependent projects, GitHub stars |
| Pricing surface | Custom quotes, RFP-driven | Public page, free tier, usage tiers |
| Founder edge | Industry tenure, ex-Big-Co | Audience reach, OSS history, technical depth in the category |
The shared spine is unit economics. The right column reflects how a developer audience signals product-market fit before the unit economics are clean enough to read.
By the numbers
Three figures that frame what VCs underwrite when they fund a DevTools company — where the category is heading, the unit economics that make it fundable, and the discovery surface it compounds on.
Share of developers using or planning to use AI tools in their work, up from 70% the previous year. The DevTools category VCs are funding is shifting under their portfolios in real time — AI-adjacent positioning is now table stakes, not differentiation.
Stack Overflow Developer Survey · 2024→The LTV-to-CAC ratio David Skok identifies as the floor for a healthy SaaS business — best operators run 7-8:1 and recover CAC inside 5-7 months. A DevTools company that can't reconcile to these unit-economics gates is hard to underwrite, however large the audience.
David Skok — SaaS Metrics 2.0, ForEntrepreneurs · 2024→Projects on GitHub at the close of 2024. The discovery surface for developer-first products keeps compounding. DevTools companies that earn presence on GitHub get a moat that does not require capital to defend.
GitHub Octoverse · 2024→What founders should prepare before the pitch
The artifact set is small and concrete. A team that arrives with all five looks meaningfully more credible than one that arrives with the deck alone.
A positioning statement. The internal document that names category, alternatives, value, and target market. The positioning a developer tool guide covers the structure. VCs do not need to see the statement; they need to hear it spoken cleanly inside the first ten minutes.
A weekly-active-developer chart. Cohort retention by signup week, last six months. If the numbers are small, show the trend; if the trend is flat, show the activation curve underneath. The chart is the closest thing to a product-market-fit thermometer in DevTools.
A docs page that activates a developer. The same docs page the audience evaluates against. VCs read it during the meeting; the partners who do not are reading it later. Treat it as a fundraising artifact, not engineering output.
A pricing page that closes. Public pricing, a free tier, tiers mapped to a primitive the buyer understands (seats, projects, request volume, retention window). If the pricing page is gated, expect the partner meeting to slow down on the same objection a developer would have raised in the first ten minutes of evaluation.
One named design partner. Even at seed. The signal is not the contract size; it is that someone has chosen to spend their political capital adopting the product internally. Lenny Rachitsky and April Dunford's advanced B2B positioning guide is the closest thing to a working method for naming that first design partner clearly enough that the rest of the GTM can be built around them.
What VCs should diligence beyond the deck
Three diligence moves that DevTools-aware funds run as a matter of course, and that generalist B2B SaaS funds tend to skip.
Run the quickstart.A partner or analyst should be able to complete the docs landing's quickstart in under thirty minutes. If the quickstart does not work, the audience has noticed before you did. If it works and is elegant, the activation funnel is already a moat.
Read the GitHub issues.The tone of issue responses tells you more about the team's relationship with the developer audience than any reference call. Slow, defensive, or non-existent responses are a red flag even when the revenue numbers look fine.
Cross-check the founder's public presence. Conference talks, OSS contributions, technical writing, podcast appearances. Founder distribution compounds; an audience the founder already has is the cheapest GTM channel the company will ever own. The developer marketing reference covers what credible founder distribution looks like.
Common mistakes on both sides
- Founders pitching as if DevTools were a flavor of B2B SaaS. The metrics that matter are different; pitching the SaaS-flavored deck to a DevTools fund is the fastest way to look unprepared.
- VCs pricing a DevTools deal as if it were a SaaS deal. Lumpy enterprise revenue with strong self-serve usage is a different shape from clean ARR with no self-serve. The first is usually undervalued; the second is sometimes overvalued.
- Skipping the docs in diligence. The product's docs are the diligence artifact. Reading them is the cheapest, most informative thing a partner can do.
- Treating logos as the proof of GTM. Logos are a snapshot. The activation curve is the trend. The trend is the prediction.
- Founder-led growth at Series B. Founder distribution is the right answer at seed and Series A. Companies that still depend on founder reach at Series B have a GTM team they have not yet built.
- Hiring an enterprise PMM by default. The hire kills the bottoms-up motion. The developer-first PMM reference covers what to screen for instead.
The author
Daria Dovzhikova is a fractional PMM with 12 years inside developer-first companies, including 7 years at JetBrains and senior roles at Lightrun and Odigos. She has helped DevTools founders prepare for seed and Series A fundraises, sat in on partner meetings, and advised investors on GTM diligence questions for early-stage portfolio adds. For the broader engagement format, see the VC services page or about.
FAQ
What is the single signal a DevTools VC weighs most heavily at seed?
Founder-product fit on the technical side. At seed there is rarely enough data to evaluate the GTM motion, so the bet is on the founders' ability to ship a credible artifact and convene the right developer audience. A technical founder who has built one of the integrations they are pitching, or who has earned audience trust in the category, is worth a multi-turn meeting even with weak numbers. A non-technical founder pitching a DevTools company without a technical co-founder is the most common reason seed rounds stall.
At Series A, what numbers should a DevTools company have?
Specific signals, not specific dollar amounts. A self-serve top-of-funnel that is generating signups without paid acquisition. An activation rate that has been measured for at least two quarters. A weekly-active-developer cohort that is retaining at 30 days. At least one design partner or pilot that converted to paid. Some component of the revenue (even $500K ARR) should be in self-serve or low-touch channels rather than entirely founder-sold. OpenView and Bessemer publish reasonable benchmarks; the exact thresholds shift with the market but the shape of the picture does not.
How do VCs evaluate the difference between a DevTools company and a SaaS company at the same stage?
Three differences. The buyer evaluation surface (docs, free tier, OSS adjacency) carries more weight than sales pipeline depth. The activation funnel matters more than logo count. And the bottoms-up adoption story has to be visible — usage stats, dependent projects, community references — even when the revenue is still concentrated in a few enterprise contracts. A DevTools company that looks like a SaaS company in every metric except product-led activation is usually mispriced as a SaaS company.
What kills a DevTools pitch in the first meeting?
Generic positioning is the most common one — "the modern observability platform" or "AI-powered developer productivity" signals the team has not done the positioning work. Inability to articulate the competitive alternative honestly (especially when the honest answer is "a Prometheus + Grafana stack the team already runs") signals the team has not done the customer interviews. And a pricing page that is gated behind a sales call signals the team does not actually believe in product-led growth, regardless of what the deck says.
Should a DevTools founder hire a PMM before raising?
Probably not full-time. A fractional or advisory engagement to set up the positioning and the launch artifacts is usually enough to make the pitch credible. The internal hire becomes worth it after the round closes and there is operating capital to support a team. The signal VCs are looking for at the pitch stage is that the founder understands developer-first PMM exists as a discipline, not that they have already built the team to run it.
Related reading
- For VCs — engagement formats for portfolio GTM diligence and post-investment support.
- Developer-first PMM — what the PMM hire actually does inside a DevTools company.
- Go-to-market strategy — the wider GTM frame VCs read against.
- Product-led growth — bottoms-up activation as a motion VCs underwrite.
- Case studies — DevTools GTM work I have run pre- and post-fundraise.
Raising soon, or diligencing a deal?
Get the DevTools-specific GTM read.
Pre-fundraise positioning, deck read-throughs, partner-meeting prep for founders; GTM diligence and portfolio reviews for funds. Fractional PMM with 12 years of DevTools operating experience.
See VC servicesReady when you are.
Discovery calls are 20 minutes. First one's on me.