“OakCore redrew our partner API map in the first week. We still had to negotiate rate limits with the carrier, but the failure modes were finally written down instead of living in Slack.”Priya N. · Head of Engineering · Melbourne logistics
Client Notes
Specific feedback and longer engagement stories from product and engineering leads.
“The backend service boundaries they proposed felt conservative at first. After two release cycles we were glad — onboarding a second marketplace didn’t require rewriting the original service.”Marcus T. · Product lead · Sydney retail
“The audit found duplicate webhook handlers we had forgotten about. Fixing them was our job; OakCore’s value was naming the risk with enough evidence that finance approved the remediation sprint.”Elena V. · Engineering manager · Brisbane fintech
“Communication was clear, though the first workshop ran long because our inventory spreadsheet was incomplete. Once we cleaned that up, the rest of the engagement moved at a steady pace.”Jonah R. · CTO · Adelaide marketplace
Longer engagement stories
Two projects where the constraints mattered as much as the technical design.
Carrier API cutover under a peak-season freeze
A Melbourne logistics team needed a new carrier API live before November peak, with a hard change-freeze after that. OakCore mapped the existing SOAP adapter, designed a transitional event bridge, and staged cutover by region. The mild friction: partner sandbox data lagged production behaviour, so we insisted on a limited production canary before full switch — delaying the marketing announcement by four days but avoiding a nationwide outage.
Marketplace orders without a god service
A Sydney retailer was stuffing every new marketplace field into a single order service. Backend Service Design workshops split catalogue sync, order intake, and fulfilment signalling. The team shipped the first marketplace on the new boundaries eight weeks later. We did not write the production code; we stayed for design reviews at each milestone and left decision records the next hire could read.