biz: add outreach-templates.md for Operation Get A Job

operation-get-a-job/outreach-templates.md

@@ -0,0 +1,216 @@
+# Outreach Templates
+
+## How to Use These Templates
+
+- Replace everything in [BRACKETS] with your specific details
+- Keep messages concise — busy people don't read walls of text
+- Always lead with value, not credentials
+- Follow up once after 3-5 days if no response, then move on
+- Track all outreach in a spreadsheet (date, platform, response, status)
+
+---
+
+## Template 1: Upwork Proposal
+
+**Use for:** Responding to job postings related to AI agents, DevOps, automation, LLM infrastructure
+
+---
+
+Hi [CLIENT NAME],
+
+I read your posting about [SPECIFIC REQUIREMENT FROM JOB POST]. This is exactly what my firm does day in, day out.
+
+We're a small engineering firm that runs a fleet of five autonomous AI agents in production. Not demos — real agents running as systemd services, shipping code to a 43-repo forge, executing 15-minute autonomous work cycles 24/7. We built the orchestration framework (Hermes), the security layer, and the local LLM inference stack ourselves.
+
+For your project specifically:
+
+- [SPECIFIC THING THEY NEED #1] — We've built [RELEVANT THING YOU'VE DONE]
+- [SPECIFIC THING THEY NEED #2] — We can deliver this using [YOUR APPROACH]
+- [SPECIFIC THING THEY NEED #3] — Our timeline estimate is [X WEEKS]
+
+I'd suggest a [STARTER/PROFESSIONAL/CUSTOM] engagement at [$PRICE] with [TIMELINE]. Happy to do a 30-minute call to scope it properly.
+
+Portfolio: [YOUR PORTFOLIO URL]
+
+Best,
+Alexander Whitestone
+Whitestone Engineering
+
+---
+
+## Template 2: LinkedIn Direct Message
+
+**Use for:** Cold outreach to CTOs, VPs of Engineering, Heads of AI/ML at startups (Series A-C)
+
+---
+
+Hi [FIRST NAME],
+
+I noticed [COMPANY] is [SPECIFIC OBSERVATION — hiring for AI roles / launching an AI feature / scaling infrastructure]. Congrats on [RECENT MILESTONE IF APPLICABLE].
+
+Quick context: I run an engineering firm with a fleet of autonomous AI agents that build production infrastructure. We handle agent deployment, security hardening, and automation for companies that want AI systems that actually work in production, not just in demos.
+
+We recently [RELEVANT ACCOMPLISHMENT — e.g., "deployed a multi-agent fleet with 3,000+ tests and local LLM inference" or "built a conscience validation system for AI safety"].
+
+Would it be useful to chat for 15 minutes about [SPECIFIC PAIN POINT YOU THINK THEY HAVE]? No pitch — just want to see if there's a fit.
+
+— Alexander
+
+---
+
+## Template 3: Twitter/X DM or Reply
+
+**Use for:** Engaging with people posting about AI agent challenges, DevOps pain, or LLM infrastructure problems
+
+---
+
+### Version A: Reply to a post about AI agent problems
+
+[THEIR NAME] — we solved this exact problem. We run 5 autonomous agents in production (systemd services, 15-min burn cycles, persistent memory). The key insight was [SPECIFIC TECHNICAL INSIGHT RELEVANT TO THEIR POST].
+
+Happy to share our approach if useful. We built an open orchestration framework that handles [RELEVANT CAPABILITY].
+
+---
+
+### Version B: DM after engaging with their content
+
+Hey [FIRST NAME] — been following your posts on [TOPIC]. Really resonated with your point about [SPECIFIC THING THEY SAID].
+
+We're running a production fleet of AI agents and have solved a lot of the problems you're describing. Built our own framework (Hermes) for agent orchestration, security, and multi-platform deployment.
+
+Not trying to sell anything — just think there might be useful knowledge exchange. Down to chat?
+
+---
+
+### Version C: Cold DM to potential client
+
+Hey [FIRST NAME] — saw [COMPANY] is working on [WHAT THEY'RE BUILDING]. My firm builds production AI agent infrastructure — fleet orchestration, local LLM stacks, agent security. We run 5 agents 24/7 on our own infra.
+
+Would love to show you what we've built. Might save your team months. 15 min call?
+
+---
+
+## Template 4: Discord Community Post / DM
+
+**Use for:** AI builder communities, DevOps communities, indie hacker communities
+
+---
+
+### Version A: Community post (value-first)
+
+Been running a fleet of 5 autonomous AI agents in production for a while now, wanted to share some lessons learned:
+
+1. **Persistent memory matters more than model quality.** An agent with good memory and a decent model outperforms a genius model with no context.
+
+2. **Security can't be an afterthought.** We built a conscience validation layer after discovering [VAGUE REFERENCE TO REAL INCIDENT]. Now every agent action goes through guardrails.
+
+3. **Local inference is viable for most tasks.** We run Gemma via Ollama for [X]% of agent operations. Cloud APIs are the fallback, not the default.
+
+4. **Systemd > Docker for single-machine agent fleets.** Hot take, but the simplicity wins when you're managing 5 agents on one box.
+
+Full system: 43 repos, 3,000+ tests, multi-platform gateway (Telegram/Discord/Slack), webhook CI/CD.
+
+Happy to answer questions or go deeper on any of these.
+
+---
+
+### Version B: DM to someone asking for help
+
+Hey! Saw your question about [THEIR QUESTION]. We've built exactly this — [BRIEF DESCRIPTION OF YOUR RELEVANT SYSTEM].
+
+The short answer: [HELPFUL TECHNICAL ANSWER].
+
+If you want, I can share more details about our setup. We also do this professionally if you ever need hands-on help deploying something similar.
+
+---
+
+## Template 5: Direct Cold Email
+
+**Use for:** Targeted outreach to companies you've researched that have a clear need
+
+---
+
+**Subject:** [COMPANY]'s [SPECIFIC CHALLENGE] — solved it, can show you how
+
+Hi [FIRST NAME],
+
+I'm Alexander Whitestone, principal at Whitestone Engineering. We build production AI agent infrastructure — the kind that runs 24/7, ships real code, and doesn't break.
+
+I'm reaching out because [SPECIFIC REASON — e.g., "I saw your job posting for a platform engineer to build AI agent tooling" / "your blog post about scaling LLM operations mentioned exactly the problems we solve" / "a mutual contact mentioned you're building an AI agent product"].
+
+**What we've built (and can build for you):**
+
+- A fleet of 5 autonomous AI agents running as systemd services, completing 15-minute autonomous work cycles
+- Custom orchestration framework with persistent memory, skills system, and multi-platform gateway
+- Local LLM inference stack (zero external API dependency for core operations)
+- Agent security layer with jailbreak resistance and conscience validation (3,000+ tests)
+- Self-hosted forge with 43 repos and webhook-driven CI/CD
+
+**Why this matters for [COMPANY]:**
+
+[2-3 sentences about how your capabilities map to their specific needs. Be concrete.]
+
+I'm not looking to send you a generic pitch deck. I'd rather spend 20 minutes on a call understanding your specific situation and telling you honestly whether we can help.
+
+Available [DAY/TIME] or [DAY/TIME] this week. Or just reply with what works.
+
+Best,
+Alexander Whitestone
+Principal, Whitestone Engineering
+[EMAIL]
+[PHONE — optional]
+[PORTFOLIO URL]
+
+---
+
+## Follow-Up Templates
+
+### Follow-Up #1 (3-5 days after initial outreach)
+
+Hi [FIRST NAME],
+
+Following up on my note from [DAY]. I know inboxes are brutal.
+
+The one-line version: we build production AI agent infrastructure and I think we can help [COMPANY] with [SPECIFIC THING].
+
+Worth a 15-minute chat? If not, no worries — happy to stay in touch for when the timing is better.
+
+— Alexander
+
+---
+
+### Follow-Up #2 (7-10 days after Follow-Up #1, final attempt)
+
+Hi [FIRST NAME],
+
+Last note from me on this — don't want to be that person.
+
+If [SPECIFIC CHALLENGE] is still on your radar, we're here. If the timing isn't right, totally understand.
+
+Either way, I write about AI agent operations occasionally. Happy to share if that's useful.
+
+Best,
+Alexander
+
+---
+
+## Outreach Tracking Spreadsheet Columns
+
+| Date | Platform | Contact Name | Company | Message Type | Response? | Follow-Up Date | Status | Notes |
+|------|----------|-------------|---------|-------------|-----------|----------------|--------|-------|
+| | | | | | | | | |
+
+### Status Options
+- Sent
+- Responded — Interested
+- Responded — Not Now
+- Responded — Not Interested
+- Meeting Scheduled
+- Proposal Sent
+- Won
+- Lost
+- No Response
+
+---
+
+*Remember: outreach is a numbers game. Aim for 10 quality touches per week minimum. One in ten will respond. One in three responses will take a meeting. One in three meetings will become a client. That means ~100 outreach messages to land ~1 client. Adjust volume accordingly.*