Your CRM can already do this. Your team is still doing it by hand.

More than most firms realise. Rethink ships Action Plan templates that apply tasks with owners and due-date offsets to a record or a whole list, automatic comp creation when a deal closes, Deal Stage Tracker for days-in-stage, suggested property matching against inquiry requirements, Showcase sync, activity capture from email and calendar, scheduled branded Activity Reports, and invoicing with draft and approval steps. Each one has a prerequisite — the tracker does not backfill, comp creation needs the Property and Space populated, Showcase needs an internal associated party. A good share of an automation engagement is configuring what you already own.

Flow for almost everything on this page, because your own administrator can then own it, change it and switch it off without a developer. Apex is for calculation where rules genuinely interact, bulk volume where governor limits bite, or orchestration that must be retry-safe — and it carries a maintenance obligation on every package release. The full comparison, including what each tier costs you at upgrade time, is on our Rethink customization and integration page rather than repeated here.

Yes, and it is one of the highest-value patterns because the manual version is slow and error-prone in a way that shows up in broker pay. Rethink raises a commission invoice from the deal with line items, payment terms and a draft-and-approval step; what we add is routing by value and desk, notification to the right approver, automatic release on approval, and a logged audit trail. The part that needs care is exceptions — house accounts, unusual co-brokes, the deal a principal runs personally — because a rule that handles those badly is a rule brokers will route around.

Governance, and it is not optional. Every rule gets a named owner who can explain why it exists and is allowed to change it. Order of execution is designed and documented rather than discovered. Failures surface through error handling and notification, because a Flow that fails silently is worse than no automation — people trust it. Exceptions are decided before launch. And rules get reviewed and retired on a schedule, which is the step that stops an org accreting automation the way it accretes custom fields.

Judgement. Whether to take an assignment, how hard to push a landlord, what a long relationship is worth, when to break a rule for a client — these get worse when a workflow decides them, and automating them is how firms end up with a CRM their best brokers work around. The dividing line we use is simple: automate the administration around a decision, never the decision. Also avoid automating a process nobody can currently describe. If your team cannot say who should own an inquiry today, a rule cannot decide it tomorrow — fix the process first.

With an inventory, not a build. We list every rule, what it does, what fires it, who owns it and whether it still runs — which in most orgs is the first time anyone has seen that on one page. Then we consolidate: duplicates merged, dead rules retired, overlapping ones rationalised, and order of execution documented. Consolidation engagements usually reduce the number of automations substantially, and the visible win is that people start trusting notifications again. Only after that is it worth adding anything new.

Badly designed automation can, and the usual causes are several rules firing on the same object in an undesigned order, recursive updates where one rule retriggers another, and logic that does not handle bulk operations. All three are design problems rather than platform limits. We design order of execution deliberately, keep record-triggered logic consolidated rather than scattered, and test against bulk operations — because a rule that works on one record and fails on a two-thousand-row data load is a rule that will fail during your next migration.