How to Set Up HubSpot for a CPA or Accounting Firm
An accounting firm does not close a sale and move on. It signs an engagement that recurs every year against a calendar it does not set, for a client group that is frequently several filers rather than one. A CRM holding four objects can record the pursuit and almost nothing that follows it: not which entity is filing, not what the engagement consumed against what it billed, and not the deadline that governs when any of it has to be finished. This walkthrough sets out the object model RevOps HQ installs for CPA and accounting firms, why the client entity is separate from the company, and the realisation and compliance reporting that becomes possible once the model holds.
Key takeaways
- Client entity, engagement, return and deadline are custom objects added to HubSpot’s standard four. Each carries figures the standard objects have nowhere to put.
- A company is a relationship; a client entity is a filer. One owner group is a single commercial relationship and several entities, each with its own entity type, fiscal year end and returns.
- The fiscal year end sits on the entity rather than on the firm, and it sets the calendar. A firm treating its own busy season as the calendar is reading its clients’ obligations through its own.
- A deal closes at signature and an engagement begins there. The engagement carries preparer hours and realisation, which is the pair that decides whether the fee was right.
- Conflict check is a gate before proposal rather than a task after it, because a conflict found after a fee is quoted is a conversation the firm has already lost.
- A contact’s relationship to an engagement carries a role. The person who provides records is frequently not the person who signs, and chasing the wrong one is how a return stalls.
- Next year’s engagement is created before this year’s is filed, so the recurring work exists as a record rather than as an intention.
- Reporting follows from the model: realisation by service line, engagements by status against the compliance calendar, fee by entity type, and referral revenue attributed to the source that produced it.
The Object Model Decides What Can Be Reported
HubSpot ships four objects. Contacts are people, companies are organisations, deals are transaction opportunities, and tickets are service issues arising from them. Those four describe a business that sells something and supports it afterwards.
They do not describe a practice. The entity that files, the engagement that is worked, the return that is produced and the deadline that governs it each carry figures with nowhere to sit in that model, and the questions a managing partner asks are all questions about them. Whether realisation can be read by service line, whether a compliance calendar exists as a board rather than a spreadsheet, whether referral revenue can be attributed to the firm that sent it: each is a consequence of the model rather than of the reporting tool above it.
A Client Group Is Not a Filer
This is the decision the rest of the model depends on. A company record represents the commercial relationship: the family, the owner group, the people who decide whether the firm is retained. A client entity represents something narrower and more consequential, which is the thing that files.
One relationship routinely spans several. An owner with an S corporation, a partnership holding the property, and a personal return is one client and three filers, each with its own entity type, its own fiscal year end and its own obligations. Collapsing them into the company record produces an account that cannot answer which return is late, because the account is not the thing that files.
The fiscal year end belongs to the entity for the same reason. It sets the calendar for everything below it, and a firm that treats its own busy season as the calendar is reading every client’s obligations through its own rather than through theirs.
The Deal Ends at Signature; the Engagement Begins There
The deal records the pursuit. It runs from inquiry through conflict check, scoping and proposal, and finishes won or lost. At that point its job is done.
The engagement records the work. It carries a status that moves from not started through awaiting documents, preparation and review to filed. It carries the service line. Above all it carries preparer hours against the fee, which together produce realisation, and realisation is the number that says whether the engagement was worth taking.
Firms holding this on the deal record end up with a closed-won deal carrying a fee that was correct at signature and no record of what the work consumed. Realisation then lives in a spreadsheet reconciled after busy season, which is the point at which the pricing conversation for next year has already been had.
Conflict Check as a Gate, Not a Task
The conflict check sits between inquiry and scoping as a stage the deal cannot pass without clearing. Modelled as a task alongside the proposal it becomes something done in parallel, and a conflict found after a fee has been quoted is a conversation the firm has already lost.
Because the check runs against entities rather than against company names, the query is answerable: whether this entity, or any entity in its group, is already engaged in a matter that conflicts. Running it against a company name is what produces the false negative, since the conflicting party is ordinarily a different entity under the same ownership.
Roles, Because the Signer Is Not the Preparer’s Contact
A contact’s relationship to an engagement is not simply that one exists. On a single engagement one person provides the records, another signs the return, and a third is the banker who made the introduction. A model recording only the association loses the distinction that decides who gets chased when documents are outstanding.
Recording the role on the relationship rather than on the contact is what allows the chase to be automated correctly. Recording it on the contact would force one role across every engagement that person touches, which is wrong for anyone the firm deals with more than once.
Next Year Exists Before This Year Is Filed
Recurring work is the ordinary case in this sector and the exceptional case in most CRMs. The mechanism is to create next year’s engagement at the point this year’s enters review, so the recurring relationship exists as a record with a deadline rather than as an assumption held by whoever ran it last time.
Two further automations follow from the same model. A document sent for signature moves the engagement to awaiting signature, and an executed document moves it onward, so the status reflects what happened rather than what someone remembered to update. And an engagement untouched for thirty days escalates, which is what stops a stalled return from being discovered in the week it is due.
The Reporting the Model Produces
Each of the following follows from the objects rather than being added on top. A mid-sized firm ordinarily runs eight to twelve dashboards, divided by team with administrative and partner views alongside.
- Realisation by service line, which is where a fee schedule is shown to be wrong rather than argued about
- Engagements by status against the compliance calendar, worked as a board rather than a spreadsheet
- Preparer hours by engagement and by preparer, read against the fee rather than in isolation
- Annual fee by entity type, separating S corporations, partnerships, C corporations and individuals
- Client risk rating across the book, and which ratings concentrate in which service lines
- Returns by filing status and by deadline, including which are on extension
- Referral revenue attributed to the source that produced it, so a partnership can be valued rather than assumed
The referral report is the one that changes behaviour outside busy season. With revenue attributed to the introducing firm, the highest-value referral relationships are a list rather than an impression, and a marketing programme can be aimed at more sources resembling them.
What Installation Involves
The objects, the properties, the workflows and the reporting described here are built. An installation configures them in the firm’s portal and then adapts the remainder, which is ordinarily a matter of the service lines offered, the entity types worked with, and the stages an engagement passes through before it is filed.
Firms differ at the edges and not in the middle. An entity files, an engagement consumes hours against a fee, a return has a deadline, and next year comes whether or not anyone recorded it. The customisation sits at the edges.
Frequently asked questions
Does this replace our tax or practice management software?
Ordinarily not. Tax preparation software carries the return itself, the calculations and the e-filing, and practice management may carry time and billing. What this model does is make HubSpot the record of the client relationship and the work in flight, with those systems integrated into it rather than duplicated by it.
Why separate client entity from company?
Because a company is a relationship and an entity is a filer, and the two are frequently one to many. An owner with an S corporation, a partnership and a personal return is one client and three filers. Collapsed into a company record, the question of which return is late has no answer, because the company is not the thing that files.
How is realisation calculated?
From preparer hours logged against the engagement and the fee agreed on it, both held on the same record. Held apart, the calculation requires an export and a join, which is why it ordinarily happens once a year rather than continuously.
Can the compliance calendar be worked as a board?
Yes. With the deadline as its own object carrying a due date and an extension flag, a board of what is due in the next thirty days is a saved view, and the document chase that should begin ahead of it is a workflow rather than a reminder somebody sets.
What does an installation cost relative to building it?
A partner building this specification from an empty portal is ordinarily a five-figure engagement, because the objects, properties, workflows and reporting are all bespoke work. This model is already built, so the engagement configures it and adapts the remainder.
Talk through the CPA & Accounting build
Book a timeOpens HubSpot in a new tab. The in-page calendar needs the cookies you declined.
Setting up HubSpot for your accounting firm?
The object model, workflows and reporting described here are already built and can be installed in an existing portal, then adapted to the service lines offered and the entity types worked with. A short call establishes whether the model fits before any work is scoped.