Stage 4 · Deploy · into real workflows

Predictive AI

Most forecasting in a New Zealand business is a spreadsheet with last year’s numbers and an experienced person’s feeling. The feeling is often right, and the spreadsheet cannot say when it is wrong. Predictive AI uses your own history to forecast demand, flag risk and optimise schedules, with the model’s confidence shown, so people know when to trust it.

Demand and stockMaintenanceRisk scoringConfidence shownExplains a prediction

What it does

Forecasting is the part of your business still done on a feeling.

Every business predicts: how much to order before Christmas, which machine will fail next, which customer will pay late, how many people to roster on Saturday. Most of those predictions are made by an experienced person looking at a spreadsheet, and most of the time they are close. Nobody knows which time, the person is on leave in January, and the spreadsheet cannot say how sure it is.

Predictive AI is a model trained on your own history. It learns the patterns that person has learned and some they have not: the sales pattern after a long weekend, the vibration reading before a bearing failure, the order size and payment history that mean a late invoice. It produces a number, a range around it and a confidence, so the reader knows when to trust it and when to look harder, and it is judged the way you would judge a person: against what actually happened, month after month.

Where it fits

Three decisions that get better with your own history behind them

Demand

Stock forecasting by product and branch

A retailer with several stores or a distributor: reorder quantities are forecast per product per site from your sales history, seasonality and promotions, with the confidence shown. The buyer reviews the uncertain lines and overrides where they know better.

Maintenance

Which units to inspect this month

A transport operator or a manufacturer: equipment history, job records and sensor readings are combined to rank which vehicles or machines are most likely to fail before the next service. The workshop plans inspections instead of reacting to breakdowns.

Risk

Scoring and prioritisation for finance and compliance

A lender, an insurer or a finance team: applications, claims or invoices are scored for the likelihood of a problem and ranked for attention, each with a written reason a person can read and challenge. The team looks hardest where it matters most.

How we build it

Predictive models built to the five rules of the architecture

  • Knowledge before models. The first weeks go on your data: what was recorded, what changed, what is missing. A simple model on clean history beats a sophisticated one on data nobody has checked.
  • Consequence needs a person. A forecast informs an order; it does not place one. A risk score prioritises a review; it does not decline anyone. The person who acts on it is named in the design.
  • Integrate, don’t replace. Forecasts appear in the ERP, the maintenance system or the report your people already use, beside the figures they compare it with. No separate dashboard.
  • Every action leaves a record. Every prediction is stored with its inputs, its confidence and what actually happened, so accuracy is measured monthly and the model retrained on the truth.
  • No vendor is load-bearing. Models are built with open methods on your data and documented so another team could rebuild them. The platform underneath can change.

From history to a forecast people trust

How a model earns the right to influence the order

  1. Weeks 1–2
    Gather and check the historySales, stock, jobs, sensor data. Gaps found, and changes in how things were recorded understood.
  2. Weeks 3–4
    Build the baselineA first model, measured against how the forecast is done today. If it is not better, we say so.
  3. A season
    Run alongsideThe model forecasts, the person decides, both are recorded. Everyone can see who was closer.
  4. Then
    Adopt where it winsThe model drives the products or units where it beat the feeling. The person keeps the rest.
  5. Monthly
    Measure and retrainAccuracy reported under AI Managed. Retrained when the world moves.

Compare

The spreadsheet, the forecasting in your ERP, or a Be AI model

  The spreadsheet you have Forecasting built into your ERP Be AI Predictive AI
Uses your full history rather than last year Rarely Partly Yes
Shows how confident it is No Rarely Every prediction
Explains a prediction in words The person can No Yes
Measured against what happened Sometimes Rarely Monthly
Sensible when Volumes are small and one person knows the business Your patterns are simple and the ERP does it well The decision is repeated, costly and made on a feeling

Questions

What people ask about Predictive AI

How much data do we need?

Less than you fear, more than a quarter. For demand, two or three years of sales history at the level you want to forecast is a good start. For maintenance and risk, it is the number of past failures that matters, because a model learns from what went wrong.

Can it explain a prediction?

Yes, and we do not build ones that cannot. Each prediction comes with the factors that drove it, in words a buyer, a workshop manager or a credit officer can read and challenge. For decisions about people, such as credit or claims, that is designed in from the start.

What happens when the world changes?

The model gets worse, and the monitoring says so. Every prediction is stored beside what actually happened, so a drop in accuracy shows within weeks. The model is retrained on the new pattern, and until then the confidence shown tells people to trust it less.

What if it is wrong and we have ordered the stock?

Then a person ordered stock on a forecast they chose to trust, which is what happens now, with less information. The design keeps the person in the decision, shows the confidence, and runs the model beside the current method for a season before anyone relies on it.

Forecast from what actually happened, and know how sure you are.

Tell us the decision you make on a feeling every month and we will tell you whether your history can do better, and what it would take to prove it.