Term-calendar re-engagement research agent for small education and training providers clearing an old institutional lead backlog in HubSpot

What The Researcher does

A training provider with a sales team of a few reps has years of leads in HubSpot from webinars, conference booths, catalog downloads and inquiry forms. Most got one email and nothing after. The list is mixed: district curriculum leads, college department heads, corporate L&D managers, but also parents and students who inquired about a course, and a few records where staff pasted notes about individual learners. Nobody knows which leads are institutions worth a call, which buyers have moved on, or when each institution is even making decisions. The Researcher owns that backlog. It sorts every record by audience, quarantines anything with possible student-record content, groups contacts under their institution, verifies who still works there, and researches each institution's term dates, budget and board cycle, enrollment trends and incumbent providers. It writes a short deep-research brief and a battlecard, assigns a re-engagement window tied to the institution's calendar, and places the account in the right rep's HubSpot queue at the right time. The team keeps it running and tuned so the backlog keeps shrinking instead of the reps doing archaeology.

Built on HubSpot

The team already lives in HubSpot, so the plan keeps every output there: company properties for audience and re-engagement window, notes for briefs, tasks for the queue and HubSpot email for sends. Breeze's company research agent and data enrichment handle baseline firmographics well and should be used for that layer. Where Breeze falls short is the education-specific work: reading board minutes and academic calendars, scheduling outreach around term and budget cycles, and enforcing a strict student-data scrub. That part is a custom AI build orchestrated in n8n, reading from and writing back to HubSpot through its API, with FullEnrich and Apollo for contact verification and Chili Piper for booking. Because they asked to have it built and maintained, this split also keeps the custom logic in one place that can be monitored and updated each academic year.

What starts it

• Initial backlog run: a one-time batch over all leads with no second touch, processed in weekly tranches so reps are not flooded
• Calendar window opening: an institution's planning window (budget season, pre-term planning, professional development scheduling) comes due within the next few weeks
• A dormant contact re-engages, such as opening a newsletter, revisiting pricing or course pages, or registering for a webinar
• Ownership change detected: a verified contact has left the institution and a replacement buyer needs to be found
• A rep requests a fresh brief on an account before a scheduled call

What it reads

• HubSpot contacts, companies, deals, notes and email engagement history
• Public institution sources: academic calendars, board meeting agendas and minutes, published strategic plans, budget documents and staff directories
• Public enrollment and program data for schools, colleges and training centers, plus job postings and news on corporate L&D buyers
• Contact verification and waterfall enrichment through FullEnrich and Apollo
• Website visit and webinar attendance signals already captured in HubSpot
• Internal win/loss notes and a maintained list of competing providers and their positioning

When a person takes over

• Possible student-record content found: the record goes to the designated data or compliance owner, who decides whether to redact, delete or keep it. The agent does not research or summarize that record.
• Active RFP or formal procurement detected in board minutes or a procurement portal: the sales lead decides whether to bid, since outreach during a quiet period can disqualify the company.
• Parent and student inquiries: handed to the admissions or marketing team for consumer nurture, never placed in a rep's B2B queue.
• Past customer with complaint, refund or churn notes, or a buyer whose replacement cannot be confirmed: routed to the account owner to decide whether and how to reach out rather than the agent guessing.

Rules it follows

• FERPA boundary: the agent never ingests, stores, summarizes or references information about individual students, and only uses institution-level public data and the professional contact details of staff buyers.
• Audience separation: sales research and outreach drafts are only produced for institutional and corporate buyers. Parents and students are never pulled into cold sales sequences.
• Every fact in a brief or battlecard carries a source link and date. If a term date, budget figure or incumbent cannot be confirmed, it is marked unknown instead of estimated.
• Nothing is sent automatically. Reps approve every first touch, and the agent respects HubSpot unsubscribes and existing lifecycle stages.
• Competitive claims stick to public, verifiable facts and the approved positioning list. No disparaging or speculative statements about other providers.

How you know it works

• Share of the dormant backlog classified, scrubbed and either researched or retired each month
• Re-engagement emails sent within an institution's planning window versus outside it
• Meetings booked from re-engaged accounts, tracked through Chili Piper and HubSpot meeting records
• New pipeline created from accounts that had no touch before the agent ran
• Rep-rated brief accuracy and number of records escalated for student-data review

From pilot to live

1. Pilot on one segmentRun the agent on a single slice, such as K-12 districts in one region, a few hundred records. Reps and the data owner review every classification, student-data flag, brief and battlecard. Tune audience rules, the competitor list and calendar logic based on what they correct.
2. Full backlog in weekly tranchesExpand to all institutional and corporate segments, releasing accounts to reps only as their windows open. Add re-engagement triggers from web visits and webinar registrations, and a weekly report on backlog progress and meetings booked.
3. Ongoing build and maintainThe agent shifts from backlog cleanup to keeping the database alive: refreshing calendars each academic year, re-verifying contacts after summer staff turnover, updating battlecards as competitors change, and monitoring source breakage, enrichment credit use and escalation volume so the team does not have to maintain it themselves.