ZoomInfo (GTM) Q1 2026 Earnings Call Transcript

ZoomInfo reported Q1 revenue of $310 million (+1.5% YoY) and adjusted operating income of $110 million, both above guidance, but cut FY2026 revenue outlook to $1.185 billion-$1.205 billion, implying a 4% midpoint decline. Management also announced a major restructuring affecting 20% of employees, or about 600 roles, with $45 million-$60 million of charges and $60 million of annual run-rate expense savings, while continuing a $90 million share repurchase in the quarter. The company is shifting to a hybrid consumption model tied to AI and data usage, but near-term guidance reflects software-sector weakness, buyer hesitation, and revenue recognition variability.

Analysis

This is less a clean beat than a controlled reset. The important signal is that management is choosing to protect long-term monetization of its data layer by deliberately impairing near-term seat-based revenue, which means the stock is now trading on execution of a business-model migration rather than simple earnings quality. That creates a sharper bifurcation: if consumption adoption shows up in renewals by late 2026, the multiple can expand quickly because the market will re-rate the company as a data infrastructure asset; if it does not, the company risks being treated as a shrinking legacy SaaS book with a stronger margin profile but lower terminal growth.

The second-order winner is CRM/HUBS, not because they win outright, but because ZoomInfo’s pricing shift validates the broader CRM ecosystem’s move toward embedded AI workflows. As data access becomes more modular, CRM platforms that control the workflow surface can intermediate the spend, while independent data vendors have to compete on utility and portability. That said, the real competitive pressure is not from the named peers but from internal customer-built tools plus model-native interfaces; the more enterprises normalize buying data credits instead of seats, the more procurement gets comfortable replacing point SaaS modules with usage-based data budgets.

The key risk is timing mismatch: the cost takeout is immediate, but the revenue model transition likely creates several quarters of weaker reported growth before consumption offsets seat compression. That makes the next 2-3 quarters a sentiment trap—operating leverage can look good while top-line optics worsen, and any soft macro or software-specific hesitation would push out the inflection into 2027. The contrarian point is that the downgrade may already be discounting the wrong endpoint: a business with 37% margins, strong FCF conversion, and buybacks at sub-$7 has optionality if management is right about the data layer becoming the default AI input.

The cleanest tell will be whether Operations/DaaS remains >20% growth while NRR holds near 90% through the pricing transition. If that mix shift holds and larger customers keep expanding through API/MCP consumption, the downside case narrows materially; if not, the company is just pre-loading cost cuts ahead of a slower decay curve.

Key Decisions for Investors

• Short GTM into the next 1-2 quarters of guide-down digestion; risk/reward favors a fade if the market overprices the margin story before consumption revenue is visible. Use a tight stop above the pre-announcement level if management shows any improvement in software renewals.
• Pair trade: long CRM / short GTM for 3-6 months. CRM can capture the workflow-layer monetization from embedded AI, while GTM absorbs transition risk from seat compression and revenue-recognition noise.
• Own HUBS vs GTM on a relative basis for 6-12 months. HubSpot’s native distribution into SMB/midmarket AI workflows should benefit from the same consumption trend with less model transition risk.
• For longer-dated upside, buy GTM Jan-2027 call spreads only on evidence that Q3/Q4 renewals show stable NRR and accelerating consumption attach. The setup is high convexity, but the timing risk is material.
• If you need a hedge against AI-driven software budget confusion, short a basket of legacy seat-based data/SaaS names versus long names with consumption or embedded workflow exposure; GTM is the prototype of the transition, not a beneficiary until proof points arrive.