Zuora

What it is

Zuora is a quote-to-cash suite for companies that sell subscriptions, usage or both. The modules are sold separately and share one data model: Zuora CPQ (with the newer CPQ X and Quote Studio experiences) for quoting, a monetization catalog for pricing and packaging, Metering for usage, Zuora Billing, Zuora Payments, Accounts Receivable, and Zuora Revenue for ASC 606 and IFRS 15 revenue recognition. Zephr, its paywall and digital-subscription product, sits beside them for media companies.

Ownership changed in February 2025, when Silver Lake and GIC completed a take-private at $10 per share and Zuora left the New York Stock Exchange. The company is alive and still shipping: Gartner published its 2026 Magic Quadrant for Recurring Billing Applications on 12 August 2026, covering 17 vendors, and Zuora is placed as a Leader again. Its own release adds the claim of the highest Ability to Execute. Chargebee is also a Leader in the same report.

Why it shows up in RevOps stacks

Two things put Zuora back on shortlists in 2026.

The first is Salesforce CPQ going end of sale on 19 March 2025. Teams that are re-platforming quoting have to decide whether billing and revenue recognition move with it. Zuora’s pitch is that one vendor should own the chain from quote to recognized revenue, so a contract amendment flows through billing and the revenue schedule without a reconciliation step.

The second is Zuora AI. The 16 April 2026 announcement made it available to all customers, with agentic capabilities that can be switched on. Finance gets several things out of it: analysis of contract modifications, side-by-side allocation changes that show the ASC 606 formulas used, draft responses to audit requests built from subscriptions, invoices and payments, and collections prioritization. The product page lists named agents per module, including Quote Rule, CPQ Setup, Mediation Code, Billing Operations, Cash Application, Reconciliation, Collections, Revenue Analyst, Billing-to-Revenue, Journal Remediation and Revenue Close. Write actions run in supervised mode, and an org admin can disable Zuora AI entirely.

Zuora MCP comes in two versions with the same operations. The local server runs on Node and authenticates with a user’s OAuth client credentials. The remote server is hosted by Zuora and authenticates through OneID OAuth. The docs name Claude, ChatGPT, Cursor and Windsurf as clients, plus n8n, Glean and Slack for automation. Zuora’s own 2026.Q1 release notes listed both servers as beta, and the 16 April release says only “available to all customers”. Ask which label your contract carries.

Milo, announced 28 July 2026, is an implementation agent. It builds a working model of your quote-to-cash setup from existing order forms, contracts and invoices, then speeds up configuration, data migration and testing. Zuora says it is engaged automatically from proof of concept onward. The “up to 80% fewer resources” figure is Zuora’s own.

Pricing reality

No list prices. Zuora’s pricing URL is a product page about packaging models, and every path ends in “speak to an expert”.

Buyer data is the anchor. Vendr reports a median of $170,000 per year across 149 purchases, with a range of $26,883 to $696,804 and average negotiated savings of 12%.

Put that against the alternatives:

• Nue: Vendr median $67,167. Zuora’s median is about 2.5x.
• DealHub: Vendr median $44,297. Zuora’s median is about 3.8x.
• Stripe Billing: priced as a percentage of billing volume on its pay-as-you-go plan, so the bill moves with revenue rather than modules.

The range spans a factor of 26, so the quote is driven by modules, volume and entities, not seats. The reason to pay the premium is Zuora Revenue. If revenue recognition stays in your ERP, you are paying for a suite you will use half of.

Best for

A revenue-finance or RevOps owner at a SaaS, AI or media company with roughly $50M+ in recurring revenue and several billing entities or currencies. The pricing mixes subscriptions, prepaid drawdown, minimum commitments and metered usage, and the controller wants billing and ASC 606 revenue schedules in one auditable system. The scoped use case where Zuora wins outright is contract amendments mid-term: upgrades, co-terms and allocation changes that have to land correctly in billing, AR and the revenue waterfall in the same close.

Not for

A company under about $20M ARR with one entity. The Vendr floor alone is near $27,000 a year, and the reviewer consensus on G2, Gartner Peer Insights and Capterra is that setup needs a specialist integrator. Also not for teams whose real problem is quoting UX on HubSpot, where DealHub fits better, or whose controller is happy running revenue recognition in NetSuite or Sage Intacct.

Versus the alternatives

• Chargebee: the other Leader in the 2026 Magic Quadrant, and the usual mid-market counterweight. It publishes self-serve tiers and goes live faster. Pick Chargebee when you have one or two entities, the revenue team works from ERP reports, and time-to-live matters more than depth on amendments.
• Stripe Billing: the default when Stripe already processes your payments. Stripe completed its Metronome acquisition in January 2026 to bring Metronome’s metering engine into Stripe Billing. Pick it for usage-heavy AI pricing with simple contracts. This is the fastest-moving option in usage billing.
• Nue: pick it when you are Salesforce-native and want quoting, credits and billing on standard Salesforce objects at about a third of Zuora’s median. Revenue recognition then stays in your ERP.
• Salesforce Revenue Cloud: pick it when procurement wants one vendor on paper and your billing is simple enough for native.

If none fit because billing is genuinely simple, use Stripe Billing plus your ERP’s revenue module and revisit at the next entity or pricing-model change. Background: what CPQ covers, seat-based vs usage-based AI pricing and the quote-to-cash stack.

Watch-outs

• Supervised mode does not cover MCP writes. Zuora’s MCP docs state that Zuora cannot enforce approval of write actions made through MCP. That depends on the client, and there is no setting that allows writes in-product while keeping MCP read-only. Guard: set the tenant’s Zuora AI permission to read-only in OneID until you have a client that enforces approvals, and give MCP users a role scoped below their in-app role.
• Developer Tools are deprecated on 31 December 2026. Zuora’s end-of-life notice moves customers to Data Loader. Guard: inventory every script and integration built on Developer Tools before signing a renewal, and get Zuora to scope the migration inside the renewal SOW.
• “Go live in weeks” is a vendor claim. Milo’s modules for configuration, catalog generation, migration and testing are marked adoption-ready, but onboarding design is still listed as coming soon. Reviewers describe implementation as structured and integrator-heavy. Guard: tie a phase one of one entity, one currency, Billing only, to a dated payment milestone, and make Revenue a second phase with its own acceptance test.
• The AI packaging is unpublished. Neither the April release nor the product page says whether agentic capabilities cost extra. Guard: get the AI and MCP line itemized at signature, with the agent list in an exhibit, so a later “agentic tier” is not a mid-term upsell.