Agents don't need more data. They need a model of your business.
Access to your data is not the same as understanding your business. Why a trade's own structure is the context AI agents need to do real work.
Picture a caterer on a Tuesday, typing one sentence to an agent:
"Get everything ready for the Dupont wedding on Saturday and tell me what we're missing."
Simple for a person who has worked there a year. What does the agent need to pull it off?
Data is not understanding
In a generic system, the agent can probably reach the data. There's a project called "Dupont", some custom fields, a spreadsheet of guests, a few emails, a supplier portal.
But it has to guess what all of that means. Which field is the guest count? Is "Menu B" the confirmed one? Do the allergies in that spreadsheet belong to this event? Which supplier order goes with which dish?
Every guess is a chance to be confidently wrong. And a wrong answer about a wedding is worse than no answer.
When the business is already explicit
In Enobase for catering, none of that has to be guessed. The trade is modeled as it is:
The Dupont wedding is an event. It has a date, a venue, 180 guests, a confirmed menu. Guests carry their dietary requirements. The menu breaks down into ingredients. Ingredients come from suppliers. The event has a staffing plan, equipment and logistics. It has a deposit, and the deposit is still outstanding.
So the agent can follow the thread. Guests to menu to ingredients to supplier orders. Headcount to staff. Venue to equipment. Event to payments.
And it can come back with something a manager can act on: two servers short for Saturday, the gluten-free dessert has no supplier order yet, and the balance deposit hasn't been paid.
The agent doesn't just have access to the company's data. It has a model of the business.
Same rules, same permissions
A model is only useful if everyone shares it. Our agents work on the same records as the team, through the same actions, under the same permissions. When an agent books a supplier or drafts an invoice, it shows up in the same history as a person's work.
That's what lets you hand over more over time. You can see what was done, by whom, and why.
One foundation, many workforces
Here's what we find exciting.
The same foundation that lets us build software shaped around each trade also gives each trade a model its agents can work in. A catering model for catering agents. A padel club model for club agents. A museum model for museum agents.
The better the model of the trade, the more real work agents can take on inside it. That's why we model each trade deeply, instead of asking every business to squeeze itself into the same generic boxes.
Vertical software used to mean one company per trade, each a single dot on the map. We're building the ground underneath a whole constellation of trades, each with its own model and its own agents.
Want to see an agent work inside a model of your business? Book a call with us.
