Starter Package ($1,000 One-Time)

# SOP — Starter Package ($1,000 One-Time)

**Tag**: Foundation
**Timeline**: 7 days from kickoff
**Owner**: Devin (Delivery Ops) · Rick (Revenue) for sales handoff

---

## Phase 0: Sales & Intake (Day 0)

### Trigger
Client books intro call via Calendly or submits intake form at `/intake`.

### Steps
1. **Rick** reviews intake submission and qualifies the lead:
   - Business type, revenue range, current lead gen setup
   - Confirm budget alignment ($1K tier)
   - Identify ICP basics (industry, company size, geography, titles)
2. **Rick** conducts 15-min intro call:
   - Walk through LeadsPanther DFY model
   - Confirm Starter scope fits their needs (upsell to Standard if multi-channel is needed)
   - Collect: business URL, existing tool logins (if any), preferred CRM
3. **Rick** sends Stripe payment link ($1,000 one-time)
4. On payment confirmation:
   - Rick creates project card in HubSpot pipeline → stage: "Paid — Kickoff"
   - Rick sends kickoff email (template: `kickoff-starter`) with access checklist
   - Rick hands off to **Devin** via Slack with intake summary

### Deliverables
- Signed intake form
- Payment received
- HubSpot deal moved to "Paid — Kickoff"
- Kickoff email sent to client

---

## Phase 1: Discovery & Scoping (Days 1–2)

### Steps
1. **Devin** reviews intake form and kickoff notes from Rick
2. **Devin** schedules 30-min discovery call with client:
   - Deep-dive on ICP: ideal customer title, company size, industry, geography
   - Understand their offer/service and value prop
   - Confirm one prospecting channel (e.g., Google Maps, LinkedIn, Apollo, industry directory)
   - Identify CRM preference (HubSpot default; migrate if needed)
3. **Devin** documents ICP definition:
   - Target titles (up to 3)
   - Target industries (up to 3)
   - Target geography (city/state/country)
   - Company size range
   - Exclusion criteria
4. **Devin** creates project brief in workspace memory:
   - Client name, business URL, ICP doc, channel selection, CRM choice, tool access status
5. **Devin** confirms scope with client via email (template: `scope-confirmation-starter`)

### Deliverables
- ICP definition document
- Project brief
- Scope confirmation email sent and acknowledged

---

## Phase 2: Build (Days 3–5)

### 2A: Lead Discovery Pipeline
1. **Devin** sets up prospecting in the selected channel:
   - **Google Maps**: Configure search queries by location + category, set up scraping pipeline
   - **LinkedIn**: Build Sales Navigator search with ICP filters, configure export
   - **Crustdata**: Build people/company search with ICP filters (Apollo as backup)
   - **Industry directory**: Identify source, build scraper or manual export workflow
2. Run initial test pull: minimum 100 leads
3. QA the data: verify name, company, email fields are populated
4. Document the discovery workflow (search queries, filters, export steps)

### 2B: Basic Enrichment
1. **Devin** configures email verification pipeline:
   - Connect to verification service (e.g., NeverBounce, ZeroBounce, or built-in Crustdata verification)
   - Run verification on test batch
   - Set acceptance threshold: only "valid" emails pass through
2. Document enrichment config and acceptance rules

### 2C: Single Outreach Sequence
1. **Devin** drafts a 4-step email sequence:
   - Email 1: Initial outreach (personalized intro + value prop)
   - Email 2: Follow-up (3 days later — social proof or case study)
   - Email 3: Nudge (5 days later — short, direct ask)
   - Email 4: Breakup (7 days later — final touch, leave door open)
2. Configure sequence in outreach tool (Instantly or Smartlead):
   - Set sending schedule (business hours, timezone-aware)
   - Set daily send limits (start conservative: 25/day, ramp to 50)
   - Configure reply detection and auto-pause
3. Load test batch of 25 leads and send Email 1 as dry run
4. QA: verify emails land in inbox (not spam), tracking works, reply detection fires

### 2D: CRM Setup
1. **Devin** sets up CRM pipeline in HubSpot (or client's preferred CRM):
   - Pipeline stages: New Lead → Contacted → Replied → Qualified → Meeting Booked → Closed
   - Create custom properties: Lead Source, ICP Match Score, Sequence Status
   - Configure list views for each stage
2. Connect outreach tool → CRM sync (bi-directional if supported)
3. Test: send a test lead through the full pipeline and verify it appears correctly in CRM

### Deliverables
- Working lead discovery pipeline (one channel)
- Email verification configured and tested
- 4-step outreach sequence built and dry-run tested
- CRM pipeline with stages, properties, and sync configured

---

## Phase 3: Install & Testing (Days 5–6)

### Steps
1. **Devin** runs end-to-end test:
   - Pull 50 fresh leads from discovery pipeline
   - Run through enrichment/verification
   - Load verified leads into outreach sequence
   - Verify CRM sync: leads appear in correct stage
   - Verify reply detection pauses sequence correctly
2. Fix any broken links in the pipeline (API failures, sync gaps, verification edge cases)
3. Load production-ready lead list (minimum 200 verified leads)
4. Activate outreach sequence on first batch (25 leads)
5. Monitor for 24 hours: check deliverability, bounce rate, reply rate

### QA Checklist
- [ ] Discovery pipeline produces leads with required fields
- [ ] Email verification filters out invalid/catch-all addresses
- [ ] Outreach sequence sends on schedule with correct content
- [ ] Reply detection works and pauses sequence
- [ ] CRM shows leads in correct pipeline stages
- [ ] CRM sync is bi-directional (replies update CRM)
- [ ] No duplicate leads in CRM

### Deliverables
- End-to-end test report
- Production lead list loaded
- First batch live and monitored

---

## Phase 4: Training & Handoff (Day 7)

### Steps
1. **Devin** prepares handoff documentation:
   - System overview (1-pager): what's installed, how it connects
   - Discovery pipeline: how to run new searches, adjust filters
   - Outreach: how to edit sequences, adjust send limits, add leads
   - CRM: pipeline walkthrough, how to move deals, where to find reports
   - Troubleshooting: common issues and fixes
2. **Devin** conducts 45-min handoff call with client:
   - Screen-share walkthrough of every component
   - Client performs key actions (run a search, add leads to sequence, check CRM)
   - Answer questions
3. **Devin** sends handoff email with:
   - Documentation links/attachments
   - Summary of what was built
   - Support contact for post-handoff questions (7 days email support included)
4. **Rick** updates HubSpot deal → "Delivered"
5. **Rick** sends NPS/feedback survey (3 days post-handoff)

### Deliverables
- Handoff documentation package
- Recorded handoff call (if client consents)
- HubSpot deal marked "Delivered"
- Client has working system and knows how to operate it

---

## Post-Handoff (Days 8–14)

### Steps
1. **Devin** provides email support for 7 days post-handoff:
   - Respond within 48 hours
   - Fix any issues that arise from the installed system
   - Does NOT include new feature builds or scope expansion
2. On day 7 post-handoff:
   - **Rick** sends retainer upsell email (template: `retainer-upsell`) offering Monitor ($250/mo) or Optimize ($500/mo)
3. On day 14:
   - **Devin** closes project in workspace memory
   - **Rick** moves HubSpot deal → "Closed — Delivered" (or "Closed — Retained" if they add retainer)

---

## Agent Responsibilities Summary

| Agent | Role |
|-------|------|
| Rick | Sales, intake, payment, HubSpot pipeline, upsell, client comms |
| Devin | Discovery call, build, install, testing, training, handoff, post-handoff support |
| Daniel | N/A for Starter (no custom design work) |
| Alfred | Orchestration — monitors timeline, escalates if behind schedule |