AileronBusinessSecrets
Outreach Templates

Four messages, tuned to channel.

Generic cold opens convert below 2%. Anchored ones convert higher. Each variant below is anchored on something the recipient already did or someone they already trust. Copy, customize the bracketed fields, send.

Jump to templates Voice rules Recruiting list
Voice rules (apply throughout)
  • No em-dashes. Use commas, periods, parens, colons.
  • No "it's not just X, it's Y". Pick one.
  • One unique thought per sentence. Tight beats clever.
  • Past behavior, not prediction. Replace every "would you" with "did you".
  • Don't promise features. Every "we could build that" is debt.
  • Don't lead with architecture. Shell mediation and PTY approvals belong nowhere in these messages.
Variant 1 — Warm intro
Anchor: The introducer
Channel: Founder / investor network
Subject line
{Introducer} suggested I reach out
Body
Hi {Name},

{Introducer} suggested we connect. They thought you'd have direct opinions on something I'm working on.

I'm running discovery on how organizations handle the operational side of agents acting on consequential systems: credentials, approvals, audit. Looking for 30 minutes to hear what you've tried and what broke.

Aileron is my bet on this layer. I'd rather learn from what's worked than ship my guesses.

Not a pitch. No slides. If 30 is a lot, 20 minutes is plenty. Calendly: {link} or just suggest a time.

Appreciated.

S,
ALR
Operator notes
  • Anchor: Lead with the introducer's name in line one. That is the entire reason this opens.
  • Past behavior: "What you've tried and what broke" is recountable. Avoid "would you find value in".
  • Friction-reducer: The 20-minute fallback lowers the bar without sounding desperate.
Variant 2 — Community post
Anchor: A specific past behavior, not a pitch
Channel: MLOps Community Slack, Rands Slack, AI Engineering Discord, r/devops
Subject line
Anyone giving agents access to consequential systems: 30 min
Body
Doing discovery on agents that act on consequential systems. Looking for 30 min with people who have shipped this, not internal demos.

Three questions I'm chasing:

1. The last time someone on your team did this. What happened.
2. What you used for credentials, approvals, audit.
3. What you tried first that you ended up rejecting.

30 minutes. Not selling anything. I'll share what I'm hearing from the other conversations in return.

Aileron is my bet on the layer for credentials, approvals, audit. I'd rather learn from what's worked than ship my guesses.

DMs open, or grab a slot: {link}

Appreciated.

S,
ALR
Operator notes
  • Anchor: "Have shipped this, not internal demos" filters out tire-kickers in line one. The subject's "consequential systems" frames the same test in the recipient's language. Anyone whose agent doesn't touch a system that matters self-deselects.
  • Past behavior: Every numbered prompt is a recall question. No future-tense asks.
  • Friction-reducer: The "share what I'm hearing" reciprocity is what converts in community channels.
  • Format note: In Slack/Discord this is the post body. The "subject" is the thread title or first line.
  • Mod policy: Check community rules before posting. MLOps Community Slack and Rands Slack require mod pre-approval. Reddit downvotes self-promotion fast, so frame as research. If a channel flags the company name, substitute "I'm building something in this space" for the Aileron line.
Variant 3 — Cold to job-signal company
Anchor: A public AI / agent role they posted or feature they launched
Channel: LinkedIn DM / cold email
Subject line
Question about {company}'s {role or feature}
Body
Hi {Name},

Saw {company} {posted the Senior Platform Engineer (AI Infra) role | shipped {feature}} ({link to posting or launch}). It caught my attention because I'm focused on agents doing real work, not just demos.

Aileron is my bet that there's a missing infrastructure layer for credentials, approval workflows, and auditing. I'd rather build it to solve real problems than imagined ones. I'd most like to hear: what you've tried, what got in the way, what you're still stuck on.

Worth 15 minutes? No slides. In return I'll share the themes I'm hearing across the other conversations. Happy to suggest times, or grab one here: {link}.

Appreciated.

S,
ALR
Operator notes
  • Anchor: Subject names the specific role or feature; body links to it. Both anchors carry weight on a cold channel. Without them you're back to generic ("saw your AI work") and conversion collapses.
  • Founder honesty: "Aileron is my bet" is the rare permission to be candid. Keep it. Don't soften to "we believe" or "we're building".
  • Past behavior: "What you tried before landing on your current setup" is the load-bearing ask. Avoid asking about plans.
  • Channel note: On LinkedIn, the subject becomes the first line of the DM. On email, it stays a subject.
  • Realistic conversion: 2–4%. Build a list of 100 for ~3 conversations from this channel.
Variant 4 — AI-mature buyer
Anchor: The public incumbent they adopted
Channel: LinkedIn DM / cold email
Subject line
Adopting {Incumbent}: 15 minutes on what you've seen
Body
Hi {Name},

I saw your team adopted {incumbent}. That kind of call is what I'm trying to learn from.

Aileron is my bet that the missing piece sits above any one vendor's slice: policy, credentials, audit, and vendor-neutral freedom to move between frontier labs and hyperscalers. I'd rather build it around what people have hit than what I imagine. I'd most like to hear: what {incumbent} covers cleanly, where it stops short, what you're still building yourself.

Worth 15 minutes? No slides. In return I'll share the themes I'm hearing across peer companies. Say the word and I'll suggest some times, or grab one here: {link}.

Appreciated.

S,
ALR
Operator notes
  • Anchor: "I saw your team adopted [incumbent]" is the anchor for this audience. Their public adoption proves AI fluency and budget, that's all you need. Resist filling in "for [specific surface]" unless you've verified the scope; wrong-specific undoes the anchor.
  • Founder honesty: "Aileron is my bet" is the rare permission to be candid. Keep it. Don't soften to "we believe" or "we're building".
  • Vendor neutrality: These buyers are NOT lost-prospects. They bought one slice and run many other agent surfaces. The pitch is the cross-cutting layer.
  • Examples: Anthropic Managed Agents (Notion, Atlassian, Asana, Sentry, Pendo, Zapier), Cognition/Devin (Nubank, Visma, Dell, Cisco), Composio/LangSmith (11x, C.H. Robinson).
Realistic conversion

To get 30 conversations, send around 150

Warm intro
~50%

Highest reply rate. Lowest selection bias.

Community post
~5%

Post once, watch the DMs. Don't pitch in-thread.

Cold (job signal)
2–4%

Anchored on a public role posting or feature launch.

AI-mature buyer
3–6%

Warmer than greenfield. Adoption proves fluency and budget.