Replan without rebuilding the plan
Replan in minutes. Not in a spreadsheet.
For the COO, the operations engineer and the head of planning: what you have promised, what you can actually run today and the constraints you cannot break sit in one connected picture of the operation, not in someone's head or a spreadsheet re-keyed every morning. When something moves, you get one proposal with the evidence behind it. Approve it and it dispatches, all on one record. And replans arrive at a pace your team can absorb.
The problem
None of this is unusual. It's the operation, every week.
A lock closes and eleven deliveries need resequencing before 06:00. Storage at a plant hits its reorder threshold while two barges are already committed elsewhere. A driver calls in sick and the day's dispatch has to be rebuilt without breaking a commitment that carries a penalty. It becomes a crisis because the plan lives in one place and the ground truth lives in another: a spreadsheet, a phone call, someone's memory of what changed this morning.
How it works
Your agents plan01 against what's actually happening, decide02 the change that protects what you promised, and act03 the moment you approve.
01
Plan against real constraints
Lock schedules, storage limits and crew rotas are part of what your agents plan against, not a spreadsheet someone re-keys every morning.
02
Decide what to change
When something moves, the agent works out the one reordering that still protects your commitments, and shows you why.
03
Act, dispatched
Approve once, and the fix goes to the crews and systems that need it. Everything else lands on the record.
Metronome doesn't write your plan. It makes sure the facts your plan rests on are still true.
Operational coverage
- Track orders from intake to delivery
- Match work to the capacity you have
- Plan recurring demand, and spot it drifting
- Hold the constraints your plan has to respect
- See what depends on what, before it breaks
- Route exceptions to whoever can fix them
Accountability
The line doesn't move.
You own
- The commitment you made to the customer.
- The exception call when the graph flags a conflict.
- The final approval on every dispatch.
The AI owns
- Recalculating the graph the instant something shifts.
- Surfacing the conflict before it cascades.
- Drafting the resequence, with evidence attached.
- Monitoring for drift after you approve.
Planning and execution run off the same picture, so what reaches a team lead is a proposal inside the constraints their crews already work in.
Running in live pilot operations
An industrial minerals supply chain on the Seine
Tugboats, barges and twelve concrete plants, running against lock schedules and storage levels that set delivery urgency. An idle barge costs on the order of €3,000 a day; a plant without material costs far more. Metronome keeps all of it in one picture that stays current. Replanning that took a morning of calls and spreadsheets now takes minutes, and the planner still approves every move, with one click.
What this is not
- Is this a forecasting tool?
- No. Metronome doesn't predict demand - it plans against the constraints and commitments you already have, and tells you the instant one of them breaks.
- Do we need to replace our ERP or WMS?
- No. The graph reads from what you already run - ERP, WMS or TMS, plus email and spreadsheets. Nothing is replaced.
- Does the AI dispatch on its own?
- No. It proposes one action with the evidence behind it. A named owner confirms or dismisses - nothing moves until they do.
Start with one week of your operation.
Describe a single week the way you already run it: the orders you have committed, the capacity you have, the constraints you cannot break. Metronome builds the picture and replans against it while you watch.
Metronome is in beta. You create a workspace and start with your own operation - nothing to install, no data migration to begin.