Problem
Service scheduling data arrived from OEM partners in wildly inconsistent formats — CSV, HTML, plain text, vendor-specific metadata — for Xtime, CDK, and ReyRey. Each new partner (MyKaarma, VUMO, HopDrive) risked becoming its own multi-month integration project. Another team had already estimated a comparable integration at 3 months.
Action
Built a single input-agnostic email/data parser architecture that normalized any of these formats into one pipeline, instead of writing a bespoke parser per source.
Result
VUMO and HopDrive were each integrated in under 1 week, versus the 3-month estimate for a comparable integration elsewhere in the org.