Client Case Study: Commonwealth Payroll & HR

Situation Overview

For a payroll service bureau, the CRM is not just a sales tool — it is the operational backbone of the entire client relationship. It is where leads become clients, where clients are onboarded, where funding issues get escalated, where NSFs are tracked and routed, and where the health of every relationship is monitored in real time. When that system stops working for you, the cost shows up everywhere: in missed signals, in manual workarounds, in time your team spends fighting their own tools instead of serving clients.

That is where Commonwealth Payroll & HR found themselves. For years, the team had invested significantly in building out a sophisticated service operation inside Salesforce — including a production management system, a multi-department case workflow infrastructure, and a custom data integration with iSolved, the HCM platform at the core of their business. The integration pulled client and payroll data directly from iSolved into Salesforce via a tool called Vue, keeping company records accurate and informing a wide range of service workflows.

But Salesforce was increasingly working against them. Licensing costs were unpredictable and difficult to control. Adding seats or functionality often triggered unexpected expenses. And every time the team had a new idea — a better way to track referrals, a smarter way to identify upsell opportunities, a more automated approach to client health scoring — the answer from Salesforce was always the same: more custom development, more cost, more complexity. The platform that was supposed to support their growth had become a ceiling on it.

When the decision was made to migrate marketing and sales to HubSpot, it initially felt like a partial solution. Service operations were going to a separate platform entirely. But after evaluating the options — and after a timely conversation through HubSpot's own team — it became clear that the smarter path was to bring everything under one roof. Commonwealth reached out to The Gist.

The Gist works almost exclusively with payroll service bureaus and brings deep familiarity with the iSolved ecosystem, the operational realities of service bureau life, and the specific ways HubSpot can be configured to support that world. For Commonwealth, that combination was exactly what the moment called for.

Process

The engagement began as a consulting relationship — strategic guidance, weekly sessions, access to The Gist's proprietary demo portal, and a library of payroll-specific workbooks and playbooks developed over years of implementations. But it quickly became clear that the work ahead demanded something deeper.

Assessing the Existing Architecture

Before a single HubSpot workflow was built, the team spent considerable time understanding what Commonwealth had built in Salesforce. This was not a simple migration. Commonwealth had spent years architecting more than twenty distinct case types, each with its own workflow, routing logic, stakeholder assignments, and completion criteria. They had built a production management Kanban system to track every payroll running through the office. They had a referral tracking system for outbound introductions. They had incident tracking that served as a permanent record of every "bump in the road" for each client.

The goal was not to move all of that directly into HubSpot. It was to understand what they had built, identify what was worth preserving, what should be optimized, and what should be redesigned around HubSpot's native strengths. This required sitting with the team, understanding their operations at a detailed level, and thinking through how iSolved data, ticket logic, and automation could all work together in a new environment.

Designing the Ticket and Pipeline Architecture

The centerpiece of the service build was a comprehensive ticketing system designed to replace Salesforce's case infrastructure. Rather than attempting to replicate every object from Salesforce directly, the team worked to translate Commonwealth's operations into HubSpot's native architecture in a way that would be cleaner, easier to maintain, and more user-friendly for the people using it every day.

The result was a suite of purpose-built pipelines covering ACH over-limit escalations, NSF handling, tax issues and tax projects, client terminations, employee ACH returns, notification-of-change events, service bureau check problems, and internal project requests. Each pipeline was carefully mapped with defined statuses, required properties at each stage, conditional routing logic, and automated notifications calibrated to the urgency of the ticket type.

A significant amount of thought went into getting the automation right for financially sensitive processes. For ACH over-limit tickets, for example, the system automatically parses inbound email notifications, creates the ticket, populates key data from the company record, routes the ticket based on the dollar threshold of the overage, and escalates through a timed sequence of notifications to ensure that nothing goes unresolved by the end of a processing day. For NSF tickets, integration with the bureau's ACH management platform allowed automated ticket creation at specific times each morning, with notification logic that escalated to the executive team if funding had not been confirmed by mid-afternoon.

Solving the iSolved Data Integration

One of the most technically demanding elements of the engagement was getting iSolved data flowing directly into HubSpot — bypassing the Salesforce sync that had been serving as a temporary bridge.

Commonwealth had been pulling client and payroll data from iSolved using a tool called Vue, which generated flat CSV files that were then processed through Salesforce's Data Loader and mapped into Salesforce fields. When that data was eventually needed in HubSpot, it was traveling a complicated path: iSolved to Vue to Salesforce to HubSpot. The objective was to get it flowing directly.

This work required a detailed analysis of the iSolved data schema, a review of which fields were being used and why, and a thoughtful decision about which data elements were still worth bringing into HubSpot versus which ones iSolved's own reporting tools now handled adequately. The team also navigated the transition from Vue to iSolved's newer Data Lake, working through the beta access period, identifying which data elements were available and which were still being built out, and developing a strategy that would work in the near term while being designed to scale as the Data Lake matured.

Custom objects, including one for Legal Services, were built to take advantage of Commonwealth's HubSpot Enterprise tier and to enable the kind of client segmentation and upsell tracking that had been a long-standing goal. A staging data issue — where iSolved was inadvertently pushing test and staging records through the Data Lake alongside production records — was identified, escalated to iSolved, and resolved before it could cause lasting damage to the company record database.

Training Across the Organization

With the build largely complete, the final phase of the engagement involved rolling out the system to the people who would actually use it. Training sessions were conducted department by department — customer service, production finance, and tax — walking each team through their specific pipelines, the logic behind each stage, the notification patterns they should expect, and the workflows that had been built to support their daily work.

These sessions were not passive walkthroughs. They were working conversations. Team members asked hard questions, surfaced edge cases that had not been anticipated, and provided feedback that led to real adjustments in the build — routing changes, notification timing tweaks, naming convention updates, and a handful of new fields that improved the visibility each team needed in their day-to-day work. That feedback loop was built into the process by design.

Wins and Breakthroughs

Building what no one else had tried. One of the most consistent themes across the engagement was the degree to which Commonwealth had already pushed further than most payroll bureaus in terms of how they use a CRM. They had not just tracked clients — they had built operational infrastructure around their payroll workflows, their ACH risk management, their employee return processes, and their client health monitoring. At one point, a member of the team reflected on what this project represented:

"We spent a tremendous amount of money and years developing this for Salesforce — and Salesforce is constantly evolving, which means the money we spent then is money we're spending again. With HubSpot, I feel like we finally have something we can build on."

A moment of recognition during the kickoff. At the official engagement kickoff, when the scope of Commonwealth's operations came into full view — the data complexity, the workflow depth, the ambition of what they wanted to build — one team member on the client side offered a reflection that captured the spirit of the whole project: "I have a lot more to say about all of that. I spent a lot of time architecting all of this stuff up. Years and years." The response from the project lead was simply: "Good answer." What followed was a multi-month collaboration built on mutual respect for the complexity of the work.

The tax pipeline that earned a standing ovation. During one of the team training sessions, The Gist walked through the tax pipeline that had been built specifically to support the tax team's daily work — capturing the exact statuses they had asked for, the conditional field logic by case type, the follow-up date reminders, and the survey-based client notification process. When the demo was complete, one of the senior members of the tax team responded:

"I just gave you a round of applause. That was a round of applause for that. You're making my day."

Replacing Salesforce's operational complexity with something that actually works. A phrase that surfaced more than once across the engagement was the relief of leaving behind Salesforce's development-heavy model. At one point, a senior leader on the client side put it plainly:

"One of the big reasons we jumped to HubSpot was to keep it simple — to be able to do things without having to stare down the barrel of ten thousand dollars in development every time we had a good idea. We know Hubspot is not simple. But it's ten times simpler than Salesforce. I can tell you that."

Outcomes and Looking Ahead

Commonwealth Payroll & HR is now operating in HubSpot across marketing, sales, and service — a single, unified CRM environment that replaces a fragmented and increasingly expensive multi-platform arrangement.

The ticket infrastructure that once lived inside Salesforce has been rebuilt in HubSpot with meaningful improvements: cleaner routing logic, tighter automation, and a user experience that their customer service, production finance, and tax teams can navigate without fighting the system. The ACH escalation process, the NSF handling workflow, the tax case pipeline, and the client termination process are all running natively inside HubSpot, connected to the company records that the iSolved data integration keeps current.

The iSolved Data Lake integration — one of the most technically ambitious elements of the project — is active and maturing. As iSolved continues to expand the data elements available through the Data Lake, the integration will deepen, unlocking additional use cases that Commonwealth has had on their roadmap for years: MRR and ARR visibility at the client level, more granular service tracking tied to billing detail, and enhanced client health scoring that draws on a richer data picture.

The immediate next horizon for Commonwealth is continued refinement of the workflows and processes they have built — not because anything is broken, but because they now have a platform that makes continuous improvement possible without requiring a full development engagement every time. Their internal project and additional business pipeline is designed to make it easy for the team to capture new opportunities, route them appropriately, and track them through to completion. Their referral tracking and relationship management capabilities are ready to be fully activated. And as they become more fluent in HubSpot's native toolset, they are already identifying new use cases that would have been cost-prohibitive in their previous environment.

The team at Commonwealth set out to replace a CRM. What they ended up building was an operational platform — one that reflects how a well-run payroll service bureau actually works, speaks the same language as their clients, and gives them the infrastructure to keep improving how they serve them.