There is a version of AI demand forecasting that dentists buy off a shelf and quietly stop using inside a month. Then there's the version that's wired into your real workflow, owned by a person on your team, and still in use a year later. We only build the second one.
AI demand forecasting that fits a dentist's week, not the other way around.
Our goal is to give dentists 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 dentists 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 |
Dentists need software built around their week, not against it.
- Dental practices live and die by a full chair and a clean recall list, and both take constant admin to keep on track.
- No-shows, insurance queries, and recall reminders are the recurring admin load behind every dental front desk.
How we build AI demand forecasting for dentists.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for a dentist 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 dentists 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 dentists
What changes for dentists after this lands: the work that used to need a person stays done, the work that needs a person gets done with their attention undivided. Stockouts down 35%, overstock down 22% in the first season.
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 dentists?
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.
Do you have proof this works for dentists?
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.
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.