Installing the package takes an afternoon. Getting your properties, spaces, owners and historical comps in — in the right order, with the ownership resolved — is the project. Twopir Consulting implements Rethink by Buildout with the scope written down before anything is configured. Sequenced migration, honest scope, brokers who actually use it.
Trusted by 500+ organizations — including property and real estate businesses running their operations on Salesforce with Twopir Consulting.
Implementation Delivery
None of these are software defects. All six are decisions made — or skipped — during delivery, and all six are cheaper to avoid than to unwind six months later.
A Contact cannot be saved without a parent Company, and Spaces are children of a Property. Load contacts first and the import fails; load spaces first and they have nowhere to attach. Order is not a preference here, it is a constraint.
Every desk wants its own stage, the list grows to fourteen, and brokers stop updating deals. Four representation types need four honest pipelines — not one flattened list, and not a stage per opinion.
The org goes live with an empty comp database, so GEOsearch shows nothing and brokers keep pitching from their own spreadsheets. Loading the back-catalogue is the difference between a tool they use and a tool they tolerate.
Properties import with owner names as free text instead of resolved Company and Contact records. The ownership view is wrong from day one, prospecting lists cannot be built from it, and every later fix is a manual merge.
Sync is enabled, the listing team is told it works, and nothing leaves the org — because a property or deal will not send without an internal broker attached as an associated party. It fails silently, which is the worst way to fail.
Training happens once, on launch day, to whoever attended. Three months later half the brokers are back in spreadsheets and leadership concludes the CRM failed. Adoption is a measured workstream, not an event.
Written down before anything is configured, so change requests are a conversation rather than an argument. This is our standard shape — yours is agreed in the audit.
| Included as standard | Separately scoped | You supply |
|---|---|---|
| Data model & record-type design | Custom objects beyond the package | A decision-maker per representation type |
| Pipeline & stage configuration, all four rep types | Apex, Lightning Web Components | Commission and house-split rules |
| Property, space, company & contact migration | Third-party system integrations beyond Showcase and email | Access to whatever holds the data today |
| Historical comp load | Purchased market data beyond your own records | Decisions on what history is worth keeping |
| Commission, split & invoice configuration | Accounting or ERP integration | Sign-off from whoever owns billing |
| Showcase sync setup & prerequisites | Buildout licensing and Showcase content | Your Buildout account and its admin |
| Profiles, sharing & permission design | Experience Cloud / external portals | Who may see which desks' deals |
| Role-based enablement & hypercare | Ongoing managed support after hypercare | Broker time for training |
Salesforce and Buildout licences are bought direct from the vendors, never resold through us. We will tell you which editions and licence types the design needs before you commit to them.
Rethink's data model enforces real dependencies. Load out of order and records either fail outright or, worse, succeed in a shape you have to unpick later.
| # | Load | Why it is here | If you get it wrong |
|---|---|---|---|
| 1 | Companies | Every Contact needs a parent Company. | Contact import fails outright. |
| 2 | Contacts | Owners, tenants and outside brokers must exist before anything references them. | Unaffiliated people end up under a "No Company" placeholder you then have to clean. |
| 3 | Properties | Buildings and land, with owners resolved to real Company and Contact records. | Free-text owners; the ownership view is wrong and prospecting lists cannot be built. |
| 4 | Portfolios | A Portfolio is a Property record type; members point at it via Parent Property. | Portfolios modelled as text, so nothing rolls up. |
| 5 | Spaces & Units | Children of a Property — and deleted with it. | Orphaned suites, or spaces silently destroyed in a later property merge. |
| 6 | Deals & associated parties | Deals reference properties, spaces, companies and contacts — all of which must already exist. | Deals without an internal broker will never sync to Showcase. |
| 7 | Comps & activities | Historical sale and lease comps, then the activity history worth keeping. | An empty map on day one, and brokers who keep pitching from spreadsheets. |
Every migration is rehearsed in a sandbox and reconciled — record counts, spot-checked relationships, and a signed-off variance report — before it touches production. We do not run an unrehearsed production load, on any engagement, at any budget.
Each phase ends with something you can read and approve. No phase ends with "we are making progress" — if there is nothing to sign off, the phase is not finished.
Produces: a written findings document — current configuration, data quality profile, adoption by desk, integration inventory, licence position, and a prioritised backlog. Needs from you: org access and an hour each with the people who run each desk.
Produces: the data model, pipeline design per representation type, sharing and profile model, commission and invoicing path, integration design, and the configuration-versus-code boundary. Needs from you: decisions, and a signature. Rework after this point is the expensive kind.
Produces: pipelines, stages, record types, page layouts, validation rules that enforce the comp-critical fields, Action Plan templates, duplicate rules and reports — built in increments you review as they land, not in one reveal at the end.
Produces: a sandbox rehearsal, a reconciliation report, then the production load in the seven-stage order above. Needs from you: decisions on what history is worth keeping, and someone who can confirm the numbers look right.
Produces: Showcase sync configured with its prerequisites actually met and verified end to end, email and calendar capture connected, and whatever else was scoped in phase 02 — each one tested with a real record, not assumed from a settings screen.
Produces: role-based training for brokers, operations and leadership, a short written reference per role, and a hypercare window with a named contact and measured adoption. Needs from you: protected broker time. This is the phase firms cut, and the one that decides whether any of the rest mattered.
We do not publish a timeline or a price, because any number quoted before seeing your org is a guess dressed as a commitment. Here is what we look at to produce a real one.
The biggest variable by a wide margin, and the one firms consistently underestimate.
A single-desk investment sales shop and a four-office full-service brokerage are different projects.
Each system that has to exchange data adds design, build and testing — and a second party to coordinate with.
The audit is scoped and priced on its own, separately from delivery. It produces the findings document and the backlog whether or not you continue with us, and it is what makes the delivery estimate real rather than optimistic.
Delivery is then quoted against the signed architecture, broken down by phase, so you can stage the investment — configure and migrate now, integrations next quarter — rather than committing to everything at once.
What we will not do is quote a fixed price for a migration before seeing the data. Anyone who does is either padding heavily or planning to raise a change request the moment the first import fails.
Three things to settle before a kick-off call. If you cannot answer the first group, start there — it is the group that delays projects.
Blocks architecture sign-off in phase 02.
Someone has to be able to decide, not just consult. These questions have no technically correct answer — they are business calls.
Blocks migration in phase 04.
You do not need clean data to start — you need to know where it is and who can arbitrate when two sources disagree.
Blocks integration and enablement, phases 05 and 06.
The unglamorous group, and the one that quietly adds weeks when it is left until it is needed.
Two kinds of evidence, labelled: what Buildout has published about the product, and what Twopir has delivered on Salesforce for operations teams.
Buildout's own customer story on Rethink CRM, cited here as product evidence — VREI is Buildout's customer, not a Twopir engagement.
The reported gain comes from dealmaking data sitting in one location instead of scattered files — which is a migration and data-architecture outcome, not a feature you switch on.
Read Buildout's customer storyRebuilding lead management and sales operations on Salesforce — the same delivery discipline applied to a brokerage's inquiry-to-deal path.
The transferable part is the sequencing: model first, migrate in dependency order, enforce the fields that downstream reporting depends on, then train by role rather than by feature.
Read the case studyRepresentative engagement shapes, not measured client results — included so you can recognise which one you are before the first call.
No legacy system, so migration is small but decisions are slow — nobody has ever had to define a stage before. The work is mostly architecture and enablement. These go live fastest and adopt hardest.
Years of properties, contacts and comps to bring across, with duplicates and unresolved ownership. Migration dominates the plan. The decisive question is how much history is genuinely worth keeping.
Rethink is installed but unused. We audit before assuming anything needs rebuilding — often the data model is sound and the failure was stages, permissions and enablement. Rarely a fresh org.
Implementations do not fail dramatically. They fail slowly — a slipped decision, an unrehearsed load, a training session nobody protected time for.
The table above is published for a reason. You will know what is included, what is separately scoped and what we need from you before any work begins — so a change request is a conversation, not a confrontation.
Sandbox first, every time. A reconciliation report with record counts and spot-checked relationships goes to you before the production load runs. No unrehearsed production migrations, on any engagement.
Buyer, Seller, Tenant and Landlord Rep are four businesses with four economics. Flattening them into one pipeline is the most common implementation shortcut and the one that quietly destroys your reporting.
Rethink is a managed package on a platform we have worked on for over a decade. Sharing models, governor limits, release management and upgrade safety are our home ground — which matters most exactly when an implementation hits something non-standard.
Role-based enablement, a written reference per role, hypercare with a named contact, and adoption measured after launch. A technically perfect org that brokers avoid is a failed implementation, and we would rather say so early.
It depends on three things, and we will tell you which after the audit: how many desks and offices you run, how clean your existing property and contact data is, and how many systems have to exchange data with the org. Data quality is the biggest variable by a wide margin. We deliberately do not publish a week count — any number quoted before seeing your data is a guess dressed as a commitment, and the firms that quote one usually raise a change request the moment the first import fails.
We scope and price the audit on its own, separately from delivery. It produces a written findings document and a prioritised backlog whether or not you continue with us. Delivery is then quoted against the signed architecture and broken down by phase, so you can stage the investment rather than committing to everything at once. Salesforce and Buildout licences are bought direct from the vendors and never resold through us — but we will tell you which editions and licence types your design needs before you commit to them.
Yes, and the source matters less than the shape the data is in. What we need is an export, and someone who can arbitrate when two sources disagree about the same building. Spreadsheet migrations are usually smaller in volume but slower in decisions, because nobody has previously had to define what a stage or an owner record means. Legacy CRE CRM migrations are the opposite: the volume is large and the hard work is duplicates and unresolved ownership.
They get loaded, and it is worth doing even when it feels optional. Comps are what make GEOsearch and your pitch material useful on day one rather than in two years, and an org that launches with an empty map is an org brokers keep a spreadsheet alongside. Going forward, Rethink creates a Sale or Lease Comp automatically when a deal closes — but only if the deal carries a Property, and a Space or Unit for lease deals. Enforcing those two fields is part of the configuration phase, because without it the comp is silently skipped.
Both, separately, because they need different things. Brokers need the shortest possible path through their own daily workflow. Operations need the exception handling. Administrators need to understand the data model well enough to change it safely. Each role gets its own session and a short written reference. What we need from you is protected broker time — enablement is the phase firms cut under schedule pressure, and it is the one that decides whether the rest mattered.
Hypercare is a defined window immediately after go-live with a named contact, fast turnaround on the issues that always surface once real deals hit the system, and adoption measured rather than assumed. It is included as standard. After it ends, most firms move to ongoing support — package upgrades, new desks and asset classes, reporting changes, the next round of automation — which is scoped separately. Some take it in-house, and we would rather hand over cleanly than keep you dependent.
Usually not, and we audit before assuming anything. In most stalled rollouts the data model is sound and the failure was elsewhere — stages that did not match how desks work, permissions that blocked people, comp-critical fields never enforced, or enablement that never happened. Those are fixable in place. A fresh org is occasionally the right answer, but it is the expensive answer, and it should follow evidence rather than instinct.
The main product page: what Rethink by Buildout is, who it is for, and how far it can be pushed.
SiblingWhen the package stops and custom development starts — and how to extend it without breaking upgrades.
SiblingThe manual work still happening after go-live, and the automation patterns that remove it.
SiblingWhat Agentforce can do with CRE data once the operating data underneath it is trustworthy.
Parent ServiceThe practice-level view across CRM, operations and reporting for a CRE business.
Next StepBring us an org, an export, or a rollout that stalled. We will tell you what we would do.
Whether you are implementing Rethink for the first time, migrating off a legacy CRE CRM, or restarting a rollout that stalled, the first step is the same: look at the data and the desks, then write the scope down.
Scope written down before anything is configured
