Entities
Orders, suppliers, shipments, customers, locations, contracts, tickets, and the other objects your workflow actually uses.
Operating model
Turn scattered company knowledge into usable context.
A useful company model is smaller than an enterprise architecture map and richer than a data dictionary. It connects the records an agent can read with the process they belong to and the rules that determine the next step.
Discuss your use caseRelationships
Which agreement applies to which account, which purchase order funds which receipt, and which promise belongs to which shipment.
Business vocabulary
Map system fields to the language operations, finance, procurement, and customer teams already share.
Source cadence
Mark which facts must be live, which can refresh periodically, and how stale data changes the answer.
Functions
Define repeatable calculations with visible inputs and breakdowns so a reviewer can contest one fact, not a black box.
Ownership
Record who owns a rule, who may change it, and which team resolves an ambiguity.
Illustrative sample · Meridian Kitchens
The same item name means two different things.
A supplier invoice says “oak panel.” The purchasing system has two close matches, but only one is certified for the customer project.
Invoice lineOak panel 18 mmSupplier PDF
Project specFSC-certified onlyContract workspace
Approved SKUPNL-OAK-18-FERP catalogue
WRITTEN RULE
Material substitutions on contract projects require the project buyer to confirm the mapped SKU.
OUTCOME
The agent prepares the match and routes it to the project buyer instead of posting the invoice.
Start with one decision
Bring the workflow your team knows by heart.
We’ll map the systems, facts, rules, and approval point before discussing a pilot.