CRM reports on deals are usually read by sales and management. Operations, the people who have to build, deliver or install what was sold, often hear about a signed deal from a forwarded email. Connect the CRM to Claude and the operations lead can get one page every morning: what is signed, what is waiting on materials and what is on fire this week.
The work nobody wants
Monday, eight in the morning. The operations lead opens a spreadsheet he keeps himself, because there is no time to dig through the CRM. Then email, looking for messages from sales with subject lines like “signed, please schedule”. Then a call to the warehouse to ask whether the profiles arrived for a job he only knows is “coming soon”.
Everything is already in the CRM. The deal stage, the signing date, the promised delivery date, the note that the customer wants installation after the tenth. It is just spread across dozens of records, and nobody translates it into the language of operations: how many people, which materials, which week. Someone does that translation by hand, every week, usually at the moment something is already on fire.
“Signed since Thursday? Nobody told me.”
— Monday operations meeting, abridged
What a connected CRM actually means
Claude is Anthropic's model. It can read, compare and write. On its own it cannot see your CRM. It needs a bridge. That bridge is a small MCP server, a narrow program that lets Claude ask the CRM and the warehouse specific questions, such as “which deals moved to Won in the last seven days” or “is the material for this job in stock”.
What matters is whose identity is asking. The MCP server carries the permissions of the person running the report. The operations lead sees jobs and dates, and does not see margins or sales commissions unless the CRM already shows them to him. Nothing is copied anywhere, and no new database appears that someone has to look after. Claude looks, builds the report, and the answer stays with you, on your infrastructure.
Concretely: Raynet and Pohoda
Take a typical Czech company that manufactures and installs, say shading systems or made-to-measure kitchens. Sales lives in Raynet (it could just as well be Pipedrive or HubSpot). Stock, supplier orders and invoicing run in Pohoda. Both stay exactly as they are. The only addition is the bridge between them and Claude. For a company with a few dozen open jobs a month, that could mean one or two hours of manual work a week that simply stop (an illustrative estimate, not a measurement).
- Finds the deals that moved to Won since the last report and lists the promised delivery date for each.
- Checks Pohoda for every job: is the material in stock, on order, or not ordered yet.
- Flags the jobs where the date and the material do not line up, sorted by how close the date is.
- Pulls out the CRM notes operations needs to know: site access, weekend-only installation, a change of scope.
- Sends the operations lead a single page by email at seven in the morning.
Picture a small installation firm in Brno with two crews. Its operations lead used to spend Monday morning assembling the plan from emails and phone calls. With the CRM connected, Monday starts with a report in three sections: newly signed, waiting on materials, on fire. The meeting opens at section three. The example is illustrative, but this is exactly the kind of work that eats companies' time today.
What a CRM report will not do, and why that is good
The report does not replan the week. It does not move a date with the customer, order materials, or tell a salesperson that the promise was impossible. It reads, compares and points. Anything that changes the state of things in the company is still done by the person responsible for it.
That limit is not a weakness. It is the reason the report can be trusted. Operations knows nobody is reshuffling jobs behind their back, and sales knows the date they promised has not quietly changed. The report only shortens the path from a signed contract to the moment the people delivering it know about it.
What it would take
No year-long project. We need access to the CRM and the stock system, one session with the operations lead about what the report should look like, and a place to run it: your cloud, under your control. The first version can be tuned on real data in weeks, not months. Once it works, it goes into your skills library, so anyone with the right permissions can run it, for example a deputy while the lead is on holiday.
What's left
The model is not the bottleneck. Claude can read the sales pipeline, check it against stock and write a clear page. The bottleneck is the gap between Claude and the data you already have: in the CRM, in Pohoda, in the crew calendar. We close that gap.
If your operations team hears about jobs too late, write to us. A short call is enough to see which data you have, where it lives, and what a morning report for your operations could look like.