Nobody wrote down how your company works. So we ask.

Every Bonofici engagement starts the same way. Before we take over a function, we have to learn how it actually runs. Not the process in the slide deck. The one people follow on a Tuesday when a supplier is late and the customer is on the phone.

That process is almost never written down. The production plan arrives as a screenshot. The stock count lives in a spreadsheet someone pastes into a chat. The rules live with the two people who have done the job for years. Even companies with a proper ERP run on this layer of habits around it, and that layer is where the exceptions get handled.

Why discovery usually takes months

The traditional way to learn a company is to send people. A consultancy, or a forward-deployed team of four or five, books workshops, sits with each team and draws the process on a whiteboard. Founders building agents for operations put this at up to a year for one company. Most of that time is calendars, not insight.

It also tends to get the wrong answer. In a workshop, people describe the process as it is supposed to run. The workaround someone built because the official route takes three days stays quiet, because nobody wants to admit it in front of their manager.

Our discovery crew

We do this with a crew of AI interviewers, run and reviewed by the person who will own your function. It works in waves.

• Leads first, for breadth. Short conversations with the head of each team sketch the outline: what the team does, who it hands work to, which systems it uses.
• Then the people doing the work, for depth. The interviewer follows up on what the leads said, asking the people closest to it how a step really happens, how often, how long it takes and what they do when it breaks.
• Fifteen minutes, on their time. Each person gets a private link. They answer by voice, between tasks, in whatever language they work in. Their exact words are kept in that language, so nothing gets lost in translation.
• Recordings, when they exist. With consent, we can also learn from calls you already record: a handover meeting, a training session, a customer call.

Because the interviews run in parallel, a team of forty can be heard in the time it takes to book one workshop.

No quote, no claim

The rule that makes this trustworthy is simple. Nothing goes on the map unless it is backed by the exact words of someone who said it. If the crew concludes that invoices wait two days for approval, you can click through to the person who told us, in their words. If nobody said it, it is not there.

This matters more than it sounds. A summary written by a model reads smoothly whether it is true or not. A quote can be checked. When we sit down with your operations lead, the conversation is about what your people said, not about what a tool guessed.

The most useful finding is a contradiction

Interview two teams about the same handoff and you often get two stories. Sales says the new customer is introduced on a call. Support says they find out from a message in Slack, sometimes a week later. Neither is lying. The handoff just has no owner, and each side fills the gap differently.

Those gaps are where the exceptions come from, so the crew looks for them on purpose. A contradiction between two teams is the best signal we have of a step where work stalls, gets done twice or falls on whoever happens to notice.

A living map of how you run

What comes out is a map of one piece of work moving across the company. Take a single order: it might cross five teams and a dozen systems. For every step, the map shows who owns it, where the record lives, who approves it and which workaround people use when the official route is too slow. Steps that everyone relies on and nobody owns are marked, so they cannot hide.

The crew also writes down what each team believes about your customers: that they leave because onboarding is slow, or that the large accounts want monthly reporting. Those beliefs become questions we can test with a few real customers before we build anything around them.

What it asks of your team

• A list of people, and fifteen minutes from each. Nothing to prepare.
• Consent, every time. People agree before an interview starts, can stop it whenever they like, and their link expires when it is done.
• Anonymity in numbers. A finding backed by fewer than three people is shown without their words or team, so nobody is singled out for being honest.

Where the map goes next

The map is not a deliverable that sits in a folder. It is the first draft of the standard we sign with you: scope, turnaround, thresholds and what happens when a job misses. It becomes the starting point of your Company OS, the place where those rules keep getting updated as the business learns. And when we run the work, every miss goes back into it, so the map stays true long after discovery ends.