The version of AI demand forecasting that works for a Emerald business is rarely the version a national vendor would sell you. We build the one that fits how your team actually operates - usually with fewer parts than the off-the-shelf pitch.
Built and supported here - the way a Emerald 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
Why Emerald businesses are a fit for this.
- Emerald sits in the Central Highlands where coal and cotton meet, serving both mines and farms out of one small town.
- Bowen Basin coal, irrigated cotton, grain and the machinery and logistics behind them. Mining procurement and agricultural seasonality pull local businesses in two directions at once.
We work with teams across Emerald: Emerald CBD · Blackwater · Capella · Springsure · Clermont.
Talk to us about this →
How we build AI demand forecasting for a Emerald team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Emerald business, so value lands before the build is finished. AI sales + stock forecasting.
Talk to usThe outcome for Emerald teams
The shape of the result for Emerald 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
What's a typical engagement length for Emerald businesses?
Six to twelve weeks for the build, then a short managed-services month while the system goes from "shipped" to "owned by your team". After that you keep us on retainer if you want, or take it from there yourself.
Are there hidden costs we should plan for?
Three to know about: model/API spend (which we set up under your own account, not ours, so you see and control it), any new SaaS subscriptions we recommend, and your team's time during rollout. We surface all three in the quote so there are no surprises.
Do you have proof this works for Emerald businesses?
Direct case study: Stockouts down 35%, overstock down 22% in the first season. Happy to walk you through full numbers on a call.
Can you work with our existing systems?
Yes. The default AI demand forecasting stack we reach for is Prophet, DuckDB, Claude, BigQuery, Vercel, but we'll bend it around whatever you already run - Xero, HubSpot, Shopify, Cin7, your own in-house apps. The discovery week maps every data source before any build starts.
Skip the pitch.
Tell us the workflow and we'll come back with what we'd build first.
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.