🎁 Black Friday: 50% off Unlimited and 30% off Pro annual plans
Pegasystems Inc. (PEGA)
NASDAQ: PEGA · Real-Time Price · USD
28.07
-0.79 (-2.74%)
At close: Nov 19, 2026, 4:00 PM EST
28.08
+0.01 (0.04%)
After-hours: Nov 19, 2026, 6:04 PM EST
← View all transcripts

RBC Global Technology, Internet, Media and Telecommunications Conference

Nov 18, 2026

Summary

AI budget reprioritization and sales execution challenges pressured recent results, prompting regional teams and AI pods focused on proving value. Q4 pipeline is record-high, but conversion remains uncertain; the $700 million 2028 free cash flow goal depends on growth reaching 10% in 2027 and 2028.

Rishi Jaluria
Software Equity Research Analyst, RBC

My name is Rishi Jaluria. I cover software here at RBC. I am delighted to have with me Ken Stillwell, who is the CFO and COO of Pega. I think we have been doing this for more than 10 years now. You have been a mainstay in these fireside chats, so always look forward to it. Ken, welcome back.

Ken Stillwell
CFO and COO, Pegasystems

Thanks, Rishi. Thanks for having me for, I think it is 11 years.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yes.

Ken Stillwell
CFO and COO, Pegasystems

So

Rishi Jaluria
Software Equity Research Analyst, RBC

That is awesome. Okay. Maybe let us just start, a little bit of an overview of Pega. I think there has obviously been a lot of different evolutions of the business from the older Pega, the digital transformation, COVID era Pega, now the AI era Pega. Maybe let us just talk about that and we can jump into some specifics from there.

Ken Stillwell
CFO and COO, Pegasystems

Sure. We went through a series of, I would call them business model transition type activities where we went away from perpetual licenses to term, we went from term to cloud. We tried to target different segments. But the reality of what we did and have done for pretty much since inception, was we help clients automate workflow at scale. So, what does that mean? In healthcare, you have got to onboard new participants. In banking, you have got to deal with disputes or credit card increase request, loan originations. In insurance, you are doing renewals or maybe even scoping out new pieces of insurance. In the government, we do a lot of constituent management work.

Pega's platform ran the 2020 Census, which was kind of a very complicated offline, online with 450,000 people around the world, trying to track down all the different methods. It really comes down to when you are trying to get scale transactions done and you need them to be done in a deterministic way, in a consistent way, meaning it is the same exact method every single time. You cannot vary on it. That is really where our sweet spot is. Although our use cases have expanded, we started in business process management, we went into CRM, we have added decisioning capabilities, the core of what we do is really managing transactions across a workflow and automating those.

Now with AI, there is a tremendous opportunity to insert AI in the front end of design and also to basically use AI to streamline those transaction flows so you can try to get the human beings out of whatever they might have otherwise had to do.

Rishi Jaluria
Software Equity Research Analyst, RBC

Absolutely. Maybe let us expand on that a little bit, because I think there are a lot of discussions I am having where investors are still trying to figure out Pega's place in the world. I think there have been two key messages that Alan and you have been talking about. Number one is knowing when to use LLMs and when not to, right? Bringing together the probabilistic and deterministic. Maybe walk us through that as well as a term that has become really important is the harness. We just had a private company session before this where they were discussing just how important the harness is beyond just the models. Maybe you could walk us through both of those messaging and how that impacts Pega.

Ken Stillwell
CFO and COO, Pegasystems

I think there are kind of three aspects of AI that we have kind of come to realize in the past 12 months or so. I wouldn't claim that we knew this from day one, but I think as we have watched this play out, the first is how do you use AI? What do you use it for? You want to use it for things that are probabilistic. You want to use it for things where you can actually ask it to use information to either give you like a dashboard or information, or to probabilistically maybe predict something that might want to. Those are very excellent use cases we use AI.

Things like, I want to address a bug that I have in my software. I am going to actually use an agent to go look at the code, to figure out what might need to change, to identify where the bug is, and to execute, and then to run testing scripts on it. It is interesting because, and I will go back to this harness thing in a second, but that is one kind of dimension of it. The second one is, what model do you use?

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

Not all models are built for every purpose, and I think we are starting to see that you can get a lot done using models that from two years ago versus using the frontier models, which are incredibly compute intensive and expensive. There is this cost, excuse me, element of it. Then you kind of get into the harness discussion.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

The way that we think about a harness is if you have a workflow that needs to be done exactly the same way every single time, and I am not talking about 10 times, I am talking about a billion times, right? Where regulators are actually coming in after the fact and say, Show me that you actually, your anti-money laundering process, and I want to know every single transaction that you had, every account that you opened. What was your process? What diligence did you do? How did you back? These are not like silly things that large organizations do.

The way to use AI in that is not to actually go into a prompt and say, Hey, go do the AML check for Rishi. Even though it might know who you are and have all our processes, what it does for you is going to be different than what it does for me.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

By definition, the model is built that way. Then you kind of think, well, how do we create harness? How do we structure it so that the models can really be powerful and can execute? And you do that through a series of rules and workflow and structure so that you kind of help the AI models do it exactly the way that it was intended to do. Now, that's not for every use case, because there's a lot of use cases that are just putting together data analysis or the new way of search, or there's other things that you can ask it something five times and get different answers and it's not a problem. But that's a problem if you do a loan origination and you run the same borrower through five times, and three times you approve it and twice you decline it.

That's a problem, right? The way that we think about harness is, we've used this analogy of like a restaurant kitchen. Right? Which is, if you were going to actually build something at scale, or you wanted to create a menu and serve that menu repeatedly, right? Fast food is probably the perfect example of this. You got to basically first create the recipe.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

That's where you use AI. But when you actually get to like, when someone comes in and says, I'd like a cheeseburger, you want it to be basically assembly line. You don't want every single time for it to go, A cheeseburger, what would be on that? How do I The whole concept of this recipe is you spend all your AI in design time, which is really where we are very big into AI token usage is in the design time. Why that's helpful for us is when you're building these enterprise workflow systems, historically, there was a lot of customization and a lot of kind of maybe more like science projects that system integrators and Pega and our clients would do when they built these systems. And then you get no repeatability. It's very hard to upgrade. There's risk of bugs and anomalies and vulnerabilities.

You really want the design to say, This is the right way to build it. Then once it's built, you want to use AI where necessary in all the different steps and stages across that workflow to try to minimize any human interaction. Really, you want to make it autonomous. So we view this kind of concept of like the harness being the workflow is the underlying harness to help AI actually drive the work across the workflow.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yep. Okay, got it. That's really helpful. Maybe let's now get into Pega specifically, and I'll just rip off the Band-Aid here, and let's talk about what's happened the past couple quarters. You've had three tough quarters in a row. You had macro pressures in Q1, you had the AI crowding out effect in Q2, and we'll dive deeper into that, and then now you called out some sales execution issues in Q3. Can you maybe walk us through each of these?

Ken Stillwell
CFO and COO, Pegasystems

Yeah.

Rishi Jaluria
Software Equity Research Analyst, RBC

What's giving you confidence that this isn't structural or there's not another shoe to drop?

Ken Stillwell
CFO and COO, Pegasystems

First, I would be remiss to say that I actually can predict the future. I will tell you what I see.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

The beginning of the year, what we saw was we saw a very big, at the end of Q1, I would say a very big shift into executives and senior leaders saying, We have to show something with AI.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

I do not think, if you went and talked to any company that was here and you asked them honestly, Did you have pressure from your board and from your leadership team to try to show AI use cases? Anybody that says no, I think would be lying. Of course there was a push for that, as well as us. What happened was you had this massive push, We just got to show AI. That carried into Q2. Q1 was not, it was not a terrible quarter for us, but at the very end of the quarter, we saw some deals kind of melt or shift.

Then we went into Q2, and what happened in Q2 was, I mean, almost without exception, every campaign that we were working on, our sponsor at our clients would say, I cannot, I have to focus on AI right now. I have got security on me about how we are going to build the model gateways. I have got to. That really kind of carried through to, I would say, maybe like July. When you got into August and September, things started to change, right? You started to see people. First of all, you probably, you saw it in the news, but also inside our clients, you started to see people say, Okay, listen, AI is not for everything.

By the way, I am not getting ROI on a lot of my AI use cases, and I cannot continue to just spend at this pace. We started to hear that and started to see that. Now, that said, there is lots of, I know it is only about 15% of AI projects show ROI, but that is still a pretty big number if you consider starting from zero. There is certainly value there. What happened is you started to see people start to lock in their budgets a little bit.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

That is kind of what we are seeing now. If you look at 2027, I would say it would shock me that we had one of our clients that said, I have no idea what I am going to spend on AI in 2027. But in 2026, every one of them spent more than they thought, without exception. I think, and I will give you a great example.

One of our large banks that we were talking about modernizing some of their legacy applications, and I will not say the name of the model provider, but they are using one of the model providers to do some of their testing and help to do some of the mapping as they move off of these like COBOL systems into a new platform. We work with this particular AI provider, and we have said, Listen, let us get some capacity. Let us get some tokens.

Let's actually start to model this out. The answer was, We're already at our budget.

You know, like, Our token budget, we're not spending any more this year, and we've got a really tight budget next year. I predict you're going to have a lot more discipline around AI spending. That's kind of the first piece, which is like the AI confusion, I'll call it. Second piece is our selling process. For those of you that don't know the history of Pega, a lot of our selling process is that we would go to a client and we would sell the license, and then a system integrator would come in after the fact, and they would take the license, and they would have a totally parallel conversation about what they were building. Many times, we weren't even involved in that. That's the way enterprise, large enterprise platforms were built. Clients don't want to do that anymore, right?

They actually want to actually see the value. This whole concept of forward-deployed engineers is largely because we don't just want a flashy demo. We want to actually see how you're building value on our platform. We want to see like a minimum lovable or minimum viable product that at least gives me some idea what I'm doing. That's the nature of selling. We were really not prepared for that in the beginning of 2026. We've made some changes to really arm ourselves around getting prospecting, getting deeper engaged with our organizations, up higher in the organization, because that's where budgets are sitting right now. Then actually taking some of our sales engineers, our product teams, and our PS teams-

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

-and putting them together into AI pods, which is essentially our equivalent of the forward-deployed engineering model. We call that Lighthouse engineering, or we call it AI pods. Think about that as just like FDEs.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

So that is kind of the change that we made, but we just anchored that in the last month, where we made those changes and announced them to the company. I do not think the changes are going to take a long period of time.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

I think it will take a little bit to settle, probably a couple quarters to settle. But this is not like a two-year kind of transition. So those are the two very different things that we saw. One was this disruption of AI and distraction, and then realizing we have to change the way we sell.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

We have to change the way we solution with our clients. So that is kind of the two pieces of it.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. Maybe that is a great segue into talking about some of the go-to-market changes that you announced on the call. You also added a little bit of a headcount reduction alongside that. Can you walk us through the tenets of this, and then when should we actually expect to see the impact of these changes?

Ken Stillwell
CFO and COO, Pegasystems

First off, I think you should see the changes that we're making as our seriousness around making sure that whatever our growth rate is, that we'll resize our cost envelope to make sure that we're focusing as being a Rule of 40 kind of principled company. The first starting point is, we can't continue to spend if we're not seeing the growth.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

We had to actually make changes to get ourselves better in line. Some of the changes we made, our sales teams, we actually wanted to put more autonomy in the regions, closer to the buying centers. We had a globalized model, which means that a lot of our groups were kind of across all three of our theaters, and we really needed to get people in regions. So in Japan, in Australia, in the countries in Europe. And that required us to change kind of our management structure a little bit around that. That's the first one. Not a huge change, but a change nonetheless. Because we wanted to create these better selling pods kind of around verticals and around regions. The second one was really trying to this change of like this forward-deployed engineering model, right?

I think the first one, the selling change, I think is going to be, to be honest with you, I think we're probably largely through that change already just in a month. I don't think that's a big one. The selling change for sales engineers and the AI pods and Lighthouse and FDEs, that is a behavior change.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

Many of our partners, the system integrators, they're not completely there, right? So we have to work with some of our historical system integrators to help get them in that too, because this is a different way of deploying technology than what you typically saw in the past. So I think that's going to be I think we will probably 25% of engagements by the time we get to the end of Q1 or Q2 will be done this way, but it is not going to be completed in Q1 or Q2. I think this is a different way of us engaging. We also wanted to change some of the operational structure because we had operations teams. Like, we wanted to focus on go-to-market, technology validation and proving, and then we wanted to figure out how to scale the ops.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

A lot of the ops groups kind of were combined and came under me, which were distributed. That was, to be honest with you, that was an alignment but also an efficiency play.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yep. Okay.

Ken Stillwell
CFO and COO, Pegasystems

Those are some of the big changes.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. No, that is really helpful. Maybe let us get into the ACV growth outlook from here, right? Obviously with all these challenges, you have seen ACV growth kind of decelerate, but you also have talked about your pipeline is kind of hitting, I think you said the strongest pipeline for Q4.

Ken Stillwell
CFO and COO, Pegasystems

Yeah.

Rishi Jaluria
Software Equity Research Analyst, RBC

You're seeing Infinity getting real traction. How should we be putting these pieces together, and how should we be thinking about what's as things, as you get more of this AI traction, what should the ACV growth look like?

Ken Stillwell
CFO and COO, Pegasystems

First, when we started 2026, we had a very backend loaded pipe, which didn't help the situation that we had at the beginning of the year. We have our pipe coming into Q4 is the strongest it's ever been. I mean, and it's up year-over-year, healthy double digits growth.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah

Ken Stillwell
CFO and COO, Pegasystems

In terms of the pipeline build year-over-year. Now, the question about conversion rates and win rates is the one that it's hard to predict, right? Because I don't know what the budgets are going to look like in Q4, are going to look like in Q1 or Q2. So that's probably the only part of this that I'm a little bit apprehensive of, and I don't feel like this is still a normal environment out there. But our pipe is great, late stage pipe is great, and it's very broad too. It's not like we have four deals that are $20 million each. We have lots of broad opportunity. So I'm very optimistic that many of those are actually going to close Q4, Q1, Q2.

But we are probably a little bit more cautious just around not knowing how budgets will play out in Q4 and into 2027.

Rishi Jaluria
Software Equity Research Analyst, RBC

Okay. Got it. Then maybe let's get into kind of the potential AI contribution. To start with, how should we think about the pricing and packaging around your agentic AI capabilities, right? Maybe a good opportunity to remind investors how your traditional business model works that has not been seat-based, which obviously is great for this world, but maybe let's tie that together.

Ken Stillwell
CFO and COO, Pegasystems

Well, I mean, we used to charge by seats, but largely we do not charge by seats. We charge by activity. So a dispute, a loan origination, a credit card request, an address change. Think about that as like activity. You could call that an outcome too, but I'm going to just be simple and call it activity. So that's the way we charge our clients. The way the system measures that is there is a case created. So we have case-based licensing. Case is like a unit of measure, okay? With AI, the way we monetize AI is we do not charge clients when they use AI on a case or in a workflow.

What we do is we actually have a markup on AI when they use it across the solution, then we allow them to use AI anywhere they want inside of those transactions. That's where picking the right model, making sure you don't use too much compute, you don't have a token issue, like that's actually where that kind of cost harnessing comes in. We have a lot of visibility. We know exactly what the AI call would be. We know which model it's being used. We use AWS and GCP are our two cloud providers, so we know Bedrock well. By the way, clients can also say, I don't want to use your AI, but I want to use my own.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

We would charge a lesser markup to allow them to basically access the workflow through an MCP call to be able to get to whatever their AI model of choice is.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. Okay. So now let's bring that in. If we think about just getting back to kind of the numbers, is there any potential visibility into a re-acceleration of ACV? Is it too early to be talking about that? Just especially coming off the targets that you laid out at the analyst day.

Ken Stillwell
CFO and COO, Pegasystems

Yeah, I think that it is not too early to see that pipe looks really good in Q4, and it should flow into Q1 and Q2. It is probably a little early to say that I have 100% certainty on our close rates.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

But the good news is we're engaging. We're engaging with our existing clients, with new clients, their late-stage pipe. We've done tons of Blueprints and tons of engagement with our clients. So that part is, I'm very optimistic. It's just I'm not as confident in terms of close rates as I have been in the past, because it's not as much of a science in the world we're in right now.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. So maybe to build on that, one of the big inputs into quarterly close rates is going to be around your sales cycles. You've talked about some deal slippage. I think Q2 to Q3 to Q4. Can you maybe talk about what do you think is causing that? Maybe bring it back, because you brought up Blueprint. I think one of the initial theses on Blueprint was this could actually speed up your sales cycles.

Ken Stillwell
CFO and COO, Pegasystems

Yes.

Rishi Jaluria
Software Equity Research Analyst, RBC

And your implementation times. Is that something that we can still expect to be a contributor to kind of bring the sales cycles back down, especially as we think about Infinity and everything coming in, maybe help a little bit?

Ken Stillwell
CFO and COO, Pegasystems

This is something that probably it would help to provide a little bit more clarity on how we see this. Blueprint speeds up the sales cycle because at the front end, it gets you to be able to get an opportunity faster into pipe and get it to move into a later stage pipe. The AI pods and Lighthouse and FDEs are actually a critical part to take it from there.

Blueprint can't take it the whole way through.

Rishi Jaluria
Software Equity Research Analyst, RBC

Right.

Ken Stillwell
CFO and COO, Pegasystems

Right? We actually need Blueprint to build visibility, design, and energy to be able to get that into the pipe and get it maybe to the second stage-

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah

Ken Stillwell
CFO and COO, Pegasystems

-maybe the third stage of the pipe. When you get into closing, that's actually where we need to engage in a different way, which is kind of that more like FDE model.

Rishi Jaluria
Software Equity Research Analyst, RBC

Got it. Okay. That's helpful. Then maybe to add on top of that, I know one constant conversation we've been having for the past several years has been the kind of mix of expansions versus new logos. There's been a little bit of a shift on that. Can you maybe walk us through what you're seeing on that front? Especially with a lot of these new capabilities you're building, do we expect that there could be a little bit more of a new logo contribution as we look forward the next couple of years?

Ken Stillwell
CFO and COO, Pegasystems

Historically, Pega was really never able to sell to new logos in a big way. The reason why we weren't able to is because the sales process to be able to get them to actually be interested was just very heavy. So although we did sell some new logos, it was normally people that used to work at a company that used Pega that then went to another company, and we would try to If you had somebody that really had never heard of Pega, it's not like we're a household brand. We don't spend a ton of money on marketing, and it was really hard to visualize how we could help them.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

That's where Blueprint changes it.

Blueprint really gives us this. I mean, we have salespeople going literally into the first meeting, showing a Blueprint, taking a use case, and actually showing almost a working production app. It is not really working production, but it is visual enough to get people to see, Oh, that is the way the experience would be. That, naturally, I get excited about that because that is our way into new logos. I do think the pipe, first of all, the pipe has, a lot of the growth in the pipe is actually new logos.

We actually are having a lot of momentum with new logos. I still think there is new use cases with our existing clients because we are not even remotely penetrated with our clients. In terms of, it is not like we are 25% penetrated with our clients. We are probably, in our biggest clients, we are probably 20% or 25%, and our average client is probably 1%-5% penetrated. So there is a tremendous opportunity with existing clients, and with Blueprint, we should be able to break in new logos. So I am very, very optimistic about our opportunity to get into new logos.

Rishi Jaluria
Software Equity Research Analyst, RBC

Okay, got it. That is helpful. Maybe let us now turn to the competitive landscape, and maybe let us bucket it into three categories. Number one is kind of the traditional back office vendors, so that could be Appian, that could be the RPA vendors to the extent they are relevant in this conversation. Second would be the broader kind of Salesforce, Microsoft, et cetera, of the world.

Ken Stillwell
CFO and COO, Pegasystems

Yep.

Rishi Jaluria
Software Equity Research Analyst, RBC

Then maybe third, let us add in the AI natives, right? There are some that are kind of messaging some of this broader digital transformation, workflow transformation.

Ken Stillwell
CFO and COO, Pegasystems

Sure.

Rishi Jaluria
Software Equity Research Analyst, RBC

There's obviously concern the model providers themselves will get a little bit more into that space over time, especially as they themselves leverage some of the FDE. Can you maybe walk us through what's kind of the update on that competitive dynamic from each of these three buckets?

Ken Stillwell
CFO and COO, Pegasystems

The competitive dynamic on the first two buckets, which is the legacy, I would say the historical platform competitors versus maybe like the CRM or horizontal type providers. The competitive landscape has not changed a lot. I mean, if you look at the companies that we compete with, there's not a huge difference. It's the same cast of characters. If you look at the Gartner Quadrant or the Forrester Wave, and you look at the companies that are in there on the top right, it's really largely the same companies. There's not much. If you look at that's a good parallel to who we would see. When you get over to the build your own, that's the one that's probably the most interesting. Listen, we always competed build your own.

When Pega first started, the whole reason why the company started was because people were custom building applications on Fortran and some of these old languages. We went in and said, Don't do that. We can actually give you a tool that's like low code so that you can actually get some of these repeatable pieces that you can almost Lego build them together, like using that analogy. That's kind of like a threat that we've always had. The question comes back to why do people not build their own? The reason why they don't build their own is if you're trying to build a disputes application at RBC, why would you build your own when you can buy one that gets maintained across 100 banks? That is not a differentiator. Your dispute application is not a differentiator.

You're not generating revenue with your dispute application. You're trying to manage regulatory risk.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

The real question becomes, why would you want to build your own, manage your own, deal with bugs, engineer? That's actually the question that I think we should all ask about these AI natives building custom applications. In some places like the federal government or large custom use cases, I think you'll still want to build your own. That's always been a competitor of ours. But when you look at the actual deterministic workflows that we do in a big way, you just can't live in that world. I don't think AI makes it a little cheaper.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

But to be honest with you, it writes 10 x as much code, which means 10x as much bugs, which means you got to manage all the engineers. You got to redo your entire development process. We know that firsthand because for those of you that don't know the way that engineering was done back in like 20, maybe 15, 20 years ago in the military, there's something called spec-driven development. What spec-driven development was really big in like missile programs and defense because what it said is you got to tell me exactly what you want to build because I can't get anything that's different than that. In commercial, that kind of just went to the wayside. Now it's back. The reason why it's back is because you have to tell the model exactly what you want to build.

If you don't tell the model what you want to build, God only knows what you're going to get.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

I think that that is still going to be something people look into, but I'm very confident that is not how you build. You're not going to want to be custom building applications that a vendor can sell, build once and sell a thousand times.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. No, that makes a lot of sense. Maybe let's go to the topic that we usually talk about, but AI has obviously been taking all the time, which is your traditional cloud transition.

Ken Stillwell
CFO and COO, Pegasystems

Yeah.

Rishi Jaluria
Software Equity Research Analyst, RBC

What is kind of the state of the union there between Pega Cloud, Client Cloud? How should we be thinking about the momentum of that going forward? Maybe I will just toss in an AI-related question.

Ken Stillwell
CFO and COO, Pegasystems

Okay.

Rishi Jaluria
Software Equity Research Analyst, RBC

Have you seen a slowdown in Client Cloud to Pega Cloud migrations because of AI?

Ken Stillwell
CFO and COO, Pegasystems

We have not.

Rishi Jaluria
Software Equity Research Analyst, RBC

Okay.

Ken Stillwell
CFO and COO, Pegasystems

I will clarify one thing. We have seen a slowdown in migrations, but I will explain that in a second.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

Our cloud, 75%+ of our new deals or our growth is Pega Cloud. We are still migrating. The clients migrate every year. So that percentage keeps going up on the Pega Cloud side. The thing that has changed, and I would not put this in the AI camp, is that there is a big push outside the U.S. for sovereign clouds.

Countries do not want to. We actually have some engagements where large countries, I mean, these are like historically very friendly governments to the U.S. said, I don't want to use one of your U.S. hyperscalers. I am going to build my own. France has done that. Germany has done that.

I do think there is a push to say, I have to control my citizen data. Now maybe that will change with the election, but certainly there was a big push to say, I am really worried about what you are going to do with my data, and I don't want my data to leave the borders, not just of the EU, but of my country. I think some of that was the Russia-Ukraine thing, but also some of it is some of the things that have happened in the U.S. around trying to get access to foreign citizen data. I definitely think that is not AI-related, but that is people saying, I really want to move to managing my own cloud infrastructure. Now, the good thing for us is we are single tenant.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah.

Ken Stillwell
CFO and COO, Pegasystems

We can go with if we want to build a cloud cluster in Germany, we can partner with, and we do partner with T-Systems, who is a German-based company, and do it. We can partner with the sovereign cloud in France. We can do the same thing in Netherlands. I do think, for us, that is maybe just as much of an opportunity

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah

Ken Stillwell
CFO and COO, Pegasystems

to be able to differentiate, because most of our competitors are not single-tenant.

They really do rely on these regional data centers. Sovereign cloud, if you haven't heard about it, I would say it has become a bigger topic-

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah

Ken Stillwell
CFO and COO, Pegasystems

-with a lot of the protectionist kind of policies all over the world.

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah, absolutely. Maybe to close out in the minute and change that we have left.

Ken Stillwell
CFO and COO, Pegasystems

Yep.

Rishi Jaluria
Software Equity Research Analyst, RBC

So you gave this target of about $700 million in annual free cash flow in 2028. How confident do you remain in that? What are kind of the key drivers and assumptions, especially given where things are, and how are you balancing margin versus this potential ACV re-acceleration?

Ken Stillwell
CFO and COO, Pegasystems

Yeah, I think we're very committed to the $700 million, but the reality is if we continue to be a single-digit grower, it's going to be harder to get to $700 million in 2028. But we're very committed to it. That's the reason why we made some of the operational changes this year to set ourselves up for 2027. If we're a 10% grower in 2027 and 2028, I have a lot of confidence in that number. If we're a 5% grower, then-

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah

Ken Stillwell
CFO and COO, Pegasystems

-it up and make sure that we're getting operating leverage each year. So that is-

Rishi Jaluria
Software Equity Research Analyst, RBC

Yeah. Okay. I think it is a great place to jump off. Ken Stillwell, thank you so much for being here. Thank you, everyone.

Ken Stillwell
CFO and COO, Pegasystems

Appreciate it.

Rishi Jaluria
Software Equity Research Analyst, RBC

Awesome.

Ken Stillwell
CFO and COO, Pegasystems

See you.

Rishi Jaluria
Software Equity Research Analyst, RBC

Thanks.