Pegasystems Inc. (PEGA) Earnings Call Transcript & Summary
September 9, 2020
Earnings Call Speaker Segments
Rishi Jaluria
analystGood afternoon, everyone. Let's go ahead and get started. My name is Rishi Jaluria. I cover software here at D.A. Davidson. I'm delighted to have with me from Pegasystems, CFO, Ken Stillwell. Any investors who would like to ask questions to Ken, please submit them through the chat function. I'm going to continue to monitor that or feel free to e-mail me directly at rjaluria@dadco.com. Ken, always a pleasure to have you. Thank you for being here.
Kenneth Stillwell
executiveThanks, Rishi. Good to see you.
Rishi Jaluria
analystLet's start with just kind of broad overview of Pega for the generalists in the room. And fortunately, you're starting to become a lot more well-known with investors over the past couple of years. But let's just start with that.
Kenneth Stillwell
executiveSure. So Pega operates in 2 segments of the market. They are kind of eerily similar in terms of the challenge and the value proposition. We're in the CRM space. And we're what's -- in what's called digital process automation, which used to be -- some part of that used to be called business process management. But they -- although they seem like very different kind of segments of the market, they're actually quite similar in terms of the problem you're trying to solve. It's where you're trying to manage large volumes of transactions either in a consumer channel, i.e., CRM or in an operational channel, i.e., BPM or DPA, and you're trying to execute large volumes of work across a series of workflow steps that likely will touch and interact with multiple systems and applications within your -- within the customer's environment. And what's important is to get that work done end-to-end using robotic process automation where possible, using AI where appropriate, to be able to minimize the amount of human touches that need to happen either by our clients' employees or by the consumer. We like to say that we're not a workflow system, but we're a work-do system. We actually try to execute the work as opposed to just running processes. And I think that's kind of where we differentiate ourselves. Our clients use us to really try to streamline work activities across their organization. And a lot of times, the front and the back office do intersect and overlap because anything that you do with the consumer is likely going to rely on certain information that you may have in the operational systems.
Rishi Jaluria
analystGreat, great start. I actually do want to ask about COVID, but I'm going to first go to something that you kind of touched on, which is there's been this evolution of the kind of back-office business from BPM into this broader DPA or digital process automation platform. Can you walk us through that evolution and how Pega's products have evolved alongside that?
Kenneth Stillwell
executiveSure. So years ago, there was this concept of back office, where you executed typically ERP adjacency areas or types of -- ticket type activities like transacting an ACH within a bank or managing a claims adjudication and an insurer. Things that you would -- that would happen kind of using operational systems and really kind of not touching the consumer, not really even any -- there was a perception that wasn't really any value to connect the types of operational activities to things like how you would do an outbound lead management program or how you would manage your sales campaign. We quickly kind of matured ourselves into the customer service automation space. Although when we did, we didn't necessarily connected to CRM because at that time, Salesforce had acquired the ticker symbol CRM, and they were really a sales automation player, and a fairly disruptive one. And so the market was more viewed as customer record management as opposed to relationship management like it is now. And so even though we were in the service automation space, there wasn't a natural relevancy in how that would connect to pipeline management or sales automation. And then as time went on, we saw more and more of our customers getting us involved in their service automation initiatives, which then drove into marketing automation, how do I want to think about communicating with my client. When they come inbound, either through a digital channel or to the call center, what do I want to do with them? Do I want to market to them? And if so, what do I want to say to try to upsell, cross-sell, retain that client? And then you naturally think, well, wow, if you're going to market to them or you're going to manage that inbound kind of interaction, what about when you're selling to them. So the concept of CRM really evolved over time. And as such, it really brought us and our relevancy of our solution into CRM. And some of it was us. We bought a company called Chordiant, as many of you know, in 2010, that got us into the marketing automation space. But I think the market kind of evolved to come closer to us, and it became obvious that we were -- that we could have some success in CRM. And that was we really went in, in a large way about, I guess, it's probably been about 5 or 6 years ago where we really -- so we went from not even being someone that anyone heard of in CRM to now being someone that, yes, I think, is reasonably well-known in the CRM space.
Rishi Jaluria
analystGot it. Helpful. All right. Let's talk about kind of the current environment with COVID, right? How are we thinking about the headwinds that we're seeing, the tailwinds that we're seeing? And maybe alongside that, right, there's this term digital transformation that gets thrown around a lot. But what really is digital transformation the way you see it?
Kenneth Stillwell
executiveSo I'll touch on COVID, and then I'll get to the digital transformation. So COVID is an unfortunate situation for a lot of companies. A lot of companies are really struggling. Employees are struggling. I mean it's taken its toll on us as a global workforce. In terms of Pega, we have some -- we've won at a faster pace, and we've had some demand move at a slower pace. I think on the total net of it all, I don't think we've been really impacted positively or negatively in the first half of the year. In fact, I would even argue to say that where we've landed through 6 months is probably where I would have thought we would have landed had COVID never happened. Now the longer term, what COVID does do is it highlights the next part of your question, which is digital transformation. It highlights the importance of having a digital footprint of making sure that when you interact with your clients, that those interactions are -- can be handled in real-time in a store, on a phone, in a digital property, at a reseller. Sometimes it's pushed, sometimes it's pulled in terms of that interaction. And I think the clients of ours were thinking about digital transformation for a number of years. What COVID did was really accelerated the prioritization of it. I first heard the word digital transformation, I can actually remember it was in the summer of 2017. At an investor conference where people started to bring up the fact that digital transformation, hey, everybody is talking about digital transformation, that should really help you. But at that time, I don't think people really understood what it was. Now people know. Well, if I have to shut down my call center in Manila and nobody can come in the office and nobody has laptops, and I don't have software that can be accessed remotely, what are my options, right? I mean how do I even have people work? So I think that it really forced the whole visibility of digital transformation in a very short period of time. Some of that was happening already with Amazon retail, really changing the whole model on how people shop and how people interacted. But now I think it's down to -- it's not about shopping. It's about everyone. It's about where we work. I think soon, it will be about how people go to college and where -- and how students go to high school, and how I just think it's the entire interaction is going to be so dependent on digital. And who would have ever guessed that, that would have happened so fast. But I think that, that is probably one of the positive aspects of all of this disruption, which is we're realizing how much more -- how much bigger reach we can have as a global workforce and how we can actually try to kind of make lemonade out of lemons, so to speak.
Rishi Jaluria
analystAll right. Let's turn to the cloud transition. So we're past the midway point now. From your perspective, a, how has it played out relative to your expectations? And b, you looked around the software landscape a lot, I know we've talked about this. But if we were to benchmark your cloud transition against some of the other famous cloud transitions and software, what do you think that you've done right? What do you think you could have done better?
Kenneth Stillwell
executiveSo given that I've seen a few cloud transitions myself at places where I've worked, I feel like I have a reasonably broad view of the -- there are companies that try to transition to cloud by forcing their clients. I mean literally saying to a client, "You no longer can use the product unless you move to our cloud." And although that does work financially in some sectors, it doesn't -- it isn't client-centric. It's not actually focused on the client. It's focused on the own economics of your business model as a company. Because you're being quite -- you lack a lot of empathy when you go to a client and say, "Thank you for all the investments that you've made. Now you have no choice, but please buy my new product, pay more for it and I'll manage it for you." I don't think that's -- that might be reasonable to do in commoditized products, where you're going to take the price down and you're actually giving them an option. But in enterprise software, I don't think that's the right way to behave with clients. They have complicated environments. There's another kind of transition that is more like a mechanical transition, but not really anything different. Meaning, I'm going to stop selling you perpetual licenses, I'm just going to sell you term licenses. And there, really nothing has changed. It's just the contractual elements have changed. And although that can make sense for clients, what real value have you created? You haven't added any type of a managed offering or an upgrade in service 24/7, the ability to stay current. You haven't offered anything other than maybe a different contractual relationship. And then there's a transition where you're really thinking about, I have a client that is using a certain type of capability in a way, perpetual license on servers. And that isn't going to work for them in the long term. They need to actually have maybe someone else manage that or they need that to exist in their own virtual private cloud. And as part of that, they need the ability to keep all the rich capabilities continually current. Meaning when releases come out every week, every 2 weeks, every month, they're getting that new capability. When bugs are addressed. When security vulnerabilities are addressed. When they need to access the system at 3 in the morning on a Sunday, they actually know that there's a reliable partner behind that. And I think that giving them the option to have that partner be Pega, with Pega Cloud, or if they elect being their own client cloud because many large companies actually have their own virtual private cloud teams that are actually quite capable, and they want that flexibility. So that's our transition. Our transition isn't a forced "You have no choice, you must move." And it's not just a contractual kind of cash flow-type valuation play. It's really around a new set of capabilities that clients need to help us manage them in some cases, but giving them the ability to buy what they need and expand as they need it. The biggest problem with perpetual license that I think most companies would agree is you don't know your need, you don't know your demand, which then requires you to overbuy and requires the vendor to deeply discount. It creates this very weird awkward contractual discussion, which is, I want you to buy as much as you can, and the client says, great, I'm going to buy more than I need, but I need you to give me a really big discount or maybe even give me the product or some maintenance. It's just -- it's not a partnership, it's more of a negotiation. It's a play-on usage. And I've always struggled with how that was right for clients. And so we are trying to balance that client need and client centricity and focus with also what makes sense for our shareholders and our stakeholders as well.
Rishi Jaluria
analystAll right. So now at your Virtual Analyst Day that you held a few weeks ago, you reiterated your targets, right? 2022, $1.3 billion in ACV, $1.6 billion in total revenue. But you also said you'd be disappointed if you didn't do better. And I think the other interesting thing was you stuck to these Rule of 40 target but with a greater balance towards growth than you initially expected. Can you maybe talk about what's giving you confidence in the targets? What's changed that you're pivoting more towards the growth side of the equation while still being responsible about balancing growth and profitability?
Kenneth Stillwell
executiveSo there's 2 factors that change from when I first started thinking about our long-term targets. When I first started to think about our long-term targets, I didn't think Pega Cloud or maybe I didn't anticipate. I hoped, but I didn't anticipate Pega Cloud would grow as fast as it has. That's become such a big part of our business. So that's one thing. And that changes a lot. That changes the ACV growth. That actually even delay some of the profitability improvements because naturally, there's a delay with SaaS accounting revenue. It actually gives us the ability to increase backlog at a faster pace because more of it is going to backlog. So there's lots of that -- I mean generally, that is a good outcome, right? The Pega Cloud is more popular. The second thing was that I didn't model that we would penetrate and grow as fast as we have with -- in the markets that we're in. I modeled a growth rate that was more at the higher end of what we had seen up until that time. But if you look now, our growth rate in the last 18 to 24 months is the fastest the company has ever grown in terms of the size, are not only in dollars but actually, the rate of growth. And so with the rate of growth increasing and more and more of that becoming Pega Cloud, that means you're going to get higher top line, but some less revenue conversion and certainly, you have to invest in the business, which causes the pressure on the bottom line. And so that's -- there's really not anything that's changed in the model other than that dimension.
Rishi Jaluria
analystYes, that's totally fair. And by the way, I tell you there's a lot, but you deserve a lot of credit to being one of the first public software company CFOs to be talking about the Rule of 40 and really kind of bring it out there. I think a lot of CFOs now talk about it, but a lot of credit to you for being one of the first to bring up that.
Kenneth Stillwell
executiveYou know what, Rishi, just a quick comment on that. Coming from private equity, that's all they talk about, right? And so my background of -- and if you think about the role of private equity is really to try to run an operationally superior model and Rule of 40, even Rule of 50, quite frankly, at some of the places that I've worked, is not uncommon. In the public markets, I think we are -- we need to be accountable to that kind of result. And we -- if you look at the average for public companies on the Rule of 40, it's about 31 or 32. If you look at the Rule of 40 in private companies, it's closer to 40. I think that we have to accept this, public companies, that we have an accountability to that kind of performance. So that's kind of the reason why I'm passionate about it.
Rishi Jaluria
analystThat makes a lot of sense. All right. So now as we think about the gross margin piece because I get that question a lot, right? You've seen cloud gross margins start to improve. How do we think about the drivers for further gross -- cloud gross margin expansion because that's ultimately going to be the biggest driver towards future, just cash flow margin expansion?
Kenneth Stillwell
executiveSo there's some kind of impact to the margin that's just based on scale, right? Higher amount of clients allows us to get better pricing with our infrastructure, allows us to get scale. Some costs are more fixed, like our FedRAMP certification, cost us the same on an annual basis, whether there's 1 or 2 customers or 20 customers, right? There's some level of efficiency that you gain. So there's a -- I would say there's a fairly consistent operating leverage play that will happen for a few more years, right? The other factor is that our product in the way that we manage our product in the cloud environment is -- we made some good improvements already and more to come. We're using kind of things like Kubernetes to be able to virtualize the nodes in the cloud, which actually allows us to scale across multiple clients but we have -- through automation, have no risk of degradation or any capacity. It almost let you simulate multi-tenancy in a single tenant, you get the best of both worlds. There's also things with our product and how our product operates and runs that we've released in the Infinity products, which really allow us to manage the capacity usage much more efficiently in a cloud environment versus the way that our product may have been built 10 or 20 years ago, which is more built for servers. So that -- so I think there's -- those are 2 big factors, right? Just the operating leverage of scale and the things we've done and the tools that we're using to manage the scalability. I mean even hibernating our clients when they're not being used, just also not only in the interest of reducing cost, but also in the footprint environmentally, right, to be environmentally conscious around not using capacity when it's not necessary.
Rishi Jaluria
analystThat makes sense. All right. Let's go to, I think, 2 areas that have become buzzy, I guess, in the recent years. One of those being RPA, robotic process automation. And then the other being low-code, which one of your competitors talks a lot about. Can you walk a little bit through these spaces? How you play and on how you think broadly about them?
Kenneth Stillwell
executiveSure. So this is a -- these are 2 interesting points. They are similar in some ways. And I'll tell you how they're similar. Robotic process automation or robotics automation where you can take humans out of steps if they're not necessary, obviously, that is a wonderful advancement in technology, and it should be leveraged. Low-code, no-code philosophically as a way to build products so that you don't have to write Java code or C++ code every time you check-in, check-out, go through complicated release cycles, regression, testing, et cetera. Obviously, that is a wonderful way to develop enterprise software for scalability. So totally agree with those 2 aspects of it. What I have been very vocal about is there's a lot of, I would say, unrealistic expectations around what RPA would become as a product. I mean to think that building out kind of the modern version of screen scraping was going to somehow turn into enterprise software. I don't think -- I think that was a stretch. To think that companies are going to start with low-code product and ideate on it and turn that into the next ERP system that JPMorgan Chase or Bank of America or Morgan Stanley or any of the -- that's not really realistic either. So although I think the concepts and the capabilities are tremendously relevant for helping enterprise clients, I think that we have a tendency of making those new solution areas to solve for every problem under the sun. And I think that we have to understand that there is a place for low-code as a technique. And certainly, people like to ideate in a quick low-code environment on kind of long tail-type use cases, tremendously helpful. Of course, RPA will help when you don't have APIs between applications where you can use this screen scraping, copy-and-paste kind of capability to automate, love it. But we have to be careful that we don't then take those narrow use cases and say that they're going to take over the world in terms of how they disrupt all other software vendors. And that's kind of where I have tried to give my position of -- to pause and think about whether that's realistic or not.
Rishi Jaluria
analystGot it. All right. I get asked by investors about one of your recent hires, Hayden Stafford, right, came from Salesforce and then Microsoft, like spent what, like, 6 years there or something like that. So what -- how should we be thinking about his hiring? What's kind of his broader role? What do you think that he can bring to the table that's new and incremental for Pega?
Kenneth Stillwell
executiveSo the -- in a nutshell, Hayden has seen -- when he started at Microsoft Dynamics, they were about $1 billion, as I understand it. And in the last 6 or 7 years, they grew from $1 billion to over $3 billion. Pega is ironically $1 billion as he -- or thereabouts as he starts. And we have aspirations to grow into a multibillion-dollar company as well. The things that he did and drove better partner involvement, really pushing through the ecosystem, building lots of really good coverage on all of the large organizations, reinforcing the vertical model and really enforcing a sales cadence and operating kind of accountability for how you deliver value as a field team, as a sales pod, all super relevant at Pega. The work that Jeff Taylor did 2 years ago when he came in of building out the operational infrastructure and the go-to-market strategy is completely consistent with Hayden coming in to now be our leader around that area. So I'm super excited. I think he's a perfect fit. He's been with us for about 90 days, incredibly collaborative person, really aggressive. I mean I love having someone that's kind of been there, done that, but yet still has enough energy and youth of saying, "I've got to run here, and I've really got something to prove to myself and to the market." So I think he's a perfect fit for us.
Rishi Jaluria
analystAll right. Also I want to ask about Pega Process Fabric. I think you've introduced at a conference in June. And by the way, I think, really fascinating that you've committed already to turning next year's May conference a virtual this many months out. I just saw that press release this morning. But why is Pega Process Fabric important for Pega? What does that bring? How should we be thinking about that product?
Kenneth Stillwell
executiveSo I've talked a lot about Pega, helping to orchestrate work across applications. Process Fabric really allows not only that to be the visualization, the actual user experience, the tool that you use to set up those relationships, but also to govern and manage the activity in the volume and to look for exceptions or areas where the system may need to have some calibration as it scales out and handles more and more transactions. So Process Fabric is really not something different than what our mission has been, it's much more of a delivery mechanism. It also allows us to start with a kind of a very good UI tool with clients that have never used Pega, right? We can sell Process Fabric as their orchestration work basket across executing work. But we can also sell it to clients that already use Pega as the visualization of how that happens. So I think it's really exciting to see that orchestration of what we did under the hood actually come up right into the dashboard.
Rishi Jaluria
analystI think we're at time. As always, Ken, really appreciate the time and all the insights. So thank you so much for being here.
Kenneth Stillwell
executiveThanks, Rishi. Thanks, everyone. Bye.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete Pegasystems Inc. transcript — plus 251,000+ transcripts from 12,000+ companies, speaker segments, AI summaries and full-text search — through the EarningsCalls.dev API.
Get the API View API docs →This call discussed
For developers and AI pipelines
Programmatic access to Pegasystems Inc. earnings transcripts and 251,000+ others is available through the
EarningsCalls.dev REST API. Plans from $24.99/month — full transcripts, speaker segments,
full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.