Technology, Media & Healthcare

How to Underwrite an Infrastructure or DevTools Company

Underwrite an infrastructure or DevTools company by separating committed contract revenue from variable usage, then testing gross margin after cloud costs and the conversion of free or open source users into paying accounts. Key metrics are committed versus on-demand revenue, net revenue retention driven by consumption, gross margin after hosting, and enterprise customer count.

What makes infrastructure / devtools software underwriting different

Infrastructure and developer tools companies sell databases, observability, security, CI/CD, APIs and cloud services to engineering teams. Many grow bottom-up: developers adopt a free tier or open source project, then teams convert to paid plans and enterprises sign committed spend contracts. Value comes from deep technical integration, consumption that grows with customers' own workloads, and strong expansion revenue. Risk comes from usage that can fall quickly when customers optimize cloud spend, thin gross margins when the company resells compute or storage, competition from cloud providers' native services, and open source projects that competitors can fork or host.

Lenders find usage-based revenue harder to underwrite than seat-based subscriptions. They focus on committed contracts, minimum spend agreements and gross margin after infrastructure costs, and they discount on-demand usage that can decline without notice. Equity investors underwrite expansion potential: consumption growth inside existing accounts, the conversion funnel from free users, the size of the developer community and the product's position in the technology stack. They pay premiums for net retention driven by real workload growth rather than by one-time data migrations.

Key metrics

Committed vs on-demand revenue

Committed spend contracts are contractual and predictable, while pay-as-you-go usage can fall when customers optimize.

Consumption-driven net retention

Growth in existing accounts is the main growth engine, but it reverses quickly when customers cut cloud budgets.

Investors often expect infrastructure companies to show NRR well above 100 percent, and they look for stability through optimization cycles.

Gross margin after hosting

Companies that run workloads on public cloud carry significant cost of revenue, and pricing must cover it.

Free to paid conversion

Shows whether community adoption turns into revenue, which matters for open source and freemium models.

Customers above a spend threshold

Growth in large accounts indicates enterprise adoption and more durable revenue.

Remaining performance obligations

Contracted but unrecognized revenue gives visibility into committed future revenue.

How to underwrite it, step by step

Separate revenue into committed contracts, on-demand usage, support and services, and reconcile to billing data.
Analyze consumption trends by customer cohort, including periods of customer cost optimization.
Calculate gross margin after cloud hosting, third-party services and support, and review cloud provider commitments.
Review the open source license, community metrics and the commercial features held back for paid tiers.
Assess competitive exposure to cloud provider native services and open source alternatives.
Examine enterprise contracts for minimum commitments, overage pricing and rollover of unused credits.
Model revenue sensitivity to declines in usage and lower conversion rates.
Size debt on committed revenue and stable usage, with liquidity covenants for unprofitable companies.

Due diligence checklist

Customer-level usage and billing data by month
Enterprise contracts with committed spend and overage terms
Remaining performance obligations schedule
Cloud provider invoices and committed use agreements
Gross margin bridge showing hosting and support costs
Open source license and contributor license agreements
Community and adoption metrics such as active users and downloads
Free to paid conversion funnel data
Security certifications and incident history
Product roadmap and competitive analysis

Key risks and mitigants

Customer cost optimization reduces usage

Stress usage revenue for declines seen in prior optimization periods and size debt on committed revenue.

Margin squeeze from cloud costs

Review cloud commitments and pricing, and model margins if hosting costs rise or discounts expire.

Open source fork or cloud provider competition

Assess license protections, proprietary features and switching costs, and avoid aggressive growth assumptions.

Committed contracts with unused credits

Analyze credit consumption against commitments to predict renewal risk.

Security incident in critical infrastructure

Review security practices and incident response, confirm cyber insurance, and require breach reporting.

Typical financing and deal structure

Growth-stage infrastructure and DevTools companies typically raise venture equity and supplement it with venture debt or recurring revenue loans. Lenders size facilities on committed recurring revenue and stable usage, apply minimum liquidity covenants, and often take warrants. Profitable companies may access larger unitranche or term loan facilities sized on EBITDA. Because usage revenue can be volatile, lenders sometimes base availability on a trailing average or on committed contract value rather than peak monthly revenue. Acquirers of DevTools companies are often larger software firms paying in cash or stock, with earnouts tied to revenue or product milestones and retention packages for core engineering teams and open source maintainers.

Red flags

Most revenue from on-demand usage with no committed contracts
Gross margin falling as usage grows, signaling underpriced infrastructure
Large customers consuming far below their commitments ahead of renewal
A permissive open source license that lets cloud providers offer the product as a managed service
Net retention driven by a few large customer migrations rather than broad expansion

Frequently asked questions

How do you value a usage-based software company?

Usage-based companies are typically valued on revenue multiples tied to growth and net retention, with adjustments for gross margin. Investors examine how much revenue is committed versus on-demand and how consumption behaved during cost optimization periods. Higher gross margins and committed contracts generally support higher valuations.

Can open source companies get debt financing?

Yes, once they have meaningful paid revenue. Lenders underwrite the commercial revenue base, not the community size. They look at committed contracts, retention and burn, and they typically require minimum liquidity covenants. Venture debt is common for venture-backed open source companies, and lenders may take warrants alongside the loan.

Why does gross margin matter more for infrastructure software?

Infrastructure products often run on public cloud, so each unit of customer usage carries real hosting cost. If pricing does not keep pace with cloud costs, margins shrink as the company grows. Underwriters review cloud contracts and cost per unit of usage to make sure growth improves rather than dilutes profitability.

What happens to DevTools revenue when customers cut cloud budgets?

Usage-based revenue can decline quickly as customers reduce data retention, compute or API calls. Committed contracts provide some protection, but customers may consume less and renew at lower commitments. Underwriters review cohort usage during past optimization periods to estimate how much revenue is at risk.

Underwrite a infrastructure / devtools software deal in minutes

Drop a deck or data room. Underridge returns a verdict, investment memo, term sheet and a live model, with every headline figure traced to a page, a formula or a labeled assumption. Ten underwrites free.

Try Underridge free

Educational content, not investment, credit, legal or tax advice. Benchmarks are common practitioner rules of thumb and vary by lender, market and cycle.