The situation
Where they started.
Three plants, three ERPs, and a month-end that was a person copying numbers into a corporate workbook and explaining the differences by email. Every figure had a story, and the story lived with whoever assembled it. New ownership wanted a report it could trust without a call to ask what the numbers meant.
What FlatClaw does
What was built.
- Governed connectors into each ERP, read-only, with the mapping between plants' units, cost centers and product families held in one maintained model.
- Agents assemble the operating report on a schedule: pull, normalize, reconcile, and flag mismatches between systems rather than quietly picking one.
- A drafted narrative around the numbers, in the company's own format, for the controller to edit rather than write.
- Every figure carries a reference back to the source transaction set, so a question about a number is a click, not a call.
Results
What changed.
- One monthly report instead of three reconciled by hand.
- Mismatches between systems surface as findings rather than getting averaged away.
- The controller edits a draft instead of building a workbook.
- A foundation for consolidating the ERPs later, without waiting for that project to read the numbers now.