Most of our Broome engagements start the same way: a 20-minute call where the owner describes a workflow we've heard before in shape but never in detail. AI demand forecasting is then designed against the detail, not the shape.
Built and supported here - the way a Broome business would actually use it.
What AI demand forecasting actually does
Forecasts that account for school holidays, NZ weather, tourist seasons, and your own promo calendar. Order the right stock, roster the right hours, plan the next quarter with actual numbers.
- 01 Combines your sales history with weather, calendar, and event data
- 02 Per-SKU and per-store forecasts, not whole-business averages
- 03 Re-forecasts weekly as new data comes in
- 04 Explains the why behind every number
Built on: Prophet DuckDB Claude BigQuery Vercel
Without Koala Dynamics
With Koala Dynamics
The Broome context, plainly.
- Broome is Kimberley tourism and pearling, with a dry-season economy that has to earn a full year in six months.
- Tourism, pearling, Indigenous enterprise and remote services across an enormous region. The wet season shuts much of it down, so peak-season capacity is the whole commercial question.
We work with teams across Broome: Broome CBD · Cable Beach · Old Broome · Bilingurr · Derby.
Talk to us about this →
How we build AI demand forecasting for a Broome team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Broome business, so value lands before the build is finished. AI sales + stock forecasting.
Talk to usThe outcome for Broome teams
The shape of the result for Broome teams: Stockouts down 35%, overstock down 22% in the first season. Built on Prophet, hardened with the rest of the stack as it scales.
Not your typical AI agency.
Honest about what AI can and cannot do
Ships the one workflow that pays for itself
Hours given back, never the size of the invoice
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
FAQ
When does AI demand forecasting actually pay back?
Inside the first quarter, in our experience. We pick the first slice specifically because it's the highest-leverage workflow for a Broome - so the savings start landing before the rest of the build is finished.
Do you do hourly billing or fixed price?
Fixed price for the pilot, every time. After that it's your call - fixed price per milestone or a small monthly retainer for ongoing iteration. We don't run open-ended T&M because it disincentivises us from finishing.
Can you walk us through a comparable build?
Yes - on the first call we'll pick the closest engagement we've shipped to what you're describing and walk through the outcome, the headcount and the time it took. Stockouts down 35%, overstock down 22% in the first season.
Will this run on our own infrastructure?
Yes, where it makes sense. AI demand forecasting can sit entirely in your cloud account, with model calls routed through endpoints you control. We default to Prophet, DuckDB, Claude, BigQuery, Vercel but the architecture supports your existing platform choices.
Talk to us about this
Tell us what you're trying to do and we'll reply with how we'd build it - no obligation.