See what's new and next in Zuora innovations

Our legal team does ask that we share this in our presentations. I won’t read it word for word, but please do take a moment to read it as a forward-looking statement. And with that covered, let me bring up our speakers for today. So I’ll go through these one by one, as you’ll be meeting them shortly, but here’s who you’ll be hearing from today. Before we get into what shipped this quarter, here’s why we’re building it. AI is changing how software gets priced. Two years ago, seats were roughly three-quarters of the market. Today, that’s down to a third, uh, with usage and hybrid models taking over and expected to dominate within two years. Here’s the catch for finance. More usage means more cost. Gen AI products

run meaningfully lower margins than traditional SaaS, and pricing isn’t, is only the front end. The real complexity hits after when finance has to reconcile credits, prepaid balances, and revenue recognition across constantly changing models. The real question isn’t whether to charge your AI, it’s how you operationalize it without breaking everything downstream. That’s exactly where our strategy comes in. Three pillars, one foundation. First, monetize AI, helping finance actually operationalize every time the model changes, all the way grounded in finance-grade trust, auditability, controls, explainability. You’ll see these three threads run through everything today. Billing and CPQ updates mostly serving monetizing AI and going live in weeks. While revenue and AI plus MCP updates mostly serving supercharging your quote to cash.

Keep that lens as we move category by category. So let’s get into what shipped this quarter. Go through a few sections, starting with what’s new in Zuora, and then we will shift into what’s next, and then close out with Zuora AI and MCP. Let’s dive in. I’ll hand it over to Roli next. Hello, everyone. Good morning. My name is Roli Shah, and I am Product Manager with Zuora Commerce. And today I’m here to present to you two new capabilities which we are launching as from Zuora Commerce’s, uh, initiative. So most companies today are stick-stuck with rigid static product catalogs. Every time a customer needs something slightly different, a different mix of products, a custom plan structure, a one-off charge,

that request has to go through either deal desk as a manual exception, but that’s slow. It’s inconsistent, and it doesn’t scale. As product line grows and go-to-market motions multiply, that friction only gets worse. Here we are with Configured Bundles. It let companies dynamically assemble product plans and charges into personalized configured bundles. And this works whether you are selling through CPQ or through digital self-serve channels. Instead of hard-coding every possible SKU combination, you define a guided configuration experience. Sales reps or buyers in digital channel can tailor the bundle to the specific deal, and the system automatically enforces your master policies underneath, pricing rules, governance, approval logic,

all of it. You are not trading control for flexibility. You get both. If you look at the screenshot on the slide, you can see what looks like in practice. A bundle group where a customer or rep picks product, sees the associated rate plans and charges, and can drill into view charges or view plans without ever touching a static price book. It’s a genuinely a different way of building and selling packages now. What’s actually impact for the business? Let’s hear about that. Two big ones. First, speed. Companies can launch and modify packages in days instead of quarters. You are no longer waiting on a catalog rebuild or a pricing team sprint every time you want to test a new bundle. And then what’s the impact on revenue?

Because this is embedded directly in the quoting flow, sales rep close more deals through guided cross-sell and upsell, and everything flows cleanly through order, billing, and revenue recognition without manual reconciliations on the back end. So the summary here. Configurable bundles takes the tension between give the customer what they want and keep finance deal desk in control. You get tailored solutions at the speed of business needs without losing the governance you depend on. Uh, next slide, please, Caleb. Now, building on the configured bundles, we are also launching something called Offer Management, and this is, I would rather call it intelligent offer management because packaging is just half the story. The other half is

knowing actually what to offer to the customer and at what time. Their situation matters a lot. So here’s the problem today. Most companies rely on static merchandising rules or an individual sales rep’s judgment to decide when to cross-sell, upsell, or suggest a substitution. That leads to inconsistent execution. One rep pitches the right upgrade, but another one misses it entirely, and it leaves real revenue on the table. When those decisions aren’t systemized, you are basically living gr– uh, leaving the growth to scale, to chance. Offer Management solves this by personalizing those recommendations for each customer’s specific situation while optimizing for the business objectives that matter to you. Per segment, existing subscription,

and uses the rules and AI to recommend the single best offer for that customer in that scenario. For standard cases, you can use out-of-the-box logic for cross-sells, upsells, downgrades, and substitution. But for more complex company specific scenarios, there’s a flexible rule builder. You can see an example on this particular slide where a rule is built around the conditions like product, customer, MRR, and contract term length. All these gets feed into the decision and optimization layer that drives the recommendation action. But why does this matter again to the business? I’ll back to the, again, two outcomes. First, consistency. You can execute the same go-to-market strategy across direct sales, partner channels, and digital

self-serve without rebuilding the logic separately for each one. And second, revenue capture. Sales and marketing team surfaces more automated cross-sell, upsell and retention recommendations tied directly to the channel, segment and business goals instead of hoping a remember– a, a rep remembers to make the right pitch. If you put simply, configurable bundles gives you the flexibility to package anything and offer managements make sure you are always presenting the right package to the right customer, which automatically scales. Thank you so much. Debali. And with that, we’ll hand it over to Sam. Good morning, everybody. Uh, my name is Sam Njoroge. I’m a product manager in the

billing, uh, product. So today I’ll talk about, uh, prepaid drawdown and commitments, uh, two areas where enterprise deals gets very complicated, especially on a finance side. So we’ll start with prepaid. Um, enterprise customers managing large prepaid, uh, commitments need to know exactly where their funds stand at any moment, especially with AI monetization. This is something that is critical such that, um, consumers as well can see where their balance is at. But rigid drawdown routes, fixed validity periods, and account-by-account tracking make it– make that visibility very hard to get. Finance ends up doing manual reconciliation just to answer a basic question,

how much prepaid balance is actually left and where. So with this release, we have addressed most of that, and we are adding shared prepaid funds across subscriptions and parent-child accounts, configurable drawdown priorities, so you can control which accounts or subscription drawdown funds first, and probation for midterm purchases. The last one matters commercially. It means sales reps can close prepaid deals midterm instead of waiting for renewals. Underneath all this, we are replacing rigid per-account tracking with flexible unit-based fund management, plus better validity period alignment and rollover. All this is also very much aligned with the finance and, and revenue recognition such that there’s no breakage.

The business impact, the finance teams get real-time visibility into prepaid balances across every account with no manual reconciliation. Drawdown priority puts funds where they matter most, and probation unlocks deals that used to be stuck waiting on renewal dates. Uh, let’s go to the commitment. Next slide, Caleb. Uh, with commitments, as enterprise deals gets complex, multi-entity structures, ownership changes midterm, nested commitments, rigid commitment structures force teams into manual workarounds outside the billing system, often in spreadsheets, and it’s very risky and does not scale. So with this release, flexible commitments lets commercial terms is

evolve with the deal without breaking the commitment track-tracking underneath, specifically overlapping commitments, which is new. Let a child commitment roll its spend and true up into a parent supporting nested parent-child structures. Commitment lifecycle management lets teams extend or short-shorten a schedule end it directly through an order instead of rebuilding the whole commitment, breaking revenue management. Owner transfer, uh, is now available, which can reassign subscription to a new owner mid-commitment without losing the drawdown history, and this connects to prepaid drawdown feature that I just talked about. So prepaid amounts can now contribute directly to the commitment

balance as well as any other funds. So what’s the impact? Multi-entity and parent-child structures are now natively supported. So commitment no longer live outside the system and spreadsheet to know how the funds are distributed and who should actually be consuming them. So ownership changes and term adjustments preserve commitment history automatically, cutting the manual rebuild work that renewals and renegotiations require today. Um, let’s go to the next, uh, slide. So the next big feature that we have here in the billing space is actually e-reporting. And as you know, we had already issued the e-invoicing, so e-reporting follows that.

So I may start with maybe just highlighting what is the difference between the two. So e-invoicing is a mandate whereby two parties need to exchange electronic invoices, and this is mandated in, in several countries. The e-reporting is actually the auditability of that, such that if a taxing authority or government authorities need to actually understand what is happening through those, um, e-invoice transactions, you can be able to report those transactions. So with this re-release, so we have e-reporting. This is how businesses meet government reporting obligations for transactions, so that aren’t covered by invoicing. So you think of B2B transactions, cross-border flows. It gives tax authorities

visibility into those transactions. And as more countries roll out mandates, staying compliant here is becoming, you know, ne-non-negotiable and non, not optional. What’s new? We now support, uh, a variety e-reporting templates that can be assigned by transaction types. So you get flexibility to configure re-reporting differently depending on country-specific, partner-specific requirements. And these templates are managed directly within Zuora and work through the existing Avara integration. So this release specifically covers both invoice and payment reporting for France and Mexico. So why does it matter now? France has a mandate coming up in September 2026, so this is a very timely,

uh, release, and you’ll be able to use this capability So this specifically improves the readiness for that deadline, but the value goes beyond just one mandate. By enab- enabling flexible transaction-aligned reporting, we are reducing the country-specific implementation efforts and manual workaround that used to be required. So you simply just configure a template, and you connect to, to, to the authorities. So the bottom line, instead of building custom reporting logic by country every time a new mandate lands, teams c- can configure it within Zuora and stay ahead of compliance requirements as they expand. Thank you. Thank you, Sam. And with that, we’ll jump into experiences. And we’ll welcome Sean.

Thanks, Caleb. So, yeah, let’s, let’s talk about experiences. So today, standing up a subscriber portal or a storefront or a billing view inside your CRM usually means that we have months of custom front-end work, and usually it also means that there’s a data sync that drifts from your actual catalog over time. So you end up with a portal that shows a price that isn’t quite right or a checkout flow that doesn’t reflect the plan that you just changed in Zuora. So Ex- Zuora Experiences fixes that at the root. It lets teams launch self-service and commerce journeys fast with Zuora as the live source of truth, and it’s not just another copy of the data that can go stale. So Zuora Experiences combines pre-built

templates, reusable components, and live Zuora context in a single platform. Practically, that means you can embed billing and subscription actions directly in systems you already run, such as Salesforce or Zendesk, or you could stand up customer-facing portals and checkout flows. Either way, everything is fed from the same catalog. So the concept that’s underneath it all, and it’s worth spending just a moment on this because it’s part of the, the whole value proposition, is what you model in catalog and in billing, your products, packages, features, entitlements, et cetera, that’s exactly what your customers see is what they buy and what they get billed for. There’s no re-entry. There’s no drift. There’s no glue holding it all together.

You just edit a price or a bundle once, and it propagates automatically to every surface. Uh, your product or displays always shows the live catalog prices. The paywalls always pull the offer and price straight from the catalog the moment they fire. To make this a bit more concrete, two examples of what this looks like in practice. First would be a customer portal. So end customers always get a fully branded self-service My Account experience where they can go and view their account balance, open invoices, or usage stats. Uh, it c- could also be their next billing date, how they manage their own credit cards, et cetera. All of it live Zuora data replacing support ticket round trips and self-service.

The second example would be an embedded CRM view. Your sales and support teams can see live Zuora data such as active subscriptions and real-time invoice history directly inside Salesforce or HubSpot or, or Zendesk, and then they can even take actions like guided amendments or issuing credit memos without having to log in a second time or swivel chairing between the different systems. So this means less custom development, less data sync, and faster iteration across all your subscriber, partner, and back office experiences. Your engineers can stay focused on core product instead of building one-off portals. And this is the payoff. A pricing change ships in minutes, not a release cycle, because the storefront, paywall,

checkout, and billing never disagree. And we can show you a bit of what that looks like. We’ve got a pre-rec- recorded demo for you. So Caleb, if we can just go on to the next slide, and we can, uh, play that for you now. Experience Builder is Zuora’s visual code-integrated platform for building customer-facing experiences such as portals, checkout flows, and registration journeys, all of this without ripping out your existing code base or design system. This means that developers keep control of integrations and infrastructure while business users can build and update pages themselves through a visual editor with no separate dev cycles for every single content change. This means we can build out common use cases such as this, a My Account page that customers can log into, update their

contact information or their subscription data or any payment methods that they might have on file. What I’ll show you today is how we can quickly and easily prompt out updates to an experience such as this. Now, within the editor using the Zuora AI agent, we can prompt out something such as update the styling to be a professional news publication. Now, this could al- also be done by adding in your specific CSS or style guide directly into the

agent. But for now, we’ll keep it something simple and generic so we can see how the agent works. Now, the agent will give you updates every step of the journey, showing you exactly what it’s doing, even for something like this where we can see that it is just working on changing styles right now. It’ll update for you in real time so you can see exactly what is going on. Now, while that is completing, we can see that within the Experience Builder we also have a number of pre-built Zuora components that are hooked directly into the Zuora APIs with… which means you can build out

components such as a cart checkout or an account switcher by just dragging and dropping the component in or prompting the agent to do the same thing, and it will hook up everything based on your tenant configuration and build the component in real time. Once this is complete, we’ll be able to publish and host the component or page directly using Zuora hosting as well. Now we can see the, the page is updated with a very simple prompt. Alongside telling us exactly what it has done. Now, we can also add something in here

such as… add a component which allows me to cancel a subscription from the subscription card. And again, it’ll u-understand what we’re asking it to do, look through the Zuora documentation to work out exactly what it needs to do, and build the component in front of you. For any, any clarifications, it may ask you in the chat where you can respond,

and it will think about what you have responded and add in those details here. Now this is complete, like see that the cancellation date has been added into the subscription card. This is the type of activity that would’ve needed to be scheduled into engineering cycles, but we have been able to prompt out wide directly to the Zuora APIs and built all within a matter of minutes. Thank you, Sean. Anything to add there? N- uh, no. I think we might have had some audio issues at the beginning,

um, so I’m tempted to get the demo sent out afterwards. And if there’s any clarifications, I can answer those in the chat now as well. Thank you, Sean. With that, I’ll hand it over to Tyler who will be speaking about Zuora Payments. Thank you, Caleb. So today we’re excited to show you Zuora Payments, our new payments orchestration platform that gives you unprecedented control and flexibility over how you accept, process, and optimize payments. Most companies are locked into a single payment processor. That means limited payment methods, higher costs, and no way to route intelligently when things go wrong. Zuora Payments lets you orchestrate payments across multiple processors and payment methods from a single unified control plane.

You can route transactions intelligently to optimize cost and success, support any payment method your customers need with over one thousand payment methods and four hundred payment, payment service providers at launch, recover failed payments automatically, and get unified reporting and settlement across all your payment flows. In the next ten minutes, we’ll walk through the platform, show you how to set up your payment flows, and demo how easily you can manage payments at scale without any custom integration work. If you’d like to hear more, we’ll share the link after the presentation for you to sign up. Hello and welcome to Zuora Payments. Zuora Payments is Zuora’s first payments orchestration platform offering over fourteen hundred payment methods,

four hundred PSPs, agnostic three DS services, network tokenization, and account updates included. Now let’s get started. The first thing that you’ll see is that Zuora Payments has its own menu item here now in the left-hand menu alongside Zuora Billing, Zuora Revenue, and Zephyr. So when Zuora Payments is selected, you’ll see that we have three new menu items, Connections, Routing, and Checkout. With Connections, this is where we will define all of the various credentials and other characteristics of the connections to the PSPs and other providers that we will connect to. Routing is where we will determine per payment method which payment methods we want to enable, but also where those transactions actually

process with the connections that we defined above. And then Checkout. This is where we use all of the payment methods that have now been enabled to display them in a single drop-in component form that can be used on any webpage to collect payment method information. So let’s look at Connections. Under Connections, the first thing that you’ll notice is that we have this large table tile view. What you can see here are all of the various connections that Zuora currently has available. This list will continue to grow as we add more connections over time. Now, let’s come up to the top. The first thing that you’ll see alongside that is that each of these connections has a different

category or label associated to it. So there are gonna be four core labels. The first is Processor. This is your standard gateway-like connection, similar to Stripe, Checkout.com, Adyen, et cetera. You will see Payment Methods. This is different from enabling a payment method. This will be similar to PayPal, where PayPal is both, uh, h-has its own payment method as well as a platform to process those payment methods. You have Fraud Solutions like Ascertify here. These are going to be standalone fraud connections that can be established. Um, and then lastly, you will see three D Secure connections as well. All of these connections will require merchant con-contracting between

you and those particular services. Zuora is not offering that through these particular connections. What we are offering are the connections or the integrations to these connections So as we go further into showing you what these connections look like, you will need to be ready and come with your credentials in order to populate them. So not every connection that you see listed is immediately going to be usable by you. You still must have a commercial agreement with those partners. Now, having said that, you will notice that here we have all of the listed connections that we have created in our demo environment. So I’m going to start with Adyen. I will quickly jump in here and show you that this should look and feel familiar to anyone

who’s ever, uh, created a payment gateway connection in Zuora today. The first thing that you do is you give each instance of a connection its own name. For here, I’ve called it What’s New, What’s Next Demo. The account code, this is going to be your merchant ID or merchant account code associated, uh, with that particular connection, and then the, the credentials associated with actually connecting to that particular platform. So it can be an API key, it can be an HMAC key in certain cases, or some other form of authentication. Everything else that is listed here is entirely optional. Uh, it will depend on your particular use case. Uh, for customers who process 3DS, for instance, today, you will notice that there is an onboard 3DS option here. So if you use

Adyen and process 3DS today, you would want to check, uh, Ad- enable Adyen 3DS validation flow. But if you want to pull 3DS out and use one of our standalone services, you would then want to disable this and create that connection, uh, or rather, uh, modify that connection in the routing flow, which I’ll show you momentarily. So next, we will select Next, and you will see the Setup Costs page. This page is entirely optional. It’s for folks that want to utilize smart routing, which I, I will show you momentarily. With this, you essentially establish the successful and unsuccessful payment costs by currency for your current merchant contract with that particular provider.

Now, since this connection is already created, we will go to Routing. Under Routing, you will notice that again we have this tile view, but it is now listed purely by payment methods. As I mentioned before, this is how you actually enable payment methods. But the tiles that display here will always be the tiles or rather payment methods that are already enabled for those particular connections that you have created. So if you have a single connection and that connection has three payment methods supported, you would only see those three tiles available for that particular connection. In this case, because we have so many connections created, you can see all of the various payment methods that we can enable. Many of them still say Setup, meaning they are not published. But I will jump into

the card connection for you here. Um, the first thing that you’ll see on this particular view is that there is a versioned history. A single route can be published at a time. Anything that has been published before is archived. You can always roll back simply by clicking into that and viewing and publishing it, or you can go back and edit previous rules by duplicating and edit. Additionally, every time you go into the canvas for a particular rule, we will create an auto-save draft for you as well. So let’s quickly look at what’s new, what’s next demo as a route. Now, what you’ll see here is that there are large nodes on the left and then smaller nodes shooting off on the right. The large nodes denote conditions and groups of conditions. And then in the bottom, it’s a little hard to see,

it says all other payments. This is basically the route that you will define as a fallback. So if no other conditions are met, then we will fall back to this node. So what do conditions look like? The conditions are, um, individual per the specific payment method type. So the conditions that you see here are all card-specific conditions. ACH will have its own, SEPA will have its own, Pix will have its own, et cetera. You can choose to use any conditions that you want. You can choose to not use conditions, and you can use any combination of con- of conditions as well. So for the sake of this demo, I will quickly show you that I have created a route here that says if the condition is the card issuing country is Germany, then I will step up to a 3DS

solution, the Cybersource 3DS solution, to perform 3DS at this point. If it declines for any reason whatsoever, we’ll stop right there. Otherwise, if it succeeds, we’ll then fail over or succeed over to Adyen. If that declines for any reason, we will then issue a fraud step-up using the risk conditions shape. And then if that succeeds, we’ll fail over to 2C2P. So this, uh, enables us to build in redundancy to the flow as well as completely dictate when and how we call fraud in 3DS in the flow. So for Germany, I’m stepping up the challenge for 3DS. But for the United States, where 3DS is not a requirement, I don’t want 3DS in the flow at all. So I have removed 3DS, and I’ve said, let’s

have smart routing handle this. So what does smart routing mean? I, uh– Oh, sorry. When Zuora is able to, um, connect to more than one connection at a time in a route. So let’s say that as you’re selecting a connection, you choose or within your route, you’re selecting multiple connections, uh, Zuora will immediately give you this option for smart routing. So with smart routing, you then can say, how do we want to split that traffic? You can do it by latency. You can do it by cost. As I showed you before, we will tell you if the costs are not set up for one or more of the connections that you’ve selected. And then we can also define whether we automatically route that for you or if you want to manually split that. So you can do some A/B testing of your own to say, let’s have smart routing handle fifty percent of this,

and then the other fifty percent is split in some other way across those other providers that we’ve selected. And then the last thing I’ll show you here is that all decline codes are now also normalized across the board. So you no longer need to know individual codes for individual providers. Okay, so that’s routing. Now, after routing is configured, you now have the ability to define your own checkout. With checkout, this will look and feel very familiar to HPF today or hosted payment forms. So as you can see, it’s a drag and drop form. All of this is a drop-in component, so all payment methods display from a single form, so you install a single form on your page. Existing home-hosted payment form,

hosted payment form, uh, pages today can be easily migrated with a single button. Otherwise, uh, hosted payment page users will need to install a new hosted payment page that points to this. But within it, you can decide which payment methods display under which conditions. For instance, with Pix, I’ve said that I want this to display in Brazil. You can do it based off of other metadata, which is custom information coming into the system or order currency and amount. But the point with all of this is that you have complete control over what payment methods display and in what order. All at your fingertips from a functional perspective. Your tech teams, all that they need to do is install it one time.

Your functional users can simply move forward with a quick installation. Thanks. Thank you, Tyler. And next, we’ll be moving on to revenue features. And we’ll start with you, Shiro. Thanks, Caleb. Um, thanks everyone for joining. I’m part of, uh, revenue product management. Um, I’m going to talk about Deployment Manager, and that’s my first topic for today. Um, so why this feature? So this feature is available from Q3 major release. Um, the reason why we added is it brings, uh, the platform capability as a parity for revenue. Uh,

this has been asked by several customers in the past. And this feature, uh, like historically, uh, there’s a migration feature, legacy migration center feature, which is completely based on SQL scripts that engineering and like IT team has to involve and run, download these scripts, run these scripts, grow to– go through support process and then have support and, you know, um, uh, sort of take care of your, uh, migrations. With this feature, it’s a self-serve feature, uh, you know, uh, the Deployment Manager. So even non-engineers, non-technical people, business admins can leverage this feature, use this feature to do an online migration from source to target tenants, or they can do offline migration. They can download from a source tenant all the configurations and then

go onto a target and upload these configurations. Um, and then they can do this granularly. Um, they can actually migrate a component by component. All the revenue components, revenue configurations that we support in the legacy migration are, are supported in Deployment Manager. So you have a self-serve UI. Before you migrate, you can also do a comparison, granularly compare what, what is the value on source, what is the value on target, how are these different? And then, you know, based on your judgment, you can, you can migrate the source configurations to your target tenant, right? It can be from sandbox UAT to prod, from prod to, uh, you know, sandbox for testing. So you can avoid some of your sandbox refreshes. You don’t have to do a sandbox refresh just to bring your configurations.

So you can leverage Deployment Manager to bring your stable configurations from prod tenants to into sandbox for new feature testing. And then you also have the ability to, you know, revert and roll back in just in case if you have deployed or migrated anything accidentally that, you know, it’s impacting your, um, ongoing testing in UAT or in production. You have the, uh, ability to look at the logs and then also you can revert the deployment. And you also get to see the full audit trail of what has been deployed, what components have been deployed by whom and at what, at what time of, uh, you know, what time of the day. And what, uh, value this brings, um, you know, this was a cumbersome process, uh, would take multiple days and weeks. You know, when, when you have a schema changes, when you have your release upgrades, changes in any

of your features, uh, that, that goes through a, a long process. But with Deployment Manager being a self-serve capability, with you have all the power in your hands to, you know, run your migrations, and then you can just, you know, do this within, within hours. You know, once you have set up, once you have configured, um, all the basic prerequisites to use the Deployment Manager, um, you can just, um, have your configurations moved across tenants. Uh, one thing that I want to call out as the prerequisite for this Deployment Manager is every tenant has to be on one ID, uh, sort of one ID. Uh, all the new features, all the platform features that revenue has, uh, make sure your tenants are on sort of one ID. Next slide, please.

Yeah, workflow. Yeah, this is another addition. Uh, we, um, you know, this also was a great, uh, addition to revenue. Uh, we are giving the ability for customers, partners, and implementers, asset partners, you know, who can actually build some of the customizations, custom jobs. Unlike previously, it was more, uh, Oracle-centric, it was more SQL, and it’s a lot of legacy scripts that are involved, which would require very deep knowledge about the system. Um, but what we are doing with, uh, Q3 major release is, you know, we are exposing a lot of revenue tasks inside workflow. This workflow is available for all type of revenue customers, both, uh, customers who have both billing and revenue or just revenue-only customers. Um, essentially, this would enable, um, your revenue operations

team, revenue teams to, you know, quickly build, uh, some of the, uh, end-to-end, uh, use cases. You can actually orchestrate and stitch your revenue tasks To automate your multi-step processes from start to finish. Um, you can create your custom jobs using workflow, you know, which is all backed up by revenue APIs. All the APIs that revenue has can be triggered, can be called from, um, workflow. You can, um, you can also use out-of-the-box revenue task what we have, uh, you know, surfaced, published in workflow, like the workbench operations. All the workbench operations that you can, uh, perform today by… in revenue, you know, you can, you can automate those processes. For example, you can try to defer a revenue contract or defer a PoB. Um, it can, it can do that, right? And it can also gives you…

Essentially, there’s a shift with, with this feature, there’s a shift from, uh, you know, the legacy way of implementing your customizations, custom jobs. The shift is from legacy code to a configurable workflows, more composable and configurable workflows. And then you can run these workflows and register them inside revenue. Uh, you can access workflow from revenue, you can access workflow, uh, revenue tasks from billing, either ways. And then you can register this as a background job. So similar to how you do a custom job in the… you know, historically how you’re doing it, um, you can create a background job and select the workflow that is active workflow, and then, you know, register as a background job and you can run it. You can schedule the job, you can run it. So this would give you all

the power, uh, that, you know, you can do all the pre-validations, anything, any data updates, uh, data validations, um, you know, before you, you collect the data, right? So, uh, with this feature, you have all the power now to, you know, manage your customizations. Uh, that-that’s all I have, uh- Thank you, Sriram… back to you. Wonderful. We’ll continue on revenue and talk about reporting. Karan, hand it over to you. Thanks, Caleb. Thanks, Sriram. Uh, hey, everybody. Excited to be here. Uh, and I’m going to be talking about an important enhancement that we’ve made to the waterfall report. Um, so as most of you

who use Aurora revenue on a day-to-day basis know, today we have two reports: the waterfall report and the historical waterfall report. Now, historical waterfall, uh, report has, uh, traditionally had a limitation wherein you can only view live data, live revenue for only thirteen periods, and therefore you have to stitch multiple reports if you want to get a comprehensive end-to-end historical view of live revenue. So what we have very helpfully now done with this, uh, release is we’ve introduced the ability of the historical report, uh, historical waterfall report in the waterfall report, right? So what that means essentially is that we’ve, uh, added a new optional filter directly into the existing waterfall report

that lets you choose between a historical or a live revenue view. So in practice, as you can see in the screenshot, uh, what that means is, uh, one single report now gives you true end-to-end visibility, whether you’re looking at revenue based on the current open period or any closed period in the past, right? So you’re not switching reports or rerunning the same report under different settings anymore. It’s all in one place. This is live today in both sandbox and production. You don’t have to pay for anything. And as you can see in the screenshot, you simply need to go into your report setup and add this optional filter in your existing report layouts, right? Um, so as a result of this, uh, what happens is,

um, finance teams are basically able to close their periods, uh, while running lesser number of reports. You don’t have to spend more time reconciling, right? Because you get the same functionality in one single, uh, report. Um, and, uh, both historical and current. And, um, yeah, that pretty much describes this, uh, functionality that we have introduced. Um, happy to take on any questions and, uh, take any feedback on this new enhancement, uh, that we’ve introduced for the waterfall report. That’s all from my side. Thank you. Over to you, Caleb. Thank you. Very exciting updates on revenue. And as we close out

what’s new, we will now dive into what’s next. And first up will be Manfred talking about configurable bundles in CPQ. All right. So I’m talking about configurable bundles. Um, you have seen what Rolly, um, explained about maintaining configurable bundles. So this section is about consuming those configurable bundles in CPQ. Now, this is functionality that’s coming out in… Sorry? We can’t see you, by the way. Oh, uh, sorry about that. All right, now here you go. Wonderful. Okay. So this, this functionality is coming out in September. And, uh, so why does it matter,

right? So unlike, uh, fixed bundles, so these configurable bundles, they let actually the sales rep, uh, tailor a bundle to what the customer really needs and wants, and it makes it more flexible and more, uh, customizable, uh, for the sales rep. So what’s, uh, really new is, so the rep selects bundle components while the system guides them through the bundle configuration process using rules that are already set up by the catalog admin. So the result is then a simpler experience for the rep and error-free bundles. So all required components are included, all quantities are correctly entered by the rep, and the rules can calculate the quantities. So this ensures that the quote is ready and then can be passed to billing,

uh, with no issues. Uh, and the impact is, as Rolly actually explained earlier, is complex bundle launch faster- Um, and the reason is because, uh, through the guided selling experience, through the bundle configuration, it is simpler, uh, the, the learning curve is less for, for sales reps. And then organization can expect an increase in quote value. Um, and that’s– the reason is because upselling cross-sell items are, uh, easier to add for the rep because they’re right there. And then lastly, customer satisfaction improves because the rep can adjust the bundle con-content to, uh, what the customer really, uh, needs and requires. So, uh, now it’s actually time to see this in action. And, uh, Caleb, if you wanna

start up the demo. In Quote Studio, config bundle A, bundle rate plan A version one has been added. Clicking on config launches the bundle configurator. In the bundle configurator, we can see that there are three errors that the user has to resolve. So by entering a quantity or correct quantity, the first error is resolved. And, uh, the user goes step by step selecting bundle components, which are added dynamically to the right-hand side. And, um, as I said, they get guided in entering correct values as they make the selections. Um, mandatory selections are requested

and, uh, optional selections can be either single select or multi-select. Quantity entries can be allowed for certain bundle components. In this case, a quantity rule has been violated, and the user can correct that. The system guides them through this process. Support plan is another mandatory selection.

So here they’re selecting add-ons like SAML integration, advanced audit logs. And because audit logs require a HIPAA compliance package, they can select that. And on the right-hand side, the component list has grown, and the prices are aggregated to the bundle level. And at the end, when everything is fine, they pick Save Configuration, and that will be then saved to Quote Studio. Wonderful. Very exciting to see that passing through from one to the next. Okay. And, uh, so then another thing, uh, is the advanced approvals I’m talking about. So advanced approvals is,

uh, coming out, uh, with Quote Studio, uh, on CPQX, and we’re also targeting September for that. Um, th-this has been a, a direct ask from our enterprise customer because large organizations have usually more complex approval workflows, so therefore, they need often also more sophisticated functionality in that area. So what, what’s the gap compared to today? So simple approvals are already built into CPQX today, uh, because CPQX is a native Salesforce application. Uh, so we just take advantage of the built-in, uh, platform, Salesforce platform approvals. Uh, but that’s, that’s okay for simple cases, but not so good if, you know, there are many different parties involved,

there is a complex conditional routing, uh, there are parallel sign-offs required. Um, there may be, uh, you know, approvals that are, uh, should be avoided if, uh, you know, they already have been approved and re-approval is required. So there are different situations where, um, the simple workflow that’s built into Salesforce doesn’t work, right? So how does our workshop actually work? So there are, uh, in, in, in, um, about four new objects that define how the approval workflow is put together. So on the most granular level, uh, there are approval steps. So these steps can be put together into chains. So you can see that here on the right-hand side, there’s a graph. You see the, the steps

one, two, three, in this case, put together into cha– uh, chain one. And, um, and then there are, there are also, um, the, there are– The chains are building blocks, and an admin can then put them together into flows. So you see here two flows, flow one and flow two. Now, uh, and then there’s the last part, uh, which are rules. So rules are the orchestrators, uh, of the entire workflow, and they decide which flows and chains are needed for a specific quote approval. So they also decide if a flow is executed after another flow, so sequentially, or if two or more flows are stored at the same time, so in parallel. So with that, they are pretty important and, uh,

the admin can decide on that. So they decide on, uh, parallel or sequential approvals. Um, so they also can decide if a chain or, or the chains, if there are multiple chains, if they start, uh, in parallel or sequentially. So if a, uh, if a quote gets, uh, rejected and resubmitted, the system has also something we call approval memory. So it compares the new change quote version to what’s already have been approved, and it skips that approval if there are no facts that did change for him, for that approver, so that they’re not asked to reapprove if nothing changes for him. So this avoids kind of, uh, uh, many reapprovals that are re-requested, uh, and the annoying kind of, uh,

emails they can get in asking for reapproval. So it streamlines the approval process further. And, uh, there is also safety net Um, so if someone sits on an approval too long, uh, the approval gets escalated to a backup user automatically. So additionally for more automation, we’re also exploring, um, the AI-assisted sign-off for kind of routine l- maybe lower risk cases, uh, where the system, uh, uh, you know, makes a decision automatically what should be approved to avoid, uh, maybe approvals altogether, so only exceptions are, um, surfaced to the, to the person. So what, what’s the impact? So, well, so the bottom line is that, uh, you

know, our goal is to make the approval cycle shorter, right? And less redundant. So the back and forth, um, that usually happens during approval when, uh, um, quotes get kicked back from approvers through a rejection. So, um, we want to make that faster, more efficient and, uh, still enforcing, you know, company policies. So again, this will get the quote out faster, and with that, the likelihood that you win the deal is actually higher. So that, that has been proven, you know, uh, the, the faster the quote turnaround time is, the more likely you’re able to, to win a, a deal. So with that, I am passing it on to Ramesh. Thank you, Manfred.

Hey, thanks, Manfred. Hi, everyone. I’m Ramesh, Product Manager at Zuora Revenue. In what next section I’m excited to cover breakage accounting. Okay, think about the scenario. The customer, uh, prepay for obligation, but it not u- but not using it fully. Okay, so the unused may be credits, tokens, uh, gift cards and loyalty points. The- For revenue recognition, the unused portion not going to remain in the– remaining in the books forever. Okay, it need to be recognized. Okay, when the ca- when the reduction is improbable at this point, revenue to be recognized, then breakage accounting is the, uh, solution. Okay. So now the most of the companies move towards the consumption models,

AA monetization. Obviously, uh, there may be, uh, a, a, a few unused, uh, unused usages that need to be recognized. Now, what the companies are using is most of them are not systematic, not accurate manual methods, which end up with a, a lot of inconsistency and audit problems. So what Zuora is going to provide? Okay, the solution is we are going to come up with three different, uh, methods to recognize the breakage, uh, uh, uh, breakage accounting, breakage revenue. So first one is proportional recognition. With this model, we are going to, uh, estimate what is the, uh, breakage is going to happen or the remaining use for that, uh, particular usage. Okay, identify it, using it, uh, using it through the variable consideration,

recognizing the revenue through the customer redemptions. Okay, next one is recognition upon expiry. Whatever the, uh, remaining portion, when it comes to the conclusion the contractual redemption, its period is going to lapse, we get the, uh, signal. Based on that signal, uh, recognize the unused, uh, uh, usages. Then the third method is recognition based on the non-redemption. Okay, recon– Uh, the, the revenue can be recognized on the– once the customer will come, uh, will, uh, is going to non-exercise the remaining right means, then the signal is provided, then the rema- remaining revenue is going to be recognized. So what is the impact it is going to create? This is one of the vulnerable area when it comes to accounting. The people are not, um, recognizing the, uh, the remaining balances. So Zuora is a go-to solution for automatic

revenue recognition. We provide a accurate, uh, consistent and auditable, uh, method which help the customers to recognize the, uh, uh, the remaining balance or to, uh, the, or the breakage amount perfectly. Okay, this is going to be a, uh, a trendsetter or, uh, it’s a path forward for g- having a clean accounting for the unused balances. That’s all from my side. Uh, Caleb. Thank you, Ramesh. Thank you. Now that we’ve heard about Zuora Revenue, we will dive into one last component, data warehouses. Thank you, Kevin. Yeah. Hey, everyone, uh, I’m Kevin. Uh, uh, I work on our platform team as

well as our AI products here at Zuora. Excited to be with you. Yeah. So next we’re gonna talk about, uh, something a lot of revenue customers have been asking for. Uh, so many of you are already centralizing your financial data in a cloud warehouse or a, or a, a data lake. And the problem until now is that our data warehou- warehousing connectors for the destinations you see on the screen, uh, covered only billing objects. So if you wanted your revenue data sitting alongside that billing data, you may have had to run multiple reports, um, as exports, write a custom sync script, uh, that may be brittle or pay for a third-party ETL. Um, that adds complexity for you, and it creates reconciliation risks between systems that should already agree with one another.

So I’m excited to share today that, uh, we’re now extending these connectors, uh, to Zuora Revenue. Uh, and these are now available today in beta. So what this means for you in practice is you can continuously replicate your revenue data into your own data warehouse or your data lake. Um, it uses the same connector framework that we have with billing. Um, so the 16, uh, supported destinations you see here, including Databricks, BigQuery, Redshift, uh, these are all available. The setup of these is very easy. Uh, it’s a self-service, um, interface through our integration hub, uh, where you can go in, configure your sync. Um, there’s a twelve-hour sync option and a twenty-four-hour sync option. Uh, there’s no APIs,

uh, that you have to implement, no custom pipelines that you have to build, and then your data starts flowing from revenue into the, into these destinations. Uh, so the payoff, uh, is essentially you’re gonna get governed access to your revenue data for business intelligence, uh, forecasting, reconciliation, uh, AI use cases that you might be running off of your data lake, um, all using team, uh, tools your teams already know. Um, now one thing I do wanna flag with this is that the revenue connectors are, um, are an add-on. However, during the beta period, uh, they are available, uh, uh, free of cost to, to evaluate. So if you run Zuora revenue and you want, uh, that data in one of these destinations,

uh, you can reach out to your customer success manager or your Zuora, uh, connection, um, to, to learn more about how to join the beta program. Um, looking ahead, uh, we are looking, uh, to move this into early availability and general availability. Um, and that’ll include different options from, uh, lower latency below the twelve-hour frequency sync, uh, as well as expanded object coverage. Okay. So now the final section of the day, um, is, uh, we’re gonna, we’re gonna spend some time talking about Zuora AI and Zuora MCP. Um, so everything I’m going to talk about, uh, I’m gonna walk you through, um, is designed to work with all your Zuora data permissions and operating controls that you already

use in Zuora. And, um, and so the way we’re gonna structure this is first I’ll cover, uh, the various brand-new capabilities in AI that we’ve been, uh, releasing. Zuora AI is on a weekly release schedule so, um, uh, a lot of you, um, have, uh, you know, are, are aware of this, but we are releasing, um, uh, updates in Zuora AI and MCP on a weekly basis. Um, and I’m gonna cover some of the highlights of some of the things that we’ve released over the last few months. Um, after that, I’m also gonna talk about where we’re going next. So I’m gonna show you guys a few concepts of, of, of new product features that we’re actively exploring. And then after that I’ll hand it over to Richard on our team to talk us through some of the MCP updates

specifically. Okay. So let’s start with, uh, we’ve been adding a variety of new agents. We have a roadmap theme in AI that we call Army of Agents, which is essentially adding more and more agents under the hood in Zuora AI to power the AI capabilities. Uh, the first agent I’m gonna talk about that we’ve released is the analytics agent. Um, so, you know, as you know, you, you’ve got a wealth of great data inside of Zuora. Um, there’s, um, uh, you know, really, really great information to understand how your business is functioning, uh, insights and opportunities that, that you can get from the data. Uh, one of the hard parts though is being able to, um, essentially access that data, query it in the right,

right way to answer the questions that you have. This is where the analytics agent comes in. Um, it, it’s avail-available natively in Zuora AI. Um, and you can essentially ask natural language questions of your metrics in, in Zuora. So whether it’s AR- MRR, ARR, churn rate, net dollar retention, average revenue per subscriber, what’s happening with billings and payments, um, all of the various metrics and data sets that you’ve des- defined in Zuora Analytics is now available from within the Zuora AI. And so the value of it is, um, uh, more than just charting, although we do have charting in Zuora AI, so you s- you see in the screenshot there that, um, AI will draw, um, charts and graphs

to help you understand the data. But, um, this should really make it a lot easier for you to answer questions about key subscription metrics in the business. Um, so, uh, for existing users, uh, should make accessing this data faster, uh, more accessible, um, and, and giving you all the same depth and ability to kind of slice and dice as you do in Zuora Analytics today, uh, natively from AI. Uh, the next agent, um, that we were excited to have released is our payment operations agent. So this one is focused on all the, you know, the exceptions that slow down cas- cash collection and create friction for your customers. So existing Zuora users can use this agent to investigate

things like payment status, understand payment gateway responses, diagnose payment run issues. Um, it supports, uh, payment and refund management, including payment schedules and payment schedule items. Uh, and it all operates, again, as with everything in Zuora AI, within your existing, uh, permission structures that you’ve set up for your users. Uh, one important piece here is explainability. So instead of just seeing a total on an in-invoice, a user can ask how that invoice or credit memo charge was actually calculated, including prorations and discounts. Um, and it gives itemized answers that, um, you can kind of see in the screenshot there on, on, on the page. Uh, it really goes into a lot of detail to,

to give you that information, um, as you’re managing your payments. Um, the goal of this is really simple. We’ll, uh, we wanna help, help you all have less time moving around the different screens in Zuora or, you know, moving around different reports, um, to be able to quickly and confidently, uh, resolve various exceptions as they come up. And, um, and so, so this is something that, uh, we recently released in Zuora AI, uh, really excited about. Uh, the next, uh, agent that we’ve released as well is the product catalog agent. Um, so let’s talk about something that, you know, you all may be familiar with as, as a challenge, uh, which is, uh, catalog complexity. Uh, this is where the product cat- uh, catalog agent really shines.

Um, so as your product catalog grows and, and perhaps it gets harder, uh, to see structural issues in the catalog Possible duplication of SKUs or configuration gaps. Uh, this analy- uh, this agent can actually analyze your product catalog. It can find opportunities for optimizing your product catalog. It can, it can walk you step-by-step, uh, through those, those opportunities, including things like, you know, um, analyzing, like building a price waterfall, uh, view of, of your catalog or, um, you know, really digging into the details and mechanics of how, how the catalog is, is optimized and s- uh, can be optimized and set up, uh, in a better way. Um, one of the things we do have is supervised mode,

right? So, um, uh, with the product catalog agent, not only does it analyze your catalog, it can help you actually update it, um, in a governed way. So if you need to make updates to how charges are configured, um, it can help you with that as well. Uh, the example we see on screen, uh, is, uh, just a very, uh, simple natural language request around, “Hey, show me my active products, my rate plans, my charges, billing periods and prices.” And, um, you know, that’s the kind of question your team might spend, uh, multiple searches, multiple exports to try to piece together. Now, the intent with this is, you know, through, through just a really simple chat with Zuora AI, you can get at, get at this information really quickly. Okay.

And then, uh, the last agent I wanna talk about, uh, that we’ve added recently and enhanced quite a lot is the revenue analyst agent, um, and, and exposing its tool functions, uh, within the, uh, Zuora MCP. Um, so revenue a- analyst is now available through MCP. I, I know we had a question on that in the chat a little earlier. Um, this means that all the revenue analyst skills, so contract modification analysis, revenue impact simulation, allocation change previews, scheduled job monitoring, staging data validation, revenue reports, these are, these are now also… previously they were available in the Zuora AI within the product.

These are all now available through MCP. Um, so if you’re using external clients, uh, such as Claude Desktop or Cursor, uh, or whatever your favorite, you know, MCP client is, um, you can now connect those, uh, to the revenue, um, MCP server and have access to all those capabilities. Um, so for existing revenue users, um, you know, this is, this is really powerful, right? Because now you have all of these, these revenue capabilities, um, uh, at your fingertips. Uh, and the idea is that, you know, this can help you bring, um, close critical revenue questions. You know, you’re in the middle of close, you need to figure something out. Um, uh, this is all now available to you, um, through MCP. So,

so we’re hoping this will help, uh, speed up a lot of the processes you do around, uh, around your revenue management. Okay, so in addition to new agents, we have also, um, you know, been spending a lot of time on just improving the visibility, control and accountability of Zuora AI. Um, and we know a question on a lot of your minds is, you know, as AI does more work inside the quote to cash, uh, life cycle, um, how, how can I actually trust it? Um, and so finance and operations leaders need to know, uh, what was requested, what the AI did, and where a human was required to step in and improve. Uh, and so we’re addressing that really in three ways, and

we, we’ve shipped, uh, three what I’d consider major updates around AI, uh, in the last few months, um, that address this. The first is what we call Watchtower. So Watchtower, if you’re an organization admin, uh, you can go in and get visibility of all the AI activity across your organization in any given tenant, whether it’s a sandbox tenant or a production tenant. You can go in, you can see all the different, um, AI conversations that are happening. Um, and in each of those conversations, you can see, uh, what your users are requesting, how the AI responded, the thought process that the AI went through, um, how different users approved the AI to take action, and all the underlying API function calls, uh, that were made. In addition

to this, we have also added in, um, new metadata into the Zuora audit trail. So for instance, if you’re in the change, uh, object change log, uh, audit trail, you can now see that a given user, um, who changed a record if they used AI to do that, and then you can even trace that to which specific conversation the user made that change in, so that you can see, um, again in, in the Watchtower there, you know, exactly how that conversation went, what, what was asked, how the AI responded and so forth. Um, putting this all together, it means you can move, uh, from, you know, a world where, you know, you’re not really sure, you don’t have true visibility into exactly what AI is doing

in your order to cash but, uh, to, to a world where, yeah, it’s, it’s fully auditable. Um, you can see exactly, um, what’s happening, um, uh, throu- throughout that whole, that whole process using AI. Uh, so this is available to everyone. All, all these capabilities, all the different, um, agents that we’ve released and all these various governance, uh, features have all been, uh, released to, to everyone. And then, um, the, the last thing I just want, I wanna mention, uh, to you all, a- another thing we released recently in Zuora AI in the last week or so is prompts. Uh, so, uh, you know, prompts, um, addresses one of the problems that, you know,

when I talk to customers A question I often get from folks is like, “Hey, h-how do I know what to ask AI?” Right? Like, what, what can it do? Um, what… How should I use it? Um, and so Prompts is in-intended to address that. Um, it gives you a curated library of high-value prompts, um, organized by different product areas, different use cases, um, covering both billing and revenue. Um, so instead of your, you know, our users starting from a blank chat window, uh, you can actually start with, uh, example prompts. Um, and the prompts themselves are also permission aware, so they’re aware of what’s set up in your tenant. They’re s- they’re aware of what the individual user is permitted to do,

um, and they’re aware of how you’ve configured your AI. So if you’re only in read-only AI versus supervised, it’ll, um, it’ll, it’ll, um, you know, be aware of that and show the relevant, uh, prompts. And, um, yeah, so, so this is something we’re really excited about. There’s around 150 prompts in the library now. This is gonna be expanding over time. Um, and then in the foreground screenshot we have there, the prompts themselves too will surface throughout, uh, the product. So if you’re using the side panel in AI, um, we will surface relevant prompts from the prompt library, um, as you’re using the tool. Uh, so encourage you all to check this one out. Okay. Um,

so that covers what’s new. Uh, team has been really busy over the last few months adding in all those capabilities. Uh, now let’s talk about where all of this is heading. Um, so the broader direction for Zuora AI is to become, you know, more complete, more proactive, more personalized, and more connected while keeping the controls that matter to finance fully intact. Um, that direction breaks down into a few threads. Uh, so specialized agents and skills that support entire workflows, not just, uh, single tasks. Trust and control through permissions, approvals, and audit trails. Personalization built on the tenant’s context, terminology, and preferences. Proactive experiences that monitor work and surface it before you have to ask. And also, we’re exploring agent-to-agent

connections. So as, as you all build your own agents, um, how can we have those connect with Zuora agents and Zuora MCP tooling? Uh, today we’re gonna zoom in on a couple product concept, uh, concepts in particular, uh, around, um, the ability to possibly schedule runbooks and also have better knowledge and memory in Zuora. So scheduled runbooks are about turning proven one-off workflows, um, into a de- a dependable operating rhythm, uh, for AI. And then knowledge and memory is all about helping the AI actually, uh, work from more and more context about your business, uh, so that the answers get more and more personalized and better over time.

Okay. Uh, so scheduled runbooks. Let-let’s, let’s talk a little bit about this concept. So, you know, many finance and operation teams are spending real capacity, uh, repeating the same investigations, uh, reviews or exception handlings on, on a week-to-week by basis. Um, so, you know, a one-off AI conversat-conversation may help in the moment, but it doesn’t turn a proven best practice or process that you run into something that you can reliably run re… in, in a repeated fashion. Um, so the concept here is that we do have the runbook capability in Zuora AI. Uh, if you haven’t tried it, I encourage you all to check it out. Um, it’s a way to essentially, once you have a process set up in Zuora AI that, that you find works

and, um, is useful, you can go ahead and, um, run that over and over. Uh, it saves the prompt, um, that you’ve created. What scheduled runbooks would do is allow you to actually set a schedule for the runbook. So you… We’ve got a little screenshot there in the foreground where you can see, hey, may-maybe there’s some AI process I want to run, uh, every Friday at five o’clock. Uh, maybe it’s a certain report or analysis that you’re running. Uh, with scheduled runbooks, you’d be able to go in, schedule this, um, and then in addition to scheduling, you’d also be able to set additional controls. So we have, we have two kinds of controls today in Zuora AI. We’ve got the behavioral controls and the approval controls. These are a layer of guardrailing that you can put

on all the AI that’s happening inside the Zuora tenant. Um, the idea with, uh, runbook level controls is that a certain process may need a certain additional level of control. So for instance, let’s say it’s a, um, a, a process that’s affecting financial transactions. Uh, you may say, “Hey, any, any transaction over a certain dollar value, uh, this scheduled runbook will ignore, uh, and it’ll only operate on lower dollar value things, um, uh, in, in your, in your business.” So, so this is a concept that we’re, we’re exploring at the moment. Um, something, um, uh, we’re, we’re looking to build. Um, and, uh, yeah, po-potentially a very useful, useful capability

for you all. Uh, the next item is knowledge and memory. And so this one, I think, uh, really has a potential to improve how you use Zuora AI. Um, so Zuora AI right now, it does have a certain level of, of knowledge and memory around, around your, um, around your tenant a-and so forth. Uh, what we wanna do with this one is take it to the next level. Um, there’s a couple elements to this. One is just increasing the visibility- Of the types of knowledge that the AI is working off of. So imagine an interface, which you can see in the background there in the screenshot, is a series of facts that the, um, Zora AI knows about your tenant

in terms of how it’s configured, um, uh, in terms of how you, um, operate your tenant and so forth. Um, these facts would be, uh, visible to you, um, so you can see them. Uh, you’d also be able to potentially upload your own information. So if you have standard operating pr-procedures, um, that you want Zora AI to know about so that all the users can benefit from that when they’re using AI, um, you’d be able to load that in. And then all the conversations that happen in Zora AI would be aware of this. The other aspect of this is memories. So as you’re, um, interacting, individual users are interacting with Zora AI, they may have certain preferences for things. Um, so the example I have in the foreground is around how, how, how a particular user might want to see reports in a certain currency

when AI responds. Um, these are things you could set as memories, um, and then, uh, essentially personalize your AI experience inside of Zora. I think the combination of these things, uh, we’re excited could really take the Zora AI to the next level, uh, to make it, um, you know, not just really capable, which, you know, we’ve been spending a lot of time building out the different capabilities of, of what it can actually do, but make it more efficient and personalized for, for your particular use case and for your particular organization. And speaking of personalization. Yeah. Yeah. So, um, so yeah, we would just love you– W-we’re gonna do a little poll. Um, we are considering,

uh, giving a personified identity to Zora AI, you know, such as a name. Uh, like for instance, let’s imagine we called Zora AI Luca. Um, so we just want to get your feedback. Um, do you think this is a good ide-idea for Zora to do to kind of, um, name the AI, give it an identity, um, or keep it more of a, you know, generic name like Zora AI? So we’ll, we’ll let you all respond to that poll. Okay. Uh, I, I am actually not able to see the response- That’s all right. -at the moment. So, uh, you know- We will be. Maybe we’ll, we’ll let everyone know, um, uh, in the, in the follow-ups after this, uh, what, what the vote was. But yeah, please do give us your, your opinion,

your feedback. We, we value what you all think, um, on this one. Thank you, Kevin. Uh, looks like right now current winner is neutral, so bit undecided at the moment. Okay, great. So with that running in the background, Richard, hand over to you to talk about MCP. Thank you, Caleb. Hey, everybody. Um, if you’re not familiar with the term, Zora’s MCP server enables, uh, your Zora tenant data to be available in your preferred AI client. Could be Claude Code, could be Claude Desktop, could be C– uh, ChatGPT, you know, Cursor, you get to pick. Um, the– We released– It’s almost coming up on a year since we first released this.

Over the past year, we’ve, uh, dramatically expanded its scope. Um, the vast majority of the products and features within Zora are now available through, you can access through the Zora s-MCP server from your favorite client. Kevin alluded to one of the more recent additions, which is, uh, much more revenue support for revenue, including, uh, you know, looking at waterfalls and, uh, managing revenue contracts. Um, these– this will continue on a, on a pace. It’s– we’re not done yet. Um, one of the first questions we always get asked about MCP is, uh, permissions and controls and audits and being able to follow up. Um, specifically the Zora MCP server, even though it’s external to the Zora UI,

the stuff that Kevin was showing was all in, you know, in the Zora UI, you still have to authenticate with the Zora login on a OAuth client ID. Therefore, all actions you take through MCP are traced back to and invoke your specific permissions and controls. Um, additionally, I was talking to a customer yesterday, while we released this feature a couple of months ago, there’s now user login-specific permissions about either to read AI, uh, read using AI tools, including MCP, or to be able to supervisory mode, which means being able to make, potentially make changes, uh, do a bill run that generates an invoice through the MCP server. These are all supported, um, but on a user-by-user basis, you now have control over who can do these things. Everything that

both MCP and AI do is routed through these r-r-rules and permissions that already exist for any time you’re in the Zora, you know, UI doing ordinary things in Zora. Um, any time you ask MCP to do something for you, um, modify a, a custom field on an invoice, for example, that’ll get tracked by Audit Trail, and it’ll be recorded as you the human. There’s no generic, there’s no AI shortcuts, there’s no generic AI user that everything gets lumped under. Everything that changes is tracked by the usual Audit Trail feature, uh, within Zora, and is tracked to the human who requested it. Um, one other thing that’s about to come out, hopefully very shortly, is CIMD authentication. This is a standard method of authenticating. It’ll

mean more AI tools will be available for you to use using Zora MCP. You’ll be able to get access to your Zora tenant data using additional AI tools that some of you, um, have been frustrated not being able to utilize yet. All of this is in early, uh, EA. It’s available now. You’re welcome to use it now. Um, if you have any questions, the documentation about installing it and using it is up in the Knowledge Center. You’re welcome to reach out to, uh, the account team. If you have any issues, please file a support ticket. Um, in terms of futures, if you don’t mind going to the next slide, Caleb, um, the next place we see taking MCP is that next level in terms of an, an agent-based toolkit. So this is you perhaps using AI, perhaps doing it the old-fashioned

way and just writing code. Um, but you’re building applications, and you want that application to have access to your Zuora tenant data. Um, uh, with a– with our agent toolkit, SDK toolkit, you’ll be able to quickly do that in a few lines of code, as it says in the right-hand side. So this is basically, you know, instead of having to use Cursor or, uh, Claude Code to access Zuora’s MCP feature functions, uh, build your own app that can access Zuora’s MCP, uh, features and functions and tools. Um, this is in alpha right now. We’re about to go into beta. If this is something of interest to you, please reach out either to your account team or to me or Kevin directly, and we’ll, um, uh, discuss, uh, and update you on what’s going on.

Um, that’s pretty much all I had. I’ll hand you back to Caleb. Thank you, Richard. So as we wrap up, I wanted to flag a few key dates coming across September and October, our community table talks. You’ll get a link after the presentation to sign up on Zuora Community, but as a quick preview of what’s in the calendar, credit and debt memo adoption, implementing AI monetization, observability for telemetry tools with event schedulers, automating revenue using tools we covered today, and Quick Assist. We’ve also got a few upcoming Zuora events worth putting on your calendar. A UK user group in London on September fifteenth, a France

user group in Paris on October eighth, and a virtual live revenue demo on September twenty-second covering end-to-end AI auto- monetization, connecting billing to revenue recognition. We’ll share the registration link afterwards if any of these are of interest. And before we close out, we would love to hear from you. There’s no better way of showing the value of what we’ve built than through your own experiences using it. So if you’d be open to sharing your story with us, please do reach out to your account team. We’d love to stay in touch. And so before you head out, a second poll that we would love to know what you’d like to hear more about. And based on everything we covered today, we’ll use this as a, a method of scheduling follow-ups accordingly.

You’ll notice the topics in the poll are consolidated a bit, but we are happy to set up deep dive sessions tailored to your business in any or all of them. So whether it’s billing and catalog, Zuora Experiences, revenue and AR, quote, and/or Zuora AI and MCP, we would love to utilize this to set up those tailored conversations and drive the business outcomes that you are intending to accomplish. We’ll wait a few moments before we jump ahead, but that poll will be available, uh, at the same time. So hopefully, today’s session gave you insight

into where we’re investing and more importantly, which parts are most relevant to your business. Thank you all for the time today. We look forward to a tailored follow-up conversation to help you get the most out of these features. Have a wonderful day.