A professional-services firm automated its follow-up without automating its relationships

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Partners at a regional accounting and advisory firm carry the client relationships personally: seminars, trade dinners, and referral conversations produce most new work, and a promise to follow up next week is made in good faith at every one. The firm's marketing function is one manager with an email newsletter and a list of four thousand contacts gathered over years. Partners themselves log into the CRM rarely enough that their assistants print things for them — the inbox, not the database, is where the firm remembers its relationships.

What it was costing

Partners met prospects at events, promised follow-up, and forgot. Marketing sent quarterly newsletters to everyone regardless. The CRM had 4,000 contacts, no lifecycle stages, and partners checked it roughly never — relationship memory lived in inboxes.

What they could see

• Partners return from industry events with pockets of business cards and verbal promises to follow up; some of those promises simply evaporate.
• Long-standing clients receive the prospect newsletter, discount framing and all, aimed at people who already pay retainers.
• When a partner is asked how a specific prospect conversation ended, the answer is usually a search of their sent folder.
• Marketing cannot say which of the four thousand contacts are clients, active prospects, or names from a 2019 seminar list.
• The CRM's opportunity records go quiet for months at a stretch, so the pipeline view is neither trusted nor argued with.

The constraints we worked inside

• Partner relationships are the firm's asset; automation must prepare the human touch, never replace it.
• The partners would not log into the CRM daily — anything that required it would fail.
• Compliance rules on client communications shaped what could be automated at all.

What had been tried before

Marketing sent partners a weekly reminder email listing contacts awaiting follow-up, pulled by hand from the CRM.

The reminder came from marketing, not from the partner's own world; it read as homework from another department and was ignored within three issues.

A shared follow-up tracker spreadsheet was introduced at a partners' meeting and warmly endorsed.

Nothing fed it automatically, so it recorded promises as well as anyone remembered them; it was two months stale when we first saw it.

The existing Marketing Hub was configured around the quarterly newsletter as the firm's main nurture.

One send for clients, prospects, and decade-old seminar contacts alike; partners began describing the newsletter as spam, which it partly was.

What we proposed

Automation here should prepare the human touch and never replace it. Post-event contacts enter the CRM with a follow-up-by date; a workflow drafts the partner's personal follow-up email, attaches the conversation context, and reminds — the partner reads, edits, and sends it themselves with one click. Contacts split into clients, active prospects, and long-tail so each group gets honest communication and the newsletter reaches only those who welcome it. Everything the partners need surfaces in a Monday digest email — new leads, overdue follow-ups, stalled opportunities — because the design assumption was fixed from day one: the partners will not log in, so the system must come to them.

Just as important is what we ruled out, and why:

• Fully automated follow-up sequences to clients — Compliance rules govern client communications, and a client receiving an automated sequence from their own adviser damages the relationship the firm sells.
• A standalone CRM replacement — Advisers and assistants would relearn a new tool for a problem the existing platform could solve; another migration was cost without benefit.
• AI-drafted follow-ups sent automatically — Nothing unreviewed goes to clients or prospects under the firm's compliance rules, and a partner's voice misfires too expensively to trust unedited.

How the work ran

Delivered by the systems pod — automation specialist over 8 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

HubSpot CRM

The contact base already lived there; partners would tolerate one familiar system and would not tolerate a second login.

Workflows

Follow-up-by dates, drafted emails, and reminders are deterministic jobs; workflows do them identically every time, which is what partner trust requires.

Sequences

Reserved for long-tail prospects only — clients and active relationships keep human-sent mail, a line compliance and the partners both demanded.

Lifecycle stages

Clients, active prospects, and long-tail contacts behave differently; honest segmentation is what stops the newsletter insulting long-standing clients.

Digest reporting

Partners manage from their inbox by long habit; a Monday digest meets them there instead of asking for logins they will never make.

What went wrong

How we worked together

Cadence

A fortnightly working session with the marketing manager through the build, a digest pilot with one partner for a month, and compliance checkpoints at each workflow launch.

Client side

The marketing manager owned configuration and data; one partner championed the pilot and later recruited the others simply by being seen using it.

Decisions

Anything touching client communications was decided by the compliance officer; everything else was decided by the pilot partner's reaction to the actual Monday digest.

They provided

Access to the four-thousand-contact list for cleanup, the event calendar and past attendee lists, and the compliance policy on client communications.

What changed

The headline: event-promised follow-ups actually sent within two weeks, over two event seasons — 68% → 94%, read from CRM task completion records. A second check: engagements opened from followed-up event contacts, year over year at +11.

Event follow-up stopped being a debt the firm repaid in guilt. Partners' assistants no longer print CRM pages because the partners read the digest on their phones on Monday mornings, and the firm's conversation about prospects moved from memory to a shared record nobody has to defend. The newsletter went out to people who might actually read it, and the replies it gets are the friendly kind.

The result was read from CRM task completion records against the pre-engagement baseline over the stated window, with a guardrail check on engagements opened from followed-up event contacts, year over year. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The workflow set — event capture, draft-and-remind, digest — with a one-page diagram of each branch.
• The lifecycle definitions and the segmentation logic that routes the newsletter.
• A compliance-approved template library for partner follow-up drafts.
• The digest configuration, owned by marketing, including who receives it and what it lists.