At Vodafone, the awkward part of building software happened before anybody built software. Teams could spend months turning a business process into requirements. The resulting slides looked settled. Whether the application would actually make sense to its users remained an expensive question for later.
- Pega coordinates decisions and work across people, software and AI.
- Its buyers include banks, insurers, telecoms and government agencies.
- The useful lesson: test the process while changing it is still cheap.
The meeting before the machine
Vodafone’s network team tried Pega Blueprint, which generates application designs from descriptions of work. Then it changed the meeting. Business owners and delivery teams gathered around a live preview, adjusted the workflow together and left with an agreed backlog. The method acquired an acronym, RUDI: Rapid Understanding, Design and Innovation.
At PegaWorld 2025, a Vodafone representative described one workshop, two iteration meetings and seven weeks of effort to deliver a radio optimization process. A separate budget movement process went from idea to delivery in under 40 hours of effort. Those are specific examples, not a stopwatch guarantee for the next buyer.
“No sprint without a Blueprint.”
Vodafone Center of Excellence mandate
The distinction matters. A preview gives users something concrete to challenge. A requirements document gives them something to interpret. Pega’s appeal begins in that gap.
A chess problem wearing a business suit
Alan Trefler tied for first place at the 1975 World Open chess tournament. He later worked on computer chess at Dartmouth. In 1983, aged 27, he founded Pegasystems, passing up Stanford Business School, according to his company biography. The relationship between those pursuits is more interesting than the familiar image of a chief executive thinking several moves ahead.
A chess program needs rules, a representation of the current position and a way to choose among legal moves. A business has analogous problems: what is happening, what is permitted, what should happen next? The resemblance helps explain Pega’s emphasis on making decisions executable.
Pega Platform supplies case management and workflow orchestration. Think of an insurance claim moving through evidence gathering, review and payment, with people handling exceptions. Its low-code tools let teams model that journey visually. Customer Service applies workflow to service interactions. Blueprint helps design the application before teams commit to implementation.
One architectural idea has a gloriously untechnical name: the Situational Layer Cake. Shared business logic can coexist with variations for a country, product or customer. That matters when a multinational wants consistency without pretending that every market has identical rules.
The company calls its broader approach center-out: organize around the case and the decision, then connect the channels and underlying systems. A customer might start online and finish with an employee. The work should retain its context along the way. That is a useful buying question: can the proposed system follow the case when the customer changes channels?
The next conversation, at bank scale
Customer Decision Hub handles another kind of move: deciding which action makes sense for a particular customer now. Commonwealth Bank of Australia used it to create a Customer Engagement Engine spanning branches, phones and digital channels. A published Pega case describes responses in 200 milliseconds, happening around 20 million times daily.
The point is coordination. A mobile interaction should inform the conversation a customer has with an employee. The software evaluates context and possible actions rather than simply storing a customer record. Pega also names Aflac, Wells Fargo, Cisco and Elevance Health among its customers.
That places it across several crowded markets. Salesforce is an alternative for customer engagement and service; ServiceNow and Appian overlap in workflows; Microsoft Power Platform competes for low-code projects. Pega’s distinctive pitch combines decisions, cases and processes in a shared architecture. The right comparison depends on the job, including what the organization already runs.
The expensive part is agreement
Pega earns money through subscription services, software licenses and consulting. Blueprint is free to try. Operating enterprise applications involves a different commitment: connecting systems, agreeing on data, testing exceptions and training the people who will use them.
A December 2024 Forrester study commissioned by Pega makes the proportions visible. For a modeled Customer Decision Hub customer, three-year risk-adjusted costs in present-value terms were $11.6 million for licenses, $17.5 million for implementation and training, and $6.1 million for ongoing management. This is a composite scenario, not a quote or one customer’s invoice.
The software also needs the right problem. Pega Academy’s qualification guidance for Customer Decision Hub favors organizations with more than a million customers and enough possible actions to make arbitration worthwhile. These are product-fit guidelines, not requirements for every Pega application. A small team with a simple approval chain may have little reason to purchase this much machinery.
Even in a suitable enterprise, a generated design needs scrutiny. A workflow can look convincing while omitting the exception that consumes the service team’s afternoon. Buyers should ask to see a failed verification, an overdue task and a human override, alongside the clean demonstration. Those questions test the process the business will actually have to operate.
The cloud grows. The sale gets harder.
Pega reported $1.746 billion in 2025 revenue. Its July 2026 Infinity release promised governed AI agents and a pricing model eliminating consumption-based AI charges. An AWS collaboration connects Blueprint with tools for understanding and modernizing legacy applications. The ambition is to give new intelligence an operating structure.
The commercial picture is less tidy. In its October 20, 2026 results, Pega reported cloud annual contract value up 20% year over year, but total ACV up 6%. Management acknowledged go-to-market execution challenges and buyers scrutinizing large investments. Growing interest in AI does not automatically close a software contract.
For a buyer, the practical calculation starts with the bottleneck: which decision is delayed, how often does it happen, and what does the delay cost? Those answers make a better starting brief than a request to add AI. They also give a pilot something measurable to prove before the organization expands it.
The portable lesson from Vodafone is therefore pleasantly practical. Gather the people who own a process and the people who build it. Put a working preview in front of them. Ask where it fails, who can override it and what happens next. A machine can suggest the moves. Somebody still has to agree on the game.