Pegasystems Inc Oppenheimer 29th Annual Technology, Internet & Communications Conference
Review the key takeaways and the transcript of this earnings call.
Transcript
Preview the first fifteen paragraphs, organized by speaker.
Hi. Good morning, everyone, and thank you for joining us on the second day of Oppenheimer's 29th Annual Technology Conference. I am Param Singh, the Senior Analyst covering storage and info software. We have with us today, Ken Stillwell, Pegasystems' COO and CFO. Ken, thank you for joining us today. Before we begin, just for the audience, we have a question bar for you that you can send in questions, or you can separately email me at param.singh@oppco.com and I can ask the questions on your behalf. Again, Ken, thank you for joining us today.
Thanks for having me. Great.
I want to start at a very high level, because maybe some of the audience may not be as familiar with the Pega story. You've been a public company for, say, 30 years. Maybe you can take us on a very high level what Pega does, how's it positioned from the next wave of benefit on enterprise software, and some of this AI dynamics that we are seeing in the market today.
Sure. Pega, to maybe hit at a reasonably high level, what Pega does is there's a lot of use cases that large companies have that tend to be either regulated or high internal control heavy, things where you need to execute work in a very deterministic, consistent, predictable way. There are not off-the-shelf, so to speak, or out-of-the-box type solutions for many of these use cases. Companies have a few options. They can write their own, which has always been an option. They could buy a platform like Pega or someone similar to Pega to be able to configure the actual workflow and the use case similar to what is an application that they may have been able to otherwise buy off the shelf.
But since these use cases are really specific to the industry, really specific to the company, and sometimes the company differentiates the workflow based on their own advantages, companies love to do that configuration on a platform like Pega. So, we've always competed with writing your own code. The challenge with writing your own code is that the application isn't predictable, it isn't sustainable, it has a massive change overhead. So what we've really been, our tagline has been build for change. It's not just that you can actually build the workflow on Pega, it's that Pega's built to be able to evolve the workflow in a way that's very business-friendly, that's very user interactive.
And now what we've done is we've inserted AI into the upfront design, into the actual build and maintain and evolve stage, so that you can really use AI when you're developing your app, when you're evolving your app, when you're modernizing your app. And we have AI in the actual workflow. So, when you're in a workflow step and you want to automate something, or you want to use an agent instead of using a human being, you're completely empowered to do that, either with our AI or by calling your own agents or through your own gateway. So, we've taken this concept of a platform to be able to build workflow-based applications and really evolve that into an agentic workflow experience where you're leveraging all the capabilities of AI, both in the design and, when needed, at the run.
No, thanks for that, Ken. I want to dive into a few different aspects of that. So firstly, obviously, you're focused on delivering predictable outcomes, predictable cost for the client. How important do you think, and this is when enterprise move from more AI experimentation to more production deployments. Then we can talk about some of the products that you have today available to customers when they deploy these AI-centric applications, and how are they benefiting from it.
Sorry, repeat the first part of your question. I didn't follow the first part of your question, sorry.
Sure. Yeah, no. So, you were talking a little bit about predictable outcomes, right?
Yeah. So, when people build their own code, you have a wide variety of results, and it's not standardized and there's other issues Correct when you're accessing the data and getting a result.
So, the predictable outcome piece of it, probably the most interesting piece.
Yeah. I wanted to understand how you've incorporated some of the newer products that you've introduced into the platform over the last 12 to 18 months.
Got you. to deliver those predictable outcomes.
Got you. If you think about Let's pick a use case, like a loan origination for a bank. You're going to go in, and you're going to apply for a mortgage. The mortgage, the process for a bank might be different depending on if you're a wholesale bank or you're a retail bank or a mortgage originator. The process is never going to be exactly the same bank to bank, but it is going to involve a series of common steps. It's going to be a call to grab a credit rating, let's say. It's going to need some type of appraisal step, maybe. Some asset underwriting. But through that process, although there can be some variations, there are regulatory steps in there.
There are things that require disclosures, things that require anti-prejudicial type activities to make sure that you stay in compliant with the Fair Lending Act, for example, but also state lending acts, also national rules and regulations, et cetera. That workflow needs to be consistent, predictable, and always producing the same outcome. Generative AI cannot solve that problem because it is not producing a predictable outcome. It is producing a uniquely generative outcome each time that you actually ask it to do something.
FULL TRANSCRIPT
Continue the full translated transcript in StockNow.
Access every statement, the English original, and speaker-by-speaker history with StockNow Pro.
View the full transcript with ProCall participants
2 people spoke on this call — only 1 are shown here.
PARTICIPANT LIST
View participant details in StockNow.
Log in to see executives and analysts, their roles, and complete speaking history.
Log in to view all participantsKeep exploring
