Selling into property management portfolios is never a single transaction. A “closed” deal might mean two pilot properties today, ten more next quarter, and a handful of one-off acquisitions the quarter after that, with each one needing to move through implementation, go live, and get reported on individually while still rolling up to one parent account. That kind of complexity needs a system built for it.
This client didn’t have one. Sales tracking lived in a HubSpot instance the team had quietly stopped using, while the real operational picture, every property, every unit count, every implementation status, was being held together in a personal monday.com account by a single operations lead, with no connection back to the deals that created it.
This is how OrangeDot rebuilt that system from the ground up.
What We’ll Cover
- About the client and how their sales-to-implementation process actually works
- Challenge 1: Two disconnected systems, with no link between a closed deal and the properties behind it
- Challenge 2: No structured way to handle canceled, blocked, or reassigned properties mid-implementation
- How OrangeDot built a connected CRM and implementation workflow
- The impact: one source of truth, real-time visibility, and a clean foundation to scale
About the Client
The client is a property-technology company that partners with property management groups nationwide, including large multifamily operators managing tens of thousands of units apiece, to roll its product out across their portfolios. New relationships typically start small, with a pilot on a handful of properties, and expand from there through regional rollouts, phased batches, or one-off acquisitions as a partner’s portfolio changes hands. Revenue is tied to a per-unit fee and, once a partner’s live units cross a contracted threshold, a revenue-share agreement on top of it.
That growth model depends on knowing exactly where every property stands: signed but not yet active, mid-implementation, live, or dropped out, at any given moment. The client’s systems weren’t built to answer that question.
Two Problems Compounding Each Other
OrangeDot was brought in to solve two related problems. The first was structural: sales and implementation were tracked in entirely separate systems with no automated link between them, so every closed deal required manual translation into implementation work. The second was operational: once a property was in motion, there was no defined path for what happened if it got blocked, changed hands, or canceled outright — and no real-time way for leadership to see where the business actually stood.
The client’s HubSpot instance held years of contact and company history (82,847 contacts and 16,337 companies at the time of migration), but the sales team had stopped actively using it. Real pipeline management had moved into a personal monday.com account, where the operations lead had hand-built a mirrored pair of boards, a sales pipeline and a property list, for every single property management partner individually.
Nothing connected the two halves automatically. When a deal closed, someone had to manually create a new line item on the implementation side for every property in that deal, then keep status columns in sync by hand across both boards. That manual syncing produced real errors: one review session surfaced a duplicated implementation item that had silently lost its connection to the parent account, and a separate audit found that a reporting dashboard was defaulting properties without a go-live date to 12/31/1969, quietly distorting the company’s average-days-to-go-live metric until someone caught it.
There was also no shared vocabulary for describing a deal. “New logo,” “expansion,” and “add-on” were used inconsistently, with no structured way to capture whether an expansion was a regional rollout, a phased batch, or an acquisition. That gap meant the business had no reliable way to measure its own land-and-expand performance.
When sales and implementation live in separate systems with no automated link, every closed deal becomes a manual translation exercise. Status has to be updated by hand in two places, which means it eventually won’t be, and by the time someone notices the gap, the reporting built on top of it is already wrong.
Once a property was in active implementation, there was no defined process for what should happen if things changed. A property might get stuck behind a product limitation, get reassigned to a new management company (disposition), or cancel outright, and each of those needed to route back to the sales team, since a canceled or dispositioned property is a new sales conversation, not a dead record. But the system had no mechanism for making that handoff, and no way to preserve the unit-count history once a property left the active implementation board.
Compounding the problem, leadership had no real-time view into any of it. Unit penetration across the client’s own partner portfolios, and how close any given account was to crossing its revenue-share threshold, lived in a spreadsheet the CEO was assembling and updating herself.
Implementation isn’t linear. Properties get blocked, reassigned, and canceled, and a system that only tracks the forward path loses visibility the moment something goes sideways. Without a defined route back to sales and a way to preserve history, every one of those scenarios either falls through the cracks or has to be reconstructed by hand.
The Solution
OrangeDot rebuilt the client’s CRM and implementation workflow as one connected system in monday.com, designed to be structured enough for accurate revenue-share reporting yet flexible enough to handle a property at any stage of its lifecycle.
A system built around how a deal actually moves
Rather than treating sales and implementation as separate tools, OrangeDot rebuilt the connection between them so a property’s status is never tracked in more than one place at a time. Each property management account was organized into its own dedicated boards, with a clear distinction between the deal pipeline and the properties it governs.
Full HubSpot history migrated
The client’s full HubSpot contact and company base, along with 5,576 historical emails, 924 meetings, and 348 notes, was migrated into a new monday.com CRM.
A required deal taxonomy
Every deal now needs a Deal Type (New Logo, Expansion, or Add-on) and a matching Scope Identifier (Region, Phase, Property, or Acquisition) before it can move forward, enforced by the workflow itself instead of left to habit.
Dedicated property boards for every account
Each property management account got its own property-list board, keeping every account’s full portfolio, unit counts, and status data organized without running into platform item limits as the client’s own client list grew.
Automatic handoff from closed deal to implementation queue
When a deal is marked closed-won, the system automatically creates one line item per associated property in an implementation queue. On one expansion deal alone, closing a single opportunity generated 15 individual property records automatically, work that used to be re-created by hand every time.
Status-triggered routing back to the sales pipeline
A workflow automatically moves any property marked blocked, dispositioned, or canceled into a dedicated group on the sales Opportunities board, notifying the team the moment a property drops out, while its unit-count history stays intact on the implementation side for reporting.
Connected mirror columns that sync both directions
Status changes in implementation, a property moving to “live,” for example, now update the originating deal and the account’s property list automatically, closing the loop that used to require manual double-entry.
A revenue-share tracker with automatic threshold alerts
A report multiplies an account’s live units by its contracted rate, and an automation flags the team the moment an account’s live units cross its contracted threshold (10,000 units for the client’s largest accounts).
Connected email so activity logs itself
Gmail was connected directly to the CRM so contact and account email activity logs automatically, with a browser extension that lets the team add new contacts straight from their inbox.
Executive dashboards built for how leadership thinks about the business
Native monday.com dashboards and monday.com’s AI-assisted “Vibe” reporting now surface units signed, units pending go-live, units live, percentage of portfolio activated, and average days to go live, with gauge and bar-chart views the CEO can filter by month or quarter against a company-wide unit goal, without anyone manually compiling the numbers behind it.
The Impact
What was once two disconnected systems held together by one person’s manual updates is now a single, self-updating pipeline from first deal to live property.
One Source of Truth Between Sales and Implementation
A closed-won deal now generates its own implementation line items automatically, replacing the manual, property-by-property re-entry that used to happen every time a deal closed. Sales and implementation are finally working from the same data instead of two systems that had to be reconciled by hand.
Leadership Has Real-Time Visibility for the First Time
The CEO now has a live view of unit penetration and revenue-share exposure across every partner account, replacing a spreadsheet she had been piecing together herself.
Canceled, Blocked, and Dispositioned Properties No Longer Fall Through the Cracks
Properties that drop out of implementation now route back to sales automatically, with their unit-count history preserved for reporting, closing a gap where those scenarios previously had no defined process at all.
A Deal Taxonomy the Team Can Actually Report On
With Deal Type and Scope Identifier now required fields, the business can measure land-and-expand performance in a structured way for the first time, instead of relying on inconsistent, free-text descriptions of past deals.
82,847 contacts and 16,337 companies migrated · 5,576 emails, 924 meetings, and 348 notes preserved · 15 properties created automatically from a single closed deal · revenue-share exposure tracked automatically against a 10,000-unit threshold
FAQs
How do you migrate a CRM without losing historical context, especially when the client wants to leave old deals behind?
We separate the two decisions. Contacts, companies, and their historical email activity are almost always worth preserving in full, since they represent real relationship history that has nothing to do with how clean the deal data behind them is. Deals are a different story — if the historical deal data is inconsistent or was never really used, migrating it forward just carries the mess into the new system. In this engagement, we brought over the full contact and company base (82,847 contacts and 16,337 companies) while letting the team start its live deal pipeline clean.
How does the automatic handoff from a closed deal to individual property line items work without creating duplicate data entry?
The property information lives in one place, a dedicated property list per account, and the deal simply references it. When a deal closes, a workflow reads which properties were associated with that deal and creates one implementation line item per property automatically, pulling the account name, unit count, and a unique deal ID along with it. On one expansion deal, that meant 15 property records were created in seconds instead of by hand.
How do you handle a property that gets canceled or changes hands in the middle of implementation without losing reporting accuracy?
We build a status-triggered workflow rather than relying on someone remembering to update multiple boards. The moment a property’s status changes to blocked, dispositioned, or canceled, it’s automatically routed into a dedicated group back on the sales side, while its unit-count history stays exactly where it was for implementation reporting.
Can a system like this scale as the client adds new property management partners?
Yes. That’s the point of giving each account its own dedicated property board rather than combining everyone into one. As new partners sign on, they get their own board following the same structure, so the system scales by addition rather than by restructuring.
Final Thoughts
A growing PropTech company can’t run its pipeline on a spreadsheet-adjacent workaround forever, not when every closed deal represents dozens of individual properties that each need to move through implementation, get tracked, and eventually go live. The problem here wasn’t a lack of effort; one person had built a genuinely thoughtful system by hand. The problem was that it depended entirely on that one person maintaining it manually, with no automated link back to the sales data that should have been driving it.
What OrangeDot built closes that gap: a CRM that hands off closed deals into implementation automatically, a defined path for properties that get blocked or canceled along the way, and real-time reporting that gives leadership the visibility they’d previously had to assemble by hand.
If your team is managing a growing portfolio of accounts and properties through disconnected systems or manual workarounds, we can help you build something that scales with you. Talk to an OrangeDot expert →