Real Estate · Propertybase · Salesforce

Streamlining Real Estate Operations With Propertybase on Salesforce: A Lead-to-Close Guide

Propertybase Salesforce Edition puts contacts, inquiries, listings, offers and closings in one Salesforce org. This guide shows how to streamline real estate operations with Propertybase at every stage, from lead routing and listing matching to portal syndication, transactions and reporting, and where brokerages usually need more than the package gives them.

Inquiry Match Offer Closing
Where we sit in this: Twopir Consulting is a Salesforce Partner that implements, migrates, integrates and optimizes Propertybase on Salesforce for brokerages. We do not sell Propertybase licences; Propertybase is a Lone Wolf Technologies product. Product facts below come from Lone Wolf, the Propertybase help center and Salesforce documentation, linked where they appear.

Key Takeaways

  • Propertybase Salesforce Edition is a real estate CRM installed as a managed package in a Salesforce org. Lone Wolf Technologies has owned Propertybase since 2021 and still sells the Salesforce Edition.
  • To streamline real estate operations with Propertybase, connect five stages in one org: capture, routing, matching, transaction and reporting. Most of the time savings come from removing hand-offs between those stages.
  • Out of the box you get Inquiries, Listings, Offers and Closings, two-way matching, Lead Routing (Click to Claim, Auto-Assign, Round Robin) and portal syndication, including a Middle East portal package.
  • What you still have to design yourself: routing rules that fit your offices, the data model your reports need, feed monitoring, data migration and role-based adoption.
  • Run the implementation as an org build and a migration project, not a software install. That is the difference between a CRM agents use and one they work around.

Real estate operations rarely break inside one tool. They break between tools. A portal inquiry lands in an inbox, someone copies it into a CRM, an agent searches listings by hand, the offer is tracked in a spreadsheet, and the closing paperwork lives in email. Every hand-off adds delay and a chance to lose the client. Agents are still central to most deals: in the National Association of Realtors' 2025 profile, 88% of buyers and 91% of sellers used an agent. So the systems behind your agents decide how many of those clients you keep.

Propertybase on Salesforce exists to remove those hand-offs. This guide explains what the platform includes today, how each operational stage maps to a Propertybase or Salesforce feature, what to configure first, and the gaps that growing and mid-market brokerages usually have to close themselves.

Section 01 · Quick Answer

How Does Propertybase Streamline Real Estate Operations?

Propertybase streamlines real estate operations by putting every stage of a deal on one Salesforce data model. Web and portal leads become Contacts and Inquiries. Lead Routing assigns them. Matching pairs Inquiries with Listings, and Offers turn into Closings. Salesforce reports show the whole pipeline. Each stage feeds the next, so nobody re-enters data.

Propertybase on Salesforce fits you if you run several agents, teams or offices, take leads from portals and your own website, need listing, matching and transaction data in one place, and want reporting or integrations that a closed real estate CRM cannot give you. It suits brokerages that already use Salesforce or expect to extend the CRM over time.

It is probably more platform than you need if you are a solo agent or a small team with no administrator and no integration needs. Lone Wolf now offers its non-Salesforce CRM, website and marketing tools as Lone Wolf Front Office (formerly Propertybase GO). A Salesforce org pays off when someone owns its configuration.

Section 02 · Definitions

What Is Propertybase on Salesforce in 2026?

Propertybase Salesforce Edition is a real estate CRM and back-office application that installs into a Salesforce org as a managed package. Lone Wolf Technologies acquired Propertybase in August 2021. The Salesforce Edition is still sold under the name Propertybase by Lone Wolf.

The naming changed after the acquisition, and older articles, including the earlier version of this one, still use the old names. In 2024 Lone Wolf announced that Propertybase GO became Lone Wolf Front Office, alongside Propertybase websites and marketing, and that Propertybase Back Office became Lone Wolf Workspace. This guide covers the Salesforce Edition only.

The AppExchange listing describes a Lightning-ready managed package that supports multiple currencies. Its apps, tabs and objects do not count against your org limits. At the time of writing, Lone Wolf lists pricing from $89 per user per month with the Salesforce platform licence included. Confirm current pricing with Lone Wolf before you budget.

Contacts and Inquiries

A Contact is the person. An Inquiry records what they want: property type, bedrooms, baths and budget. You can extend the search criteria with custom fields.

Listings and Linked Listings

Listings hold the inventory. Linked Listings record a contact's feedback on a specific property and stay attached to their Inquiry.

Offers and Closings

An Offer links a listing with buyer and seller records. It supports counter offers and addendums, follows a status path, and creates a Closing from the data already on record.

The Salesforce platform

Flow automation, reports and dashboards, Experience Cloud sites, the mobile app, AppExchange integrations and Agentforce all work on Propertybase data.

Object descriptions come from the Propertybase help center's lead-to-close series and its Offers article.

Section 03 · Bottlenecks

Where Do Real Estate Operations Lose Time?

Most brokerages lose time in the same five places. Each one is a hand-off between people or systems, and each maps to a Propertybase or Salesforce feature covered later in this guide.

1. Leads wait for a person to triage them. Portal and website inquiries sit in a shared inbox until someone forwards them, so response time depends on who is at a desk.
2. Listing data is typed in more than once. When feeds and portals are not connected to the CRM, staff re-key listings, and agents end up quoting stale prices or statuses.
3. Matching buyers to stock is manual. Agents search listings from memory instead of from recorded buyer criteria, so new listings miss the buyers who already asked for them.
4. Transactions live in email threads. Offers, documents and approvals are scattered, so managers learn a deal has stalled from the agent, not from the system.
5. Reporting is assembled after the fact. Weekly spreadsheets show what already happened. They cannot show which lead source converts or which agent has capacity today.
Section 04 · Workflow Map

Which Propertybase Feature Fixes Which Operational Gap?

Use this table to scope the work. Each row pairs a workflow with the feature that handles it and the decision you have to make before you configure it.

WorkflowPropertybase or Salesforce mechanismDecide before you configure
Lead captureWebToProspect REST service from your website; inbound portal dataWhich sources create Contacts, Inquiries or Listings, and how duplicates are handled
Lead assignmentLead Routing: Click to Claim, Auto-Assign or Round Robin, by team and by timeTeams, territories, after-hours rules, and who owns a returning lead
Buyer-to-listing matchingInquiry Matching and Reverse Matching, configured in the Control CenterWhich fields must match exactly and which are ranges
Listing marketingPortal Syndication through Portal Mapping; generic XML feed; Middle East portal packagePortal accounts, required fields per portal, and the auto-publish rules
Follow-upQuicksend email, property alerts, Salesforce FlowWhich events trigger a task, an email or an escalation
Offer to closeOffers with counter offers and a status path, Closings, e-signatureStage definitions, required documents and approval steps
Management visibilitySalesforce reports and dashboardsThe handful of metrics leadership will actually act on
Section 05 · Architecture

What Does a Lead-to-Close Architecture Look Like on Propertybase?

A streamlined Propertybase org works as four connected layers. Each layer creates or updates records that the next layer consumes, so a deal moves forward without anyone re-entering it. If a layer is skipped, the work behind it goes back to spreadsheets.

Layer 1 · Capture

Website, Portals and Referrals Into Contacts and Inquiries

WebToProspect creates Contacts, Inquiries and Listings from your own website. Portal inquiries arrive through syndication. Duplicate rules decide whether a returning person updates an existing record.

trigger: new contact or inquiry
Layer 2 · Route and Match

Lead Routing, Inquiry Matching and Follow-Up Automation

Lead Routing assigns the lead to a team or an agent. Matching proposes listings. Flow creates tasks and alerts, so the agent starts with a qualified shortlist instead of a blank record.

trigger: offer created
Layer 3 · Transact

Offers, Closings, Documents and E-Signature

Offers follow a status path. Required documents and approvals gate each stage, and a Closing inherits the offer data. Signing happens inside the CRM.

every stage writes data
Layer 4 · Report

Pipeline, Source Attribution and Agent Capacity

Salesforce reports read the same records the agents work in, so dashboards are current without anyone exporting them.

Section 06 · Speed to Lead

How Should You Set Up Lead Capture and Routing in Propertybase?

Capture every source straight into Salesforce, then let Lead Routing assign each lead without a person in the loop. Website forms post to the WebToProspect REST service, portal leads arrive through syndication, and Lead Routing assigns them to teams using one of three distributors.

DistributorHow it worksUse it when
Click to ClaimEvery team member is emailed and the first to claim gets the leadA team of peers competes on speed, and leadership wants to reward responsiveness
Auto-AssignThe lead goes straight to one named userA specialist owns a segment, such as a development, a language or a luxury tier
Round RobinLeads rotate through team members in orderYou want even distribution and predictable workloads across agents

Two built-in behaviours matter in practice. Routing can run at designated times, which lets you send evening or weekend leads to an on-duty team. And when a new Contact or Inquiry belongs to someone who was assigned before, Lead Routing returns it to that agent and skips the other routing steps. That protects the agent's relationship with a returning client.

Most brokerages need more than the distributors provide. Common additions built in Salesforce Flow include a follow-up task with a deadline on every new inquiry, an escalation to a team lead when that task is overdue, and a priority flag for high-intent behaviour such as a viewing request. Keep the routing rules themselves simple enough that an operations manager can explain them to a new agent.

Section 07 · Listings

How Do Listing Matching and Portal Syndication Work?

Matching connects recorded buyer criteria to inventory in both directions. Portal syndication pushes the same listing records out to the portals you subscribe to. Together they mean each listing is entered once, marketed everywhere, and offered automatically to the buyers who asked for that kind of property.

Inquiry Matching and Reverse Matching

Buyers ↔ Stock

Best for: turning every new listing into an immediate shortlist of buyers, and every new buyer into a shortlist of listings.

From an Inquiry, Matching searches available listings. From a Listing, Reverse Matching searches Inquiry data and returns the contacts who fit, ready to email. From the results, agents can generate a PDF, send listings with Quicksend, or create a Linked Listing to record feedback. You set filter fields, exact-match fields and result columns in the Control Center. A custom criterion has to exist on both the Inquiry and the Listing with the same API name, and numeric ranges use min and max fields on the Inquiry. Plan those fields during design. Adding them later means backfilling data.

Portal Syndication

Publish Once

Best for: brokerages that market listings on several portals and want status changes to reach all of them.

Portal Syndication is configured under Portal Mapping. You need your own account with each portal, and the portal's required fields must be mapped before you can activate it. Feeds can separate residential and commercial listings. Listings flagged for portals and for auto-publish go out automatically, and publishing runs in the background. For aggregators, a generic Propertybase XML feed can be picked up and distributed further.

UAE and Middle East Portals

Regional

Best for: Dubai and wider UAE brokerages listing on regional portals with permit requirements.

Propertybase's Middle East portal package integrates with Dubizzle, Bayut, Houza and Property Finder. It adds fields that include the RERA permit number (Trakheesi), a DTCM permit number for short-term rentals on Property Finder, and an optional Arabic title. Make the permit fields required in your listing process, not just on the portal mapping. A listing without a permit should never reach the publish step.

When a portal you need is not covered, the integration can be built on Salesforce directly. In one Twopir case study, a UAE luxury brokerage needed to publish to Zoopla and Rightmove. We built an Apex integration and a Lightning Web Component that let agents publish, check status and unpublish listings in one click, without leaving Salesforce.

Section 08 · Transactions

How Do You Manage Offers, Closings and Compliance in Propertybase?

Manage the deal on the Offer record and gate each stage. An Offer links the listing to buyer and seller records, holds counter offers and addendums, and moves along a status path. When it is accepted, the Closing is created from the data already captured. Required documents and approvals at each stage give managers an audit trail without chasing anyone.

  • Define the stages once. Agree the offer and closing stages across all offices before you build. Different stage names in different offices make every report wrong.
  • Gate the stages. Use Flow or validation rules so a deal cannot move forward until the required documents or approvals are on the record.
  • Sign inside the CRM. Lone Wolf says Authentisign is built into Propertybase. If your brokerage standardises on Docusign, Docusign eSignature for Salesforce sends, signs and tracks agreements from the Salesforce record.
  • Automate the deadlines. Inspection, finance and document-expiry dates should create reminders for both the agent and the manager.
Section 09 · Reporting

What Should a Brokerage Report On in Propertybase?

Report on outcomes by source, agent and office, not on activity counts. Because Propertybase data lives in standard Salesforce objects, Salesforce reports and dashboards can join inquiries, listings, offers and closings. That only works if the data model was designed with those joins in mind.

MetricWhat it tells youRecords it needs
Time to first contactWhether routing and follow-up rules are workingInquiry created time and first logged activity
Conversion by lead sourceWhich portals and campaigns produce closings, not just inquiriesA source field set on capture and carried to the Offer and Closing
Pipeline by stage and officeWhere deals stall and which office needs attentionConsistent Offer stages across offices
Agent load and capacityWho can take the next leadOpen Inquiries and Offers per owner
Listing days on market and portal statusStale inventory and syndication failuresListing status history and publish flags
Commission forecastExpected revenue by monthClosing dates and commission values

If your dashboards exist but nobody trusts them, the cause is usually upstream: duplicate contacts, a source field nobody fills in, or stages used differently in each office. Our Propertybase reporting work starts there, before any dashboard gets rebuilt.

Section 10 · Scale

Can Propertybase Run a Multi-Office or International Brokerage?

Yes. Lone Wolf positions the Salesforce Edition for multi-office and multi-territory structures, and the Salesforce platform underneath adds the controls those structures need. Teams and routing schedules separate offices. The sharing model limits who sees which records. Currency and language settings support cross-border work.

  • Currencies: Salesforce multiple currencies lets admins set a corporate currency, active currencies and conversion rates. Advanced currency management adds dated exchange rates.
  • Languages: Translation Workbench translates labels and picklists for multilingual teams.
  • Client and partner portals: Experience Cloud builds branded sites for clients, developers or referral partners on the same data.
  • Visibility: decide early whether agents see all listings and only their own contacts. Matching includes a "show only owned records" option, and Salesforce sharing rules handle the rest.
Section 11 · Mobile and AI

How Do Mobile Access and Agentforce Fit Propertybase?

Agents work Propertybase records from the field in the Salesforce mobile app, which supports offline caching and offline edits. AI is the newer layer. Agentforce is Salesforce's platform for AI agents, and Lone Wolf markets Agentforce-based lead scoring and deal predictions for Propertybase.

AI does not fix operational data. An agent that summarises inquiries or drafts follow-ups is only as reliable as the listing feed, the duplicate rules and the sharing model behind it. Practical starting points:

  • summarising an inquiry and its activity before a call
  • drafting follow-up emails that an agent reviews before sending
  • flagging deals that have stalled past a stage threshold

Keep deterministic work, such as routing and permit validation, in Flow. Our Propertybase AI and Agentforce work starts with data readiness for that reason.

Section 12 · Roadmap

What Is the Right Order to Implement Propertybase?

Implement in the order deals flow: map the workflow, design the data model, migrate clean data, then switch on routing, transactions and reporting in phases. Each phase should be tested in a sandbox and accepted by the people who will use it before the next one starts. In our published Propertybase engagements, a brokerage of 50 to 200 agents typically needs 8 to 14 weeks for a full implementation.

1. Discovery: map how a lead becomes a closing today.
Interview agents, operations and leadership. List every hand-off where data is re-entered or lost. That list becomes the scope.
2. Design the org: data model, sharing and matching fields.
Decide the stages, the source tracking and the visibility rules before configuring anything. Reports depend on these decisions.
3. Migrate data as a project, not an import.
Profile the source, deduplicate, bring the history and documents agents rely on, and rehearse the load at full volume. See our Propertybase data migration approach.
4. Connect feeds, portals and capture.
Set up WebToProspect, portal mappings and any listing feeds. Give every feed an owner and an alert for when it fails.
5. Switch on routing, follow-up and transaction gates.
Start with a few rules people can explain, measure them, then add more.
6. Train by role and run in parallel.
Agents, operations and managers each rehearse their own day in the new org. Avoid an overnight cutover with no way back.
Section 13 · Pitfalls

Why Do Propertybase Implementations Fail to Streamline Anything?

Installing the package takes an afternoon. Most failures come from what happens after it. These are the patterns we see most often when brokerages bring a stalled Propertybase org to us:

1. The data model was inherited, never designed. Default fields are used for things they were not meant for, and reporting breaks first.
2. Migration was scoped as an import. Current records move but history does not, so agents keep the old system open "just to check".
3. Feeds are connected but nobody owns them. A portal or listing feed fails quietly and stale data reaches clients.
4. Routing rules nobody can explain. Agents stop trusting assignment and go back to claiming leads by hand.
5. Training was a platform tour. People saw the screens but never rehearsed their own workflow, so adoption fades after go-live.

If your org already shows these symptoms, it usually needs a structured implementation or rescue, not another round of features.

Section 14 · In Practice

What Does a Streamlined Propertybase Org Look Like in Practice?

One published Twopir engagement shows the full pattern. A multi-office residential brokerage with 120+ agents had been through two failed CRM projects. It was triaging leads by hand, re-uploading listing exports twice a day, and running transactions from email. We delivered the work in five phases over 12 weeks: discovery, Propertybase implementation, Flow-based lead routing and nurture, stage-gated transactions, and dashboards with role-based training.

The case study reports that first-contact time fell from 4–6 hours to under 15 minutes. It also reports a 35% lift in lead-to-appointment conversion within 90 days of go-live, and new-agent onboarding that dropped from 14 days to 3. Results depend on the starting point. The sequence is what carries over: map the workflow, fix the data, then automate.

Twopir Consulting has worked with 500+ clients over 12+ years. We implement, rescue, optimize, and integrate complex CRM and revenue systems, and for real estate firms that means Propertybase and Salesforce working as one operating system. Explore our Propertybase practice and our wider Salesforce for real estate services.

Ready to Start

Find Where Your Lead-to-Close Process Leaks

On a 30-minute discovery call, a Twopir Salesforce architect will walk through your capture, routing, listing and transaction workflow. You'll leave with a clear view of where Propertybase can remove hand-offs and what to fix first.

Schedule a Discovery Call
Section 15 · Bottom Line

The Bottom Line

Propertybase on Salesforce streamlines real estate operations when it removes hand-offs. Leads route themselves, buyers match to listings automatically, listings reach portals from one record, and deals move through gated stages into dashboards leadership trusts. The package supplies the objects and the core features. The results depend on how deliberately the org is designed, migrated and adopted.

  1. 1

    Propertybase Salesforce Edition is a Lone Wolf managed package on Salesforce. GO is now Lone Wolf Front Office, a separate product.

  2. 2

    Connect five stages in one org, capture, routing, matching, transaction and reporting, and measure the hand-offs between them.

  3. 3

    Choose a routing distributor per team, and use Flow for deadlines and escalations.

  4. 4

    Design matching fields, stages and source tracking up front: reporting depends on them.

  5. 5

    Treat migration, feeds and training as projects with owners, not tasks after go-live.


FAQ

Frequently Asked Questions

Propertybase Salesforce Edition is. It installs into a Salesforce org as a managed package and adds real estate objects such as Inquiries, Listings, Offers and Closings. Lone Wolf's non-Salesforce CRM, formerly Propertybase GO, is now sold as Lone Wolf Front Office.

Lone Wolf Technologies announced its acquisition of Propertybase in August 2021. The Salesforce Edition is still sold as Propertybase by Lone Wolf, and Propertybase GO, websites and marketing have been rebranded as Lone Wolf Front Office.

Lead Routing assigns incoming leads to teams with one of three distributors: Click to Claim, Auto-Assign or Round Robin. It can route at designated times, and it returns a new contact or inquiry to the agent who owned it before. Salesforce Flow can add deadlines and escalations.

Yes. Propertybase's Middle East portal package integrates with Dubizzle, Bayut, Houza and Property Finder, and adds fields such as the RERA permit number (Trakheesi). For portals it does not cover, a direct integration can be built on Salesforce.

In Twopir's published Propertybase engagements, a full implementation for a brokerage of 50 to 200 agents typically takes 8 to 14 weeks, delivered in phases so core functions go live first. Data migration scope and the number of feeds and integrations are the biggest variables.

Usually, yes. Propertybase supplies the real estate objects and core features, but routing rules, matching fields, transaction stages, reporting and integrations have to be configured around how your brokerage actually works. That design work decides whether the org streamlines operations or adds another tool.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. Our real estate practice implements, migrates, integrates and optimizes Propertybase on Salesforce for brokerages, including in the UAE and other international markets.