The AI Startup Cold Email Kit
1. Key Themes
Theme: Effective cold outreach starts with a problem you have personally touched, so the recipient has to imagine very little
Prior hands-on use makes the ask credible
Elliot's email worked because he had already used the product for a real client task and hit a real limitation, which gave Lovable something concrete to react to.
"Elliot Lindberg emailed Lovable with a problem he had already run into: connecting a client's website to Shopify."
"The useful part is how little the recipient had to imagine. Elliot had used the product for a real task. He could explain where it broke and propose work he wanted to do."
The outreach itself delivers value even if rejected
Product feedback from a real user is useful on its own, which lowers the recipient's cost of engaging.
"The email contains something valuable even if the company passes on him: feedback from someone who tried to use the product for a customer."
Role-specific proof-of-work formats
The author translates the "touch the problem first" principle into tailored deliverables by role.
"For an AI engineering role, I would adapt this with a small reproducible example of a failure. For a product role, I would show where a user gets stuck and a proposed acceptance test. A commercial candidate could bring a sample account brief built from public information."
"Keep the work small enough that you can explain every decision. A focused example gives the team a place to begin assessing your judgment."
Theme: Design outreach for easy routing and a low-friction handoff
Brevity and a scannable structure let the recipient forward the message
Niraj Pant's short internship request to Evan Spiegel drew a reply that thanked him for being brief and copied Snapchat's lead recruiter.
"Niraj Pant sent Evan Spiegel a short internship request in 2014. The visible reply thanks him for being brief and copies Snapchat's lead recruiter."
"Pant makes his experience easy to scan and finishes with an explicit internship request. Spiegel can route the email with a short reply."
The forwardability test
A practical check for any outreach draft.
"Could the person forward it to the relevant colleague without writing an explanation of what you want?"
Founder-to-buyer equivalent: scope the ask narrowly
"For an AI startup founder, the equivalent is a narrowly scoped pilot request. Say which workflow you want to test and what the buyer would need to provide. The recipient should be able to tell whether it belongs with them."
Theme: Preparation and qualification matter more than the template
The gap between an example and a useful email is research
"The gap between an interesting example and a useful email is the preparation. You need a recipient whose work fits your request, plus evidence that supports what you say."
The tooling emphasizes qualification and measuring useful outcomes
The paid kit's structure signals what the author considers essential: gating prospects, scheduled follow-ups, and distinguishing replies from real progress.
"The editable XLSX outreach workbook, with qualification gates, follow-up review dates and a dashboard that separates replies from useful next steps."
2. Contrarian Perspectives
Treat famous cold-email success stories as unreliable predictors of your own results
Against the typical genre of "this one email changed everything," the author explicitly warns about survivorship bias.
"One caveat: these are selected success stories. They show what people sent, and they say nothing about your likely reply rate."
Supporting evidence: the Spiegel example is labeled as lacking outcome evidence.
"Historical email reproduced in Next Play's collection. The screenshot establishes a recruiter handoff; it provides no evidence of an offer."
The scarce asset in outreach is the recipient's imagination, not the sender's polish
Most cold-email advice focuses on subject lines and copy. Here the thesis is that reducing the recipient's cognitive work (concrete problem, specific dates, explicit ask) matters more.
"He names a real client use case and describes the experience he wished the product had. He also gives exact internship dates, so the founder knows what he is being asked to decide."
Measure useful next steps, not replies
The kit's dashboard design implies that reply rate is a misleading vanity metric.
"a dashboard that separates replies from useful next steps."
3. Companies Identified
Lovable
- Description: AI app-building startup.
- Why mentioned: Case study of a cold email that led to an internship.
- Quotes:
"Elliot Lindberg emailed Lovable with a problem he had already run into: connecting a client's website to Shopify." "In a public post, he later credited that email with getting him into the company at 17."
Snapchat (Snap)
- Description: Social media company.
- Why mentioned: Case study of a short internship request that was routed to the lead recruiter.
- Quotes:
"The visible reply thanks him for being brief and copies Snapchat's lead recruiter."
- Description: E-commerce platform.
- Why mentioned: The integration target in Elliot's email.
- Quotes:
"connecting a client's website to Shopify."
Next Play
- Description: Newsletter/collection of historical emails.
- Why mentioned: Source of the Spiegel/Pant email.
- Quotes:
"Historical email reproduced in Next Play's collection."
The AI Corner (author's publication)
- Description: Newsletter selling AI resources, templates, and community.
- Why mentioned: Publisher; promotes related products (Agent Workforce Kit, AI-Era Fundraising Toolkit) and subscriber perks.
- Quotes:
"$3M+ in perks: credits and discounts from AWS, Google Cloud, Microsoft, Anthropic, Stripe, HubSpot, Notion, ElevenLabs and more"
4. People Identified
- Description: Young developer who joined Lovable via cold email.
- Why mentioned: Primary case study of problem-first outreach.
- Quotes:
"In a public post, he later credited that email with getting him into the company at 17." "Elliot's email is dated March 7, 2025. He shared it publicly in October 2025 and described the outcome himself."
Niraj Pant
- Description: Sent a short internship request to Evan Spiegel in 2014.
- Why mentioned: Example of a scannable, explicit-ask email that was easy to route.
- Quotes:
"Pant makes his experience easy to scan and finishes with an explicit internship request."
Evan Spiegel
- Description: Snapchat co-founder.
- Why mentioned: Recipient who replied briefly and looped in a recruiter.
- Quotes:
"Spiegel can route the email with a short reply."
- Description: Author of the post.
- Why mentioned: Source of the framework and the paid kit.
- Quotes:
"That is the starting point I would use for AI startup outreach: give someone a concrete reason to continue the conversation."
5. Operating Insights
Lead with a small, inspectable work sample rather than a pitch
Build something narrow enough that you can defend every decision, and adapt it to the role or buyer.
"Keep the work small enough that you can explain every decision. A focused example gives the team a place to begin assessing your judgment."
Specify dates, scope, and the exact decision you want from the recipient
Remove ambiguity so the recipient knows what they are being asked to decide.
"He also gives exact internship dates, so the founder knows what he is being asked to decide."
Pitch design partners with a narrowly scoped pilot
Name the workflow, state what you need from the buyer, and make it easy to self-qualify.
"Say which workflow you want to test and what the buyer would need to provide. The recipient should be able to tell whether it belongs with them."
6. Overlooked Insights
Cold outreach is a two-sided tool, used by founders to hire as well as by candidates to get hired
The kit is positioned for both sides of the market, which suggests the same principles (proof, specificity, easy routing) apply to evaluating inbound candidates.
"It also covers founders approaching design partners or hiring candidates."
Reply handling and follow-up are treated as first-class parts of the system
The kit includes dedicated materials beyond the initial email, implying that most outreach value is lost without process discipline.
"It also includes follow-ups and reply handling." "12 synthetic cases and expected routes so you can build a small, inspectable work sample."