The hidden cost of the brokerage spreadsheet stack

No brokerage decides to run on spreadsheets. It accretes. The transaction tracker started as a stopgap in a busy spring. The commission worksheet was inherited from the previous office manager. The trust log, the contact list, the leave calendar, the document index — each one was the fastest reasonable answer to a real problem, and each one worked.

The stack is what they add up to, and the stack has costs that never appear on an invoice.

The four invisible line items

1. Reconciliation labour

The same deal exists in four files maintained by three people, so somebody — usually the most reliable admin in the office — spends hours a week making the copies agree. That work is invisible because it looks like diligence. It is actually interest paid on fragmentation.

2. Status blindness

When the answer to "where is the Hastings deal?" lives across a tracker, an inbox, and a hallway conversation, leaders stop asking the system and start asking people. Every status question interrupts someone, and the office’s real state is only as current as its last interruption.

3. Key-person risk

Every brokerage has the person who knows how the sheets actually work — which columns are formulas, which are typed, which tab is stale. The stack runs on their memory. Their two-week vacation is an operational event; their resignation is a small crisis.

4. The audit tax

Records assembled informally must be evidenced formally — for FINTRAC examinations, for trust reviews, for the accountant. The brokerage pays for the same work twice, and the second payment always lands at the worst time.

A useful exercise for any managing broker: list the spreadsheets the office actually depends on — not the ones that exist, the ones whose loss would stop work — and next to each, write who maintains it and what other file it must agree with. Most offices find eight to fifteen load-bearing sheets and are surprised by both numbers. That list, not a vendor demo, is the honest starting point for deciding what to fix first.

Why the stack survives — and the staged exit

What makes the stack durable is that the exit looks expensive: "replace everything" is a project nobody has time for. The honest answer is that nobody should replace everything at once — and a modular platform exists precisely so you do not have to.

• Stage one: the office layer — tasks, shared calendar, CRM, staff records, leave and expense workflows. Least risky migration, fastest payback. On OpSphere that layer is OfficeOps, and it is free.
• Stage two: transactions, when the office is ready — DealFlow brings the deal pipeline, commission engine, compliance checklists, and trust workflow records onto the same tenant.
• Stage three: the field — brokers join from their phones with DealFlow Mobile, which is in early access.

Each stage retires specific spreadsheets — and, more importantly, retires the reconciliation between them, because the modules share one data model, one permission system, and one audit trail.

Running a stage well

The difference between a migration that sticks and one that quietly reverts to the old sheets is usually process, not product. The pattern that works:

• Name an owner per retired spreadsheet — the person who maintained the sheet is usually the right one, because they know its exceptions.
• Freeze the sheet on a announced date: read-only, with a banner pointing to the new home. A sheet that stays editable stays alive.
• Parallel-run for one cycle — one month of expenses, one pay period of leave — comparing outputs before cutting over.
• Retire explicitly: archive the file and say so. Ambiguity about which system is authoritative recreates the original problem inside the new tool.

And measure the payback in the terms that motivated the change: how long does a status question take to answer now? How many hours did month-end reconciliation take this quarter versus last? The numbers are usually persuasive enough to fund the next stage without a debate.

When a point solution is the right call

Worth saying plainly: if your office has exactly one pain point, a single specialized tool may solve it with less change than a platform. The platform case is strongest when the pain is the stack itself — when the cost is the reconciliation between tools rather than any one tool’s weakness.

Free is the price of each spreadsheet. The stack charges differently: in hours, in blind spots, in one indispensable person, and in every audit. The brokerages that retire it in stages stop paying all four.