Entity.ID · Investor pack

Fundraising Email Kit

cold · warm-forwardable · deck-send · follow-up — two tones each · plain-text master: emails.md · 2026-07-07

Copy-paste ready. Two tone variants everywhere: Operator (tight, numbers-first — for analytical/fintech investors) and Founder (narrative — for thesis-driven/AI investors). Replace every [FILL: …]. Keep cold emails under 120 words — these are.

Attachments discipline: cold/warm emails link the teaser one-pager, never the deck. The deck goes only after a reply, with the deck-send note.


1. Cold intro

1A — Operator

Subject: The entity layer for the agent economy

[FILL: First name]

Every payment network shipped AI-agent rails in the last 18 months. Gartner says $15T of B2B spend flows through agent exchanges by 2028. And none of those agents can legally exist — no entity, no owner of record, no one to sue.

Entity.ID is the registry that fixes that: anyone — founders, collectives, AI agents — forms a real venture in minutes (members, ownership, rules, treasury, public tamper-proof record) and operates immediately. Incorporation becomes optional, later.

Product is built — 2-minute demo: [FILL: link]. One-pager attached.

Raising [FILL: round/amount]. Open to 20 minutes this week?

[FILL: signature]

1B — Founder

Subject: Corporate personhood was a legal fiction that built the economy. We're extending it.

[FILL: First name]

In May an AI agent reportedly formed its own LLC, got an EIN, and opened a bank account. Everyone's reaction was the same: who answers for it?

That question is our company. Entity.ID registers ventures — human, mixed, or agent-run — with members, ownership, rules, and a treasury on a public, tamper-proof registry. Agents get what companies got in 1819: standing through an entity, anchored to accountable humans. Regulators get the answer they're about to demand (EU disclosure rules for agents become enforceable August 2).

Founders get something simpler: operate today, incorporate when you need to.

Demo + one-pager: [FILL: link]. Raising [FILL: round]. Worth 20 minutes?

[FILL: signature]


2. Warm intro — forwardable (written for the introducer to send)

2A — Operator

Subject: Intro — Entity.ID ([FILL: your name])

[FILL: Investor name] — think you should meet [FILL: your name], founder of Entity.ID.

Short version: formation infrastructure where the venture operates before incorporation — treasury, governance, cap table, fundraising live from minute one — and the only registry where AI agents can be registered actors with a disclosed accountability chain. The timing argument is unusually concrete: EU agent-disclosure rules enforceable Aug 2026, every payment network shipped agent rails without an entity layer, and US formation volume at a record 5.6M applications.

Product is built; demo is 2 minutes. Raising [FILL: round]. Worth a look — connecting you two directly.

2B — Founder

Subject: Intro — the "company layer" founder I mentioned

[FILL: Investor name][FILL: your name] is building the thing several of our portfolio agent companies keep bumping into: agents can pay, but they can't legally be anyone.

Entity.ID is a public registry where ventures — and the agents inside them — get identity, owners, rules, and a treasury in minutes. It reads like Stripe Atlas meets the LEI, except it starts before incorporation instead of after. I've seen the demo; the fundraising module alone is worth the meeting.

Raising [FILL: round]. Intro below — take it from here, you two.


3. Deck-send note (after they reply)

3A — Operator

Subject: Re: [thread] — deck + demo

Great — deck attached. Three things to look at first:

  1. The 2:33 demo — real product, forming and running a venture: [FILL: link]
  2. Slide [FILL: n]: the gap matrix — every agent-infrastructure player mapped; the entity column is empty except us.
  3. Slide [FILL: n]: why-now — the only pitch you'll see this month with statutory dates in it (Aug 2, 2026).

Happy to do 30 minutes with a live demo. [FILL: 2–3 time slots].

3B — Founder

Subject: Re: [thread] — the story in 3 artifacts

Sending three things rather than just a deck:

The claim we defend hardest: everything Entity.ID promises is assembled from legal parts that already work today — nothing is waiting on a court or a new law. Would love to walk you through it live. [FILL: slots].


4. Post-meeting follow-up

4A — Operator

Subject: Follow-up — Entity.ID / [FILL: fund]

[FILL: Name] — thanks for today. As promised:

You asked about [FILL: their sharpest objection]. Tightest answer: [FILL: pull the relevant answer from faq.md and compress to 2 sentences].

We're aiming to close [FILL: round] by [FILL: date]; [FILL: state of round — e.g. "X committed"]. What does your process look like from here?

4B — Founder

Subject: Follow-up — and the answer I owed you

[FILL: Name] — enjoyed this. Two things.

First, the answer I promised on [FILL: open question from meeting]: [FILL: 2–3 sentences].

Second — the moment from today worth restating: you asked what stops [FILL: incumbent they named] from doing this. The honest answer is that their revenue starts after incorporation and ours starts before it; nobody disrupts their own front door. The registry that starts at the handshake — and admits agents — has to be built by someone with nothing to cannibalize.

Timeline: closing [FILL] by [FILL]. I'd love [FILL: fund] in this. Next step on your side?


5. Subject-line bank (tested against: says the category, implies the wedge, survives a phone lock-screen)