Build a new rep ramp pack

<context>
A new rep just joined the team. Before their first day of prospecting, I want to build them a complete starter pack — a verified account list for their territory, the right contacts at each account, signal scores, and a first-week outreach plan. The rep should be able to start making calls on day one, not spend the first two weeks building a list.

New rep details:
- Rep name: [NAME]
- Territory: [REGION / VERTICAL / COMPANY SIZE — e.g. "Mid-market SaaS, US West Coast, 200–800 employees"]
- Function they sell into: [e.g. "Sales, RevOps, Finance"]
- Seniority floor: [e.g. "VP and above" / "Director and above"]
- What we sell: [PRODUCT / SOLUTION]
- Number of accounts to build: [e.g. "30" / "50"]
- Accounts already assigned: [PASTE LIST OR "none yet"]
- Slack channel to notify: [CHANNEL NAME OR "skip"]
</context>

<task>
1. Use Lusha to find companies matching the territory criteria:
   - Industry, headcount range, and geography as specified
   - Exclude any company already a customer or in active pipeline
   - Prioritize companies with a signal in the last 30 days

2. For each company, find the right contacts:
   - Primary: most senior verified contact in the target function at or above the seniority floor
   - Secondary: one level below — the evaluator or champion layer
   - Verified work email and direct mobile for each

3. Score each account:
   - Priority A: live signal in last 30 days + verified decision-maker
   - Priority B: verified decision-maker, no signal
   - Priority C: contact below seniority floor or partial data

4. Build the rep ramp pack:

   ## Territory Overview
   Total accounts · verified contacts · Priority A / B / C breakdown

   ## Priority A Accounts — call first
   Company · size · signal · primary contact · email · direct mobile · suggested opening angle

   ## Priority B Accounts — week 2 onwards
   Company · size · primary contact · email · direct mobile

   ## Priority C Accounts — needs research before calling
   Company · what's missing · recommended next step

   ## First Week Outreach Plan
   Day 1–2: all Priority A accounts — signal-based openings
   Day 3–4: top 10 Priority B accounts
   Day 5: research Priority C gaps

   ## Quick Reference Card
   3 opening lines — one per signal type (funding / exec hire / headcount surge)

5. Post to Slack if channel specified — tag rep and manager.
</task>

<constraints>
- Lusha-verified contacts only.
- Priority A requires both a signal AND a verified decision-maker.
- First week plan must name specific accounts — not generic advice.
- Quick reference card opening lines specific enough to use verbatim.
</constraints>

The situation: A new SDR — Jamie — joins the team on Monday. Territory: mid-market B2B SaaS, US, 200–600 employees, VP of Sales and RevOps, selling sales intelligence software.

Territory Overview

Jamie — Mid-market SaaS US · Week starting June 2

Total accounts built: 8 · Verified contacts: 14 · Priority A: 3 · Priority B: 4 · Priority C: 1

Priority A Accounts — call day 1 and 2

Dunmore Analytics · 580 employees Signal: Series B closed 18 days ago · New budget cycle, headcount targets being set now Primary contact: T.K., VP of Sales · t.k@[dunmore].com · direct mobile available Opening angle: “Your Series B just closed — SDR data quality is usually the first thing that breaks at scale. Worth a quick call?”

Crestline Software · 340 employees Signal: New CRO hired 12 days ago · New leader evaluating the full stack in first 30 days Primary contact: R.V., VP Revenue Operations · r.v@[crestline].com · direct mobile available Opening angle: “A new CRO is usually when the data layer gets reviewed. Happy to show you what that looks like at Crestline’s stage.”

Falcrest Tech · 380 employees Signal: Series A closed 9 days ago · Post-funding stack evaluation window is open Primary contact: P.N., VP Revenue Operations · p.n@[falcrest].com · direct mobile available Opening angle: “Congrats on the Series A — most teams your size hit the SDR ramp problem right after the round closes. Worth 15 minutes?”

Priority B Accounts — week 2 onwards

Ashford Platforms · 420 employees Contact: M.L., Head of Sales Operations · m.l@[ashford].com · direct mobile available No signal — ICP fit. Call week 2.

Briarway SaaS · 290 employees Contact: P.O., VP of Sales · p.o@[briarway].com · direct mobile available No signal — ICP fit. Call week 2.

Greenway Cloud · 510 employees Contact: J.A., SVP of Sales · j.a@[greenway].com · direct mobile available No signal — ICP fit. Call week 2.

Halcyon Data · 470 employees Contact: S.P., VP RevOps · s.p@[halcyon].com · direct mobile available No signal — ICP fit. Call week 2.

Priority C Accounts — research before calling

Elmont Systems · 610 employees Issue: Only Director-level contact found — below VP floor Next step: Run the find decision-maker prompt to find VP or above before calling.

First Week Outreach Plan

Day 1: Call T.K. at Dunmore Analytics (Series B) · Call R.V. at Crestline (new CRO)

Day 2: Call P.N. at Falcrest Tech (Series A) · Follow up on any Day 1 voicemails

Day 3: Email M.L. at Ashford + P.O. at Briarway

Day 4: Email J.A. at Greenway + S.P. at Halcyon

Day 5: Research Elmont Systems VP contact · Review responses from Days 1–4

Quick Reference Card

Funding signal opener: “Your [Series A/B] just closed — most teams at your stage hit the SDR data quality problem before the first new hire ramps. Worth a 15-minute call?”

New exec hire opener: “A new [CRO/VP Sales] is usually when the data layer gets reviewed. Happy to show you what that looks like at [company]’s stage — 15 minutes?”

Headcount surge opener: “Your [SDR/AE] team is growing fast — data quality is the first thing that breaks at this scale. Worth a quick call before it becomes a ramp problem?”

Illustrative example — fictional company names used. Run with your own territory parameters to see live results.