Evidence from recent engagements. Names and brands are shared with permission; some roles are generalised where a client preferred quieter attribution.
The mobile address-form chart was the slide that finally got engineering time. I still wish we had booked the follow-up session sooner after Black Friday — the first audit aged faster than we expected.Jordan Hale · Conversion lead, outdoor goods retailer
ForestCore Utility refused to average desktop and mobile into one cheerful funnel. That stubbornness saved us from “fixing” a step that only failed on smaller screens.Amrita Cole · Analytics manager, beauty subscription
We brought them a messy export and three competing theories. The review call was brisk — almost curt — but the ranked list matched what warehouse returns had been hinting at for months.Neil Okonkwo · Operations partner, homeware catalogue
The visualisation pack for our board paper landed on time. Definitions were pedantic in the best way; finance stopped arguing about what “started checkout” meant.Sophie Rankin · CFO office, regional grocery online
Extended story: fashion retailer, spring redesign
A mid-market fashion client approached us after a redesign shortened the path from bag to payment. Orders rose slightly, yet support tickets about “payment looping” climbed. Our Checkout Funnel Drop-off Audit reconciled guest and account paths separately and found the largest absolute loss between delivery-option selection and payment method — not on the payment page itself.
We annotated the timing gap: visitors who lingered over delivery choices were more likely to exit when a wallet button reloaded the page. Merchandising had assumed the problem sat later. After the review call, the client deferred a planned coupon experiment and instead stabilised the wallet reload. Six weeks later they booked a Follow-up Review Session to confirm the leak had narrowed on mobile.
Extended story: specialty foods, dual locale
A specialty foods brand selling into England and Scotland asked for charts that would travel well into a supplier meeting. Tracking differed by locale. We scoped a visualisation pack that kept locales on separate boards rather than blending them, and labelled a week where a carrier API outage distorted delivery-step events. The supplier meeting used those boards as a shared reference instead of live dashboards that kept changing mid-conversation.