AI for the COO
A Chief Operating Officer does not lose sleep over the forecast. You lose it over the commit: the production and inventory plan you have to stand behind when the demand signal is uncertain, capacity is fixed and working capital is finite. The Havruta Methodology (formerly the Think Partner Methodology) turns AI on that decision, so the machine reasons from your real constraints and argues the plan with you, instead of handing you a tidier forecast and calling it a decision.
The operations question is almost never "can AI forecast demand better?". It usually can, which is exactly why a better forecast does not settle anything. The decision a COO owns is the sales-and-operations-planning call: committing a plan that reconciles that forecast with real capacity, lead times, supplier reality and cash, knowing the signal will move. Gildoni installs the Havruta Methodology into how a COO reasons with AI on that commit, so the machine reasons from your plant's actual constraints, stresses where the plan is fragile, and helps you defend the plan you sign, not just the number that fed it. This is not a demand-planning tool. It is the reasoning discipline behind the plan.
A better forecast is not the decision. The commit is
Every demand-planning vendor sells the same promise: a sharper forecast. And the forecasts have got sharper. Yet the COO's hardest problem has not moved an inch, because the problem was never the prediction. It is the commitment made against it: how much to build, what to hold, where to place capacity, when the signal you are planning against will be wrong in a direction you cannot yet see. A more confident forecast that is still wrong does not help you; it just makes the wrong plan easier to sign.
This is the sales-and-operations-planning decision, and it is judgement, not arithmetic. It reconciles an uncertain demand signal with the things that do not flex on demand: machine and labour capacity, supplier lead times, working capital, the cost of a stockout against the cost of dead inventory. A manufacturer weighing a production commit, a distributor balancing service level against cash, a consumer-goods operator timing a launch against a line: each faces the same shape of call in its own language, and each depends on constraints only that operation knows. A generic AI cannot make it, because it does not know your plant. That is exactly what the methodology puts the machine to work on.
The accuracy of the forecast.
The quality of the commit you defend.
Constraints as parameters you typed in.
Your plant's real capacity, lead times and cash.
A recommended plan.
A plan that has survived a stress test.
What the methodology installs for a COO
The Havruta Methodology changes the default. Instead of a machine that hands over a plan and a confidence figure, it installs the discipline that makes AI stress the plan before it recommends it, which for a COO maps directly onto the S&OP cycle.
The Flip turns the machine on the plan. Rather than endorsing the build you proposed, it attacks it: which assumption is this plan most fragile to, what happens to it if the signal moves ten points, where does the capacity or the cash break first, what are you not seeing. You make it pressure-test the commit before the market does.
Ground Truth keeps it honest. A plan built on an AI that has guessed your line capacity, your supplier lead times or your real working-capital position is worse than no plan at all. The methodology insists the machine reason from your verified operational reality, not a textbook supply chain, so the answer is about your plant and your network, not a plausible average.
And the discipline holds the clock. The planning cycle does not wait, and a COO decides against it. Reasoning with AI as a partner compresses the distance from a moving signal to a plan you can defend in the S&OP review, without handing the judgement to the machine. The fuller account of how all of this works is on the methodology page.
What this is not
This is not a planning tool, and it is not for your stack. It is not a demand-planning or demand-forecasting system, an APS or ERP module, a forecasting model, or another platform to evaluate. It is not AI training, and it is not generic AI literacy. It changes how you, the COO, reason with AI on the decision you own: the operations plan you commit and defend. The tooling is a separate, crowded problem. This is about the judgement.
- A demand-planning tool
- A forecasting model
- An APS or ERP module
- A supply-chain platform
- Another tool to evaluate
- AI training
- Generic AI literacy
This is about the judgement.
Where a COO starts
The methodology is installed along a ladder, and a COO enters at the rung that fits. Most begin with the Eye-Opener Workshop, a half-day in which an operations leadership team sees the shift on its own real planning decision. A COO who wants to embed the discipline personally goes deeper through the Executive 1-1 Coaching Programme; an operations leadership group builds the rhythm through the Havruta programme; and a single high-stakes question, a major capacity commit, a network redesign, a launch plan, can be worked end to end through Advisory Havruta. A Strategic Briefing is how to decide which fits.
- Most begin here
Eye-Opener Workshop
A half-day in which an operations leadership team sees the shift on its own real planning decision.
- For the individual COO
Executive 1-1 Coaching Programme
The deeper, individual rung for the leader who owns the operation.
- For the operations leadership group
The Havruta programme
An ongoing rhythm that embeds the practice across the planning team.
- For one high-stakes question
Advisory Havruta
A capacity commit, a network redesign, a launch plan, worked until it is answered.
Frequently asked questions
How should a COO use AI for demand planning in manufacturing?
Use it on the decision, not the forecast. The value is not a sharper demand number; it is a machine that reasons from your real capacity, lead times and working capital, stresses the production-and-inventory commit you are about to make, and shows you where the plan breaks if the signal moves. The forecast feeds the call; the call is yours. The Havruta Methodology installs that as a repeatable discipline, so AI sharpens the sales-and-operations-planning judgement instead of just predicting demand.
What is the difference between demand planning and demand forecasting?
Forecasting estimates what demand will be; demand planning decides what to do about it, reconciling that estimate with capacity, inventory policy, lead times and cash to set an actionable plan. AI has made forecasting cheaper and sharper, which only raises the value of the planning judgement on top of it. The forecast is an input; the plan is a decision a leader owns.
Can AI replace the S&OP process?
No, and trying to is the mistake. AI can prepare and pressure-test the inputs to a sales-and-operations-planning cycle far better than a spreadsheet can, but the commit, balancing service, cost, capacity and cash against an uncertain signal, is a leadership decision with real consequences. The right use makes the machine the sharpest voice in the room that argues with you, not the one that decides for you.
How is this different from a demand-planning tool?
A demand-planning tool improves the forecast and recommends a plan from the constraints you typed in. This changes how you reason with AI to commit and defend the plan, anchored in your plant's real constraints, not assumed ones. The tooling market is crowded; this is a different problem, your own operational judgement, which no tool addresses.
Who is it for, exactly?
COOs, operations and supply-chain leaders, and the planning teams around them who own the operations plan and answer for service, cost and cash. It is sharpest in manufacturing, distribution and consumer goods, where the S&OP commit is a board-level lever, and it suits leaders who are past asking whether AI can forecast and are now deciding what to do with the forecast.
Where should we start?
With the Eye-Opener Workshop. It is the gateway: a half-day, built around your own real planning decision, where the difference between instructing a machine and thinking with one becomes obvious. A Strategic Briefing is the fastest way to map the right entry point for your operations leadership.