PegaWorld 2025: Ask Me Anything: Pega GenAI Blueprint

PegaWorld 2025: Ask Me Anything: Pega GenAI Blueprint

So I'm going to just walk through to start out with before I open the floor up for questions. Um, kind of the differences between we have two, two Blueprint options for you. So the first is Pega GenAI Blueprint we call um, Platform or legacy or original. Um, and this is a way for all of you to, um, envision your workflow transformation. How many of you in the room have used, um, Pega. GenAI. Blueprint. Anyone? Yeah.

Cool. What about Customer Engagement Blueprint? Cool. Little in the back. Awesome. Well, essentially, both of these tools enable, um, collaboration and help you do work faster. But for, um, GenAI Blueprint, it's really the original is aimed at the developer, and it helps you transform ideas into applications. I'm hoping you saw, um, the Vodafone keynote yesterday where we saw that they created an app in under 40 hours, which is kind of insane when you think about how long it usually takes to create an app. So that's that's the OG Pega GenAI Blueprint.

And then in February we launched Customer Engagement Blueprint. Now, this is a way for folks who are trying to transition into AI powered customer engagement and customer journeys, and next best action to visualize what their marketing programs can look like, and also for those who are in the implementation phase to help jumpstart the implementation and visualize what that could look like for you. Also, if you're already a prolific user of Customer Decision Hub, this is a way to see how you can expand your use cases. Try different product lines. Figure out um, you know how to collaborate and socialize across functional area. So, um, one of the challenges we have with specifically Customer Decision Hub clients is that they really have to educate and continue to educate their stakeholders on CDH and what it does and how it works. And Blueprint really helps them to do that because it visualizes something that's complex and an aspirational way. Right? Um, You can also invite people in to collaborate with you on your live Blueprint, which is amazing.

And if anyone hasn't created blueprints yet, take a picture of this slide. Let's see here. Great. It's working. Um, that's about all I had in terms of prepared content. I really wanted to kind of turn this over to you guys and learn more about your experience and, and what you might want to know, and I'll do my best to answer what I can about og Platform GenAI Blueprint. And I'll probably know a little bit more about Customer Engagement Blueprint, but yeah. Are there any questions about the tool? Hi, my name is Vinod Kumar.

I'm from TCS. So last time when we tried a Blueprint there were multiple Bas who were working on the team and there was no versioning control in Blueprint. So do you have any version control in Blueprint now or still the same? So is that directly at Customer Engagement Blueprint or. No. It's the. Yeah. So. Um, there have been a lot of updates in recently like in the last two weeks.

So I'll get the specifics. And if you can find me on LinkedIn, I'll get that answer for you. All right. Thank you. So much. Yeah. Anyone else? Hi. Hi.

Well, I struggle with sometimes in the use of Blueprint is, um. We're not actually creating new applications all over again, but we're trying to add new process to an existing application. So what is your roadmap or looking ahead towards using more the existing Pega applications as foundation to load also into Blueprint and to use that to add a process to it or something like that? Yeah. You know, we're we're ideating on the tool so frequently, so frequently. And I think that's a problem that other users have had. So I know that it is in the roadmap, but I don't know specifically when it will be available. Yeah. Unfortunately us product marketers are very slippery like that.

Hi. I'm from I'm Indu from AIG. Hi. I'm following the same question. Right. We were trying to use the Pega Blueprint, um, to kind of integrate one of the legacy application, creating the Blueprint and integrate onto the existing application. Yeah. So we were not able to make it work. We worked with Pega as well.

So the current Blueprint that you're talking about, it's actually only applicable for any new, um, applications or it can work with the existing application as well. Yeah. So I think existing applications is on the product roadmap. New applications is where we're at at this point. Okay. Yeah, absolutely. Okay. Thank you. Yeah.

No problem. Hi. Sorry. The mic so far. Hi. I'm the CIO at Pega. Um, if you have any questions that you want to field to me for Blueprint, feel free to throw them over. Oh, great. So there was a question around versioning.

Yes. We do not support versioning. And that's intentional. It's not an application in of itself. It's just for ideation. And then all of the work that you're doing to build the application is in the Platform, which is where we have all the versioning. Come on up. Sure. Come on up here.

David, good to meet you in person. Finally. All right. We got David on board here. Oh, you turn me on. There we go. Great. Um, this question over here was wanting to use with existing apps. So.

So we do have a feature that will allow you to put blueprints into existing apps as well. So those can be added or modified existing case types. Do you want to talk through a little bit on that? Sure, sure. So there's a process to pull the applications out from the platform and reimport them into Blueprint where you can see the case types. You can make some modifications and support the full round trip. Great. Um, does anyone want to give feedback about Blueprint? Because you have a very captive audience right now, and if there are things that you're on your wish list, or you want to talk about your experience in the blueprints.

Hi. Yeah. Based on that last question there, when you import the blueprint you created, let's say you have your Constellation application modeler built and your own data model when importing the blueprint is that it's going to mess things up, or how do you keep track on the data model and everything behind it. So there's a step in the import process where you can choose to replace or keep what you have in the system. So you do avoid those situations where you would be overwriting anything. But you don't know in the Blueprint part what your data actually is in your current system. So you have to then import that part so it knows what your structure is, or. You have the stages and the steps. So if you added some additional stages to the process flow, you can you can insert those as part of it.

So you avoid that screen. But let's say you want to reuse a model that you created in your current application. You want to reuse that, let's say an employee or a customer data model part. And that same data model part is used in the Blueprint. It's more like maybe an association or so. It's already there. Do you then copy that part in the Blueprint? So the Blueprint knows that you're going to use that model or just leave it out when importing, then say, reusing it? So that's a more nuanced question I don't have the specific answer to that, but I can certainly put you in touch with the team.

Who can answer that. That may be on the maybe on the roadmap. I'm not sure. Okay. Thank you. Hi, I'm Cath from Navy Federal. Um, I'm kind of excited to play with the tool at the innovation booth. Yeah. My question pertains to the Blueprint.

How do you guys look at industry models to come up with these default templates? Right. It's kind of like a template where you can go and look. Okay. Operational risk or something. It gives you all the use cases. Yeah. How often do you guys go to the industry and look at okay, what's the new industry best practices or standards. And then update your blueprint template.

So as the industry evolves, as the market evolves, your blueprint recommendations I assume, will also evolve to give the most up to date type of use cases. So kind of curious to know about that. Yeah. So specifically for Customer Engagement Blueprint, That's a feature that was just added the industry use case templates. But we have a really robust, um, group of industry principles that are constantly updating us on what the trends are in, in each industry. Um, and if that is something that, you know, could be improved, definitely open to feedback. Just kind of curious to help us understand, like if I pick a specific use case, let's say incident response, cyber security incident response. Right? There might be a niche recommendations.

There could be, you know, the government recommendations to kind of like these are minimum things you need to do as a process. So do you embed those things into your use cases. So next time when you want to go and try out a new process, the template is going to give you okay. These are steps that were added because of new industry regulations or new requirements. So your blueprint is evolving with the industry right. Yeah. So we make use of like you know because our business changed dynamically. Yeah. So new things come.

So when you go back and try to use the Blueprint, we want to see the most updated blueprints to be used. Kind of kind of curious to know what your process is. And if somebody could speak to or behind the scenes who might be able to talk about that would be great. Yeah, absolutely. So you're talking specifically about customer engagement? Blueprint just in general. Yeah, because we have a wide variety of use cases. Yeah, right across the company. So just kind of curious to know how does the blueprints work.

And can you add custom blueprints like use yours and then bump it against industry best practices and see where the delta is, where we need to add things like that. Yeah. So on the customer engagement side, um, we're still sort of iterating. So 25.1 goes live in September. And so we can take take this back to our product team and have them sort of help and explain. But um, you know, more robust capabilities are coming. And so we will be able to add additional use cases. Also it helps um, the, uh, for you, you can bring in your data objects and your data assets and your, your brand assets. I think that's to going to help the, um, the Blueprint be smarter about what you're trying to achieve.

So even if you pick a template in real time, you can see that as you're putting in your objective and things are changing as, as you interact with the tool. Okay. Yeah. So as far as the, the Platform Blueprint, you know, we're encouraged as employees to put in blueprints all the time. Okay. So as you can imagine, we have over 40 years of industry experience across a number of verticals. So there's a lot of IP and information baked into blueprints from that. But we're also getting feedback from people all the time. Just people just coming up with ideas.

And then those blueprints are actually turned into templates, which is where you're seeing the blueprints that are behind all of those different categories. Yeah. Very nice surprise. You spend a lot of project. We spent just recently finished one spend six months ideating. When I go to your booth, I see that it's already done. You could have saved us a lot of time. So that's kind of like, curious because there's so many other use cases we have that this could have saved us a lot of time. So it's kind of curious.

Like it changes. It changes all the time. So, you know, Kerim and others say like come back and check all the time. There are new features, there are new templates added every single week. There's a a vlog that Matt Healy does. Is it weekly? Monthly? It's basically a what's new with Blueprint. And he chit chats with Jeremy Trimble and they talk about what's new.

So that would be something great to follow. And you could access that on Pega community. Sure. Thank you. Thank you. Yeah. And for those of you who who aren't active with Pega community. I really encourage you to go there because there's a lot of great Blueprint documentation, and also your peers are commenting and chatting on there about their experiences. So I always find I learned the most from doing and having my peers there.

So give Pega community a visit. During the keynote, we have seen the ability to use Blueprint to migrate a legacy systems towards Pega. Is there also a use case already there that you can use Blueprint to migrate actually from cosmos or UIKit to what? Constellation. So we're working on a utility. It's called application signature, still in alpha stage, but we will get to a point where we can inventory. We call it a heritage Pega application, and we'll be able to inventory a number of different rule types from the system, and to be able to bring that into a Blueprint, to reimagine, to redesign and then insert that back into the system. As a Constellation and compliance system, we are targeting certain types of UI constructs. The main one that we're focusing on now are the sections.

As we evolve that I'm anticipating, we'll see other ones being added as well. Hey Dave, I know as the CIO of Pega that my understanding is the Blueprint development has a pretty unique development process. My understanding is part of the development is done by your team and the CIO's office, and then part of the development is done by Kerim Akgonul team, the chief product officer. Is that true? If it is true. Can you talk a little bit about why you're approaching it that way? And if it is true, if folks in the room have enhancement requests, which ones do you have roadmap control over? If you could share that with them, they might want to make some requests to improve the product with the guy who controls the product resources. So.

So yes, development is divided between products and it. So I have responsibility for all the enterprise applications at Pega infrastructure as well as digital. So Pega.com community Academy. They're all under my team because you log in with your Pega credentials. The the whole front end experience is built and managed by my team as well. So we want to make sure we have a seamless experience. You know, sharing authentication. You also have the option if you'd like to extend your company's SSO into Pega. So if you want to do further securing of the assets, blueprints, all the other things that are available to you, you know that is an option as well.

And there's instructions on Pega community on how to do that. Um, so so yes, the work is divided, but we still do work as one Pega so if there are enhancement requests, you know, they'll still go through the same, the same process for consideration. And we are rolling things out all the time. So, um, you know, chances are if you have an enhancement request, there's probably ten others out there that have that as well. So we're always looking for feedback on how we can make it a better experience and provide you better agility with with your application build outs. Great question Peter. Thanks for answering questions today. Yeah. Um, I'm curious as to some of the benefits for those of us who are not on legacy applications or structure within Pega.

Um, what are some of the benefits, maybe that we haven't heard in a highlighted fashion this week to coming in at this point and getting to take advantage of what exists there today. Um, what are some of the the benefits and the value that we get from having waited till today. The benefits of using Blueprint? Yes. Yeah. Where we don't have to migrate off of what I'm hearing is cosmos or other other legacy applications. Um, you get to just kind of start with a clean slate here. I'm starting with a clean slate is a beautiful thing. We've done that for a few applications ourselves internally.

Um, we have seen, no joke, 40 to 50% efficiencies using Blueprint, because a lot of the build work that we traditionally would have to do is simplify tremendously by starting out with a Blueprint and leveraging all the capabilities that it provides. So it's given us a lot of accelerated capabilities to get things out much quicker. So apart from just not having to figure out ways to patch things together, to be able to get some of the benefits. Um, are there other uses that you've found for Blueprint that you don't have to overcome struggles or hurdles in the same way, then apart from just you get to use it. Just for ideation purposes. You know, typically when you start projects and you do requirement sessions, you're limited to the knowledge of the people in the room. So what I find refreshing is you still have those people, but you have, you know, this, this amazing capability that can think out of the box and pull in ideas that you may not normally think of. And then my last question, um, is do you have any sort of sense of the customer use of Blueprint from just as an ideation tool to actually implementation? What is the kind of attach rate, if you will, of what Blueprint spits out as as a recommendation.

And like, what percentage of the time is it that it's being adopted as more than just ideation but implementation? I don't have the exact numbers, and I know those numbers are obviously increasing as the awareness grows. But, um, we, we use it internally just for ideation as well. Um, because again, you know, outside of the box thinking, um, you know, suggestions just how quickly you can pull together those thoughts, it really has helped us in a number of areas. Just think through some of the problems that we have. So no feedback yet from clients as to like if they're actually implementing it or just using it as POC. They're doing both. No, they're doing and actually, I was talking to some folks here over the past two days and before they would put a lot of energy into putting together proposals to get budget to do something. And, you know, they can pull together these things much quicker, you know, in a matter of hours or minutes in some cases.

So it's just made it much easier to have those conversations, to get approval, to go to the next step. Same on the customer engagement side too. It's it's been a great tool for helping us understand and articulate, you know, what the needs are of certain functional areas to their stakeholders and other departments. Um, we are at the stage right now where you it's mostly ideation, but you can import, um, and create, uh, actions and treatments, which is basically a marketing offer. Um, and in the roadmap for 25 one, we have full, full import there. So hopefully we'll have the full gamut from ideation to implementation, but um, partial now more in the future. Great. Thank you. Yeah.

There's no question about when you've built a Blueprint, right? And then because I know you guys are upgrading like weekly, right kind of thing, does it take any of the the new enhancements that are being put in on a weekly basis and apply it to that Blueprint or, you know, so, I mean, will you go in and suddenly something's a little different, but you don't know why. Or does it does it maintain where wherever you left it? If you build a Blueprint and then say they come in the next week and add some capabilities, your information will still be there. Typically they're net new things. So you may find that, you know, something that you created is, you know, has some additional options, but they haven't been populated. Okay. Um, but it's not like you get into a situation where the blueprint you built two weeks ago would no longer be functional. Okay?

Because there's there's not really a place right now, right? Where it just lists, you know, like this week we implemented X, right? There's nothing that tells us what's new in blueprint. I think that's where it goes back. To just that that. Blog. Yeah Okay. Okay. Thank you.

Do you have an option to. You have the upload option now, right? So is there an option to upload a Blueprint itself to generate an additional information to generate a revised version of the blueprint. The blueprints will will live on in the system. So you can always pull them back up, make enhancements and then regenerate the blueprint file. Okay. Thank you. Hi. I have two questions.

So as an enterprise, I don't have visibility on all the blueprints which are created by the, you know, employees within that organization. So would that be a feature where I can look at it, or is there already a feature where, you know, I can see all the blueprints created by the organization? That's the first question. Second is, uh, what is the roadmap for the Agentic AI fabric that we have? Uh, is it anyway? Uh, you know, uh, related to the Blueprint or what would be the roadmap for that? All right. So the first question is just visibility around blueprints that are created for your organization. I believe there is an ability to see across all the blueprints that are created for an org.

I believe there's a role to do that. Um, there either is right now or I know there will be. Um, and then my team is also working on some features for, uh, broader organizational visibility. And I know one of the aspects of that was some insights into blueprint creation activity. Okay. Um, second question was around Agentic. Fabric, the Agentic, uh, AI fabric that we have, which is just rolled out. Right. Uh, how would that be?

You know. How would how would we work with along with Blueprint to generate, you know, Agentic AI orchestration layer or the overall, uh, AI flavor, right. How how would we do it? What would be the roadmap? So that would be resident within your your system operating. And really what that does is helps you to get access to agents and capabilities that are built across multiple applications. So you're not just having siloed experiences and capabilities. So that helps to bring it all together and make it accessible from any any system that you're calling it from. And you know, as you heard probably earlier today or yesterday with MCP and Ada, a, you know, that will also open it up even further to agents that are built in other technologies.

But within the Blueprint, can we integrate it? Like can we say we want to build agents and then it will automatically, you know, create the Blueprint which will have the AI agents, Didn't. To my knowledge, that's not something that's currently on the roadmap, but certainly that's something that I can take back to the product team for consideration. Okay, thanks. All right, you guys. Oh, yeah. Come on up. Come on down like the price is right. Just one more, I promise.

No, please. As many as you want. An ability or maybe a future ability where as you use Blueprint more and more, it. The system is already recognizing prior blueprints you've created or implemented. So it can be smarter about your business and your practice, and the way you've created and adapted this tool. So you don't have to retell it, right? You're not saying connect it to these data sets or models. Yes, there will be concepts of reusable assets that are being introduced in the coming months for that very purpose. You know, you shouldn't have to define the same thing multiple times.

So enterprise integrations to systems and other things. And then the other thing which they are working on is the ability to have your own Knowledge Buddy, where you can put other informational assets that could be pulled in for, for reference. So then there, from what I'm hearing, I'm going to repeat it back in case I misunderstood it. In the future it will be able to, as I'm saying, you know, referencing this prior Blueprint that was created, I'm creating this new one and you can sort of point it to familiar information. So as it's creating a new workflow, you don't have to do as much of front loading of information or preferences. Yeah, technically it may not be from referencing of the Blueprint, but it could be from just an enterprise data store of reusable assets. Okay, but conceptually, yes. But not Blueprint specifically. Yes, I believe so.

Okay, I'll submit it as a request. Okay. Thank you for Customer Engagement Blueprint we have on the roadmap. One of the features will be the ability to upload brand assets and creative briefs. And then also on the roadmap is to be able to take your insights from Customer Decision Hub on how your marketing offers and treatments have performed, and import that back into Blueprint. David, thank you so much for coming to my rescue up here. You're welcome. I thought I was just sitting in the back but happy to contribute. No.

It's great. I mean, better than Matt Healy. Don't tell him that, please. I might have to. Thank you all so much. Please contact me if you want to talk about customer engagement. Blueprint. And contact Matt Healy and tell him you missed him. All right.

Thank you.