How many CRM seats does a real estate team need?

Count the humans who own leads or talk to clients. That’s the answer in one sentence — every complication in CRM seat math is a role someone hopes can squeeze under another person’s login, and most of them shouldn’t. Here’s how the count works role by role, and what it costs.

The rule that decides every case

A seat is an identity: leads route to it, messages send from it, activity stamps against it. So the test for any role is identity-shaped — does this person need leads assigned to them, do they communicate with contacts as themselves, does anyone ever need to know what they did? Three yeses is unambiguous; even one usually justifies the seat. The counter-test is just as clean: someone who never logs in, owns nothing, and contacts nobody needs a report forwarded to them, not a licence.

The worksheet, role by role

Run the roster:

• Producing agents — one seat each, no exceptions. Routing, claim mechanics, and accountability all hang off individual identity.
• Team lead — a seat, even if they’ve stopped taking rotation. Reassignment, oversight, and reporting are seat-level actions.
• ISA — a seat, and arguably the busiest one on the team; an inside sales agent lives in the CRM by job description.
• Transaction coordinator — a seat in almost every real configuration, because TCs message clients and complete tasks that must be attributable.
• Admin / operations — a seat if they touch contacts or tasks; possibly not if their entire involvement is receiving an exported report.
• Marketing VA or social-media help — usually no seat. Posting content isn’t CRM work. The exception is a VA who answers inquiries, at which point they’ve become an inside role by another name.
• Showing assistants — borderline; if appointments are assigned to them and they confirm with clients, that’s identity work.

A typical five-agent team with a lead, an ISA, and a TC lands at eight seats — a number most teams underestimate by two because the support roles were invisible in the first count.

Why shrinking the count backfires

Seat-squeezing has one honest motive — per-seat pricing adds up — and two hidden costs that exceed it. Shared logins destroy attribution: routing can’t target half a login, and when a client says “someone told me X,” a shared identity means nobody told them X. And departures get dangerous: offboarding a person who shared credentials means rotating access for everyone left, instead of deactivating one seat and reassigning its contacts cleanly. The deeper mechanics are covered in the team CRM seats page; the summary is that a seat’s price buys the two properties a team CRM exists to provide, and sharing quietly refunds both.

Pricing the count without surprises

Once the worksheet gives you a number, read plans by their included seat counts rather than headline prices. BrokerFold’s Team plan includes five seats and the Brokerage plan includes twelve, with extra seats at $70 CAD per month — so the eight-seat team above runs Team plus three seats, and a growing team crossing roughly ten to twelve should price the Brokerage tier before stacking add-ons. The pricing page lays the tiers out, and the 14-day trial takes no credit card, which makes the honest test cheap: load your real roster, run a week of real leads through the CRM, and let the seat count prove itself before you pay for it.

Recount twice a year

Seat math drifts. New hires borrow logins “temporarily,” departed agents’ seats sit paid and empty, and a role that was reports-only in January is messaging clients by June. A ten-minute audit each half-year — who has a seat, who’s sharing, who’s paying for nobody — keeps the count matched to the team you actually run, which is all seat math ever needs to do.