Scale Real Estate Teams with Propertybase and Salesforce: A Multi-Office Playbook
Adding agents is easy. Adding offices without slower lead response, leaking client data and weekly spreadsheet reports takes design. This playbook covers teams and offices, access, lead routing, onboarding and offboarding, data, change control and reporting, in the order a growing brokerage meets them.
Key Takeaways
- To scale real estate teams with Propertybase and Salesforce, design the org for the brokerage you will be in two years: teams and offices, an access model, lead routing per team, and a repeatable way to add and remove agents.
- Growth breaks the same things in the same order: lead distribution first, then visibility between teams, then onboarding speed, then data quality, then the automation nobody owns.
- Propertybase ships Team and Office records and Lead Router teams. Salesforce adds roles, sharing rules, permission set groups, delegated administration and dashboards by office.
- Plan for leavers as carefully as joiners. A deactivated agent can silently break Action Plans, Front Desk and dashboards, and still holds a Propertybase licence.
- Every change goes through a sandbox first, because more agents means more people affected by a bad release.
To scale real estate teams with Propertybase and Salesforce, a brokerage has to stop treating the CRM as a contact list and start treating it as the operating system for every office. Adding agents is easy. Adding agents without slower lead response, lost client data, disputed leads and a weekly reporting scramble takes design decisions most brokerages only make after something breaks.
This playbook is for broker-owners, COOs and operations leaders at growing and mid-market companies in real estate: a single team heading for a second office, or a multi-office brokerage that has outgrown its first setup. It replaces our 2025 article of the same name. Unsourced statistics and case studies are gone, the outdated MLS terminology has been fixed, and every product detail now links to Salesforce, Propertybase or RESO documentation.
What Does It Take to Scale a Real Estate Team on Propertybase?
Five design decisions, made before you need them. Model your teams and offices, decide who sees whose clients, route leads to teams rather than people, make adding and removing an agent a checklist, and put every change through a sandbox. Get those right and a new office is configuration work rather than a rebuild.
What you need depends on where the brokerage is. The agent counts below are rough guides, not thresholds: a brokerage with many small teams hits the second row sooner than one big team.
| Stage | What usually breaks | What to put in place |
|---|---|---|
| One team up to about 25 agents | Leads triaged by hand; everyone sees every client | Lead Router with one team, the PB Agent profile, a baseline dashboard |
| Several teams about 25–75 agents | Disputed leads; team leads can't see their team's pipeline | Propertybase Teams, a role per team, private contacts shared to team groups, a distributor per team |
| Several offices about 75–200 agents | Slow onboarding; office reports built in spreadsheets; automation conflicts | Offices, permission set groups by job, delegated administration, dashboards by office, a sandbox release process |
| Network or franchise 200+ agents | Data volume, ownership skew, storage, offices that want their own rules | Archiving, Full sandbox testing, restriction rules where sharing is too wide, a change board |
What Is Propertybase on Salesforce in 2026?
A real estate CRM installed as a package inside a Salesforce org. Propertybase adds real estate records such as inquiries, listings, offers and closings, plus lead routing and matching. Everything a growing brokerage needs to scale (roles, sharing, user management, automation and reporting) comes from the Salesforce platform underneath it.
Lone Wolf Technologies acquired Propertybase in 2021 and now offers two products: Propertybase, the CRM built on Salesforce, and Front Office, formerly Propertybase GO. This article is about the Salesforce edition. On its product page, Lone Wolf says the CRM is used by more than 20,000 users and pitches it as able to scale from 10 agents to more than 200; treat those as the vendor's own claims.
Terms you will meet when scaling
| Term | What it means for a growing brokerage |
|---|---|
| Team and Office | Propertybase records that group agents. Office members can be a Primary Manager, Office Manager or Office Administrator, and a team can belong to an office. |
| Lead Router | Propertybase's assignment engine: routing sources, teams and distributors (Click to Claim, Auto-Assign, Round Robin). |
| Organization-wide default (OWD) | The baseline access to records you don't own: Private, Public Read Only or Public Read/Write. |
| Role hierarchy | Lets managers see records owned by the people below them. |
| Permission set group | A bundle of permissions for one job, such as agent, transaction coordinator or office manager. |
| RESO Web API | The current standard for receiving MLS data. It replaces RETS, which RESO has deprecated. |
| Ownership skew | One user owning more than 10,000 records of an object, which slows sharing changes. |
What Breaks First When a Real Estate Team Grows?
The parts nobody designed because the team was small enough to work around them. At ten agents, a coordinator can forward leads, everyone can see every client, and the broker can build reports by hand. At fifty, each of those workarounds becomes a full-time job, a privacy risk or a reason good agents leave.
Our guide to Propertybase Salesforce CRM architecture covers the technical design behind each of these. The rest of this playbook takes them in the order a growing brokerage usually meets them.
What Does a Scalable Propertybase Org Look Like?
One org, four layers, and a gate in front of production. Every lead and listing source lands in Propertybase. Propertybase holds the real estate records and routes leads by team. The Salesforce platform decides who sees and changes what. People work in it by job, and every change is built and tested in a sandbox before anyone in an office sees it.
Two rules keep this shape intact as offices are added. First, one org: separate orgs per office split reporting, duplicate clients and multiply admin work. Second, the package owns the real estate records: don't build a parallel "deal" or "transaction" object beside Propertybase's offers and closings, or reports will disagree.
Where MLS data comes in
The old version of this article described MLS feeds in terms of RETS. RESO, the body that sets real estate data standards, has deprecated RETS and no longer supports it. Its successor is the RESO Web API, and RESO reports that at least 90% of MLSs now offer RESO-certified Web API services. If a growing brokerage adds a market served by another MLS, ask that MLS and your integration partner for a Web API feed, and load only changed listings on each sync, keyed on the MLS listing ID. For large one-off loads, Salesforce recommends Bulk API 2.0 for operations over 2,000 records.
How Should a Multi-Office Brokerage Set Up Teams, Offices and Access?
Model the structure in Propertybase, then build access in Salesforce from the most private setting up. Create Team and Office records, put each agent in exactly one team, set client records to private, and open them deliberately: to team and office groups through sharing rules, and to managers through the role hierarchy.
Model teams and offices in Propertybase
Propertybase added Team and Office records, with team and office members, in version 1.598. They were released as a beta for customers with a Propertybase Website, so confirm availability for your org. The documented rules are worth adopting even if you build your own structure: an agent should belong to only one team, every team needs at least one user, and a team can itself be a member of an office. Teams and offices sync to the Propertybase Website every ten minutes, and once migrated they are edited only in the CRM.
Open access deliberately
Salesforce sets a default access level for every object and then lets you widen it, never narrow it. The role hierarchy lets users see and report on data owned by people below them, and sharing rules open records to groups or roles, up to 300 rules per object. Propertybase's own recipe for teams uses exactly these tools: a public group for each team or office, the Contact default set to Private, and an owner-based sharing rule that shares members' records with the group, read-only for an office and read/write for a team.
| Who | Should see | How to grant it |
|---|---|---|
| Agent | Own clients and deals; active listings across the brokerage | Private contacts; listings shared to all agents |
| Team member | Teammates' clients, to cover for each other | Owner-based sharing rule to the team's public group, read/write |
| Team lead or office manager | Everything owned by their team or office | Role hierarchy, plus a read-only office sharing rule |
| Transaction coordinator | Offers and closings across an office | Criteria-based sharing rule to a coordinators group |
| Leadership and finance | All offices; commission fields | Top of the hierarchy; a permission set for commission fields |
Build the hierarchy around data access, not the org chart, and keep it shallow. Where an office must not see another office's activity even though sharing would allow it, restriction rules can filter records further, but only on custom objects, tasks, events and a few others, with two active rules per object in Enterprise Edition and five in Performance and Unlimited.
How Do You Route Leads Across Teams and Offices?
Route every lead to a team first, then to an agent inside it. Lead Router assigns a routing source to the contact, the source points at a team, and the team's distributor picks the agent. One team per office or specialty keeps rotations fair, and a Salesforce Flow escalates any lead nobody contacts in time.
- Pick a distributor per team. Round Robin suits teams that share leads evenly, Click to Claim suits teams that compete on speed, and Auto-Assign suits a single specialist. Each team can use a different one.
- Route office and team leads from the website. With Teams and Offices, Lead Router can route office leads to the office's Primary Manager and team leads to the Team Lead, through a routing team and distributor. Leads only reach users who synced to the website without errors.
- Remember returning contacts. Lead Router sends a returning contact back to its previous owner, and that behaviour is not configurable. When an agent leaves, reassign their contacts before the next inquiry arrives.
- Add the clock Propertybase doesn't ship. A record-triggered flow with a scheduled path can check whether a lead has been contacted a set time after assignment, then reassign it or alert the team lead.
- Don't park unassigned leads on one user. Salesforce calls a user who owns more than 10,000 records of one object ownership skew, and gives parking unassigned leads on a dummy user as its example. Use a queue, spread ownership, or keep that user out of the role hierarchy.
Our guide to Propertybase workflows from lead to close walks through the escalation flow step by step.
How Do You Onboard New Agents Without Slowing Down?
Turn agent setup into a checklist that a template completes. A new agent needs a Salesforce user, a Propertybase licence, the right profile and permission set group, a team, a website role and a short training path. When each of those is automatic or one click, an office manager can add an agent in minutes.
userlicense_sync setting is enabled.One warning from Propertybase's documentation: never rename a former agent's user for a new hire. It renames the change history of everything the former agent touched.
What Should Happen When an Agent Leaves?
Freeze the user, move their clients, fix what ran as them, then deactivate and free the licence. Agents leave more often than offices open, and a sloppy exit costs more than a slow start: clients go unanswered, automation fails silently and you keep paying for a licence nobody uses.
Bulk ownership changes are among the most expensive operations in Salesforce, so move a large book of business outside working hours.
How Do You Keep Data Clean and Fast as the Brokerage Grows?
Stop duplicates at the door, load only what changed, and watch storage and ownership. Most brokerages never come close to Salesforce's large-data thresholds, but more agents, more portals and more listings multiply duplicates and storage use quickly. A few rules set early keep the org fast and the reports trustworthy.
- Block duplicates. Salesforce matching and duplicate rules can warn or block when an agent creates a contact that already exists, and duplicate jobs find the ones already there.
- Plan storage. Salesforce allocates 10 GB of data storage per org plus 20 MB per user licence in Professional and Enterprise editions, or 120 MB in Performance and Unlimited. File storage is separate. Activities, listing history and portal leads are what usually fill it.
- Know the large-data line. Salesforce's large data volumes guide describes tens of thousands of users, tens of millions of records or hundreds of gigabytes. A national network syndicating every historical listing can approach it; archive what nobody works.
- Defer sharing on big changes. Reorganizing roles or groups for a new office triggers sharing recalculation. Salesforce lets you defer sharing calculation and run it later, overnight or at a weekend.
Moving several offices' data into one org is a project of its own. Our Propertybase data migration service covers the mapping, de-duplication and cutover.
How Do You Change the Org Without Breaking Every Office?
One owner, one backlog, one release path. Name a single admin or partner who owns the org, collect office requests in one backlog, build and test every change in a sandbox, and release on a schedule. Retest after each Propertybase release, which Lone Wolf says ships every three to six weeks.
- Use the right sandbox. Salesforce documents four sandbox types. Partial Copy sandboxes suit user acceptance testing and training. Only Full sandboxes support performance testing, load testing and staging.
- Track changes in source control. DevOps Center, renamed Lifecycle Center from October 2026, is Salesforce's alternative to change sets.
- Keep one entry point per object. Follow Salesforce's Flow best practices: plan first, build in a sandbox, never hard-code record IDs, add fault paths, and test many variations. Per-office logic goes into decisions inside one flow, not one flow per office.
- Check security as you grow. Run Salesforce's Health Check after big access changes, and review who holds admin permissions every quarter.
How Do Managers See Performance by Office and Team?
Build each dashboard once and let the role hierarchy filter it. A dashboard that runs as the viewer shows each manager only their own office or team, so leadership, office managers and team leads share one design. Baseline the numbers before you change anything, and compare offices on the same definitions.
In Salesforce, a dashboard set to view as "The dashboard viewer" is a dynamic dashboard, and the "View My Team's Dashboards" permission lets a manager view it as anyone below them in the hierarchy. Dynamic dashboards are limited, though: five per org in Enterprise Edition and ten in Unlimited and Performance, and they can't be subscribed to. Spend them on the views every office needs.
| Metric, by office and team | What it tells you |
|---|---|
| Time from inquiry to first logged contact | Whether routing and escalation keep up with volume |
| Active inquiries per agent | Capacity, and whether distribution is fair |
| Conversion by lead source | Which sources each office should spend on |
| Days from accepted offer to closing | Back-office speed per office |
| Days from hire to first logged activity | How fast onboarding really is |
| Open records owned by inactive users | Whether offboarding is finished |
What Does Scaling Look Like in a Real Brokerage?
A US brokerage with four offices and more than 120 agents is a good example. It had grown past a basic CRM, spreadsheets and manual MLS exports, and had been through two failed implementations. Twopir Consulting implemented Propertybase on Salesforce in five phases over twelve weeks, each validated in a sandbox before going live.
The work followed the order of this playbook: a data model and access design first, then Flow-based routing by zip code, property type and agent workload across all four offices, an automated MLS feed with health checks, stage-gated transactions, live dashboards by region, and role-based training. According to the published case study:
- Lead response time went from 4–6 hours to under 15 minutes.
- New-agent onboarding fell from 14 days to 3.
- Each agent recovered about four hours a week of admin.
- Compliance audit preparation fell from two days to under two hours.
- Live regional dashboards replaced weekly Excel reports.
These are one brokerage's results against its own starting point. The onboarding figure matters most for scaling: every agent hired after go-live started faster.
What Is a 90-Day Plan to Make Propertybase Ready to Scale?
Thirty days to baseline and design, thirty to build in a sandbox, thirty to roll out and measure. Do it before the next office opens, not during. Each phase ends with something agents or managers can use, so the brokerage sees progress while the foundations go in.
Our Propertybase consulting team runs this plan for new Propertybase implementations and for brokerages whose org has fallen behind their growth.
The Bottom Line
Propertybase and Salesforce can carry a brokerage from one team to many offices, but the platform doesn't scale your processes for you. The brokerages that grow smoothly decide early how teams, access, routing, joiners and leavers, data and change will work, and then let the system enforce it.
- 1
Model teams and offices, and put each agent in one team.
- 2
Start client records private and open access on purpose.
- 3
Route leads to teams, then agents, with an escalation clock.
- 4
Make joining and leaving a checklist, and hand it to office managers.
- 5
Put every change through a sandbox, and measure every office the same way.
Is Your Propertybase Org Ready for the Next Office?
On a 30-minute discovery call, a Twopir Salesforce architect will review how your teams, access and lead routing are set up today, show you what will break first as you add agents, and suggest where to start.
Schedule a Discovery CallFrequently Asked Questions
Design the org before you need it. Model teams and offices in Propertybase, set client records to private and open them through sharing rules and the role hierarchy, route leads to teams before agents, make adding and removing agents a checklist, and put every change through a sandbox before it reaches the offices.
Lone Wolf says Propertybase is used by more than 20,000 users and pitches it as scaling from 10 agents to more than 200. Because it runs on Salesforce, user numbers are rarely the limit. What limits growth is design: access, routing, data quality, storage and how changes are released.
Propertybase has Team and Office records with members, released as a beta for customers with a Propertybase Website. Put each agent in one team, give offices a Primary Manager and Office Manager, and pair them with public groups and sharing rules: read/write within a team, read-only across an office.
Freeze the user so they can't log in, transfer their contacts and deals to another agent, repoint Action Plans, Front Desk and dashboards that run as them, then deactivate the user, set the Website Role to No Sync and remove the Propertybase licence, which otherwise stays assigned.
Yes, with Salesforce delegated administration in Enterprise Edition and above. A delegated group can create and edit users in specified roles and those below them, reset passwords and assign chosen profiles and permission set groups, without being able to change sharing defaults or grant Modify All Data.
Build dynamic dashboards that run as the viewer, so each manager sees only their own office or team through the role hierarchy. Enterprise Edition allows five dynamic dashboards per org and Unlimited and Performance allow ten, so reserve them for the views every office needs.
Yes. With more agents, a bad change affects more people. Build and test changes in a Partial Copy sandbox for user testing and training, use a Full sandbox for load testing and staging, and retest routing, matching and closings after each Propertybase release.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Propertybase implementations, migrations and automation for real estate brokerages.