Client Case Study: Candoor HCM

Situation Overview

For a payroll service bureau, the CRM is not a luxury — it is the operational spine of the business. Every client relationship, every payroll run, every support ticket, every tax notice, and every upsell conversation flows through it. When that system doesn't work the way the team actually works, things fall through the cracks. And in payroll, that is not an option.

Candoor Payroll & HCM had been operating out of Zoho for several years. The platform had served its purpose at first, but over time it became clear that the team was working around the CRM rather than through it. The support ticketing experience — built on Zoho Desk — was frustrating, particularly around searchability. Finding a specific client's ticket history, cross-referencing payroll runs, or quickly surfacing a prior email chain required too many steps and too much manual effort. The team had built a series of workarounds, including a custom-built "payroll runs" module that tracked each processing event per client, as well as ACH exception tracking and change logs managed through repurposed Zoho modules. These were clever, but they were patchwork.

Equally important was the question of growth. Candoor had reached a point where they wanted to do more with their CRM than store contacts and log notes. There was a real appetite for client segmentation, automated communications, marketing outreach, and upsell identification. The honest reality was that Zoho, as they were using it, was not the platform that would get them there — and they did not have the internal bandwidth to become Zoho specialists.

They had also been following conversations within their industry peer network and had heard strong, consistent praise for The Gist from another payroll bureau in the same industry group. That, combined with a timely question posted in an industry forum about CRM options and HubSpot integrations with iSolved, brought them to the table.

What they were looking for was not just a CRM migration. They wanted a partner who already knew their industry — someone who understood payroll processing workflows, client service models, iSolved, and the specific operational realities of running a payroll bureau. They found that in The Gist.

Process

Starting with Strategy, Not Software

Before a single workflow was built or a single property was created in HubSpot, The Gist invested several weeks in strategy sessions. These were not onboarding calls or check-ins — they were working sessions, often ninety minutes long, focused on understanding exactly how Candoor's team worked day to day. The team walked through their Zoho environment screen by screen, sharing their payroll run import process, their ACH exception tracking, their tax support pipeline, and their client-level notes structure.

That discovery process became the foundation for everything that was built. One of the first and most valuable outputs was a detailed blueprint mapping out every ticket pipeline, every stage, every property, and every automation that would eventually live in HubSpot. Nothing was built until it was mapped.

The Core CRM Build

The core CRM buildout was the most labor-intensive phase of the engagement. Candoor operates out of iSolved, and a significant amount of the planning work focused on how to get the right client data into HubSpot, keep it accurate, and make sure it was visible where the team needed to see it.

Custom company and contact properties were created to receive synced data from iSolved, including client status, pay group, active employee count, input method, payroll processor assignment, and more. Record views were customized so that anyone who clicked into a company record could immediately see the information most relevant to them — a client profile that gave a 30-second overview of everything the team needed to know.

Contact associations were structured thoughtfully. Payroll contacts, CPAs, third-party partners, and referral sources were all given distinct association labels so that at any point, anyone on the team could pull up a client and immediately understand who their payroll contact was, who their accountant was, and who referred them.

Lifecycle stages were configured and automated, so that when a client's iSolved status changed, HubSpot would update accordingly — keeping the CRM self-regulating and reducing the burden of manual data maintenance.

Building the Service Infrastructure

The ticket pipeline architecture was one of the most distinctive and involved elements of the build. Because Candoor's operational model relies heavily on processing payroll runs as individual trackable events per client, the team worked through a highly specific solution to replicate and improve that functionality inside HubSpot.

A dedicated payroll run ticket pipeline was built with stages that mirrored the team's actual workflow: scheduled, submitted, awaiting client response, processed, skipped, and voided. The import process was refined so that each week's payroll schedule — exported from iSolved — could be imported as tickets and automatically associated with the correct company records. Properties were built to capture the specific data the team relied on during processing: check count, voucher count, total payroll cost, third-party payment amounts, run number, and a checkbox indicating whether the client had previewed their payroll before submission.

Beyond payroll runs, the team built out a full suite of support pipelines: ACH exceptions, tax notices, change orders, and client implementation. Each pipeline was designed with its own stage-specific properties, automation rules, and routing logic. For ACH exceptions in particular, a dedicated inbox was configured so that notifications from the payment vendor would automatically create tickets, routed to the right team members based on exception type, with task lists that varied depending on whether the exception was an NSF, a notice of change, or a credit return.

The implementation pipeline was built to create a clean, accountable handoff from the sales side of the business. When a deal reached the signed stage, an implementation ticket was automatically generated with all of the relevant client information, the appropriate internal notifications were triggered, and the process of onboarding the new client was tracked through to their first payroll run.

Client change orders were also given their own pipeline — a lightweight but purposeful system for tracking anytime a client-directed change was made, such as adding a deduction code, modifying a 401(k) contribution setup, or updating an earning type. The intent was simple: create a documented, searchable record of what was changed, when, and why.

The Sales and Marketing Layer

With the service infrastructure in place, The Gist turned its attention to building out the tools Candoor needed on the sales and marketing side. A sales pipeline was configured with defined stages and required properties at each step, keeping deal data clean and consistent. Referral partner tracking was built in from the beginning, with association labels, leaderboard potential, and closed-deal attribution.

On the marketing side, the work began with foundational infrastructure: HubSpot forms embedded on the Candoor website, workflows to route inbound inquiries, internal notification automations, and a base set of email templates for client communication. The team also built out a systematic approach to client feedback, using NPS-style surveys and ticket-close satisfaction prompts, with automated follow-up logic to flag detractors for immediate attention and promoters for referral outreach.

Holiday email reminders for federal banking holidays became a recurring deliverable — fully planned, templated, and scheduled within HubSpot so that client notifications about upcoming processing schedule changes go out consistently throughout the year.

Wins and Breakthroughs

A New Standard for Client Visibility

One of the most meaningful moments in the engagement came during an early strategy session, when a member of the Candoor team articulated a simple but ambitious goal: the team should only ever need two tabs open — iSolved and HubSpot. Everything about a client — their payroll history, their correspondence, their services, their contacts, their changes — should live in one place. That vision became the north star for the entire build, and it shaped every decision made along the way.

"The goal is all of our processing, all of our work, is done in iSolved. Anything we need to know about a client, any communication, any notes, any whatever, lives in HubSpot. At a quick glance, we can look at the client profile in the CRM and anybody here can know 95 percent of what they need to know."

That goal was achieved. The client profile built inside HubSpot became exactly what was envisioned — a centralized, intelligently organized view of each client that any team member could interpret in under a minute.

Solving the Payroll Run Problem

The payroll run tracking workflow was one of the most technically involved problems solved during this engagement. No other CRM in the payroll industry has a native solution for this. It required thoughtful mapping, import configuration, workflow logic, and a round of testing before it performed reliably. The result was a ticket-based system that tracks every payroll run per client, associates it to the right company record, and houses all of the relevant processing notes, attachments, and status history in one place — accessible from within the client's company record at any time.

When the team saw how reporting could be layered on top of the payroll run data — average payroll cost per client, checks and vouchers over time, overdue run flags — their reaction captured the spirit of the whole engagement well:

"Being able to do this is freaking amazing."

An Internal Idea System That Got Used Immediately

As the engagement matured and the team grew more comfortable inside HubSpot, a new need surfaced: a way to capture internal suggestions, bug reports, and process improvement ideas before they disappeared into team chats or post-it notes. The Gist designed and built a lightweight internal suggestion form and ticket pipeline — simple, practical, and immediately adopted. Within an hour of it going live, the first real suggestion (not a test) had already come through. The team's response said it all:

"I bet it wasn't an hour later. Already had one."

Growing Into the Platform

Perhaps the most encouraging signal throughout this engagement was how Candoor's appetite for the platform continued to grow over time. What began as a migration from one CRM to another evolved into a genuine operational transformation. The team began using AI tools to draft property structures and service object documentation. They started identifying upsell tracking opportunities they had never had before. They launched email marketing campaigns to their client base, created a knowledge base, and began planning content series around seasonal topics relevant to their clients — workers' comp audit season, year-end processing reminders, new hire reporting changes, and more.

The re-engagement that followed the initial build was not a support relationship — it was a strategic one. Candoor came back to The Gist with a content calendar, a list of topics they wanted to cover, and a vision for how they wanted to use HubSpot's marketing tools to communicate consistently and meaningfully with their client base.

Outcomes and Looking Ahead

Candoor Payroll & HCM entered this engagement with a CRM that had reached the limits of what it could do for them. They left it with a HubSpot environment that is purpose-built for how a payroll bureau actually operates.

Their payroll processing team works out of a ticket system that reflects their real workflow, with client information surfaced in the right places, assignment logic that reduces manual routing, and a historical record of every payroll run tied back to every client. Their support team fields incoming requests through a structured inbox that auto-creates tickets, routes them to the right pipeline, and escalates when things go unanswered for too long. Their sales pipeline captures the right information at the right stages, feeds the implementation team automatically, and tracks where referrals come from. Their marketing list is clean, segmented by client attributes pulled directly from iSolved, and powering a growing cadence of targeted, relevant communications.

The iSolved-to-HubSpot data sync is now live, which means that for the first time, Candoor's CRM and their payroll platform are in meaningful communication with each other — keeping contact records accurate, client statuses current, and service data consistent without requiring manual reconciliation between two systems.

Looking ahead, Candoor is well positioned to continue expanding what they do inside HubSpot at a pace that fits their team's bandwidth. Service objects are being built out to give every active client a structured, queryable record of the services they receive — providing visibility that never existed before. Knowledge base articles are in development to serve as both a client resource and a marketing asset. Email nurture campaigns are being refined. And conversations about deeper iSolved integration continue, with the long-term vision of automating even more of the operational work that the team currently manages manually.

For a payroll company, the measure of a great CRM is simple: does it make the people who work out of it every day faster, more informed, and more confident? By that measure, Candoor is in a fundamentally different place than they were when this engagement began — and the work they have put in positions them to keep growing into it.