RevOps HQ
BACK TO HUBSPOT FOR INDUSTRY
HubSpot for IndustryEpisode 3Law Firms11 min read

How to Set Up HubSpot for a Law Firm

A law firm does not sell to a person and it does not deliver a project. It opens matters, each with a responsible attorney, a limitations date that cannot be missed, and a fee arrangement that determines what the work is worth. A CRM without a matter object can record none of that, which is why firms end up with the real state of the practice in a spreadsheet and the CRM reduced to a contact list. This walkthrough shows the object model RevOps HQ installs for law firms, the cardinality decision at its centre, and the intake and risk reporting that only becomes possible once the model holds.

Already built and installed in one step — tell us about your portal.
ContactsCompaniesDealsTicketsMatters

Key takeaways

  • Matter is a custom object alongside HubSpot’s standard four. It carries matter status, responsible attorney, limitations date and the date opened.
  • A deal relates to many matters, not one. Clio’s native integration maps them one to one, and the workaround firms adopt — matter-two-date and matter-three-type columns on the deal — stops scaling at the third matter.
  • A contact relates to many matters and each relationship carries a role, so the same person can be the client on one matter and the opposing party on another without either record contradicting the other.
  • The limitations date is automated rather than remembered: a dynamic list of matters within thirty days, and a workflow that warns the responsible attorney when the date is missing or approaching.
  • Referral source is credited on the matter, which is what makes fees by referral source reportable rather than anecdotal.
  • Closed-lost reason is recorded against a defined set, so the reason a practice area loses work is a distribution rather than an impression.
  • Reporting is built on the object model rather than bolted on: intake funnel by practice area, matters by attorney and status, realised fee by arrangement, and first-response time against an SLA.

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, because the thing a firm actually runs — the matter — has no table.

This is the part most firms are never asked about, and it determines everything downstream. Whether the intake funnel can be reported by practice area, whether a limitations date can be automated, whether fees can be attributed to the referral source that produced them: each of those is a consequence of the model rather than of the reporting tool.

The law firm object model, with matter as a custom objectCompanies and contacts on the left, deals and matters in the centre, tickets on the right. Matter is a custom object added to HubSpot's standard four. A deal relates to many matters rather than to exactly one, which is the decision that distinguishes this model from the native Clio integration. A contact relates to many matters and each relationship carries a role, so the same person can be the client on one matter and the opposing party on another. Matters raise tickets for service and internal operations.LAW FIRM — MATTER ADDED TO THE STANDARD FOURassociationrole (N:M)one deal, many mattersassociationCOMPANYPKhs_object_idreferral_fee_valuereferrals_sentCONTACTPKhs_object_idemailrole_on_matterDEALPKhs_object_idpractice_areafee_arrangementconflicts_checkedMATTERPKhs_object_idmatter_statusresponsible_attorneylimitations_dateTICKETPKhs_object_idsubjectstatusOne deal to many matters. The alternative is matter-two-date and matter-three-type columns on the deal, which stops scaling at the third.
Matter added to the standard four, with one deal relating to many matters and a contact holding a role on each

One Deal, Many Matters

The cardinality between deal and matter is the decision that distinguishes this model. Clio’s native HubSpot integration relates them one to one, which is correct for a firm where an engagement produces a single matter and nothing else.

It stops being correct the moment a client brings a second matter under the same engagement. What firms do at that point is visible in their own portals: they add columns to the deal — matter two description, matter two date, matter two type — and repeat until the record is unreadable. Those columns cannot be filtered as records, cannot be counted, and cannot carry their own status or responsible attorney. A separate matters object associated to the deal solves all three, and costs a one-time decision at design.

Roles, Not Just Relationships

A contact’s relationship to a matter is not simply that one exists. The same person may be the client on one matter, the opposing party on another, and a witness on a third, and a model that records only the association loses the distinction that makes a conflicts check possible.

Recording the role on the relationship rather than on the contact is what allows the conflicts question to be answered as a query: is this person an opposing party on any open matter. Recording it on the contact would force the record to hold one role across every matter it touches, which is wrong for most people a firm deals with more than once.

Intake, and the Obligations That Outlive It

Intake runs from inquiry through conflicts clearance, consultation, the fee agreement and its ageing, to an opened matter with an attorney assigned. Each stage records its outcome, including the negative ones — a consultation that did not happen and a conflict that was found are both data the firm needs.

Intake from inquiry to opened matter, with the obligations that followSix stages run left to right: inquiry received, conflicts cleared, consultation held, fee agreement sent and ageing, agreement signed, and matter opened with an attorney assigned. Two obligations attach once the matter opens and continue for as long as it is open: a limitations date watch that warns the responsible attorney before the date lapses, and referral credit attributed to the source that produced the inquiry. These are standing obligations rather than stages, which is why they are drawn beneath the path.INTAKE — EVERY STAGE RECORDS ITS OUTCOMEInquiry receivedFrom form, call or referralConflicts clearedChecked against every matterConsultation heldOutcome recorded either wayFee agreement sentAnd begins ageingAgreement signedCountersigned and storedMatter openedAttorney assignedONCE OPEN — OBLIGATIONS THAT DO NOT END WITH INTAKELimitations date watchWarns the responsible attorney before it lapsesReferral creditedAttributed to the source that produced the inquiryA missed limitations date is the one failure a firm cannot report its way out of, which is why it is automated rather than remembered.
Intake to opened matter, and the two obligations that attach once it opens and continue for as long as the matter is open

What distinguishes a firm from most businesses is what happens after intake finishes. The limitations date is a hard deadline with professional consequences, and it is automated rather than remembered: a dynamic list of matters whose limitations date falls within thirty days, and a workflow that raises a warning when the date is missing altogether. Referral credit is the second obligation, and attributing it at the matter is what turns fees by referral source into a report rather than a recollection.

The Systems Around It

The practice stack connects to HubSpot in both directions, and the direction matters more than the connection. Matters can be held in HubSpot and synchronised to Clio, or held in Clio and mirrored into HubSpot for reporting. Both work; they differ in which system a partner opens to answer a question, and that choice should be made deliberately rather than inherited from a connector’s default.

The law firm stack around HubSpot, drawn by direction of flowHubSpot holds contacts, companies, deals, tickets and matters. Clio exchanges matters in both directions. Document tools send fee agreements out and return signature status. Forms, advertising and social send inquiries inward. Calls, email and transcripts log inward onto records. Address validation exchanges both ways. Dashboards read the matter roll-ups outward. The direction of each connection, rather than its presence, is what determines which system a partner opens to answer a question.PRACTICE SYSTEMSACTIVITY AND OUTPUTClioMatters, two-wayPandaDoc / DocuSignFee agreements out, status backForms, ads, socialInquiries inVOIP and emailCalls and transcripts loggedMiniMapAddress validation on recordsDashboardsReads the matter roll-upsHubSpotContacts, companies, deals,tickets and mattersMatters can be held here and synchronised to Clio, or held in Clio and mirrored. The choice decides which system answers a partner's question.
The practice stack, drawn by direction of flow rather than by which tools are connected

Fee agreements go out through PandaDoc, DocuSign or HubSpot’s own eSignature and return their status, so an agreement’s age is a property rather than a memory. Calls and email log to the contact and roll up to the matter. Address validation runs on the record itself.

Reporting the Managing Partner Asks For

The reports below are the ones firms consistently want and consistently cannot produce, and each is a direct consequence of the model rather than of a reporting feature.

  • Intake funnel by stage and by practice area, counted or valued at estimated fee
  • Limitations dates approaching, with matter status and responsible attorney
  • Matters by attorney broken down by status, as counts or as fee value
  • Fees by fee arrangement broken down by practice area
  • Closed-lost reason by practice area, against a defined set of reasons
  • Fees and matter counts by referral source, which read differently and should both be seen
  • First response time against the service level, and satisfaction rating beside it

The referral pair is worth dwelling on. Matter count by referral source and fee value by referral source rank differently, and a source producing a high volume of low-value matters is not obviously worth what it costs. That comparison is only available where referral source is recorded on the matter and fee value is recorded beside it.

What Installation Involves

The objects, properties, associations, workflows and dashboards described here are pre-built and installed into a portal directly, rather than specified from scratch at implementation rates. That covers the structure common to firms.

What remains is specific: how your intake team actually works, which practice areas you run, what your fee arrangements are called, and what a partner expects to see on opening a matter. That part is configuration against your practice and is where the engagement should spend its time.

Frequently asked questions

Which HubSpot objects should a law firm use?

Five. HubSpot’s standard contacts, companies, deals and tickets, plus a custom matter object carrying matter status, responsible attorney, limitations date and date opened. The matter is what the firm actually runs, and without it the practice’s real state lives outside the CRM.

Should a deal map to one matter or many?

Many, in most firms. Clio’s native HubSpot integration maps deal to matter one to one, which is correct where an engagement produces a single matter. Where a client brings several under one engagement, a one-to-one model forces attorneys to add matter-two and matter-three columns to the deal, and those columns cannot be filtered, counted, or given their own status and responsible attorney.

How does HubSpot handle a limitations date?

As a date property on the matter, with two automations over it: a dynamic list of matters whose limitations date falls within a chosen window, and a workflow that warns the responsible attorney where the date is approaching or has not been set. The point is that it is enforced by the system rather than held by a person.

Can HubSpot run conflicts checks?

It can answer the query the check depends on, because the role a contact holds is recorded on the relationship to each matter rather than on the contact. That makes “is this person an opposing party on any open matter” a filter. It does not replace the professional judgement a conflicts check requires.

Does this replace Clio?

Not necessarily. Matters can be held in HubSpot and synchronised to Clio, or held in Clio and mirrored into HubSpot for reporting. The decision is which system a partner opens to answer a question, and it is worth making deliberately rather than accepting a connector’s default.

Do we have to build this from scratch?

No. The objects, properties, associations, workflows and dashboards are pre-built and installed into your portal directly. What remains is configuration to your practice areas, fee arrangements and intake process, which is where the engagement should spend its time.

Talk through the Law Firms build

Pick a time that suits you. Thirty minutes, no deck — we go through your portal and what installing this would actually involve.

Book a time

Opens HubSpot in a new tab. The in-page calendar needs the cookies you declined.

Setting up HubSpot for your law firm?

RevOps HQ is a certified HubSpot Solutions Partner. We install the matter object model in your portal, connect it to Clio and your document tooling, and build the intake and risk reporting your partners ask for.

Meet with me

Our HubSpot Services

From implementation to optimization, we handle every aspect of your HubSpot journey

WEEKLY PROGRAM

RevOps Office Hours

A recurring weekly RevOps operating program. Live support plus hands-on HubSpot implementation work.

$1,500/mo
Monthly Operating Program
  • 1 live Office Hours session per week
  • 4 hours of hands-on implementation work per month
  • We determine how hours are allocated based on priorities
  • Recurring monthly cadence