Client Case Study: Unify Payroll
Learn how a payroll service bureau went from zero CRM infrastructure to a fully operational HubSpot system — with integrated pipelines for sales, implementation, tax notices, and client service.
Situation Overview
For payroll companies, the technology migration never really ends with the platform. You migrate off your old system, you clean up the mess, and then — if you are honest with yourself — you look around and realize the rest of your operations still look exactly the way they did before. Client records scattered across software tools. Tax notices living in a shared inbox nobody fully controls. Sales happening in a spreadsheet. A team that communicates across channels, but communicates without context.
That is where Unify Payroll found itself when they reached out to The Gist. Having recently completed a significant migration to iSolved — their first major platform move in years — the partners were ready to take their next step. They had done the hard part of getting onto a modern HRP platform. Now they needed to build the infrastructure around it.
There was no CRM in place. A previous attempt with another platform had been abandoned after data fell chronically out of sync and maintenance became too burdensome to justify. In its place, the team had patched together a set of tools — a Gmail-based inbox management add-on for ticket routing, a spreadsheet-driven process for tracking new business and implementations, and payroll software that, for all its strengths, was never designed to serve as a system of record for client relationships.
The partners knew what they needed. They wanted HubSpot. They just did not want to figure it out alone. As one partner put it during our first conversation: they needed someone who had already done this for other payroll companies and could help them think through the things they had not even thought of yet. That is exactly what brought them to The Gist.
Process
The Gist approached this engagement the way it approaches every payroll bureau implementation: with the philosophy that a CRM should be an instrument for growth, not just a repository for data. That distinction matters more than most people realize when scoping a project like this one. It is the difference between building a database and building a business tool.
Discovery and Scoping
Before any configuration work began, The Gist conducted a structured discovery process across multiple calls, involving all key stakeholders from the Unify team — from the sales-focused partners to the payroll tax department to the implementation specialists. The conversations were detailed and specific. What does a tax notice look like from the moment it arrives to the moment it is resolved? Where does a new deal go after the sales partner closes it? Who is responsible for the client after go-live, and how does that handoff actually happen today?
What emerged from that process was a clear picture of a business operating across multiple silos — payroll, accounting, tax, treasury — that all touched the same client relationships but had no shared visibility into them. The decision was made to build a unified foundation that housed clients from all divisions of the business in a single HubSpot portal, while concentrating operational workflow improvements on the payroll side first.
Foundation and Data Architecture
The first phase of the project centered on getting the data right. This meant defining the full set of custom properties that would live on contact and company records — client status, pay frequency, employee count, start date, assigned CSR — along with the logic for how records should be segmented and surfaced to different users depending on their role. A client that is active in payroll but not in accounting should look different from one that uses both services. A prospect record should show different information than an active client. Getting those views right is foundational to adoption, and adoption is what determines whether a CRM succeeds or fails.
As part of this phase, The Gist also configured an integration between iSolved and HubSpot, allowing client data from the payroll platform to sync automatically and keep HubSpot current without requiring duplicate entry from the payroll team. iSolved was established as the authoritative source of record for payroll data, while HubSpot became the master record for client relationships, communication history, and operational activity across the whole business.
Sales Pipeline and Marketing Infrastructure
The sales process got a complete rebuild. The team had been managing deals in a spreadsheet and a separate project management tool that was not integrated with anything else. HubSpot replaced both with a structured deal pipeline that captures the information that matters — employee count, pay frequency, current provider, target run date — at each stage, and that triggers an automatic handoff to the implementation team the moment a deal is signed. Sales outreach tools, meeting booking links, and email templates were configured so that whoever handles business development can move quickly and consistently without reinventing the process each time.
The marketing infrastructure was also established as part of this phase, including email sending configuration, list management, and lifecycle stage automation. This gave the team the building blocks needed for client communications — holiday payroll schedule reminders, ACA season notices, year-end preparation checklists — without requiring manual list exports or third-party tools.
Implementation and Service Operations
The handoff from sales to implementation was one of the most critical workflows built in this engagement. When a deal moves to closed-won, HubSpot automatically generates an implementation ticket with all the relevant client details populated, notifies the implementation team, and initiates the process of moving that client toward their first payroll run. The stages of the implementation pipeline were designed to give leadership visibility into where every new client sits in the process, with escalation triggers that flag any ticket that has gone too long without activity.
On the service side, the tax notice problem — one of the most consistently cited pain points across the team — was resolved through a dedicated ticket pipeline connected to the team's shared tax inbox. Every notice that arrives now generates a ticket, is assigned to the appropriate team member, and is tracked through resolution. The previous scenario, in which the same notice could be worked twice by two different sides of the business without either knowing the other had touched it, is no longer possible. All client communication is now logged against the client record, giving every team member context before they respond.
A general support pipeline handles everything outside of tax notices and implementation: routine client inquiries, add-on requests, payroll schedule exceptions, and anything else that comes into the shared service inbox. Tickets can be escalated, split, and reassigned, with automated notifications keeping clients informed at every step — a meaningful improvement over the previous experience, in which client issues would go into the proverbial black box and come out resolved at some unknown future point without any communication in between.
Wins and Breakthroughs
The Moment the Vision Clicked
Early in the engagement, one of the partners described the vision they had for what HubSpot could do for their sales process. They had seen firsthand — through work with another business — that a prospect who books a meeting converts at roughly double the rate of one who fills out a contact form. The goal was to build a system that filtered out unqualified inquiries, routed serious prospects directly to a booking experience, and removed the inefficiency of sorting through low-quality leads to find the valuable ones. When The Gist walked through exactly how that could be built — using HubSpot's native scheduling tools, form qualification logic, and automated lead routing — the connection between the technology and the outcome they had in mind became immediately tangible. "You pretty much have someone on the line," one partner said. That is the moment a CRM project shifts from an IT initiative to a growth strategy.
Solving the Tax Notice Black Hole
If there was one operational problem that every member of the Unify team mentioned unprompted, it was tax notices. The existing process was a known liability. Notices would arrive by mail and by email. The payroll tax team might work one while a version of the same notice was still sitting unopened on the accounting side. Resolution timelines stretched into weeks, and there was no reliable way to know at any moment which notices were open, who owned them, or whether the IRS had responded. One partner described wanting to build workflows that accounted for known IRS response windows — so that a follow-up was automatically triggered if two weeks passed with no resolution. That exact capability was built into the tax notice pipeline. The reaction when the team saw it in action was immediate. "I selfishly hope to get out of this that when we get tax notices we can actually track them, find them, make sure they got corrected instead of dying in the nether realm," said one team member. That is exactly the outcome that was delivered.
An Implementation Specialist Who Arrived Ready
One of the more energizing moments of this engagement came during the project kickoff, when the client's implementation specialist introduced himself and shared his perspective on what they were building together. With experience using multiple CRM platforms across his career — and with a stated belief since joining the company that a real CRM could make a meaningful difference — he was, as he put it himself, "a sucker for a good CRM." His enthusiasm and hands-on perspective during the strategy sessions helped shape a more practical and immediately usable implementation pipeline. His involvement is a good indicator of how this system will be adopted and maintained going forward — because the person who will use it every day was part of building it.
A Partner Who Knew What "Good" Looked Like
Throughout the engagement, one of the partners demonstrated a level of operational clarity that made the strategy sessions move quickly and purposefully. He came in with a strong point of view about what the business needed, a healthy skepticism about over-engineering the first phase, and a clear sense of priority. "I think that's how we work best — taking smaller chunks of it, especially because you're deploying it to thirty people." That instinct — to build something people will actually use rather than something impressively complex — is exactly right, and it made this project stronger. When a client knows what they want and can articulate it clearly, the outcome reflects that.
Outcomes and Looking Ahead
Unify Payroll entered this engagement without a CRM and completed it with a fully operational HubSpot environment built specifically for the way a payroll service bureau operates. Client records from across the business — payroll, accounting, and related services — are now housed in a single portal. The implementation and tax notice pipelines are live. Sales activity is tracked. Inboxes are connected. The team has been trained.
The business is no longer managing its client relationships through a patchwork of shared inboxes, spreadsheets, and payroll software workarounds. That infrastructure has been replaced by a system that logs every email, call, and client interaction automatically — and that surfaces the right information to the right person without requiring anyone to dig for it.
The iSolved integration ensures that HubSpot stays current as client data changes inside the payroll platform. Employee counts, client statuses, and core account details now flow automatically, which means the team's attention can stay on clients rather than on data maintenance.
What lies ahead is, in many ways, the most exciting part. The foundation that was built is designed to grow. The team can now begin exploring the optimizations that were intentionally deferred in phase one: more sophisticated lead scoring, referral partner tracking, year-end workflow automation, client satisfaction surveys, and the kind of upsell and cross-sell visibility that comes from having all service lines represented in a single record. These are not gaps — they are natural next steps that the business is now positioned to pursue at its own pace, with a system that is already doing the foundational work.
For a payroll company that runs this close to the business of its clients — handling tax compliance, filings, notices, and the kind of relationship work that never really ends — having a CRM that works the way the business works is not a luxury. It is the infrastructure that makes everything else possible.