Plan-year-timed second-touch workflow agent for retirement plan advisory firms on HubSpot: backlog waves sized to advisor calendars and a permanent no-single-touch rule

What The Second-Touch Operator does

A firm of 11 to 50 people that advises small and mid-size employers on retirement plans has thousands of HubSpot contacts from webinars, plan-cost calculators, conference lists and old referral campaigns. Each got a single email or call, then nothing, because advisors chased whatever was newest and nobody owned follow-up. The RevOps lead wants that backlog worked, but cannot flood two or three registered advisors with meetings they cannot staff, cannot send anything compliance has not approved, and does not want the same pile to rebuild next year. The Second-Touch Operator owns three things. First, it drains the backlog in weekly waves sized to open advisor calendar slots, prioritizing employers whose plan anniversary or renewal window is approaching. Second, it runs branching nurture by original lead source, plan status (no plan, existing plan with another provider, recently switched) and company size, using only pre-approved message modules. Third, it enforces a permanent rule: any new lead that reaches day 10 without a second touch is automatically enrolled. The consultancy builds and maintains it, including module library updates, wave tuning and archive reconciliation, so RevOps owns outcomes and not upkeep.

Built on HubSpot

The firm already runs HubSpot, and its workflows, sequences, lifecycle properties and email records are the right home for enrollment logic, the day-10 rule and the activity trail that supervisors review. HubSpot Breeze can help reps summarize threads and prep for calls, but free-form drafting is the wrong tool where every outbound word needs prior approval. So message assembly and reply classification run in a custom AI agent orchestrated in n8n that is restricted to selecting approved modules and filling whitelisted fields. Chili Piper handles state-aware advisor routing better than native meeting links, FullEnrich handles re-verification of aged records, and an Airtable module library gives compliance a clear approval ledger that HubSpot alone does not provide.

What starts it

• Weekly wave release every Monday: the agent reads open advisor meeting slots for the next two weeks and releases that many backlog contacts, with a buffer for no-shows
• A contact's plan anniversary or renewal date falls 90 to 120 days out, which moves them to the front of the next wave
• Any new lead reaches 10 days since first touch with no second logged activity (the standing no-single-touch rule)
• A dormant contact revisits the site, opens a plan-cost calculator, or registers for a webinar
• Compliance approves a new or revised message module in the library, which unlocks the branches that were waiting on it

What it reads

• HubSpot contacts, companies, activity history, lifecycle stage, lead source and email subscription status
• Compliance-approved message module library, kept as an Airtable base with module ID, approval date, approver, expiry and allowed segments
• Advisor calendars and state registration roster (which advisor is registered in which states) synced through Chili Piper and an ops-maintained table
• Plan-year data: plan anniversary, current provider and plan status captured from forms, public plan filings research and advisor notes
• FullEnrich waterfall enrichment to re-verify emails, titles and phones on contacts older than 12 months
• The firm's books-and-records archive, which receives a copy of every outbound message and reply

When a person takes over

• A reply asks something specific about fees, fund lineups, fiduciary status or performance goes straight to the registered advisor as a task with the thread attached, and the agent sends nothing further, because answering would be individualized advice that only a registered person can give
• Complaint-like language (accusations, threats to report, references to a past problem with the firm) is routed to the compliance officer within one business day and the contact is frozen, since these may trigger complaint-handling and reporting obligations
• A segment has no approved module for the next step, or a module is nearing its expiry date: the agent stops that branch and sends the compliance officer a request listing the segment and intended purpose, rather than reusing a module approved for a different audience
• The weekly wave would exceed advisor capacity or a state lacks a registered advisor: the RevOps lead decides whether to hold contacts, add calendar time or reassign, so the agent never books a meeting nobody can legally or practically take

Rules it follows

• Every outbound message is built only from library modules with a current compliance approval, an approver name and an approval date, and the module ID is logged on the HubSpot email record and in the archive so supervisors can reproduce exactly what was sent
• No message may include performance figures, projected savings, testimonials, rankings or comparative fee claims unless that exact language is in an approved module, reflecting SEC marketing rule and FINRA communications standards
• Sending pauses automatically if archive capture drops below a full match with HubSpot sends for any day, because unarchived business communications are a books-and-records failure
• Meetings are only offered with advisors registered in the prospect's state, and unsubscribe, do-not-contact and existing-client flags are checked at send time, not just at wave release
• Wave sizes and daily send volume per domain are capped and warmed (with Warmy monitoring placement), so reactivating a large, aged list does not damage deliverability for the firm's client communications

How you know it works

• Share of the original one-touch backlog that has received a compliant second touch, tracked weekly
• Meetings booked per advisor per week from reactivated contacts, compared against the capacity each wave was sized for
• Pipeline created from reactivated contacts, split by plan status branch and original lead source
• Percentage of new leads receiving a second touch within 10 days (the no-single-touch rule)
• Archive match rate between HubSpot sends and captured records, with a target of complete capture

From pilot to live

1. Pilot: one segment, one waveCompliance approves modules for a single branch (employers with an incumbent provider and an anniversary in the next two quarters). The agent cleans the full backlog, but only releases a small wave to one or two advisors. RevOps and compliance review every sent message, reply classification and archive record for the first weeks before anything scales.
2. Expand branches and turn on the standing ruleAdd the no-plan and webinar or calculator branches once their modules clear review, raise wave sizes based on actual reply-to-meeting rates, and switch on the day-10 no-single-touch workflow for all new leads. Weekly reconciliation and the Databox dashboard become the operating review.
3. Full operation with ongoing maintenanceAll advisors and states are covered, waves run unattended within caps, and the maintainer handles module expiry renewals, enrichment refreshes, sequence tuning and archive checks. Quarterly, RevOps and compliance review which modules convert and retire weak ones, with any new language going back through approval.