Solanasis Docs

VC_Pipeline_Implementation_Prompt

5 min read

VC Pipeline Implementation Prompt

Purpose: Copy-paste this into Claude Code on the new server to kick off the VC pipeline build.

Prerequisites on the new server:

  • All three repos cloned: solanasis-scripts/, solanasis-docs/, solanasis-site/
  • Python 3.10+ installed
  • Working directory set to the parent of all three repos (e.g., _solanasis/)
  • The CLAUDE.md files in each repo will auto-load and provide project conventions

The Prompt

I need you to build the VC Portfolio Discount Cold Outreach Pipeline for Solanasis. This is a fully planned project with a senior-reviewed PRD. Your job is to implement it, not redesign it.

## Step 1: Read the PRD (this is your master plan)

Read this file first and completely. It is 850 lines and contains everything you need:

solanasis-docs/playbooks/VC_Pipeline_PRD_2026-03-22.md

This PRD covers:
- Product definition (two-tier startup offering: SSB $2,500 + CRA $5,000)
- All 11 pipeline scripts with detailed specifications
- SEC Form D data source with exact field names and download strategy
- 6 supplemental free databases with URLs
- 18-signal scoring model with weights and tier thresholds
- 5 email templates + 2 follow-ups (full body copy)
- /for/startups landing page spec
- 30-40 pytest test specifications
- 30-day pilot design with success metrics
- Fork warnings and known bugs to fix
- 16-point verification checklist

## Step 2: Read the fork source files

Before writing any code, read ALL of these files. They are the codebase you're forking from:

1. solanasis-scripts/fcto-pipeline/config.py — pipeline config structure, scoring model pattern, keyword lists
2. solanasis-scripts/fcto-pipeline/templates.py — email template structure, voice rules, mailto generation
3. solanasis-scripts/fcto-pipeline/generate_daily_outreach.py — daily brief system, tracker, follow-up scheduling
4. solanasis-scripts/fcto-pipeline/score_prospects.py — scoring engine
5. solanasis-scripts/fcto-pipeline/generate_outreach_csv.py — outreach CSV builder
6. solanasis-scripts/fcto-pipeline/enrich_websites.py — website enrichment (543 lines)
7. solanasis-scripts/fcto-pipeline/import_prospects.py — multi-source importer, column mapping pattern
8. solanasis-scripts/foundation-pipeline/tests/conftest.py — pytest fixture patterns

## Step 3: Read the context files

These provide voice rules, strategic context, and compliance constraints:

9. solanasis-docs/solanasis-voice-profile.md — voice rules for ALL copy (no em dashes, forbidden words list)
10. solanasis-docs/playbooks/Manual_Cold_Outreach_Cheat_Sheet.md — daily outreach safety rules, domain hygiene
11. solanasis-docs/playbooks/solanasis-investor-list-vc-ecosystem-outbound-playbook-handoff-2026-03-20.md — strategic playbook (segments, messaging principles, compliance, 30-day pilot)

## Step 4: Read the landing page fork source

12. solanasis-site/src/pages/for/foundations.astro — fork source for /for/startups landing page

Also read the solanasis-site/CLAUDE.md for site conventions (Astro + Tailwind patterns, test conventions, etc.)

## Step 5: Build in this exact order

Follow PRD section 12 (Implementation Sequence). Build each script, run its tests, then move to the next:

1. config.py — All new content, same structure as fCTO config
2. download_form_d.py — SEC Form D quarterly ZIP downloader. Run it after building.
3. import_form_d.py + tests — Parse SEC data. Run tests.
4. import_free_databases.py — Multi-source CSV importer
5. merge_sources.py + tests — Combine SEC + free sources
6. enrich_websites.py — Fork from fCTO, change keywords and scrape targets
7. enrich_emails.py — Email discovery (Hunter.io optional)
8. score_prospects.py + tests — Fork from fCTO, new signal evaluation
9. templates.py + tests — NEW email copy, same function signatures. Voice rules are NON-NEGOTIABLE.
10. generate_outreach_csv.py — Fork from fCTO, change CRM columns
11. generate_daily_outreach.py — Fork from fCTO, output YYYY-MM-DD-vc.md
12. requirements.txt — Copy from fCTO
13. /for/startups landing page — Fork from foundations.astro
14. SSB one-pager PDF
15. Operational playbook
16. Short URLs (go.solanasis.com/startup-security and /ssb via short.io API)

## Critical rules during implementation

### Voice rules (check EVERY template and landing page):
- NO em dashes (— or –). Use semicolons, periods, commas, parentheses.
- NO "seamless", "frictionless", "audit", "genuinely", "SMBs"
- Email bodies under 125 words (50-80 ideal)
- End emails with a specific question, not a generic CTA
- Plain text only in emails, no HTML

### Fork bug to fix:
- When forking generate_daily_outreach.py, fix ~line 336 which contains "SMBs" (forbidden) and an em dash. Replace "SMBs" with "small and mid-size organizations" and the em dash with a semicolon.

### What NOT to build (explicitly out of scope):
- discover_prospects.py — SEC Form D replaces web discovery
- migrate_to_baserow.py — deferred to post-pilot Phase 2
- Motion B (founder-direct outreach) — separate Phase 2 effort

### config.py SCORING dict:
Section 5.1 of the PRD shows `SCORING = { ... }` as placeholder. Copy the FULL scoring dict from PRD section 5.8 into config.py.

### Template 1 word count:
Template 1 is ~95 words. With personalized first line (~20 words), total may exceed 125. If so, trim the "For more mature companies" sentence.

## Step 6: Verify against the checklist

After building everything, run through PRD section 16 (Verification Checklist):

1. download_form_d.py downloads and extracts SEC ZIPs
2. import_form_d.py produces 4,000-6,000 unique VC funds
3. No PE/hedge/real estate funds in output (spot-check 20 records)
4. merge_sources.py deduplicates correctly
5. enrich_websites.py caches and rate-limits
6. Email coverage 40%+ for A/B-tier
7. Tier distribution: A ~5-8%, B ~15-20%
8. All templates: no forbidden words, no em dashes
9. Subject lines < 60 chars, bodies < 125 words
10. All pytest tests pass
11. Daily brief generates with working mailto: links
12. Test 3 mailto: links in email client
13. Top 10 A-tier are real VC funds (manual review)
14. /for/startups renders correctly
15. Short URLs resolve
16. Pipeline report has meaningful stats

## Summary

The PRD is the single source of truth. When in doubt, check the PRD. Do not redesign the scoring model, change the pricing, or rewrite the strategy. Just build what's specified. The senior review already verified alignment with existing infrastructure.

Quick-Reference: File Paths

If the new server uses different paths (e.g., Linux), adjust these:

RolePath
PRD (master plan)solanasis-docs/playbooks/VC_Pipeline_PRD_2026-03-22.md
Strategy playbooksolanasis-docs/playbooks/solanasis-investor-list-vc-ecosystem-outbound-playbook-handoff-2026-03-20.md
Voice profilesolanasis-docs/solanasis-voice-profile.md
Cold outreach rulessolanasis-docs/playbooks/Manual_Cold_Outreach_Cheat_Sheet.md
fCTO pipeline (fork source)solanasis-scripts/fcto-pipeline/ (8 .py files)
Foundation tests (fixture pattern)solanasis-scripts/foundation-pipeline/tests/conftest.py
Foundations page (landing page fork)solanasis-site/src/pages/for/foundations.astro
Output directorysolanasis-scripts/vc-pipeline/ (to be created)
Daily briefs outputsolanasis-docs/daily-outreach/YYYY-MM-DD-vc.md
Short URL API guidesolanasis-docs/operations/short-io-api-guide.md
Short URL tracking logsolanasis-docs/operations/short-url-tracking-log.md

Graph View