Monday list-building replacement agent for education and training sales teams on Salesforce

What The Prospector does

Right now, a sales team at a 51 to 200 person education and training company spends every Monday morning building lists by hand: pulling district and campus names from old spreadsheets, hunting for the current director of curriculum or dean of continuing education, and pasting contacts into Salesforce before anyone makes a call. The Prospector takes over that work. It runs on a weekly cadence (plus mid-week refreshes when signals spike), works for the account executives and SDRs who sell to schools, districts, colleges, training providers and corporate learning teams, and owns three things end to end: maintaining the ICP and persona rules by institution type, producing a de-duplicated, enriched and prioritized list per rep that respects territory and account ownership in Salesforce, and drafting first-touch outreach that references the right point in the academic or fiscal calendar. It does not own replies, pricing, pilots or contracts. It hands those to reps with the research attached.

Custom build

The team lives in Salesforce, so a custom Claude build orchestrated with n8n is the best fit: n8n handles the Sunday schedule, Apollo, FullEnrich and Warmly calls, and Salesforce reads and writes through the API, while Claude does the account research, scoring and drafting where judgment matters. This keeps Salesforce as the system of record for ownership and activity, avoids moving reps to a new CRM, and lets the FERPA redaction and audience filters be built as explicit steps that are logged and auditable. Salesforce's native agent tooling can be layered on later for in-app summaries, but the calendar-aware sourcing and multi-vendor enrichment are easier to control in a custom build. Instantly handles sending on separate warmed domains so cold outreach never risks the deliverability of admissions or customer email.

What starts it

• Scheduled weekly run every Sunday night that builds each rep's Monday list in Salesforce, sized to their capacity for the week
• Academic calendar milestones in the agent's calendar table (budget planning season, board meeting dates, term start and end, summer purchasing window) that shift which segments get prioritized
• A known institution showing buying intent: repeat visits to pricing or district solutions pages, a webinar registration, or a published RFP or curriculum adoption notice
• A rep marks an account Closed Lost with a revisit date, or a champion contact changes jobs to a new institution
• A rep requests an on-demand list for a specific territory, state or segment through a Salesforce quick action

What it reads

• Salesforce accounts, contacts, opportunities, territories, activity history and Closed Lost reasons (read and write via API)
• Apollo for institution and contact sourcing by role, institution type, enrollment size and geography
• FullEnrich waterfall enrichment for verified work emails and direct dials on contacts Apollo misses
• Warmly for identifying which institutions are visiting the website and which pages they read
• Public institutional sources: school board agendas, procurement and RFP portals, grant award announcements and published academic calendars, read through a web research step
• An internal calendar table (Airtable or a Salesforce custom object) mapping each segment to its fiscal year start, budget window and term dates

When a person takes over

• Any positive reply, question about pricing, pilot or pilot data, or meeting request goes straight to the owning rep in Salesforce with the account brief. The agent never negotiates or answers product scoping questions.
• A reply or inbound that includes student names, grades, IDs, accommodations or any other student-level detail is quarantined, redacted from logs and routed to the designated compliance or operations owner before anyone responds.
• Parents, students or individual learners who reply or come in through signals are removed from sales sequences and routed to the admissions or support team, since they are not the institutional buyer and need different handling.
• Changes to ICP rules, personas, calendar priorities or outreach frameworks are proposed by the agent and approved by the sales manager before the next weekly run.

Rules it follows

• FERPA boundary: the agent never requests, ingests, stores or references student education records or student-level data. It only works with publicly available institutional information and professional contact data for staff and administrators, and any student data that arrives in a reply is redacted and escalated, not processed.
• Audience separation: no outreach is sent to parents, students or personal email addresses. Sequences target institutional staff and corporate buyers only, and K-12 contacts are filtered to administrative and procurement roles.
• Calendar sensitivity: sends pause during known exam weeks, term starts and major breaks for each segment, and procurement blackout periods on active RFPs are respected so the company does not contact evaluators improperly.
• Ownership respect: the agent never adds a contact or account that has an open opportunity, an active customer relationship or recent rep activity without notifying the owner first.
• Nothing sends without a person: first-touch drafts stay paused until a rep approves them during the pilot, and only pre-approved frameworks can be auto-sent after that, with claims limited to an approved library (no invented outcomes or student results).

How you know it works

• Rep hours spent on list building per week, tracked by self-report before and after launch
• Meetings booked per rep per week from agent-sourced prospects, measured in Salesforce
• Pipeline created from agent-sourced accounts, by segment and calendar window
• Positive reply rate by persona and framework
• Data quality: bounce rate on agent-sourced contacts and share of list items reps reject as wrong-fit

From pilot to live

1. Pilot (weeks 1 to 4)Two reps in one segment (for example, K-12 districts in a few states). The agent builds their Monday lists, all drafts require approval, and reps tag each prospect as good fit or wrong fit. The calendar table and FERPA redaction step are tested against real replies.
2. Expand (weeks 5 to 10)Add higher ed and corporate training segments and the rest of the team. Tune ICP rules from pilot tags, add Warmly signals and mid-week refreshes, and allow auto-send on the best-performing frameworks with rep spot checks.
3. Run and operate (ongoing)Weekly runs become standard. The operating team monitors deliverability, enrichment spend, data quality and FERPA quarantine logs, refreshes the academic calendar each term, and reviews performance monthly with the sales manager to retire weak frameworks and adjust segment priorities.