marketing case 1
From barley to bar: a digital integration journey

Ideate, build, measure, iterate and scale solutions seamlessly with our end-to-end framework of design thinking, agile and DevOps practices. Achieve speed-to-value and adopt breakthrough technologies through the partnership created with your team and a diverse set of IBM experts in business, design and technology.

Heineken initially functioned as downloadable software that analyzed target prospects based on business preferences for cultivating strong business connections. They approached us to address major pain points reported by their users and revamp the product into a brand-new SaaS platform along with a dedicated Chrome Extension. We began by carefully mapping the existing user workflows for each feature and closely examining user feedback, business priorities, and key performance indicators (KPIs). This helped us prioritize our design objectives. Next, we crafted low-fidelity wireframes to visualize the target vision for each SaaS feature.

Integration at Scale

The digital integration platforms connect thousands of of business-critical applications

Automation at Scale

The platforms handle 100% of HEINEKEN’s bank payments

Messaging at Scale

HEINEKEN uses the platforms to process more than 24 million messages per month across all business functions

“When an OpCo comes to me and says, ‘I need the data from the customer interface between application Y and Z,’ I point them to the API Connect self-service portal, explain how to get the key to this API, and they can start using the integration right away. ”

Heineken initially functioned as downloadable software that analyzed target prospects based on business preferences for cultivating strong business connections. They approached us to address major pain points reported by their users and revamp the product into a brand-new SaaS platform along with a dedicated Chrome Extension. We began by carefully mapping the existing user workflows for each feature and closely examining user feedback, business priorities, and key performance indicators (KPIs). This helped us prioritize our design objectives. Next, we crafted low-fidelity wireframes to visualize the target vision for each SaaS feature.

“When an OpCo comes to me and says, ‘I need the data from the customer interface between application Y and Z,’ I point them to the API Connect self-service portal, explain how to get the key to this API, and they can start using the integration right away. ”
When EBank’s senior leaders formed the plan to expand into retail banking, they knew that to really make an impact on the market, the bank would need to offer the best in 21st century banking. And they knew technology would be key. Mohamed Mostafa Tawfik is the Head of IT for Digital Banking at EBank. He and his team, Ahmed Wehady and Mina Mouneer Shoukry, E-Banking Team Leaders, were responsible for selecting and incorporating the technology that would enable the bank’s expansion strategy. Automating processes to boost internal efficiency was one important goal. Another was more flexible integration between systems. EBank had relied on point-to-point integrations between legacy solutions, and this architecture could not support the agility that new digital services would demand. “One of the cornerstones required in our architecture was a banking-as-a-service integration layer,” explains Tawfik, “so that we could more easily upgrade our core banking capabilities by adding new digital channels and automation services.” Tawfik and team also wanted to containerize their automation and integration solutions. This was a bit of a risk, says Tawfik, because other banks in the region hadn’t yet adopted containerization. But the long-term advantages in flexibility and cost efficiency outweighed the risk. “We knew it was the better approach in terms of availability, scalability and deployments. It would allow for rapid speed-to-market and modification ability,” says Tawifk. “So we decided to be the pioneer.” EBank then issued a request for proposal (RFP) to identify the right technologies and the right partner to help implement them.
“When an OpCo comes to me and says, ‘I need the data from the customer interface between application Y and Z,’ I point them to the API Connect self-service portal, explain how to get the key to this API, and they can start using the integration right away. ”
When EBank’s senior leaders formed the plan to expand into retail banking, they knew that to really make an impact on the market, the bank would need to offer the best in 21st century banking. And they knew technology would be key. Mohamed Mostafa Tawfik is the Head of IT for Digital Banking at EBank. He and his team, Ahmed Wehady and Mina Mouneer Shoukry, E-Banking Team Leaders, were responsible for selecting and incorporating the technology that would enable the bank’s expansion strategy. Automating processes to boost internal efficiency was one important goal. Another was more flexible integration between systems. EBank had relied on point-to-point integrations between legacy solutions, and this architecture could not support the agility that new digital services would demand. “One of the cornerstones required in our architecture was a banking-as-a-service integration layer,” explains Tawfik, “so that we could more easily upgrade our core banking capabilities by adding new digital channels and automation services.” Tawfik and team also wanted to containerize their automation and integration solutions. This was a bit of a risk, says Tawfik, because other banks in the region hadn’t yet adopted containerization. But the long-term advantages in flexibility and cost efficiency outweighed the risk. “We knew it was the better approach in terms of availability, scalability and deployments. It would allow for rapid speed-to-market and modification ability,” says Tawifk. “So we decided to be the pioneer.” EBank then issued a request for proposal (RFP) to identify the right technologies and the right partner to help implement them.
“When an OpCo comes to me and says, ‘I need the data from the customer interface between application Y and Z,’ I point them to the API Connect self-service portal, explain how to get the key to this API, and they can start using the integration right away. ”
When EBank’s senior leaders formed the plan to expand into retail banking, they knew that to really make an impact on the market, the bank would need to offer the best in 21st century banking. And they knew technology would be key. Mohamed Mostafa Tawfik is the Head of IT for Digital Banking at EBank. He and his team, Ahmed Wehady and Mina Mouneer Shoukry, E-Banking Team Leaders, were responsible for selecting and incorporating the technology that would enable the bank’s expansion strategy. Automating processes to boost internal efficiency was one important goal. Another was more flexible integration between systems. EBank had relied on point-to-point integrations between legacy solutions, and this architecture could not support the agility that new digital services would demand. “One of the cornerstones required in our architecture was a banking-as-a-service integration layer,” explains Tawfik, “so that we could more easily upgrade our core banking capabilities by adding new digital channels and automation services.” Tawfik and team also wanted to containerize their automation and integration solutions. This was a bit of a risk, says Tawfik, because other banks in the region hadn’t yet adopted containerization. But the long-term advantages in flexibility and cost efficiency outweighed the risk. “We knew it was the better approach in terms of availability, scalability and deployments. It would allow for rapid speed-to-market and modification ability,” says Tawifk. “So we decided to be the pioneer.” EBank then issued a request for proposal (RFP) to identify the right technologies and the right partner to help implement them.