Avayler replaced a manual CSV handoff with real-time SAP integration.

Bridgestone needed tighter integration between the Avayler SaaS platform and their SAP ERP system. Financial data moved between the two on scheduled CSV exports, with manual intervention and asynchronous workflows filling the gaps.

That created steady operational overhead for the finance team and, more importantly, capped what the platform could support. A process that depends on someone checking a file cannot scale to a 2,200-site rollout — and every new enterprise customer would have meant rebuilding the same integration by hand.

Architecting for the second customer, not just the first

I architected and led delivery of a real-time integration platform synchronising financial data directly with SAP. The design brief I set was deliberately wider than Bridgestone: the integration layer had to be extensible to future ERP systems, so the next enterprise customer would be a configuration exercise rather than another project.

Working across three organisations

Requirements ran through Bridgestone, Accenture and internal stakeholders simultaneously. I worked directly with all three to define scope, surface risk early and agree the architecture, then produced the technical designs and roadmaps and led the technical discussions that kept those decisions visible as the build progressed.

Making the failure cases boring

Real-time financial data means failures happen in production, not in a batch window. I drove the implementation across the team — including retry and error-handling logic, and test coverage written specifically to expose edge cases — and mentored team members through the integration patterns so the knowledge did not sit with one person.

Full-stack development and integration architecture in an Agile/Kanban environment, with RESTful API and microservices design, and a lead role on the SAP integration project.