Ritz Banc Group: Spreadsheets vs SSOTs

About the client

Ritz Banc Group (RBG) is a private equity and alternative asset management firm headquartered in Washington, D.C., with a global investor base spanning North America, the Middle East, LATAM, and Asia. Founded in 2012, the firm has managed a real estate portfolio exceeding $850 million by identifying US income-producing real estate opportunities, raising debt and equity, and managing assets through to exit on behalf of high net worth individuals, family offices, and institutional investors.

The team managing investor relations and deal origination at the time of this engagement numbered approximately five to seven people, operating across time zones between Dubai, Mexico, Panama, and Arlington, Virginia.

The Challenge

RBG's leadership faced a strategic problem as much as an operational one. The firm runs multiple active capital raises simultaneously, each with narrow acquisition windows and real commitment deadlines. At any given moment, the Managing Director and senior team needed to know which investors were in which deal, how much equity had been committed, how much remained to close, and where each investor conversation stood.

That information lived with individual people, spread across Excel spreadsheets and the firm's asset management platform (AMP). The AMP handled post-investment management: asset tracking, investor positions, distributions, and reporting once a deal closed. Everything before close, from deal origination to investor qualification and communication management, existed in spreadsheets.

The team had no system of record for investor engagement or commitment status, no way to assess the probability of closing any given raise, and no analytical view of investor history across the business: who had been approached before, in which deals, with what outcome, and how that history might inform a new opportunity. That knowledge resided with individuals rather than in any shared system.

Diagnostic and process mapping

Before any configuration work began, Xcelerate ran a Making Toast process mapping session with the RBG team: a structured exercise conducted via Miro, covering the full investor lifecycle from initial outreach to deal close.

The session surfaced something common in firms that have grown without documented processes. One team member mapped the process as they understood it; the Managing Director described it differently; the firm's Acquisition Analyst had a third version. Working through those differences to establish a single agreed process was one of the most valuable outcomes of the session. The HubSpot configuration that followed was built against what actually happened, rather than what anyone assumed happened.

The session also produced a critical architectural decision: the boundary between HubSpot and the AMP. HubSpot would own the full pre-close journey. The moment a deal closed, it moved into the AMP for asset management and investor reporting. That boundary, agreed and documented before any configuration began, shaped every decision that followed.

The platform scope also changed during this phase. The original engagement was scoped for HubSpot Sales Hub Professional. As the process mapping clarified the data model requirements, it became clear that the firm needed to track investment properties as standalone entities with their own data structure, distinct from any individual investor transaction. This required a custom object, available in HubSpot Sales Hub Enterprise. The platform was upgraded accordingly.

Implementation

The implementation was delivered across five workstreams, sequenced so that data structure decisions preceded configuration, and configuration preceded training.

1. Custom data model

Standard HubSpot objects (Contacts, Companies, and Deals) were configured for their specific roles in RBG's business. Contacts represented individual investors; Companies represented institutional investors and family office entities; Deals represented individual investor transactions, meaning a specific investor's commitment to a specific capital raise.

The critical addition was a fourth, custom object: the investment property itself, referred to internally as the New Deal. This object captured everything relevant to an acquisition opportunity, including asset type, location, deal size, equity requirements, investment structure, return profile, and timeline. Individual investor Deals were associated to the relevant New Deal object, giving the team a two-dimensional view: which investors were participating in a given property, and which properties a given investor had been approached on or committed to.

A suite of custom properties captured investor-level criteria: investment strategy, asset type preferences, minimum IRR, minimum yield, equity per deal, deal size range, deployment quarter, GP co-invest preference, debt type (including Shariah and conventional structures), investor priority, and relationship status. These properties enabled the team to match investors to opportunities systematically, rather than relying on individual memory or manual spreadsheet cross-referencing.

2. Historical data migration

RBG had years of investor relationships, closed deals, and committed positions recorded in the AMP. A blank CRM with no historical context would have prevented the investor base analysis the team required from day one. The decision was made to migrate all relevant historical data.

This involved thousands of records across multiple entity types: individual investor contacts, family office companies with multiple associated individuals, historical deal positions, and investment values. The AMP and HubSpot have fundamentally different data structures, requiring explicit field mapping before any import. The source data required significant cleaning: duplicates were common, the same entity had been recorded in multiple ways, contacts were associated to incorrect records, and many historical deals lacked deal owner assignments. All data was handled with the care appropriate to sensitive financial information.

The output was a fully populated CRM: every relevant investor contact, every family office entity, and every historical deal correctly associated to the corresponding investor records and property objects.

4. Pipeline configuration and automation

The investor pipeline was configured to mirror the process agreed during the process mapping session, with deal stages tracking progression from initial investor approach through qualification, investment proposal, active engagement, and committed close. Automations were configured to handle notifications, task assignments, and follow-up triggers, reducing the manual coordination load on the team. Email and calendar integration was set up for each user, enabling all investor communications to be logged directly within HubSpot contact and deal records.

5. Reporting and dashboard

A sales dashboard was configured covering the firm's core reporting requirements: open deals by stage, committed equity versus target by property, investor activity by team member, and overall pipeline health. This gave the Managing Director and the senior team a single-screen view of where each capital raise stood, replacing the individual status conversations that had previously been the only way to obtain that information.

6. User configuration and training

Two 90-minute training sessions were delivered covering HubSpot CRM basics, Sales Hub features, email integration, contact and deal management, and the RBG-specific workflows built during the implementation. Custom training documentation was produced using RBG's own terminology and data structures, rather than generic HubSpot guidance. Training was delivered across US and Dubai time zones.

Outcomes

The Managing Director and senior leadership team can open HubSpot and see the status of every active capital raise: which investors have committed, how much equity has been pledged, how much remains, and where each investor conversation sits in the pipeline. For a firm managing time-sensitive acquisition windows across multiple simultaneous raises, this changed how leadership planned and how confidently they could assess the probability of closing any given deal.

The investor relations team has a complete view of every investor in the business, with historical deal involvement, total capital committed, investment criteria, and communication history consolidated in one place. Approaching investors for a new deal begins with a clear picture of prior involvement and current preferences, rather than individual recollection or multiple disconnected sources.

Leadership can see what the investor relations team is doing, who they are engaging, and how conversations are progressing across every open deal simultaneously. The individual status conversations that previously consumed management time have been replaced by a single system of record.

Xcelerate's access to RBG's HubSpot portal was deactivated in January 2025, following the completion of training and handover. The team has been running the system independently since. When the subscription came up for renewal in July 2025, RBG renewed with limited involvement from Xcelerate. By that point, the platform had expanded to five active enterprise users and two view-only users.

"He helped us implement our CRM system very smoothly and efficiently."

What this engagement revealed

Capital-raising businesses require a different data model.

Standard CRM data models are built around a buyer-seller relationship: a contact, a company, and a deal. That model does not fit capital-raising. In this business, the asset is the primary sales object, and a single asset has multiple investors approaching it simultaneously, each at a different stage, with different criteria and different committed amounts. Until the asset exists as a first-class object in the system, tracking the investor relationships that matter against it remains impossible. Firms that attempt to retrofit a standard pipeline CRM onto this model typically end up with a system the team tolerates rather than uses.

Process mapping surfaces variance that prevents adoption.

Every member of the RBG team had a different version of the investor lifecycle. If those differences had remained unresolved before configuration began, the system would have been built against one person's mental model. The process mapping session was the starting point of the implementation, rather than a preliminary step before it.

Explicit system boundaries determine whether the architecture holds.

HubSpot and the AMP coexist effectively only when the boundary between them is defined before either is configured: what lives where, what gets transferred when, and what remains within each system. These decisions determine whether the overall architecture resolves the problem or creates a more expensive version of it.

Sequence is the logic of the entire engagement.

Process mapping had to precede configuration because the data model depended on understanding the actual process. The system boundary had to be agreed before data migration because the migration required knowing what needed to live where. The data model had to be correct before training could be meaningful. Each step depended on the one before it, and compressing any part of that sequence would have undermined everything that followed.

Implications for similar organisations

Real estate private equity firms and capital-raising businesses with investor relations functions are often poorly served by standard CRM implementations because their data model is structurally different from the buyer-seller dynamic most CRMs are designed for. The investment property needs to exist as a record in the system before investor activity can be tracked against it meaningfully. Firms that skip this architectural step typically rebuild within 12 months.

Firms at this stage of growth almost always have years of investor history distributed across asset management platforms and spreadsheets. A blank CRM carries no context, and a team cannot use it for the analysis that justified the investment. The right approach is to bring historical data across, clean it properly, and structure it correctly before the team begins working in the system.

A well-structured CRM is the prerequisite, rather than the destination. Within 12 months of go-live, RBG's leadership had initiated conversations about layering AI-driven analysis on top of their operational and investor data, exploring automated reporting, investor behaviour analysis, and forecasting capabilities. That conversation became possible because the data is now clean, structured, and in one place. Firms that defer the foundational work defer that possibility along with it.