Client stories from usage and forecast engagements

Project note: quarterly capacity for a logistics API

A Korea-based logistics team asked for an Operational Forecast Review ahead of a summer volume rise. Their workbook assumed linear growth from March; recent usage showed Friday peaks rising faster than weekday baselines.

We annotated the model with elevated and stress bands tied to Friday order cutoffs, and named the decision date for additional capacity lead time. The team kept their mid-case purchase but moved the stress-band trigger one week earlier.

Project note: campus-season traffic for a learning product

During a Usage Trend Assessment, campus calendar effects explained most of a March dip that marketing had treated as churn. Feature-path completion for the assignment flow was steady. The findings workshop redirected budget from a recovery campaign into instrumentation for a new cohort path.

“They refused to give us a single peak number for Chuseok traffic. The three-band forecast made our capacity call easier—even though the mid-case landed a bit high.”

“The assessment caught that our ‘flat’ month was really a swap between two feature paths. We had been about to pause a release that was quietly winning.”

“The telemetry audit was blunt about our UTC mix-ups. Fixing that took longer than we hoped, but the forecast review afterward finally matched what operators saw on weekends.”

“I wanted a longer retainer. They insisted on a bounded assessment first. That boundary kept the document usable—though I still wish we had covered a second app in the same pass.”