For years, commission reporting at Klabin — a commercial real estate brokerage — ran through a single bottleneck.

A broker who needed their numbers filed a request with the COO. The COO remoted into a virtual machine, ran the report, and sent it back. The system of record sat on-prem, single-threaded, and inaccessible to the people whose earnings it held. Shareholder AR reporting followed the same path.

That is not a tooling preference problem. It is an access problem: the people who need the numbers cannot reach the system that holds them, so every pull becomes executive labor.

Here is what changed when the transaction system moved to a cloud, AI-ready platform and brokers queried it through Claude under their own permissions — instead of building yet another reporting UI nobody would log into.

The bottleneck was the process, not the data

The old path had three failure modes that stacked:

1. Single operator. One person owned the remote session. Vacation, overload, or a stuck VPN meant silence for everyone waiting on a report.
2. No self-serve surface. Brokers could not see their own credits without an intermediary. Requests piled up; context got lost in email.
3. Same choke point for AR. Shareholder AR reporting burned the same executive calendar on top of the weekly commission load.

Buying another dashboard would have added seats. It would not have fixed role-scoped access to the live system of record.

Approach: migrate the SoT, then expose it through MCP

The engagement had two sequenced moves:

1. Migrate the transaction system off the on-prem VM onto a cloud, AI-ready platform — same facts (transactions, commissions, invoices, payments, vendors), new substrate.
2. Expose that system through an authenticated MCP endpoint so brokers query it in Claude directly, under their own role and permissions.

MCP was the deliberate product choice. The alternative — a custom reporting UI — would have competed with every other unused internal tool. Brokers already live in Claude for research and drafting. Putting the system of record behind an authenticated tool surface meant the interface was already adopted.

The in-app agent sits in the architecture as a secondary surface. It is not the adoption story. The adoption story is authenticated tool calls against live data, with role checks, from the chat window brokers already use.

Delivery: live numbers, not aspirational ones

Migration completed in February 2026. The MCP endpoint went live to users on May 26, 2026.

Production system of record now holds:

Record	Count
Transactions	836
Commission credits	3,521
Invoices	1,036
Invoice line items	3,638
Payment records	1,004
Vendors	1,614

Thirteen users are provisioned across four permission roles. Rollout is phased — not every seat is in daily use yet. The next cohort is the remaining brokers and ops staff still on the old request path; they come online as role packs and training land, not as a big-bang cutover.

Sustained use across a full quarter: 236 authenticated tool calls between May 26 and August 21. Monthly volume ran 44 → 105 → 55 (August partial). That is not a growth claim. It is evidence the system stayed in use across a full quarter — including a quieter month — rather than peaking once and going dark.

Impact: three outcomes that matter

1. The bottleneck is gone

Brokers pulled 100 commission reports directly in the thirteen weeks after go-live — roughly eight per week, each of which previously routed to the COO. Schulz estimates that work had been consuming 4–6 hours of his week, with another 4 hours monthly on shareholder AR reporting.

2. Executive capacity returned

Using the midpoint of that estimate — about 5 hours per week on commission reporting plus 4 hours per month on shareholder AR — annualizes to roughly 308 hours of COO time, or about 7.5 working weeks. That capacity does not disappear; it moves back to work that actually needs an executive.

3. Self-service is real, not theoretical

Beyond commission pulls, users ran 23 AR queries directly, plus broker rankings and transaction lookups — all against the same system of record, with no export step and no intermediary. Permissions stay on the user. The data stays in one place.

What Klabin's COO says

"The implementation has fundamentally changed how we handle commission tracking and reporting. It's cut out a lot of the back-and-forth email chasing and made our whole process more efficient."

— Darrell Schulz, Chief Operating Officer / Principal, Klabin

Why MCP beat another report builder

Most brokerages that "go digital" on commissions ship a portal. Adoption stalls because the portal is one more login. Here the system of record became a tool Claude can call under role-aware auth — so the interface was already open.

That pattern travels: any SMB where one person is the human API to a locked system of record can migrate the data, expose it with permissions, and retire the request queue. The product is not a prettier PDF. The product is self-service against live facts.

If your commission or AR reporting still routes through one executive's remote desktop, we have run this motion end to end. Book a discovery call at cloudbeast.io/schedule.