5 roles
The scaling stack
At this size the constraint stops being any one tool and becomes the joins between them. What breaks is not the CRM — it is the third place a client’s address is typed, and the report that cannot be produced because two systems disagree.
For: Past roughly 50 settlements a month, with brokers and support staff who have never met.
The roles this stage has to fill
One tool per role, no overlap. We have not named the tools, because naming them is a recommendation five deep and no product has been tested yet — what follows is the shape, and the whole field for each part of it.
A CRM that is genuinely the source of truth, because at this volume a second one is a liability.
12 products we track →
The application layer, connected. Double entry at scale is a full-time salary.
7 products we track →
Integration and automation, treated as a system rather than as glue somebody added.
17 products we track →
Commissions and analytics. Not for a dashboard — for finding which stage the pipeline stalls at.
14 products we track →
Audit and compliance tooling, before a review asks for it rather than after.
15 products we track →
What this stage leaves out
A stack is defined as much by what is not in it. Every one of these is a real category a broker could buy from today, and at this stage it does not earn the money.
- Anything requiring every broker to change how they work on the same day
- A second CRM for a team that "works differently" — that is the failure this stage exists to prevent
Before this names a single product
Every tool in each role has to have been run in a real account for a working week and scored against the published criteria, and its list price confirmed in AUD rather than converted. Until then this gives you the shape and the field, which is worth more than a stack naming three products nobody has used.