# Outreach drafts

Cold-email drafts and follow-up plans for Nobulex's first carrier, regulator, and standards-body contacts. These are *drafts*, not sent emails — actually sending them is the next operational move.

Each draft includes:

1. **Context** — why this contact, why now, what the empirical question is
2. **The ask** — what a successful reply looks like
3. **The draft email** — actual text, ready to copy and send
4. **Notes** — design choices in the draft, things to know before sending
5. **Likely objections and responses** — anticipated pushback
6. **Follow-up cadence** — when to follow up, when to stop

## Targets

| File | Target | Type | Objective |
|---|---|---|---|
| `armilla-karthik-ramakrishnan.md` | Karthik Ramakrishnan (CEO, Armilla AI) | Buyer / design partner | Premium-discount pilot tied to bilateral receipt issuance |
| `munichre-michael-von-gablenz.md` | Michael von Gablenz (Head of Insure AI, Munich Re) | Validation test | Falsifiable underwriter-signal test: would aiSure price bilateral-receipt insureds differently? |
| `agntcy-vijoy-pandey.md` | Vijoy Pandey (GM, Outshift by Cisco; AGNTCY) | Standards / partnership | Composition of AGNTCY identity with Nobulex evidence-of-record |

## Editorial principles

1. **No template language.** Each draft is custom; the contact will recognize a template the moment they see one.
2. **Single ask per email.** Buyer pitch asks for a 25-minute call. Validation test asks for a single sentence. Standards email asks for a design conversation. The asks are different.
3. **Cite back to the contact's own words.** Karthik's "post-loss debates" quote, Vijoy's "community ownership, not vendor control" — these signal that the email was written for the specific person, not blasted to a list.
4. **One link, in context.** The observatory page is the proof artifact. No additional attachments, no decks, no follow-up materials.
5. **Length: ~250–350 words.** Long enough to make the case, short enough to read on a phone screen between meetings.
6. **No founder age in the cold-email phase.** If it comes up in a reply or a call, it comes up; nothing changes. The email is about the artifact.

## Follow-up policy

If the contact does not reply:
- Day 7 (or 10 for the underwriter): one short follow-up with no new content
- Day 14 (or 21): log as null result, move on

Chasing further than two follow-ups produces diminishing returns and damages the brand. The artifact is in the public record; future warm introductions (via investors, advisors, mutual contacts) will surface it again.

## What to do after a positive reply

| Reply type | Next step |
|---|---|
| "Let's talk" → call accepted | Send a 3-bullet agenda 24h before; prepare 2 minutes of opener, then listen for 23 minutes |
| One-sentence answer | Acknowledge briefly; ask one follow-up; do not push for a call yet |
| Forwarded to colleague | Treat colleague as new primary; cite the introduction |
| "Not interested" | Reply: "Thank you. May I send you Issue 010 if the data converges?" — keeps the door open without burning the contact |

## What to do after every send

Log the send in a separate spreadsheet or text file:

```
Date sent | Recipient | Channel | Reply received | Reply date | Outcome
```

Track the conversion rate honestly. The point of cold outreach is to learn the response rate, not to assume one. If 0 of 3 sends produce replies, the artifact (the observatory) is not yet sharp enough or the contacts are wrong. If 2 of 3 produce replies, the thesis is empirically grounded and the company has shifted from "documented" to "validated."
