Case study · Energy · TPI sub-vertical

How Amber Energy ended the silo between Salesforce and its payments stack with a real-time, event-driven bridge on AWS.

Client
Amber Energy
Sector
Energy (commercial supply, B Corp, third-party intermediary sub-vertical)
Challenge
A manual integration between Salesforce and the payments stack was holding back customer-facing operations
Outcome
A real-time, event-driven bridge on AWS EventBridge and Lambda; manual integration eliminated; a scalable foundation for further growth

The situation

Amber Energy is a forward-thinking B Corp and energy provider, focused on delivering data-driven, efficient, and user-friendly services to its customers. As a scaling business, the team was building modern, cloud-native systems to support the next phase of growth. If you've watched a scaling business outgrow its early integration choices, you'll recognise the shape of the conversation Amber was already having.

The challenge and the stakes

A critical data silo sat between Amber's payments platform and Salesforce, the core CRM. Both systems were effective in their own right; neither was designed to communicate with the other automatically in real time. The disconnect created significant manual integration bottlenecks, slowed operations, and meant Amber had no unified, real-time view of customer payment data within its primary business system.

For a scaling business with consumer-grade customer expectations, that gap was the constraint on the next phase of growth.

The approach

We designed and implemented a lightweight, event-driven architecture on AWS to create a real-time communication bridge between Salesforce and the payments provider. A serverless approach using AWS EventBridge and AWS Lambda meant the solution scaled with use, cost less than a steady-state alternative, and required minimal maintenance.

The architectural call wasn't to wire the two systems together with a custom integration but to build above them. A key event in Salesforce (for example a customer updating their details) automatically triggers the correct action in the payments system, and the reverse holds the other way.

The turn

The first end-to-end real-time event landed without the manual reconciliation step that had previously gated the process. The data silo was gone in a way Amber's team could see in the live system.

The outcome

A single source of truth: the solution eliminated the data silo and created a reliable, real-time view of a customer's payment status directly within Salesforce.

Complete operational automation: all manual processes related to payment integration were removed, freeing Amber's team to focus on higher-value activities.

A scalable foundation for growth: Amber now has a modern, cloud-native foundation that can support significant customer growth without the friction and cost of manual integrations.

In Amber's words

"While we led the initial business scoping and discussions with key stakeholders, it was a very smooth process working with the D55 team to expand on this vision. The D55 team took ownership of building the solution and worked closely with us throughout the process. The quality of the work, combined with the excellent support during the handover, is exactly what we value in a partner."

Andrew Thomas, Chief Technology Officer at the time of the engagement, Amber Energy

The implication

The pattern (building above two systems with an event-driven architecture rather than wiring them together with custom integration) applies whenever your operational tempo has outpaced the integration model you've been working with. The serverless cost profile means the answer scales with your business rather than ahead of it.

Start a conversation

If you're looking at a similar Salesforce-to-payments or CRM-to-operations gap, let's talk.

Jonathan Rothwell, CEO, D55
solutions@d55.co.uk · +44 161 399 0257

Let's explore the possible together.