We've worked with enough operators in One-North to know that the brief that arrives in our inbox is rarely the brief that ends up shipped. The first thing we do on any AI demand forecasting project is sit with your team for a day before we propose anything.
For One-North operators who want a working pilot in weeks, not a year-long programme.
Our goal is to give One-North businesses a three-day weekend, so people can spend more time with their families and the people they love :)
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 Kiwi Dynamics
With Kiwi Dynamics
What you actually get
Every engagement is scoped and quoted up front. This is what is in the box.
- A working pilot, in productionNot a prototype on someone's laptop. The first slice of AI demand forecasting runs against real work within weeks.
- Your data stays yoursIt runs on your accounts and your tools. If we part ways you keep the system and everything in it.
- The workflow mapped before codeWe write down what good looks like for One-North businesses first, so nobody is guessing at handover.
- Support after it landsThe people who built it stay reachable when the business changes shape around it.
How AI demand forecasting compares
The two things most businesses do instead, and where each one runs out.
| Hiring for it | An off-the-shelf tool | Kiwi Dynamics | |
|---|---|---|---|
| Fit to how you work | Fits perfectly, costs a salary | You bend your process to suit the tool | Built around the workflow you already run |
| Time to something useful | Immediate, and permanent | Quick to switch on, slow to make fit | A working slice in weeks, then hardened |
| Who owns the data | You do | The vendor, on the vendor's terms | You do, in your own accounts |
| When it breaks | That person sorts it, if they are in | A support queue and a ticket number | The people who built it |
| What it costs | A salary, every year, forever | Per seat, forever, used or not | Scoped and quoted up front |
What's different about doing this work in One-North.
- One-North is Singapore's dedicated biotech, media and tech research precinct - AI here is judged by researchers and engineers, not procurement teams.
- Biopolis, Fusionopolis and a dense cluster of biotech, media and deep-tech startups sit inside one of the most concentrated research precincts in Asia. Businesses here expect AI built with real technical rigor, since many of them build AI themselves.
We work with teams across One-North: Biopolis · Fusionopolis · Mediapolis · Ayer Rajah · Buona Vista.
Talk to us about this →
How we build AI demand forecasting for an One-North team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your One-North business, so value lands before the build is finished. AI sales + stock forecasting.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing One-North businesses the most hours or the most leads, and deliberately ignore the rest for now.
- Ship a working sliceA narrow version goes into production in weeks, against real work, so the value shows up before the build is finished.
- Prove it, then widenWe measure it against what the work cost before. If it does not pay for itself, we say so rather than scaling it.
- Harden and hand overLogging, fallbacks and a real handover, so it keeps running when we are not in the room.
The outcome for One-North teams
Stockouts down 35%, overstock down 22% in the first season. For One-North teams, that almost always shows up as fewer interruptions and a calmer week, not a dashboard chart.
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 One-North 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.
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.
Anyone else in this space using AI demand forecasting?
Plenty. Stockouts down 35%, overstock down 22% in the first season. The interesting question is rarely "does it work" - it's "is your team ready to use the output." That's what we'd scope on the 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.
The honest version of a sales call.
No deck. No discovery doc. Just whether this is worth building and what it would cost.
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.