coldcalls.dev — SDR/BDR Outreach Archive

A community-curated, redacted archive of real cybersecurity SDR/BDR outreach emails.The goal: help SDRs/BDRs learn from real examples (tone, tactics, themes) without exposing personal info.

• 📄 Static site on GitHub Pages
• 🔎 Client-side search (subject, body, tags) + filters (company, category)
• 🕶️ Light/Dark mode
• ✅ Redaction-first contribution flow

---

Live Site

https://coldcalls.dev/

https://koronkowy.github.io/coldcalls.dev/

---

Redaction Policy (Non-Negotiable)

Allowed

• Company names

Remove/Redact

• Names of individuals (sender or recipient)
• Email addresses, phone numbers
• LinkedIn/Calendly/booking links
• Any direct contact details, mailto:, etc.

Replace disallowed items with [REDACTED].

Submissions containing PII will be rejected.

---

Quickstart (Local)

1. Clone the repo.
2. Ensure you have this structure:

   coldcalls.dev/
   ├── index.html
   ├── app.jsx
   └── data/
       └── emails.json
   

3. Open index.html directly in a browser (double-click) or via a tiny static server:

   python3 -m http.server 8080
   # then visit http://localhost:8080/

No build step needed. React and Tailwind are loaded via CDN/ESM.

---

Deploy (GitHub Pages)

1. Push to main.
2. Settings → Pages
   • Source: Deploy from a branch
   • Branch: main (/root)
3. Your site will publish at:

   https://<your-username>.github.io/coldcalls.dev/
   

---

Data Schema

All examples live in data/emails.json as a flat array:

{
  "id": "string-unique",
  "company": "Acme SecOps",
  "category": "Pentesting | Training | MSSP | SOAR | SIEM | CTI",
  "date": "YYYY-MM-DD",
  "subject": "Short subject",
  "body": "Plain text body with [REDACTED] where needed.",
  "tags": ["optional", "keywords"]
}

Tips:

• Keep date in ISO format (YYYY-MM-DD)
• Use concise, realistic subject lines
• Use tags for themes (“pricing”, “free-trial”, “phishing”, “cloud”, etc.)

---

Contributing

We accept contributions via Pull Requests or by opening an Issue with the redacted content.

PR Guidelines

1. Redact PII (see policy above).
2. Add your entry/entries to data/emails.json.
3. Ensure valid JSON (no trailing commas).
4. Use clear tags and the closest category:
   • Pentesting, Training, MSSP, SOAR, SIEM, CTI.

Issue Submissions

• Use the “Submit an outreach email” issue template (if enabled).
• Paste only the redacted text content.

---

Repo Structure

.
├── index.html          # Root HTML, loads app.jsx via ESM
├── app.jsx             # React UI (fake browser, filters, dark mode)
└── data/
    └── emails.json     # Redacted examples (the “database”)

Optional (recommended):

.github/
  ├── ISSUE_TEMPLATE/submit_email.yml   # Redaction checklist for contributors
  └── PULL_REQUEST_TEMPLATE.md          # Merge checklist
scripts/
  └── pii-check.mjs                     # Simple PII pattern blocker (emails, phones, etc.)
.github/workflows/validate.yml          # CI to run the PII checker on PRs

---

Roadmap / Ideas

• Fuzzy search with boosting (e.g., MiniSearch)
• Trend views (common phrases, call-to-actions, value props)
• Faceted filters (e.g., “free trial”, “ROI claim”, “calendar link”)
• Tagging guide / taxonomy suggestions

---

Credits

Created by the community for the community. Curated by @koronkowy. Please be kind: redact responsibly and keep it useful for SDRs/BDRs learning the craft.