Enovari Cold Outreach Email Toolkit
Table of Contents
0 items1A. AI/Tech Podcast Pitch
7 items1.
AI has amnesia -- I built the fix
2. The missing layer in AI: persistent memory (guest pitch)
3. Why your AI assistant forgets everything -- and what I built about it
4. Guest pitch: solo founder solving AI's memory problem
5. MCP, memory, and the future of AI assistants (guest topic)
6. What if AI never forgot? I built that. (guest pitch)
7. The infrastructure nobody is building: AI memory (guest topic)``
Hi [Host First Name],
I've been listening to [Podcast Name] since [specific episode or timeframe --
e.g., "your episode with Simon Willison on LLM tooling"]. [One sentence about
what you liked or learned from that episode.]
I'm [Your Name], solo founder of Enovari -- an AI memory platform that gives
Claude, ChatGPT, and Cursor persistent, structured memory across sessions.
Every AI conversation today starts from zero. Enovari fixes that using the
Model Context Protocol (MCP).
I think your audience would find this interesting because:
AI memory is the infrastructure layer nobody is talking about yet, but
every power user is frustrated by
I built this bootstrapped, no funding, shipping production code solo --
the indie hacker AI story
MCP is about to become the USB port of AI, and most people haven't
heard of it
Happy to talk about the technical architecture, the bootstrapped founder
journey, or the broader question of what happens when AI assistants actually
remember you.
I keep things concise and conversational -- no scripted pitches. Here's a
quick bio and headshot if helpful: [link]
Would any of those angles work for [Podcast Name]?
Best,
[Your Name]
[Your Title], Enovari
https://enovari.ai
````
Hey [Host First Name],
Loved [specific episode] -- especially the bit about [specific detail].
Quick pitch: I'm [Your Name], I built Enovari. It gives AI assistants
(Claude, ChatGPT, Cursor) actual memory that persists across sessions.
MCP-based, bootstrapped, solo founder.
Three angles your listeners might dig:
1. AI's memory problem -- why every conversation starts from zero and
how I fixed it
2. The solo founder grind in AI -- shipping real infrastructure alone
3. MCP as the next big protocol -- and why memory is its killer app
I'm low-maintenance as a guest -- conversational, no script, happy to
go wherever the conversation goes.
Worth a chat?
[Your Name]
https://enovari.ai
````
Hi [Host First Name],
Loved [specific episode] of [Podcast Name].
I built an AI memory platform (Enovari) -- makes Claude/ChatGPT/Cursor
remember across sessions via MCP. Bootstrapped, solo founder.
Would love to come on and talk about why AI memory is the next
infrastructure battle. 30 min, conversational, no script.
Interested?
[Your Name]
https://enovari.ai
``[Host First Name] -- always use first name, never "Dear Host" or "Dear Team" [Podcast Name] -- reference it at least twice [Specific episode or timeframe] -- MUST be a real episode; this is the credibility signal The "why your audience" bullets -- adjust emphasis based on whether the show focuses on technical deep dives, founder stories, or product trends
Tuesday or Wednesday, 9-11 AM in the host's local timezone Avoid Mondays (inbox overload) and Fridays (weekend mindset)
1st follow-up: 5 business days later 2nd follow-up: 10 business days after original 3rd follow-up: 20 business days after original (final)
1B. Startup/Indie Hacker Podcast Pitch
7 items1.
Bootstrapped AI SaaS, solo founder, $0 raised (guest pitch)
2. From side project to paying customers -- solo AI founder story
3. I built an AI memory platform alone. Here's what I learned.
4. Guest pitch: the unglamorous reality of solo AI SaaS
5. $19.99/mo AI product, no co-founder, no funding -- real numbers
6. Zero funding, one founder, real revenue -- AI SaaS story (guest pitch)
7. The anti-VC AI startup: bootstrapped, solo, shipping (guest pitch)``
Hi [Host First Name],
[Podcast Name] is one of the few shows that tells honest founder stories
instead of the curated VC version. [Reference a specific episode -- e.g.,
"Your episode with [Guest] about the early revenue grind really resonated."]
I'm [Your Name], solo founder of Enovari. I built an AI memory platform --
it gives AI assistants like Claude and ChatGPT persistent memory across
sessions using the Model Context Protocol. $19.99/month, free trial,
bootstrapped from day one.
Here's what I think would make a good conversation for your audience:
The real numbers. I'm happy to share revenue, user count, churn,
and what actually moves the needle vs. what doesn't. No vanity metrics.
Solo founder mechanics. How I ship a technical AI product without
a team -- what I automate, what I skip, what I've learned the hard way.
The AI SaaS opportunity nobody sees. Everyone's building chatbots
and wrappers. The infrastructure layer -- memory, context, state -- is
wide open and underserved.
Bootstrapping in AI. When everyone around you is raising $10M seed
rounds, choosing the bootstrapped path is a deliberate bet. I can talk
about why and whether it's working.
I respect your time -- happy to do any format (30 min, 60 min, async Q&A).
No PR team, no handler, just a founder who can talk openly.
Interested?
[Your Name]
https://enovari.ai
````
Hey [Host First Name],
Big fan of [Podcast Name] -- [specific episode] hit home for me.
I'm [Your Name]. Built Enovari solo and bootstrapped -- it's an AI memory
platform that makes Claude/ChatGPT/Cursor actually remember stuff between
sessions. $19.99/mo, real users, no funding.
Happy to come on and talk real numbers, the solo grind, and why I think
infrastructure (not chatbots) is where the AI opportunity is.
No PR filter -- just honest founder talk. Any format works for me.
[Your Name]
https://enovari.ai
````
Hi [Host First Name],
[Podcast Name] fan here. Your ep with [Guest] was great.
I'm a solo founder, $0 raised, building AI memory infrastructure
(Enovari). Happy to share real revenue numbers and the unfiltered
bootstrapping story on your show.
Worth a conversation?
[Your Name]
https://enovari.ai
``[Specific episode reference] -- critical for indie hacker podcasts; hosts know if you've actually listened The bullet points -- reorder based on the podcast's focus (if they emphasize revenue transparency, lead with numbers; if it's about the craft, lead with solo mechanics) Format offer -- some indie hacker podcasts prefer async or text-first; match their style
Tuesday through Thursday, 10 AM - 12 PM in host's timezone Many indie hacker podcast hosts are in non-US timezones; check first
1st follow-up: 5 business days 2nd follow-up: 12 business days 3rd follow-up: 21 business days (final)
1C. General Business Podcast Pitch
7 items1.
Your AI assistant forgets everything. That's about to change.
2. Guest pitch: the future of AI is memory, not models
3. What happens when AI actually remembers your business (guest topic)
4. The $0-funded AI startup solving a $100B problem
5. Guest pitch: why AI memory matters more than AI models
6. AI that remembers your business -- guest pitch for [Podcast Name]
7. The productivity multiplier nobody is talking about (guest topic)``
Hi [Host First Name],
I caught [specific episode] of [Podcast Name] and [one genuine observation
about the episode -- what stuck with you, what you agreed/disagreed with].
Quick context on me: I'm [Your Name], founder of Enovari. We make AI
assistants remember. Right now, every time you start a new conversation
with ChatGPT or Claude, it has no idea who you are, what you've discussed
before, or what matters to your business. Enovari fixes that.
Here's why this matters beyond tech circles:
Every business using AI is hitting this wall. They invest hours
training an AI on their processes, and the next session it's gone.
Enovari makes that investment persist.
AI memory changes the economics. When your AI assistant remembers
your preferences, your clients, your workflows -- the ROI compounds
instead of resetting.
This is the next infrastructure battle. Models are commoditizing.
Memory and context are where the value shifts next. Your business
audience should understand this before it's obvious.
I can make this concrete and jargon-free. Happy to frame the conversation
around business impact rather than technical architecture -- whatever serves
your audience best.
Worth a conversation?
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Host First Name],
Just listened to [specific episode] -- [genuine reaction].
I'm [Your Name], founder of Enovari. Simple premise: AI assistants forget
everything between sessions. I fixed that. Your AI now remembers your
business, your preferences, your past conversations.
For your audience, the business angle is: AI ROI compounds when context
persists. Right now every company using AI is starting from zero every
morning. That's a fixable problem.
Happy to make it concrete and jargon-free for [Podcast Name].
[Your Name]
https://enovari.ai
````
Hi [Host First Name],
Enjoyed [specific episode] of [Podcast Name].
I built Enovari -- it makes AI assistants remember your business across
sessions. Every company using AI is losing context daily. I fixed that.
Happy to talk about what this means for business productivity on your show.
[Your Name]
https://enovari.ai
``[Specific episode] -- for business podcasts, reference an episode about AI, productivity, or SaaS Industry framing -- if the podcast focuses on a specific industry (real estate, legal, marketing), reframe the "why this matters" bullets around that industry's specific pain points Jargon level -- business podcasts vary wildly; some are MBA-speak, others are conversational. Match their register.
Tuesday or Wednesday, 8-10 AM in host's timezone Business podcast hosts tend to be more traditional in their schedules
1st follow-up: 7 business days 2nd follow-up: 14 business days 3rd follow-up: 25 business days (final)
2A. Guest Post Pitch
7 items1.
Guest post pitch: Why AI memory matters more than model size
2. Article idea for [Publication]: The missing infrastructure layer in AI
3. Guest post: What I learned building AI memory as a solo founder
4. Pitch: "Your AI has amnesia" -- [word count] words for [Publication]
5. Article pitch: MCP and the future of AI context
6. Guest post pitch: The infrastructure layer every AI developer is ignoring
7. Article idea: Why the smartest AI developers are building memory, not models[2-3 sentences describing the core argument. Example: "Every
Solo founder building AI memory infrastructure. I've shipped
``
Hi [Editor First Name],
I read [specific recent article on the publication] and [one sentence
about what made it good or what angle it missed]. That's what prompted
this pitch.
I'm [Your Name], founder of Enovari -- an AI memory platform that gives
AI assistants persistent, structured memory using the Model Context
Protocol. I'd like to write a guest post for [Publication Name].
AI conversation starts from zero. We've accepted this as normal, but it's
actually a solvable infrastructure problem. This article breaks down why
AI memory is the next critical layer, what MCP makes possible, and why
the smartest developers are building memory systems instead of chatbot
wrappers."]
editorial focus. Example: "Your readers are the developers and technical
leaders who will build on this infrastructure. This gives them the
conceptual framework and practical starting point."]
production MCP integrations used with Claude, ChatGPT, and Cursor. I write
clearly about technical topics without dumbing them down.
adjust scope, angle, or format based on your editorial needs.
Want to see a draft or outline?
[Your Name]
https://enovari.ai
[Link to any previous writing samples]
````
Hey [Editor First Name],
Your recent piece on [specific article] was great -- [what you liked].
Got me thinking about a pitch for [Publication Name].
I'm [Your Name], founder of Enovari (AI memory platform). I'd love to
write a guest post on [proposed topic] -- basically, why AI memory is the
infrastructure layer nobody's building yet and what MCP changes about that.
I write tight, technical-but-accessible prose. Can deliver [word count]
words in [timeframe]. Happy to adjust the angle to fit your editorial
calendar.
Want an outline?
[Your Name]
https://enovari.ai
````
Hi [Editor First Name],
Pitch for [Publication Name]: "[Proposed Title]" -- [one sentence angle].
I'm the founder of Enovari (AI memory platform, MCP-based). I can deliver
[word count] words in [timeframe]. Writing samples: [link].
Interested?
[Your Name]
https://enovari.ai
``[Publication Name] -- mentioned at least 3 times [Specific recent article] -- must be real, recent (last 30 days), and relevant to your pitch angle [Proposed article angle] -- this changes completely based on the publication's audience. Technical publication = architecture deep dive. Business publication = market opportunity. Developer publication = practical tutorial. [Word count and timeframe] -- check their typical article length before pitching Writing samples -- link to the most relevant previous piece, not your whole portfolio
Tuesday through Thursday, 9-11 AM in editor's timezone Avoid the first and last week of the month (editorial planning cycles)
1st follow-up: 7 business days 2nd follow-up: 14 business days (offer to adjust the angle) No 3rd follow-up for guest post pitches -- if two follow-ups get silence, they're not interested
2B. Product Feature Pitch
7 items1.
New AI memory platform worth a look? (Enovari)
2. Product for your radar: AI memory that works across Claude/ChatGPT/Cursor
3. Solo founder built persistent AI memory -- product pitch for [Publication]
4. Enovari: the product that makes AI assistants actually remember
5. Worth covering? AI memory platform, bootstrapped, live now
6. Product pitch: persistent AI memory via MCP -- live and shipping
7. For [Publication]: the AI tool that solves context amnesia``
Hi [Writer/Editor First Name],
I've been following your coverage of [specific beat -- e.g., "AI developer
tools" or "bootstrapped SaaS"]. Your piece on [specific article] was
[genuine compliment -- what made it stand out].
I wanted to put Enovari on your radar. It's an AI memory platform I built
that gives AI assistants -- Claude, ChatGPT, Cursor -- persistent,
structured memory across sessions using the Model Context Protocol (MCP).
context, preferences, and accumulated knowledge every time they start
a new session.
Your AI remembers your projects, preferences, past decisions, and
accumulated context -- across sessions and across platforms.
MCP is emerging as the standard protocol for AI tool integration --
Enovari is one of the first production memory systems built on it
Bootstrapped and solo-founded in a space dominated by funded startups
$19.99/month with a free trial -- accessible to individual developers,
not just enterprises
Working today, not vaporware -- live users across Claude, ChatGPT,
and Cursor
I can provide a free account for hands-on testing, answer technical
questions, or do a walkthrough demo. Whatever's most useful for your
process.
Interested in taking a look?
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Writer/Editor First Name],
Your piece on [specific article] was solid -- [what you liked].
Putting Enovari on your radar: it's an AI memory platform I built that
makes Claude, ChatGPT, and Cursor remember everything across sessions.
MCP-based, $19.99/mo, bootstrapped, live now.
The pitch in one sentence: your AI assistant has amnesia, and Enovari
cures it.
Happy to set up a free account for you to test, or do a quick walkthrough.
[Your Name]
https://enovari.ai
````
Hi [Writer/Editor First Name],
For your radar: Enovari (https://enovari.ai) -- persistent AI memory for
Claude/ChatGPT/Cursor via MCP. Bootstrapped, live, $19.99/mo.
Free account available for hands-on testing if you're interested.
[Your Name]
Founder, Enovari
``[Specific beat] -- match their actual coverage area [Specific article] -- reference their work, not the publication generally "Why it's interesting now" bullets -- reorder based on what the writer typically covers. If they write about funding, lead with bootstrapping. If they cover protocols, lead with MCP. Demo offer -- some writers prefer hands-on access; others prefer a guided walkthrough. Offer both.
Wednesday or Thursday, 10 AM - 12 PM in writer's timezone Check if the writer is actively covering AI tools -- if they just published something in the space, send within 48 hours of that article
1st follow-up: 5 business days 2nd follow-up: 12 business days Final: 20 business days (breakup style)
2C. Technical Article Pitch
7 items1.
Technical deep dive pitch: Building AI memory with MCP
2. Article pitch: How structured memory changes AI assistant architecture
3. Technical article idea: MCP-based persistent memory for AI (with code)
4. Pitch: "Building the Memory Layer" -- technical walkthrough for [Publication]
5. Article pitch: Why BM25+vector hybrid search matters for AI memory
6. Technical pitch: production lessons from building AI memory infrastructure
7. Article idea: the architecture of persistent AI memory (code + diagrams)``
Hi [Editor First Name],
I'd like to pitch a technical article for [Publication Name] on building
persistent memory systems for AI assistants using the Model Context
Protocol.
integration (Anthropic, OpenAI, and the broader ecosystem are converging
on it). Memory is the first killer use case, and there's almost no
technical content explaining how to architect it properly.
Memory architecture: why naive "save everything" approaches fail and
what structured memory looks like in practice
MCP integration patterns: how memory connects to Claude, ChatGPT,
and Cursor through a single protocol layer
Hybrid retrieval: combining BM25 keyword search with vector similarity
for high-recall memory queries
Practical tradeoffs: what I learned shipping this in production
(Enovari, https://enovari.ai)
serving real users. This isn't theoretical; I can include architecture
diagrams, code samples, and performance data from a live system.
samples and diagrams. Happy to adjust scope and depth to your editorial
standards.
I have writing samples at [link] if you'd like to see my technical
writing style.
Interested?
[Your Name]
https://enovari.ai
````
Hey [Editor First Name],
Pitch for [Publication Name]: a technical deep dive on building
persistent AI memory with MCP.
I built Enovari (production AI memory platform) and have real architecture
decisions, code patterns, and performance data to share. Covers MCP
integration, hybrid retrieval (BM25 + vector), and why naive approaches
fail.
Can deliver [word count] with code samples and diagrams. Not theoretical
-- all from production.
Want an outline?
[Your Name]
https://enovari.ai
````
Hi [Editor First Name],
Technical article pitch for [Publication Name]: "Building the Memory Layer
for AI Assistants" -- MCP architecture, hybrid retrieval, production
lessons. [Word count] words with code samples.
I built Enovari (https://enovari.ai), a production AI memory platform.
Writing samples: [link].
Interested?
[Your Name]
``Technical depth -- adjust based on the publication. Hacker News-style = more architectural. Dev.to = more tutorial. IEEE/ACM = more formal. "What I'd cover" bullets -- choose the most relevant 3-4 from your full list of possible topics based on what the publication's audience cares about Code samples offer -- only mention this for publications that actually run code in articles
Tuesday or Wednesday, 10 AM - 1 PM in editor's timezone
1st follow-up: 7 business days (offer to send an outline) 2nd follow-up: 14 business days No 3rd follow-up
3A. AI Newsletter Submission
7 items1.
For your radar: AI memory platform using MCP (Enovari)
2. AI tool submission: persistent memory for Claude/ChatGPT/Cursor
3. New AI product worth mentioning: Enovari
4. Submission: Enovari -- AI memory that persists across sessions
5. AI tool your readers should know about
6. Submission: the memory layer AI has been missing (Enovari)
7. New AI dev tool: persistent memory across Claude/ChatGPT/Cursor``
Hi [Newsletter Author First Name],
Love what you're doing with [Newsletter Name]. [Reference a specific
recent edition or tool they featured -- e.g., "The roundup last week on
MCP tools was exactly the kind of curation that saves developers hours
of research."]
Wanted to submit Enovari for your consideration:
Cursor persistent, structured memory across sessions.
sessions. Enovari makes context, preferences, and accumulated knowledge
persist -- so your AI gets smarter over time instead of starting from
zero every conversation.
Works via MCP (Model Context Protocol) -- native integration, not a
hack
Supports Claude, ChatGPT, and Cursor today
$19.99/month with free trial
Bootstrapped, solo founder
Live and serving real users now
memory -- persistent, structured, and portable across Claude, ChatGPT,
and Cursor."
Happy to provide a free account if you want to test it yourself before
featuring it.
Thanks for considering it.
[Your Name]
Founder, Enovari
````
Hey [Newsletter Author First Name],
[Newsletter Name] is a go-to for me -- [specific thing you like about it].
Submitting Enovari for your next edition: it's an AI memory platform
that makes Claude/ChatGPT/Cursor remember across sessions via MCP.
$19.99/mo, free trial, bootstrapped.
One-liner: "Enovari gives your AI assistant persistent memory across
sessions and platforms."
Link: https://enovari.ai
Free account yours if you want to test it first.
[Your Name]
````
Hi [Newsletter Author First Name],
Tool submission for [Newsletter Name]:
Enovari (https://enovari.ai) -- Persistent AI memory for
Claude/ChatGPT/Cursor via MCP. $19.99/mo, free trial.
Free review account available.
[Your Name]
Founder, Enovari
``[Newsletter Name] and [specific recent edition] -- non-negotiable personalization Key details -- reorder based on what the newsletter typically emphasizes (if they love pricing transparency, lead with the price; if they feature technical architecture, lead with MCP) One-liner -- tailor the angle to match the newsletter's typical voice and framing
Send 2-3 days before their typical publication day (if they publish on Tuesday, send Thursday or Friday the prior week) If you can't determine their schedule, send Tuesday morning
1st follow-up: 7 days (timed to arrive before their next publication cycle) 2nd follow-up: 14 days No 3rd follow-up for newsletter submissions
3B. Tech Newsletter Submission
7 items1.
Product submission: Enovari -- persistent AI memory via MCP
2. New dev tool: AI memory that works across platforms
3. For [Newsletter Name]: bootstrapped AI memory platform
4. Submission: the memory layer AI assistants have been missing
5. New tool your readers are going to want
6. Dev tool submission: AI memory that persists across Claude/ChatGPT/Cursor
7. For [Newsletter Name]: MCP-based AI memory -- live and shipping``
Hi [Newsletter Author First Name],
[Newsletter Name] is one of my go-to reads for [what category -- e.g.,
"finding tools I'd never discover otherwise" or "cutting through AI
hype"]. [Optional: reference a specific featured tool or edition.]
Submitting Enovari for your consideration:
Enovari (https://enovari.ai) -- Persistent, structured memory for
AI assistants.
(Model Context Protocol). Stores context, preferences, and accumulated
knowledge in a structured memory system. Your AI retrieves relevant
memories automatically -- no manual copy-pasting context between sessions.
No more re-explaining your codebase, preferences, or project context
every session
Memory persists across platforms -- context from Claude is available
in Cursor and vice versa
Hybrid retrieval (BM25 + vector) means high recall without
irrelevant noise
$19.99/month, free trial, no enterprise sales gauntlet
got tired of AI amnesia.
Free accounts available for review. LMK if you'd like one.
[Your Name]
https://enovari.ai
````
Hey [Newsletter Author First Name],
Love [Newsletter Name] -- [specific thing you appreciate].
Submitting: Enovari (https://enovari.ai) -- persistent AI memory
for Claude/ChatGPT/Cursor via MCP. No more re-explaining your codebase
every session. Hybrid retrieval, cross-platform context, $19.99/mo.
Built solo, bootstrapped. Free review account if you want one.
[Your Name]
````
Hi [Newsletter Author First Name],
Submission for [Newsletter Name]:
Enovari (https://enovari.ai) -- persistent AI memory via MCP.
Works with Claude, ChatGPT, Cursor. $19.99/mo, free trial.
Free account for testing available.
[Your Name]
``Match the newsletter's format -- some want a one-paragraph submission, others want detail. Read their submission guidelines if available. If the newsletter has categories (e.g., "AI Tools," "Developer Productivity," "New Launches"), reference which category Enovari fits.
2-3 days before their publication day If they have a submission form, use the form AND send the email
1st follow-up: 7 days 2nd follow-up: 14 days
3C. Startup Newsletter Submission
7 items1.
Bootstrapped AI startup for [Newsletter Name]: Enovari
2. Solo founder, $0 raised, AI memory product -- submission
3. Startup submission: the anti-VC AI SaaS story
4. For your consideration: bootstrapped AI memory platform
5. $19.99/mo AI product, no funding, real users -- startup story
6. Submission: solo founder vs. the AI giants (bootstrapped, shipping)
7. For [Newsletter Name]: the bootstrapped AI infrastructure play``
Hi [Newsletter Author First Name],
I appreciate how [Newsletter Name] highlights founders building real
businesses, not just fundraising announcements. [Optional: reference a
specific founder or company they featured.]
Here's my story for your consideration:
Enovari (https://enovari.ai) -- I'm a solo founder building an AI
memory platform. It gives AI assistants persistent, structured memory
across sessions and across platforms (Claude, ChatGPT, Cursor).
$0 raised, solo founder, profitable path
$19.99/month, free trial -- building for developers and power users,
not enterprise procurement
Competing in AI infrastructure without the typical $10M seed round
Shipping real product to real users while funded competitors are still
in stealth
AI tool integration. Memory is the first killer app for it. The window
for an indie founder to own this space is open but closing.
where a solo developer builds critical infrastructure with pure execution
instead of capital. Your readers -- founders figuring out whether they
can compete in AI -- would find this either inspiring or instructive.
Happy to share real numbers if that's useful for the feature.
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Newsletter Author First Name],
[Newsletter Name] highlights the founders actually building, not just
fundraising. Love that.
My story: solo founder, $0 raised, built Enovari -- an AI memory platform
for Claude/ChatGPT/Cursor via MCP. $19.99/mo, real users, profitable path.
The angle: competing in AI infrastructure without the $10M seed round.
Shipping while funded competitors are in stealth.
Happy to share real revenue numbers if useful.
[Your Name]
https://enovari.ai
````
Hi [Newsletter Author First Name],
Startup submission for [Newsletter Name]:
Enovari (https://enovari.ai) -- AI memory platform. Solo founder,
$0 raised, bootstrapped, live users. $19.99/mo.
Happy to share real numbers.
[Your Name]
Founder, Enovari
``"The bootstrapped angle" bullets -- match to what the newsletter celebrates. If they love revenue transparency, offer numbers. If they love the grind, emphasize the solo execution. Story framing -- some startup newsletters want the journey narrative. Others want market analysis. Adjust the last paragraph accordingly.
Tuesday or Wednesday, 9-11 AM in author's timezone
1st follow-up: 7 days 2nd follow-up: 14 days # 4. Influencer Outreach Emails
4A. YouTube Creator Pitch
7 items1.
Collab idea: AI memory demo for your channel
2. I built the AI tool your subscribers are going to want
3. Video idea: what happens when AI actually remembers you
4. Free access to AI memory platform for potential video
5. Product demo offer for [Channel Name]
6. Video concept: AI with vs. without memory -- side by side
7. Your next AI tool review: persistent memory for Claude/ChatGPT/Cursor``
Hi [Creator First Name],
Your video on [specific video title] was [genuine, specific compliment --
e.g., "the clearest explanation of MCP I've seen" or "exactly the kind of
no-BS tool review developers need"]. [Optional: mention subscriber count
or engagement as social proof that you've done your homework.]
I built Enovari -- an AI memory platform that makes Claude, ChatGPT, and
Cursor remember everything across sessions. I think it could make a great
video for your channel.
It's the kind of "why didn't this exist before" tool that gets strong
engagement
Live demo potential is high -- you can show the before/after of AI
with and without memory in real time
MCP integration means it slots into the AI workflow your viewers are
already building
Free Enovari account for you (no strings, keep it regardless)
Happy to do a live demo/walkthrough on your schedule
Available for a joint video, interview, or just provide access for
your independent review
No script requirements -- honest review only, say whatever you think
Works with Claude, ChatGPT, and Cursor via MCP.
Want me to set up a free account for you?
[Your Name]
https://enovari.ai
P.S. [Optional: mention a specific use case that aligns with their
content niche -- e.g., "For a coding channel like yours, the killer
feature is that Cursor remembers your entire project context across
sessions."]
````
Hey [Creator First Name],
Your video on [specific title] was great -- [specific thing you liked].
I built Enovari: AI memory for Claude/ChatGPT/Cursor. Makes your AI
remember everything across sessions via MCP. The before/after demo is
pretty compelling on camera.
Free account for you, no strings. Honest review only -- say whatever
you think. Happy to do a walkthrough or just give you access to explore.
Interested?
[Your Name]
https://enovari.ai
````
Hi [Creator First Name],
Loved [specific video]. Quick pitch: I built Enovari -- persistent AI
memory for Claude/ChatGPT/Cursor. Free account for you if you want to
test it for a video. No strings.
https://enovari.ai
[Your Name]
``[Specific video title] -- must be real and recent (ideally last 30-60 days) "Why your audience would care" -- completely rewrite based on the creator's content focus. Coding channel = code context persistence. AI tool reviews = comparison angle. Productivity = workflow improvement. P.S. use case -- this is the highest-impact personalization. Make it specific to their niche. Video format -- match what they actually do. Don't suggest a "live demo walkthrough" to a creator who does scripted essays.
Wednesday or Thursday, 11 AM - 2 PM in creator's timezone YouTube creators often work non-traditional hours; email is better than DM for first contact If they list a business email, use that. If not, use the email in their YouTube "About" section.
1st follow-up: 7 days 2nd follow-up: 14 days (sweeten the offer -- e.g., "happy to hop on a call to walk through the most demo-worthy features") No 3rd follow-up
4B. Twitter/X Influencer DM
4 itemsOption 1: The Direct Approach ``
Hey [Name] -- love your threads on [specific topic]. Built something
you might find interesting: Enovari gives Claude/ChatGPT/Cursor
persistent memory across sessions via MCP. Happy to set you up with
a free account if you want to try it. No strings.
https://enovari.ai
`
Option 2: The Question Hook
`
[Name] -- curious what you think about AI memory as infrastructure.
I built Enovari (persistent memory for Claude/ChatGPT/Cursor via MCP)
and your take on this space would be valuable. Happy to give you free
access to poke around.
`
Option 3: The Value-First Approach
`
Hey [Name] -- saw your tweet about [specific tweet/topic]. Thought
you'd want to know about Enovari -- it's an AI memory platform that
solves exactly that. Works with Claude, ChatGPT, Cursor via MCP.
Free account yours if you want to test it.
https://enovari.ai
``[Specific topic/tweet] -- reference something they posted in the last 7 days Tone -- match their Twitter voice. If they're casual/meme-heavy, be casual. If they're technical and serious, be technical and serious. Length -- shorter is always better for DMs. If you can cut a word, cut it.
Early afternoon in their timezone (1-3 PM) -- that's when DM open rates are highest Engage with their content (genuine likes, replies, retweets) for 1-2 weeks BEFORE sending the DM Never DM someone cold without prior engagement on their content
1st follow-up: 7 days (only if they opened/read the DM but didn't reply) No 2nd follow-up for DMs. If they don't reply to one follow-up, move on.
4D. Free Account for Review Offer
7 items1.
Free Enovari account -- no strings, honest review welcome
2. Complimentary access to AI memory platform (for your review)
3. Would you review Enovari? Free account, no obligations
4. Free access to Enovari -- use it, review it, or just keep it
5. AI memory tool for your honest review
6. Free Enovari access -- honest review only, no scripts
7. Complimentary AI memory platform account (no strings attached)``
Hi [Creator/Influencer First Name],
I'm [Your Name], solo founder of Enovari -- an AI memory platform that
makes Claude, ChatGPT, and Cursor remember everything across sessions.
I'd like to offer you a complimentary account. Here's what I'm NOT
asking for:
No required positive review
No specific posting timeline
No pre-approval of what you say
No obligation to say anything at all
Here's what I AM asking: if you try it and find it genuinely useful,
I'd appreciate an honest mention wherever feels natural to you -- a
tweet, a video, a newsletter mention, a blog post. If you try it and
hate it, I'd rather hear that directly so I can improve.
assistant remembers your context, preferences, and past conversations
across sessions and across platforms.
to Claude/ChatGPT/Cursor via MCP, and your AI starts building memory
immediately.
Want me to set up the account?
[Your Name]
https://enovari.ai
````
Hey [Creator/Influencer First Name],
I'm [Your Name], built Enovari -- AI memory for Claude/ChatGPT/Cursor.
Free account for you. No strings: no required positive review, no
timeline, no script. If you like it, mention it wherever feels natural.
If you don't, tell me why so I can fix it.
Setup takes 2 minutes: https://enovari.ai
Want me to set it up?
[Your Name]
````
Hi [Creator/Influencer First Name],
Free Enovari account for you -- AI memory for Claude/ChatGPT/Cursor.
No strings, no required review. Honest feedback only.
https://enovari.ai
Want me to set it up?
[Your Name]
``The "what I'm NOT asking for" section -- keep this regardless of recipient. It's the trust builder. Platform mention -- if they primarily use one AI tool (e.g., they're a Cursor creator), lead with that platform specifically Where to mention -- tailor the "honest mention wherever feels natural" to their primary platform
Any business day, 10 AM - 1 PM in their timezone Best sent AFTER you've already engaged with their content publicly
1st follow-up: 7 days 2nd follow-up: 14 days (final) # 5. Press/Journalist Pitch Emails
5A. Press Release Email
5 items1.
[PRESS] AI memory platform launches -- makes AI assistants remember across sessions
2. [PRESS] Bootstrapped founder launches persistent AI memory for Claude/ChatGPT/Cursor
3. [PRESS] New: Enovari brings persistent memory to AI assistants via MCP
4. [PRESS] Solo founder ships AI memory infrastructure the giants haven't built
5. [PRESS] Enovari launch: the memory layer AI has been missing
6. [PRESS] AI memory platform live -- bootstrapped, MCP-based, shipping now
7. [PRESS] New AI dev tool: persistent memory across Claude, ChatGPT, Cursor``
Hi [Journalist First Name],
Below is a press release about Enovari, a new AI memory platform. I'm
reaching out because [reason this is relevant to their beat -- e.g.,
"you've been covering AI developer tools extensively" or "your recent
piece on AI infrastructure gaps is directly related to what we've built"].
I'm available for interviews, demos, and to provide additional context
on background. [Phone number] or just reply here.
FOR IMMEDIATE RELEASE
*Enovari Launches AI Memory Platform That Makes Claude, ChatGPT, and
Cursor Remember Across Sessions
Bootstrapped, solo-founded platform uses Model Context Protocol to
give AI assistants persistent, structured memory*
[CITY, STATE] -- [Date] -- Enovari (https://enovari.ai) today launched
its AI memory platform, providing persistent, structured memory for AI
assistants including Anthropic's Claude, OpenAI's ChatGPT, and the
Cursor code editor.
The platform addresses a fundamental limitation of current AI assistants:
every conversation starts from zero. Enovari connects to AI tools via
the Model Context Protocol (MCP), enabling AI assistants to store,
retrieve, and build upon context across sessions and across platforms.
"AI assistants are remarkably capable in a single session but have
complete amnesia between sessions," said [Your Name], founder of
Enovari. "We built the memory layer that makes AI context cumulative
instead of disposable."
Persistent memory across Claude, ChatGPT, and Cursor via MCP
Structured storage with hybrid retrieval (BM25 + vector search)
Cross-platform context -- memory created in one AI tool is accessible
in all supported platforms
Persona system for specialized AI behaviors with dedicated memory
$19.99/month with free trial
Enovari is bootstrapped and solo-founded, competing in AI infrastructure
without venture funding.
The platform is available now at https://enovari.ai.
[Your Name]
Founder, Enovari
[Email]
[Phone]
https://enovari.ai
###
Happy to provide:
Product demo (live or recorded)
Founder interview
Access to the platform for hands-on review
Technical deep dive on the architecture
Background context on the AI memory space
[Your Name]
``[Reason this is relevant to their beat] -- the single most important line in the email. This must be specific and accurate. Quote -- can adjust the founder quote based on the angle most relevant to the journalist's beat "Happy to provide" list -- reorder based on what the journalist typically uses (if they do hands-on reviews, lead with access; if they do interviews, lead with that)
Tuesday or Wednesday, 7-9 AM in journalist's timezone (journalists start early) NEVER send on the same day as major tech news events (Apple keynotes, Google I/O, etc.) If tied to a specific news hook, send the day before or morning of
1st follow-up: 3-4 business days (journalists move fast; follow up sooner) 2nd follow-up: 8-10 business days No 3rd follow-up for press pitches
5B. Story Pitch Template
5 items1.
Story pitch: the solo developer building AI infrastructure the giants won't
2. Story idea: why AI memory is the next platform battle
3. Pitch: the bootstrapped founder competing with OpenAI's memory feature
4. Story: MCP is the USB of AI, and this indie dev built the first killer app
5. Story pitch: what happens when your AI actually knows you
6. Story idea: one developer vs. the AI giants on memory infrastructure
7. Pitch: bootstrapped AI infrastructure in the era of billion-dollar rounds[Your Name], solo founder of Enovari (https://enovari.ai).
``
Hi [Journalist First Name],
I have a story pitch that I think fits [Publication Name]'s coverage of
[their specific beat].
memory platform that does what OpenAI and Anthropic haven't prioritized:
persistent, structured, cross-platform memory for AI assistants.
1. The MCP moment. Model Context Protocol is emerging as the
standard for how AI tools communicate with external systems. It's
the most important AI infrastructure development most people haven't
heard of. Enovari is one of the first production applications built
on it.
2. David vs. Goliath. The AI memory space is expected to attract
massive investment. One solo developer shipped a working product
before the incumbents. Whether that's inspirational or delusional
is an interesting question.
3. The AI context problem is real and unsolved. Every knowledge
worker using AI hits the same wall: "Why doesn't it remember what
I told it yesterday?" This is the story of the person who decided
to fix it.
Full access to the product for your review
Candid interview -- real numbers, real challenges, no PR spin
Technical walkthrough of the architecture
Perspective on the AI memory/context space and where it's heading
I'm building AI memory infrastructure because I believe the value in AI
shifts from model capability to persistent context within the next 2
years.
Is this a story [Publication Name] would want to tell?
[Your Name]
[Email]
[Phone]
``[Their specific beat] -- must match exactly what they cover "Why this is a story right now" framing -- adjust emphasis based on the publication. Business press = market opportunity angle. Tech press = protocol/architecture angle. General press = human interest/David vs. Goliath angle. Timing -- if there's a relevant news hook (MCP announcement, AI memory feature from a competitor, industry report), reference it
Tuesday or Wednesday, 7-9 AM in journalist's timezone Best timed to coincide with a relevant news cycle
1st follow-up: 3-4 business days 2nd follow-up: 8-10 business days No 3rd follow-up
5C. HARO (Help a Reporter Out) / Connectively / Qwoted Response Template
5 itemsUse the format specified in the query platform. If none specified:
[PLATFORM] [Query Topic] -- AI memory platform founder[Your Name] is the founder of Enovari
``
Hi [Journalist First Name],
Responding to your query about [exact topic from the query].
an AI memory platform that gives AI assistants persistent memory
across sessions.
[Direct answer to their specific question -- 2-4 paragraphs max.
Be quotable. Write in complete sentences that can be pulled directly
into an article. Do NOT pitch Enovari here -- answer their question
with genuine expertise.]
[If relevant, one sentence connecting your experience building Enovari
to the credibility of your answer. Example: "Building AI memory
infrastructure has given me direct visibility into how users interact
with AI assistants across hundreds of sessions."]
(https://enovari.ai), an AI memory platform that gives AI assistants
persistent, structured memory across Claude, ChatGPT, and Cursor.
I'm available for follow-up questions at [email] or [phone].
[Your Name]
``The entire response section -- this must be a genuine, expert answer to their question, NOT a product pitch Bio -- keep it to one sentence. The goal is attribution, not advertising. Relevance connection -- only include the "building Enovari gave me visibility" line if it genuinely adds credibility to your answer
IMMEDIATELY. Journalist query responses are time-sensitive. Respond within 2-3 hours of the query posting. First responses get priority -- speed matters more than perfection
No follow-up on journalist query responses. The journalist will reach out if they use your quote.
5D. Embargo Offer Template
5 items1.
[EMBARGO OFFER] Enovari -- AI memory platform launch details
2. Offering exclusive/embargo on AI memory platform launch
3. Embargo: AI memory platform built on MCP launching [date]
4. Exclusive access: AI memory platform launch (embargo available)``
Hi [Journalist First Name],
I'm offering an embargo on [news -- e.g., "the launch of Enovari" or
"a major feature release for Enovari"] ahead of our [launch date/
announcement date].
product access, and an interview window. In exchange, the embargo
lifts at [specific date and time, including timezone]. You'd be free
to publish any time after that.
Full product access starting immediately
30-60 minute founder interview at your convenience
Technical architecture details and product roadmap context
Assets: screenshots, product demo video, founder headshot, logos
to them -- their beat, their audience, their track record covering
similar topics]
Embargo access available: [start date]
Interview window: [date range]
Embargo lifts: [specific date/time/timezone]
Publication: any time after embargo lifts
Interested in the embargo? I can send the full press kit immediately.
[Your Name]
Founder, Enovari
[Email]
[Phone]
``Exclusivity -- decide before sending whether this is exclusive (one journalist) or a timed embargo (multiple journalists, same lift time). Be explicit about which. "Why you specifically" -- this is the key personalization. Journalists accept embargoes from sources they trust for beats they cover. Show you know their work. Timeline -- must be specific. Vague timelines signal amateur PR.
7-14 days before the embargo lift date Tuesday or Wednesday, 8-9 AM in journalist's timezone Never offer embargoes during major news cycles
1st follow-up: 2-3 business days (embargo timelines are tight) If no response to follow-up, offer the embargo to next journalist on list # 6. Partnership Pitch Emails
6A. Integration Partnership Proposal
7 items1.
Integration partnership: Enovari + [Their Product]
2. Adding persistent AI memory to [Their Product] -- partnership idea
3. Partnership proposal: AI memory layer for [Their Platform]
4. [Their Product] + Enovari: making AI context persist
5. Let's give [Their Product] users persistent AI memory
6. Technical integration idea: persistent memory for [Their Product]
7. Partnership: AI memory layer for [Their Platform]'s users``
Hi [Name],
I'm [Your Name], founder of Enovari -- an AI memory platform that
gives AI assistants persistent, structured memory via MCP.
I've been using [Their Product] and I see a natural integration
opportunity that would benefit both our user bases.
[2-3 sentences describing the specific integration. Be concrete.
Example: "Enovari could provide persistent memory for [Their Product]'s
AI features, so users' context and preferences carry across sessions.
This would mean [specific user benefit -- e.g., 'their AI coding
assistant remembers their project architecture, coding style, and
past decisions']."]
A feature your users are asking for (AI context persistence) without
building it internally
Differentiation vs. competitors who reset context every session
Revenue share opportunity on Enovari subscriptions from your user base
Distribution to [Their Product]'s user base
A high-value integration use case
Product validation in [their market segment]
[already supports / could support with minimal integration work]. I can
have a proof of concept ready within [timeframe].
AI memory platform: https://enovari.ai
$19.99/month, free trial
Live users across Claude, ChatGPT, and Cursor
Solo founder, bootstrapped, fast decision-making
Would a 20-minute call to explore this make sense?
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Name],
I'm [Your Name], built Enovari -- AI memory for Claude/ChatGPT/Cursor
via MCP.
Been using [Their Product] and see a clean integration opportunity:
[1-2 sentences on the specific integration idea].
You'd get a feature your users want without building it. I'd get
distribution. Technical lift is low -- MCP-based, and I can have a
POC ready in [timeframe].
Worth a 20-minute call to explore?
[Your Name]
https://enovari.ai
````
Hi [Name],
Integration idea: Enovari (AI memory via MCP) + [Their Product].
Your users get persistent AI context. Technical lift is minimal.
Worth a quick call?
[Your Name]
Founder, Enovari
https://enovari.ai
``[The integration idea] -- this must be specific and technically feasible. Do not pitch a vague "we should integrate." Describe exactly what the integration would look like. "What this gets [Their Product]" -- frame benefits in THEIR terms, not yours Technical feasibility -- research whether they already support MCP or have a plugin/extension system. Reference their specific technical architecture. Revenue share mention -- only include if you're actually willing to offer this
Tuesday through Thursday, 10 AM - 12 PM in their timezone Best sent to a specific person (partnership lead, product lead, CTO for smaller companies), not a generic partnerships@ address if avoidable
1st follow-up: 7 business days 2nd follow-up: 14 business days 3rd follow-up: 21 business days (final, with a new angle or updated value prop)
6C. Co-Marketing Proposal
7 items1.
Co-marketing idea: "Building AI workflows" content series
2. Joint webinar proposal: AI memory + [their category]
3. Content partnership: Enovari + [Their Product]
4. Co-marketing opportunity for [Their Product]
5. Let's create something together: AI workflow content
6. Joint content idea: [Their Product] + Enovari walkthrough
7. Co-marketing: AI power user stack (your product + mine)``
Hi [Name],
I'm [Your Name], founder of Enovari -- an AI memory platform. I have
a co-marketing idea that I think could drive real value for both of us.
Joint webinar/livestream: "Building AI workflows that remember:
[Their Product] + Enovari." We show developers how to build a
complete AI workflow using both products. Live demo, Q&A, shared
audience.
Co-authored content series: A 3-part blog series on "The AI
Power User Stack" -- covering [their product's category], memory
persistence (Enovari), and the full workflow. Published on both
our platforms.
Joint case study: We find a shared user (or create a demo use
case) showing both products working together. Published as a case
study both teams can use.
Our products are complementary, not competitive
We reach each other's audiences with a credibility boost (endorsed
by a product they already trust)
Content has long-tail SEO value for both of us
Low cost, high leverage -- exactly what bootstrapped founders need
Technical writing and demo ability
My audience of AI-forward developers and power users
Willingness to do the bulk of the content creation work
with 2-3 specific concepts fleshed out.
Worth exploring?
[Your Name]
https://enovari.ai
````
Hey [Name],
Co-marketing idea: joint content showing [Their Product] + Enovari
working together. Webinar, blog series, or case study -- whatever
fits your bandwidth.
Our products are complementary, our audiences overlap, and I'll do
the heavy lifting on content creation. Low cost, high leverage.
15-minute call to explore?
[Your Name]
https://enovari.ai
````
Hi [Name],
Co-marketing idea: joint content about [Their Product] + Enovari.
Complementary products, overlapping audiences. I'll do most of the
content work.
Worth a quick call?
[Your Name]
https://enovari.ai
``[Specific co-marketing idea] -- pick ONE primary concept that makes the most sense for their brand and audience. Include 1-2 alternatives. "Why this works" -- if they're also bootstrapped, emphasize the low-cost angle. If they're funded, emphasize audience reach. "What I bring" -- be honest about your actual assets. If you have a small audience, emphasize content quality and effort willingness instead of reach.
Tuesday through Thursday, 10 AM - 12 PM in their timezone
1st follow-up: 7 business days 2nd follow-up: 14 business days No 3rd follow-up for co-marketing proposals # 7. User Outreach Emails
7A. Cold Email to Potential Users (Developers)
7 items1.
Your AI assistant forgets everything. This fixes it.
2. Persistent memory for Claude/ChatGPT/Cursor -- free trial
3. What if your AI remembered your codebase between sessions?
4. Stop re-explaining your project to AI every session
5. AI memory that actually works (MCP-based, free trial)
6. Your AI doesn't remember yesterday. Mine does.
7. 10 minutes/session wasted on AI context? Fixed.``
Hi [First Name],
Quick question: how much time do you spend re-explaining context to
AI assistants at the start of every session?
I built Enovari because I was wasting 10-15 minutes per session
giving Claude the same context about my projects, preferences, and
past decisions. Now it remembers automatically.
Gives Claude, ChatGPT, and Cursor persistent memory across sessions
Remembers your project context, coding preferences, and past
decisions
Works via MCP -- native integration, not a brittle workaround
Memory is structured and searchable, not a raw dump
1. Sign up at https://enovari.ai (free trial, no card required)
2. Connect to your AI tool via MCP
3. Your AI starts remembering
$19.99/month after the trial. Cancel anytime.
Try it on your next coding session and see if you go back.
[Your Name]
Founder, Enovari
P.S. If you have questions about the MCP integration or architecture,
I'm a developer too -- happy to talk technical details. Just reply.
````
Hey [First Name],
Built something you might want: Enovari makes Claude/ChatGPT/Cursor
remember everything across sessions. No more re-explaining your
codebase every morning.
MCP-based, 30-second setup, free trial (no card). $19.99/mo after.
https://enovari.ai
Try it on your next session.
[Your Name]
Founder, Enovari
````
Hi [First Name],
Your AI forgets everything between sessions. Enovari fixes that.
Persistent memory for Claude/ChatGPT/Cursor via MCP. Free trial.
https://enovari.ai
[Your Name]
``[First Name] -- never send "Hi there" or "Hi Developer" Opening question -- adjust based on what you know about them. If they've tweeted about AI frustrations, reference that. If they work with a specific AI tool, mention that tool first. "What Enovari does" bullets -- reorder based on their likely priorities. If they're a Cursor user, lead with code context persistence. P.S. -- the P.S. gets read even when the body gets skimmed. Use it for the strongest personalization point.
Tuesday through Thursday, 10 AM - 12 PM in recipient's timezone Developers tend to check email mid-morning after their first focus block
1st follow-up: 4 business days 2nd follow-up: 9 business days No 3rd follow-up for cold user emails
7B. Cold Email to Potential Users (Businesses)
7 items1.
Your team's AI tools are losing context every day
2. What if your AI assistant remembered your entire business?
3. AI memory for business -- stop retraining your AI every session
4. Your AI assistant costs you [X] hours/week in lost context
5. The AI productivity tool your team doesn't know it needs
6. Your AI resets every morning. Your team pays the cost.
7. AI context that compounds instead of disappearing``
Hi [First Name],
If your team uses AI assistants (Claude, ChatGPT, or Cursor), they're
hitting the same wall every day: the AI forgets everything between
sessions.
Every conversation starts from zero. Your team re-explains processes,
preferences, client details, and project context -- every single time.
That's hours per week per person, lost to a problem that's already
solved.
Enovari gives your AI assistants persistent memory.
Your AI remembers:
Business processes and standard procedures
Client details and project history
Team preferences and decision rationale
Accumulated knowledge that compounds over time
instead of resetting daily.
Works with Claude, ChatGPT, and Cursor
$19.99/month per seat, free trial
Setup takes minutes, not days
No IT department required
Would a 15-minute demo be useful? I can show you the before and
after with a real workflow.
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hi [First Name],
Quick question: does your team spend time re-explaining things to
AI tools at the start of every session?
Enovari fixes that. Persistent AI memory for Claude/ChatGPT/Cursor.
Your AI remembers your processes, clients, and project context across
sessions.
$19.99/month per seat, free trial. Setup takes minutes.
15-minute demo? I can show the before and after.
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hi [First Name],
Your team's AI tools forget everything between sessions. Enovari
gives them persistent memory.
Works with Claude/ChatGPT/Cursor. $19.99/mo per seat, free trial.
15-minute demo available.
[Your Name]
https://enovari.ai
``[First Name] -- must be a real person, not a generic role "Your AI remembers" bullets -- completely rewrite based on the business type. Law firm = case history, legal research, client preferences. Marketing agency = brand guidelines, campaign history, client voice. Consulting firm = project methodologies, client context, deliverable templates. Industry pain point -- the opening should reference their specific industry's AI frustration if you know it Demo offer -- for businesses, always offer a demo rather than just linking to the site
Tuesday or Wednesday, 8-10 AM in recipient's timezone Business buyers check email earlier than developers
1st follow-up: 5 business days 2nd follow-up: 10 business days 3rd follow-up: 20 business days (final, with a case study or social proof if available)
7C. Referral Ask Email
5 items1.
Quick favor -- know anyone who'd benefit from Enovari?
2. Would you refer Enovari to a friend?
3. Who in your circle struggles with AI context loss?
4. Quick ask from [Your Name] at Enovari
5. Enovari referral -- pass it along?
6. Know a developer frustrated by AI amnesia?
7. Quick favor: one introduction?``
Hi [First Name],
Thanks for being an Enovari user. Quick ask:
Do you know 1-2 people who would benefit from persistent AI memory?
Developers, founders, or anyone who uses Claude, ChatGPT, or Cursor
regularly and is frustrated by the context reset problem.
just have them mention your name when they sign up, or forward this
email.
[Option A] I'll extend your subscription by [X days/month] for
each referral that signs up
[Option B] I'll unlock [premium feature] on your account
[Option C] Genuine gratitude and the knowledge that you helped a
bootstrapped founder (honest version for when there's no budget
for referral rewards)
If nobody comes to mind right now, no pressure at all. But if someone
does -- even just replying with their name and email -- I'll take it
from there.
Thanks for using Enovari. It means more than you know.
[Your Name]
https://enovari.ai
``[First Name] -- use their name, reference their usage if possible (e.g., "I noticed you've been using Enovari with Cursor -- really cool to see") Referral incentive -- be honest about what you can offer. A genuine "thanks" is better than a fake reward you can't fulfill. Target description -- tailor the "who would benefit" description based on what you know about the user's network
Tuesday through Thursday, 10 AM - 12 PM Send AFTER the user has been active for at least 2 weeks and has shown engagement (not to new or inactive users)
No follow-up. One ask is enough. If they don't refer, don't nag.
7D. Testimonial Request Email
5 items1.
Would you share a quick Enovari testimonial?
2. Your Enovari experience -- 2 minutes of your time?
3. Quick favor: a few words about Enovari?
4. Can I quote you on Enovari?
5. Your feedback would mean a lot (Enovari testimonial)
6. 2-minute favor: quick Enovari testimonial?
7. Your words could help other developers find Enovari``
Hi [First Name],
I noticed you've been using Enovari for [timeframe/usage detail if
available -- e.g., "about a month now" or "primarily with Cursor"].
Thanks for being an early user -- it genuinely matters for a
bootstrapped product.
I have a quick favor to ask: would you be willing to share a short
testimonial? It doesn't need to be polished -- a few sentences about:
What problem Enovari solves for you
How your workflow changed after using it
Who you'd recommend it to
Here's an example of the format I'm looking for (but use your own
words -- authenticity matters more than polish):
> "Before Enovari, I spent the first 10 minutes of every Claude
> session re-explaining my project. Now it just knows. That saved
> me [X] hours last month." -- [Name, Role]
If you're comfortable, I'd love to include:
Your first name (or full name if you prefer)
Your role/title (optional)
Where I can use it: website, social media, or both
Reply to this email with your testimonial -- that's all it takes.
Or if you'd prefer, I can draft something based on our conversations
and you can approve/edit it.
Either way, thanks for being part of building this.
[Your Name]
https://enovari.ai
``[Timeframe/usage detail] -- reference their actual usage if you have analytics Testimonial prompts -- adjust based on what you know about their use case. If they use it for coding, ask about coding workflow. If they use it for business, ask about business context. Draft offer -- some users prefer you draft it. Always offer this option -- it dramatically increases response rates.
Tuesday through Thursday, 10 AM - 12 PM Send after the user has been active for at least 3-4 weeks Best sent after a positive support interaction or after they've hit a usage milestone
1st follow-up: 7 days (make it even easier -- "Would it help if I drafted something based on your usage? You just approve or edit.") No 2nd follow-up. Testimonials should feel voluntary, not pressured. # 8. Investor Outreach Emails > Context for bootstrapped founders: Even if you are not actively raising, investor relationships matter. Angels and micro-VCs can become customers, advisors, referral sources, and amplifiers. Building these relationships early means that if you ever choose to raise, you are not starting from zero. These templates are designed for relationship-building, not pitching a round.
8A. Angel Investor / Micro-VC Introduction
7 items1.
AI memory infrastructure -- bootstrapped, shipping, would love your perspective
2. Solo founder in AI infrastructure -- not raising, but would value your input
3. Building AI memory (bootstrapped) -- your perspective would help
4. AI infrastructure founder seeking advice, not capital
5. Enovari: AI memory platform -- would love 15 minutes of your time
6. Bootstrapped in AI -- your take on the memory infrastructure space?
7. Not raising, just learning -- AI memory founder intro``
Hi [Investor First Name],
I'm [Your Name], solo founder of Enovari -- an AI memory platform that
gives Claude, ChatGPT, and Cursor persistent, structured memory across
sessions via MCP.
I'm not raising right now. I'm bootstrapped, shipping product, and
have paying users. But I admire [specific thing about them -- their
portfolio, a blog post, a tweet, a talk] and would genuinely value
your perspective on a few strategic questions.
AI memory platform: persistent, structured memory for AI assistants
Works with Claude, ChatGPT, and Cursor via MCP
$19.99/month, free trial, live users
Bootstrapped, solo founder, revenue-generating
https://enovari.ai
[Specific strategic question -- e.g., "How do you see the AI
infrastructure layer evolving over the next 18 months?"]
[Specific go-to-market question -- e.g., "What separates the
bootstrapped AI companies that scale from those that plateau?"]
I know your time is valuable. Even a 15-minute call or a quick email
reply would be incredibly helpful.
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Investor First Name],
I'm [Your Name], building Enovari -- AI memory for Claude/ChatGPT/Cursor.
Bootstrapped, solo, shipping, paying users.
Not raising -- but I follow your work on [specific thing] and would
love your take on [specific question about AI infrastructure or
go-to-market].
15 minutes of your time would be huge. Happy to give you a product
walkthrough too if you're curious.
[Your Name]
https://enovari.ai
````
Hi [Investor First Name],
Solo founder, bootstrapped AI memory platform (Enovari). Not raising.
Would value 15 minutes of your perspective on [specific question].
Your [blog post / tweet / talk] on [topic] is what prompted this.
[Your Name]
https://enovari.ai
``[Specific thing about them] -- must be real. Reference their portfolio companies, their blog, their tweets, or a talk they gave. Generic flattery gets deleted. [Strategic questions] -- make these genuine. Ask something you actually want to know, not something designed to impress them. "Not raising" framing -- this is critical. Investors get pitched constantly. Leading with "not raising" disarms them and makes them more willing to engage.
Tuesday or Wednesday, 8-10 AM in their timezone Avoid end of quarter (investors are busy with portfolio reporting)
1st follow-up: 7 business days 2nd follow-up: 14 business days (offer a specific date/time for a call) No 3rd follow-up
8B. Strategic Angel / Operator-Angel Outreach
5 items1.
AI memory founder -- your operator experience would help
2. Building in AI infrastructure -- would love input from someone who's done it
3. [Their Company] alum building AI memory -- quick question
4. Your experience at [Their Company] is relevant to what I'm building
5. AI infrastructure founder seeking operator perspective``
Hi [Name],
I'm [Your Name], building Enovari -- an AI memory platform that gives
AI assistants persistent memory across sessions via MCP.
I reached out because of your experience [at/building/scaling]
[Their Company]. [Specific reason their experience is relevant --
e.g., "You scaled a developer tools product from 0 to 10K users,
and I'm approaching that exact inflection point."]
Live product, paying users, bootstrapped
Claude, ChatGPT, and Cursor integration via MCP
$19.99/month, growing organically
Solo founder doing everything
[Specific operational question -- e.g., "When did you hire your
first person, and what role had the biggest impact?"]
[Specific tactical question -- e.g., "How did you think about
pricing evolution as you moved from early adopters to a broader
market?"]
Not asking for capital -- asking for 20 minutes with someone who has
navigated the stage I'm entering.
Would that be possible?
[Your Name]
https://enovari.ai
``[Their Company] reference -- must be specific and relevant to your actual situation [Operational questions] -- ask questions only they can answer based on their specific experience Framing -- operator-angels respond to founders who are clearly executing, not dreaming. Lead with traction.
Tuesday through Thursday, 9-11 AM in their timezone
1st follow-up: 7 business days No 2nd follow-up unless they expressed interest
8C. VC Firm Relationship-Building (Pre-Raise)
5 items1.
AI memory infrastructure update -- building in public
2. Quarterly update: Enovari (AI memory platform)
3. Not raising, but keeping you in the loop on AI memory
4. Enovari progress update -- AI memory infrastructure
5. Building AI memory infrastructure -- periodic update``
Hi [VC Name],
I'm [Your Name], solo founder of Enovari (https://enovari.ai) -- an
AI memory platform giving Claude, ChatGPT, and Cursor persistent
memory via MCP.
I'm not raising and may never raise -- I'm bootstrapped by choice.
But I respect [Firm Name]'s work in [their focus area] and want to
keep you informed about what's happening in the AI memory
infrastructure space.
[X] paying users, [growth metric]
[Notable product milestone or feature]
[Market signal or competitive development]
[One insight about the AI memory market]
[One insight about user behavior or demand]
[Next product milestone]
[Next go-to-market move]
I'll send an update like this quarterly. If AI memory infrastructure
becomes a space you're actively looking at, I'd welcome a conversation.
In the meantime, happy to be a source on the space if you're doing
diligence on anything related.
[Your Name]
Founder, Enovari
https://enovari.ai
``[Firm's focus area] -- reference their thesis or recent investments in adjacent spaces Insights -- share genuinely useful market intelligence, not just self-promotion. VCs value founders who are good sources of information. Frequency -- send these quarterly. More often is annoying. Less often and you lose the thread.
First week of a new quarter (January, April, July, October) Tuesday or Wednesday, 9-10 AM in their timezone
No follow-up on update emails. If they want to engage, they will.
9A. Speaker Application / Pitch
7 items1.
Speaker proposal for [Conference Name]: AI memory infrastructure
2. Talk proposal: "Why AI Forgot Everything" -- [Conference Name]
3. Speaker pitch: building AI memory with MCP (for [Conference Name])
4. Talk proposal: the missing infrastructure layer in AI
5. [Conference Name] speaker pitch: solo founder building AI memory
6. Session proposal: persistent AI memory -- what MCP makes possible
7. Talk pitch: when your AI remembers you (for [Conference Name])I'm [Your Name], solo founder of Enovari
``
Hi [Organizer First Name],
I'd like to propose a talk for [Conference Name] [year/date].
"Your AI Has Amnesia: Building the Memory Layer"
"MCP and the Future of AI Context"
"What I Learned Building AI Memory Infrastructure Solo"
"The Next Platform Battle: Why AI Memory Matters More Than Models"
Every AI conversation starts from zero. We've accepted this as normal,
but it's actually a solvable infrastructure problem -- and the solution
changes everything about how AI assistants work.
In this talk, I'll cover:
Why AI memory is the next critical infrastructure layer
How Model Context Protocol (MCP) enables persistent, structured
memory across AI platforms
The technical architecture of a production AI memory system
(hybrid retrieval, structured storage, cross-platform context)
Real-world impact: what changes when AI assistants actually
remember you
Lessons from building this solo and bootstrapped
This talk is [technical / mixed / non-technical -- match the
conference's audience]. I'll include [live demos / architecture
diagrams / code samples / real user stories] to make it concrete.
(https://enovari.ai) -- a production AI memory platform serving
real users across Claude, ChatGPT, and Cursor. I built this
bootstrapped because I believe AI memory is the next major
infrastructure shift.
presentations. If none: "This would be my first conference talk,
but I've presented technical content to [audiences] and I keep
things clear, engaging, and demo-heavy."]
breakout / workshop / panel / lightning talk]. I cover my own
travel.
I'd welcome the chance to speak at [Conference Name]. Happy to send
slides, an outline, or a demo video.
[Your Name]
Founder, Enovari
https://enovari.ai
[Email]
[Phone]
````
Hey [Organizer First Name],
Talk proposal for [Conference Name]:
the fix -- Enovari, an AI memory platform using MCP. I'll talk about
why memory is the next infrastructure battle, show the technical
architecture, and share what I learned building this solo.
Demo-heavy, practical, no fluff. [X] minutes works best.
I'm [Your Name], solo founder of Enovari (https://enovari.ai).
Bootstrapped, shipping, real users.
Interested? Happy to send an outline.
[Your Name]
````
Hi [Organizer First Name],
Speaker proposal for [Conference Name]: talk on AI memory
infrastructure, MCP, and building the persistence layer AI is
missing. Demo-heavy, practical.
I'm the founder of Enovari (https://enovari.ai) -- production AI
memory platform.
Happy to send an abstract and outline.
[Your Name]
``Conference audience -- technical conferences want architecture and code. Business conferences want market impact and demos. Founder conferences want the journey story. Talk format -- check what formats they offer (keynote, breakout, workshop, lightning talk) and match your proposal. Previous speakers -- if you can reference a previous speaker or talk at their conference that relates to your topic, do it. CFP vs. direct pitch -- if they have a Call for Papers process, use it. This email is for direct outreach or to supplement a CFP submission.
3-6 months before the conference date (organizers plan early) If they have a CFP deadline, send 2 weeks before the deadline Tuesday through Thursday, 9-11 AM in organizer's timezone
1st follow-up: 10 business days 2nd follow-up: 20 business days (offer to adjust the topic or format) No 3rd follow-up
9B. Conference Booth / Sponsor Pitch (Small Budget)
5 items1.
Sponsor/exhibitor inquiry for [Conference Name] -- AI memory startup
2. Booth inquiry: Enovari (AI memory platform) at [Conference Name]
3. Startup sponsor tier for [Conference Name]?
4. Exhibition opportunity at [Conference Name] -- bootstrapped AI startup
5. Exploring sponsor options for [Conference Name]Persistent, structured AI memory for Claude,
``
Hi [Organizer First Name],
I'm [Your Name], founder of Enovari (https://enovari.ai) -- an AI
memory platform. I'm exploring exhibitor/sponsor options for
[Conference Name].
ChatGPT, and Cursor via MCP. $19.99/month, bootstrapped, live users.
A startup-tier or community sponsor option (I'm bootstrapped,
so I'm budget-conscious)
Booth/table presence to demo the product
Any speaking opportunities tied to sponsorship
A compelling live demo (AI with vs. without memory)
Genuine developer engagement (I'm a founder who codes, not a
sales team)
Social media coverage of the event to my audience
Do you have startup-friendly sponsor tiers? What's the smallest
package that includes a demo presence?
[Your Name]
Founder, Enovari
https://enovari.ai
``Budget transparency -- being upfront about bootstrapped budget is an advantage. Many conferences have startup tiers, community tables, or scholarship spots. Demo value -- emphasize that Enovari demos well. Conferences want booths that attract foot traffic.
4-6 months before the conference Follow up every 2 weeks if initial inquiry goes unanswered
1st follow-up: 7 business days 2nd follow-up: 14 business days 3rd follow-up: 21 business days
10A. Hackathon Organizer Sponsor Pitch
7 items1.
Sponsor offer for [Hackathon Name]: AI memory API + prizes
2. Enovari wants to sponsor [Hackathon Name] -- API access + prizes
3. Hackathon sponsorship: free AI memory API for all participants
4. Sponsor pitch: Enovari x [Hackathon Name]
5. API sponsor for [Hackathon Name]? Persistent AI memory for every team
6. [Hackathon Name] sponsor proposal: AI memory infrastructure
7. Hackathon sponsor: give every team persistent AI memory``
Hi [Organizer First Name],
I'm [Your Name], founder of Enovari (https://enovari.ai) -- an AI
memory platform that gives AI assistants persistent memory across
sessions via MCP.
I'd like to sponsor [Hackathon Name] with API access and prizes.
1. Free Enovari access for every participant for the duration
of the hackathon (+ [X days/weeks] after to keep building)
2. A sponsored prize category: "Best use of AI memory" or
"Most creative MCP integration" -- [prize amount or description]
3. Technical mentorship during the hackathon -- I built this
and can help teams integrate quickly
4. A 10-minute workshop or lightning talk on AI memory and MCP
integration if your schedule allows
AI memory is a powerful building block that makes hackathon
projects more impressive (AI that remembers context between
demos is a wow factor for judges)
MCP integration takes minutes, not hours -- teams can add
memory to their project without burning their hackathon time
Participants walk away with a real tool they'll keep using
Exposure to developers who are exactly our target audience
Real-world testing of our API by creative builders
Projects that showcase what's possible with AI memory
lightning talk or workshop slot, and the ability to offer a
sponsored prize category.
[startup/community/API-sponsor] tier. Happy to discuss what
fits.
Can we talk details?
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hey [Organizer First Name],
Want to sponsor [Hackathon Name] with free AI memory API access
for all teams + prizes.
Enovari gives AI assistants persistent memory via MCP. Setup takes
minutes, makes hackathon projects way more impressive (AI that
remembers context between demos is a judge magnet).
Offering: free accounts for all participants, a sponsored prize
category, and technical mentorship during the event.
I'm bootstrapped, so looking for a startup-friendly tier. What
options do you have?
[Your Name]
https://enovari.ai
````
Hi [Organizer First Name],
Sponsor offer for [Hackathon Name]: free Enovari API (AI memory
via MCP) for all participants + prize category + mentorship.
Bootstrapped, so seeking a startup-friendly tier.
Interested in discussing?
[Your Name]
https://enovari.ai
``Hackathon theme -- if the hackathon has a specific theme (AI, developer tools, social good), connect Enovari's value to that theme Prize structure -- match what other sponsors at similar tiers are offering. If you can't offer cash, offer extended free subscriptions, swag, or featured placement. Workshop content -- tailor to the hackathon audience (student hackathon = more beginner-friendly; corporate hackathon = more enterprise-focused)
4-8 weeks before the hackathon Many hackathons have early sponsor deadlines -- research first
1st follow-up: 5 business days 2nd follow-up: 10 business days 3rd follow-up: 15 business days (offer to reduce scope if budget is the blocker)
10B. University Hackathon Specific Pitch
5 items1.
API sponsor for [University Hackathon]: AI memory for every team
2. Enovari wants to sponsor [University Hackathon]
3. Free AI memory API for [University Hackathon] participants
4. Sponsor offer: AI memory platform for student hackers
5. [University Hackathon] API sponsor: persistent AI memory``
Hi [Organizer First Name],
I'm [Your Name], founder of Enovari -- an AI memory platform that
gives AI assistants persistent memory across sessions.
I'd love to sponsor [University Hackathon] with free API access for
all participants.
Free Enovari accounts for the hackathon + [X weeks] after
A building block that makes their projects stand out: AI that
remembers context between sessions and demos
Quick integration via MCP -- takes minutes, not hours
Free API access for all participants
A sponsored prize: "Best AI Memory Integration" -- [prize]
A workshop or lightning talk: "Adding Memory to AI in 10 Minutes"
Mentorship during the hackathon (I'm a developer, not a recruiter)
It's a real, emerging infrastructure category
MCP skills are becoming valuable in the job market
Projects with persistent AI context are significantly more
impressive in demos
I'm bootstrapped and doing this because I want to get Enovari in
front of builders early. Happy to work with whatever sponsor tier
fits your structure.
[Your Name]
Founder, Enovari
https://enovari.ai
``Student focus -- emphasize learning, career skills, and portfolio value rather than business metrics Prize -- for student hackathons, prizes like extended free access, mentorship calls, or even modest cash ($50-$200 per category) are meaningful Workshop -- offer a hands-on workshop, not a pitch. Students can spot marketing disguised as education immediately.
6-10 weeks before the hackathon (student organizers plan further ahead than you'd expect) Academic calendar matters -- avoid midterms and finals periods
1st follow-up: 7 business days 2nd follow-up: 14 business days
11A. AI/ML Researcher Collaboration Pitch
7 items1.
AI memory infrastructure: research collaboration opportunity
2. Production AI memory system -- open to research partnerships
3. Your work on [specific paper topic] + real-world AI memory data
4. Research collaboration: persistent memory for AI assistants
5. AI memory platform with production data -- research partnership?
6. Your [paper title] and production AI memory systems
7. Collaboration: real-world data for AI memory research``
Dear Professor [Last Name],
I read your paper "[Paper Title]" published in [Venue/Journal] and
found your work on [specific aspect] directly relevant to what I'm
building.
I'm [Your Name], founder of Enovari (https://enovari.ai) -- a
production AI memory platform that provides persistent, structured
memory for AI assistants (Claude, ChatGPT, Cursor) via the Model
Context Protocol.
I'm reaching out because I believe there's a mutually beneficial
research collaboration opportunity.
Access to a production AI memory system architecture
Anonymized usage patterns and retrieval performance data
A real-world testbed for memory retrieval algorithms (we use
BM25 + vector hybrid search and would welcome comparisons with
alternative approaches)
A deployment platform for research prototypes
Improved retrieval algorithms or memory organization strategies
Academic validation of the AI memory infrastructure concept
Publication opportunities that advance the field and raise
awareness of the problem space
Optimal memory retrieval strategies for AI context (when to
remember, what to surface, how to rank relevance)
Memory consolidation and summarization for long-lived AI
memory stores
Cross-platform context transfer and the portability of AI
memory
User studies on AI assistant effectiveness with and without
persistent memory
I respect the demands on your time. If any of this resonates, I'd
welcome a 20-minute call to explore further. I can also send a
technical architecture document if that would help you evaluate
the opportunity.
Respectfully,
[Your Name]
Founder, Enovari
https://enovari.ai
````
Hi Professor [Last Name],
Your paper on [specific topic] caught my attention -- especially
[specific finding or approach].
I built Enovari, a production AI memory platform (persistent memory
for Claude/ChatGPT/Cursor via MCP). I'm reaching out because I have
real-world data and infrastructure that might be useful for your
research, and your work could improve our retrieval and memory
organization.
Would a short conversation make sense? I can share our technical
architecture and discuss potential collaboration.
[Your Name]
Founder, Enovari
https://enovari.ai
````
Dear Professor [Last Name],
Your work on [topic] is directly relevant to Enovari, a production
AI memory platform I built. I have real-world data and
infrastructure that might benefit your research.
Would a brief conversation be worthwhile?
[Your Name]
https://enovari.ai
``[Paper Title] and [specific aspect] -- MUST be a real paper. Academics will immediately detect generic references. Read at least the abstract and introduction. Research directions -- propose directions that connect their published interests to your platform's capabilities Tone -- more formal than industry outreach. Use "Dear Professor [Last Name]" unless they have explicitly indicated a preference for first names. Venue -- reference the actual conference or journal (NeurIPS, ICML, ACL, CHI, etc.)
Tuesday through Thursday, 10 AM - 2 PM in their timezone Avoid the 2 weeks before major conference deadlines (NeurIPS, ICML, ACL, EMNLP, CHI, etc.) Good times: early in a semester, or shortly after a conference where they presented
1st follow-up: 10 business days (academics are slow to respond -- this is normal) 2nd follow-up: 21 business days No 3rd follow-up
11B. PhD Student / Postdoc Outreach
5 items1.
Your research on [topic] + a production AI memory system
2. Real-world AI memory data for your research
3. Research opportunity: production AI memory platform
4. Your [paper/thesis topic] and Enovari's AI memory system
5. Potential research data source for your work on [topic]``
Hi [First Name],
I came across your [paper/thesis/talk] on [specific topic] and thought
there might be a good research fit.
I'm [Your Name], founder of Enovari (https://enovari.ai) -- a production
AI memory platform. We provide persistent, structured memory for AI
assistants using MCP, with hybrid retrieval (BM25 + vector search).
Your work on [specific aspect of their research] is directly applicable
to challenges we face in production:
[Specific challenge -- e.g., "optimizing retrieval relevance for
varied query types"]
[Specific challenge -- e.g., "memory consolidation strategies for
long-lived memory stores"]
Access to a production AI memory system for research
Anonymized data on memory usage patterns and retrieval performance
A real deployment environment for testing research ideas
Co-authorship on any resulting publications
Better algorithms for [specific area]
Academic rigor applied to design decisions I've made based on
intuition
If this sounds interesting, I'd love to set up a call. I can also
add your advisor in CC if that would be helpful.
[Your Name]
https://enovari.ai
``Research specificity -- PhD students and postdocs respond best when you show you've actually read their work Co-authorship offer -- this is the most valuable thing you can offer an early-career researcher. Be genuine about it. Advisor CC -- offering to include their advisor shows respect for academic hierarchy and can accelerate the conversation
Avoid conference deadline crunch periods Beginning of semester or right after they publish/present is ideal
1st follow-up: 10 business days 2nd follow-up: 21 business days No 3rd follow-up
11C. University Course / Guest Lecture Pitch
5 items1.
Guest lecture offer: AI memory infrastructure (for [Course Name])
2. Industry guest lecture: building AI memory systems
3. Guest speaker: real-world AI infrastructure for [Department]
4. Lecture offer: from research to production in AI memory
5. Industry perspective for your [course topic] studentsI built a production AI memory system using hybrid
``
Dear Professor [Last Name],
I'm [Your Name], founder of Enovari (https://enovari.ai) -- a
production AI memory platform. I'd like to offer a guest lecture
for your [Course Name / Department] students.
"From Research to Production: Building AI Memory Infrastructure"
"MCP and the Architecture of Persistent AI Memory"
"Building a Real AI Product: Solo Founder Technical Decisions"
"The Business of AI Infrastructure: Technical and Market Lessons"
A real-world case study of AI infrastructure design decisions
Production architecture walkthrough with actual tradeoffs
(not textbook ideals)
The bridge between academic concepts and industry implementation
Q&A with a founder who ships production AI systems
a workshop with hands-on components. Remote or in-person (I'll
cover my own travel for in-person).
retrieval (BM25 + vector), MCP integration, and structured memory
architecture. Before Enovari, [brief relevant background].
I'd welcome the chance to share industry perspective with your
students.
Respectfully,
[Your Name]
Founder, Enovari
https://enovari.ai
``Course alignment -- research the actual course syllabus or description and tailor the topic to fit Department -- CS courses want technical depth. Business courses want market/startup angles. Information Science courses want the user experience angle. Format -- match what the course typically does with guest speakers
4-6 weeks before the relevant point in the semester Early in a semester is best for scheduling flexibility
1st follow-up: 10 business days 2nd follow-up: 21 business days
12A. Email Deliverability -- How to Stay Out of Spam
4 items1. Set up SPF, DKIM, and DMARC records for your sending domain SPF: Tells email servers which IP addresses can send on behalf of your domain DKIM: Cryptographically signs your emails to prove they're from you DMARC: Tells receiving servers what to do with emails that fail SPF/DKIM All three are non-negotiable. Without them, you'll land in spam. Fact check: Google and Yahoo began strictly enforcing SPF, DKIM, and DMARC requirements for bulk senders in February 2024. Even for low-volume cold outreach, having all three properly configured is now essential, not optional. 2. Use a separate sending domain for cold outreach Do NOT send cold emails from your primary @enovari.ai domain Register a similar domain (e.g., @getenovari.com, @tryenovari.com, @enovari.co) Set up all DNS records (SPF, DKIM, DMARC) on this domain If the sending domain gets blacklisted, your primary domain is protected Practical note: Register the domain at least 4-6 weeks before you plan to send. Brand-new domains that immediately start sending email are flagged by spam filters. Let the domain age a bit while you warm it up. 3. Warm up the sending domain/address New domains/addresses that suddenly send volume get flagged immediately Start with 5-10 emails/day for the first week Increase by 5-10 per day each week Target: 50-100 cold emails/day maximum after 4-6 weeks of warming Use a warmup service (see Tools section below) How manual warmup works: Send real emails to friends, colleagues, and other accounts you control. Have them reply, mark your emails as "not spam" if they land there, move them to the inbox, and star/mark them as important. This trains email providers that your domain sends legitimate mail.
4. Avoid spam trigger words and patterns Avoid: "free," "guarantee," "no obligation," "act now," "limited time," "click here," "buy now," "order now," "congratulations," "winner" Nuance: Modern spam filters use machine learning and are less reliant on simple keyword lists than they were 10 years ago. A single use of "free trial" in an otherwise well-crafted personal email is unlikely to trigger spam filters on its own. The real danger is combining multiple spam signals: trigger words + high volume + new domain + no authentication + link-heavy emails. That said, minimizing trigger words is still good hygiene. Avoid ALL CAPS in subject lines or body Avoid excessive exclamation marks (one per email maximum, zero is better) Avoid image-heavy emails (cold outreach should be plain text) Avoid large attachments (link to resources instead) 5. Keep formatting simple Plain text or minimal HTML -- no fancy templates for cold outreach No images in cold emails (triggers spam filters, also signals "marketing email") Short paragraphs (2-3 lines max) No colored text, no custom fonts Why plain text wins: Gmail and Outlook both give higher deliverability scores to plain-text emails. They look like real human correspondence, not marketing blasts. 6. Include an unsubscribe mechanism Required by CAN-SPAM law (US), CASL (Canada), GDPR (EU/UK), and similar laws globally Add a line at the bottom: "If you'd prefer I not follow up, just let me know." A human-sounding opt-out is better than a formal "unsubscribe" link for 1:1 cold emails For bulk sends, use a proper unsubscribe link Legal note: CAN-SPAM requires that you honor opt-out requests within 10 business days. In practice, honor them immediately. GDPR is stricter -- it requires legitimate interest or consent before sending in the first place. If you are emailing people in the EU/UK, research GDPR cold email rules specifically. 7. Verify email addresses before sending Bounced emails destroy sender reputation faster than anything else Use an email verification service before any outreach campaign Target < 2% bounce rate Why this matters so much: Email providers track your bounce rate. If it exceeds 2-3%, your domain reputation drops fast, and ALL your emails (not just cold outreach) start landing in spam. 8. Send from a real person, not a brand From: "[Your Name] at Enovari" -- not "Enovari Team" or "Enovari" Reply-to should be your actual email address Your email signature should include your real name and a real way to contact you
9. Monitor your sender reputation Use Google Postmaster Tools (https://postmaster.google.com/) to monitor your domain's reputation with Gmail -- this is the correct URL (not the Gmail settings URL) Check your domain's reputation at https://mxtoolbox.com/blacklists.aspx Use Microsoft SNDS (Smart Network Data Services) to monitor reputation with Outlook/Hotmail If your domain appears on a blacklist, stop all outreach and request removal immediately 10. Manage your sending volume Never send more than 100 cold emails per day per sending address Space emails throughout the day (not 100 emails at 9:00 AM) Reduce volume immediately if bounce rate exceeds 3% or spam complaints exceed 0.1% The 0.1% complaint threshold: Google publicly states that senders should keep spam complaint rates below 0.1% (and never exceed 0.3%). At 100 emails/day, that means even 1 spam complaint in 3 days is a warning sign.
Bounce rate above 3% Spam complaint rate above 0.1% Google Postmaster Tools shows "Bad" or "Low" domain reputation Emails to Gmail addresses suddenly all land in spam You get blacklisted on any major blacklist
12B. Optimal Email Length
2 itemsIf you can cut a word without losing meaning, cut it. Every word in a cold email must earn its place. Front-load the value. The first 2 sentences must make the recipient want to read the rest. If those 2 sentences don't hook them, the rest doesn't matter. One CTA per email. Don't ask them to visit your site AND schedule a call AND check out your demo. Pick one action. The templates in this document are maximum length. In practice, trim them down for each recipient. A 100-word email that's tight will outperform a 300-word email that's comprehensive.
12C. Best Times to Send
2 itemsTuesday is the best day overall for cold outreach across all categories Avoid Mondays -- inboxes are flooded from the weekend Avoid Fridays -- people are winding down and less likely to engage with new outreach Avoid holidays, major tech events, and Apple keynote days Always send in the RECIPIENT'S timezone, not yours. Use scheduling tools to manage this. Test your own data. These are starting points. Track open rates by send time and optimize over the first 100 sends.
12D. How to Personalize at Scale
3 items1. Reference their specific work (article they wrote, video they made, tweet they posted) Highest impact. Nothing else comes close. This is what separates emails that get replies from emails that get deleted. Budget 3-5 minutes per recipient for research. It's the highest-ROI time you'll spend. 2. Reference their specific audience/readers/viewers Shows you understand who they serve, not just who they are "Your readers who are building AI tools would care about this because..." 3. Reference their company/product/project Demonstrates you know the context they operate in "I see [Company] is doing [X] -- Enovari fits into that because..." 4. Reference a shared connection or community "We're both in the [community/Slack/Discord/forum]..." Lower impact but still shows you're a real person in their orbit 5. Reference their role or expertise area Weakest personalization but better than nothing "As someone who covers AI dev tools..."
Step 1: Build a research spreadsheet For each prospect, capture: Name, email, platform One specific piece of their work you can reference (URL + your one-sentence take) Their audience description (who are their readers/viewers/listeners?) The specific angle that would resonate with them Notes on tone/style Step 2: Write 3-5 base templates (use the ones in this document) The opening line (reference their specific work) The "why you" or "why your audience" section The primary angle/hook (reorder bullets based on what they'd care about most) Step 4: Quality check before sending Read the email as if you're the recipient. Would you reply? Is the personalization genuine or does it feel automated? Is there a clear, single ask? Is it under the target word count?
Do NOT use mail merge for the personalization fields and send the same template to 500 people. Recipients can tell. Do NOT reference something vague ("I love your content"). Be specific or don't bother. Do NOT automate the personalization with AI. The irony of selling an AI product with AI-written spam would be fatal to your brand. Do NOT personalize in ways that feel creepy ("I noticed you were in [city] last week based on your Instagram...").
12F. A/B Testing Guidance
4 items1. Subject lines (highest impact, easiest to test) Test one variable at a time: length, tone, specificity, question vs. statement Example test:
"AI has amnesia -- I built the fix" vs. "Guest pitch: AI memory platform founder"
You need at least 50 sends per variant to see meaningful patterns (100+ is better)
2. Send times (high impact, easy to test)
Test morning vs. midday vs. afternoon
Test different days of the week
Track open rates AND reply rates (an email opened at 7 AM but replied to at 10 AM doesn't mean 10 AM is better -- the 7 AM send triggered the engagement)
3. Email length (moderate impact)
Test formal (full-length) vs. casual (medium) vs. ultra-short
Track reply rates, not just opens. Short emails get opened more but don't always get more replies -- sometimes the detail in a longer email is what convinces someone to respond.
4. Opening line (moderate impact)
Test personalized opening (reference their work) vs. direct opening (start with your pitch)
Test question opening vs. statement opening
5. CTA (call to action) (moderate impact)
Test different asks: "Worth a conversation?" vs. "Want me to send more detail?" vs. "Free account available -- want one?"
Test question CTA vs. suggestion CTA
6. Sender name format (low-moderate impact)
Test "[Your Name]" vs. "[Your Name] at Enovari" vs. "[Your Name], Enovari Founder"Step 1: Set up your tracking spreadsheet Create columns: Recipient name Email address Category (podcast, press, user, etc.) Variant (A or B) Subject line used Send date and time Opened (yes/no/unknown) Replied (yes/no) Reply sentiment (positive/negative/neutral) Outcome (booked/declined/no response) Step 2: Create your variants For each test, change ONLY ONE variable. Examples: Subject line test: Same email body, different subject lines Length test: Same subject line, different email lengths Time test: Same email, different send times Step 3: Randomly assign variants For each batch of sends: Alternate A/B/A/B or use a random number generator Make sure variants go to similar recipient types (don't send all variant A to podcasts and all variant B to press) Step 4: Track results After each batch completes its follow-up cycle (typically 3-4 weeks), calculate: Open rate: Opens / Sends (if you're using tracking) Reply rate: Replies / Sends (the most important metric) Positive reply rate: Positive replies / Sends (the REAL metric) Conversion rate: Desired outcomes (bookings, signups, etc.) / Sends Step 5: Decide and iterate A variant "wins" when it has a meaningfully higher positive reply rate over 50+ sends Don't over-optimize on small samples. 3 replies out of 10 vs. 2 out of 10 is not statistically significant. Wait for more data. Once you have a winner, make it your new default and test a new variable against it
1. Test one variable at a time. If you change the subject line AND the email body, you don't know which change caused the difference. 2. Don't test on high-value prospects. Use your A/B tests on medium-priority targets. Send your best-performing variant to your top-priority targets. 3. Track reply quality, not just quantity. A variant that gets 10 "unsubscribe" replies is not outperforming a variant that gets 3 thoughtful responses. 4. Be patient. Good A/B testing takes months of consistent sending. Don't change your approach after 20 emails. 5. Document everything. A month from now, you won't remember which variant you sent to whom unless it's in your spreadsheet.
12H. CRM Options for Managing Outreach ($0 Budget)
2 itemsIt's the most complete free CRM, and if Enovari grows, you can upgrade without migrating. The email integration (Gmail/Outlook) is solid.
Zero context switching. You manage your pipeline without leaving Gmail. For early-stage outreach, this might be all you need.
For the first 100-200 outreach targets, a well-maintained spreadsheet is honestly fine. Don't over-engineer your process before you have one.
The database views are more powerful than Google Sheets for CRM workflows. Kanban board view for pipeline stages is genuinely useful. But you lose email integration.
The Chrome extension that grabs contact info from social profiles is a significant time saver for influencer and partnership outreach.
Apollo combines prospecting, email verification, sending, and CRM in a single free tool. For a solo founder doing cold outreach, this all-in-one approach saves time on tool-switching.
Cost: $0 (truly free, not a trial) What you get: Up to 1,000,000 contacts (effectively unlimited for outreach purposes) Email tracking (200 notifications/month on free tier) Deal pipeline Email templates (up to 5 on free tier) Meeting scheduler Basic reporting Mobile app Best for: If you want a "real" CRM that will scale with you Limitations: Free tier has HubSpot branding on forms and emails. Limited to 5 email templates. Some reporting features require paid tiers (Starter at ~$20/mo). Limited automation on free tier. Why it's #1: It's the most complete free CRM, and if Enovari grows, you can upgrade without migrating. The email integration (Gmail/Outlook) is solid. > Fact-check note: HubSpot's free tier is genuinely free with no time limit. However, HubSpot periodically adjusts free tier limits. The contact limit was historically unlimited but may now have caps on certain features. Verify current free tier features at hubspot.com/pricing.
Cost: $0 What you get: 500 contacts (was previously higher; Streak has adjusted this over time) 50 mail merge/month Email tracking Pipeline management inside Gmail Mobile access Best for: If you live in Gmail and want the CRM right in your inbox Limitations: 500 contact limit on free tier. Gmail only (no Outlook). Limited pipeline features. Why it's good: Zero context switching. You manage your pipeline without leaving Gmail. For early-stage outreach, this might be all you need. > Fact-check note: Streak's free tier limits have changed multiple times. The 500-contact figure and 50 mail merge/month are approximate. Verify current limits at streak.com/pricing.
Cost: $0 What you get: Whatever you build Setup: Create a spreadsheet with columns: Name, Email, Company, Category (podcast/press/partner/user), Status (not contacted/emailed/followed up 1/followed up 2/responded/not interested), Date First Emailed, Date Last Followed Up, Notes, Next Action Date Use conditional formatting to highlight overdue follow-ups Use Google Sheets filters to see "all podcasts needing first follow-up" Pair with GMass or Yet Another Mail Merge for sending Best for: When you want full control and have < 200 prospects Limitations: Manual. No automation. Easy to let it go stale. You ARE the CRM. Why it works: For the first 100-200 outreach targets, a well-maintained spreadsheet is honestly fine. Don't over-engineer your process before you have one.
Cost: $0 What you get: Unlimited pages/blocks (for individual use) Database views (table, board, calendar, timeline, gallery) Templates API access (for automation if you want to build it) Best for: If you already use Notion for other business operations Limitations: No native email integration. No tracking. You have to manually update everything. Sharing/collaboration requires paid tier. Why it's an option: The database views are more powerful than Google Sheets for CRM workflows. Kanban board view for pipeline stages is genuinely useful. But you lose email integration.
Cost: Free for up to 100 contacts What you get: Contact enrichment Pipeline management Chrome extension for adding contacts from LinkedIn/Twitter Email integration Best for: If LinkedIn/Twitter outreach is a major channel Limitations: 100 contact limit on free tier. Paid plans start at ~$20/mo. Why it's worth knowing about: The Chrome extension that grabs contact info from social profiles is a significant time saver for influencer and partnership outreach.
Cost: $0 What you get: 250 emails/day sending Email sequences (automated follow-ups) Prospecting database (limited searches on free tier) Basic CRM Chrome extension Best for: If you want prospecting + sending + CRM in one tool Limitations: Limited prospecting searches on free tier. Data quality varies. Why it's worth considering: Apollo combines prospecting, email verification, sending, and CRM in a single free tool. For a solo founder doing cold outreach, this all-in-one approach saves time on tool-switching.
Previously mentioned at $49/mo, Woodpecker remains a solid option but pricing has fluctuated. Verify current pricing at woodpecker.co.
Use Streak (free) for CRM + tracking inside Gmail Use Hunter.io (free tier) for email verification Manual warmup for your sending domain Use HubSpot CRM (free) for contact management Use GMass (free tier) or Apollo.io (free) for sending and tracking Use a dedicated warmup service Use Hunter.io or ZeroBounce for verification This requires paid tools. At this volume, invest in Instantly.ai (~$30/mo) or Lemlist (~$39/mo) which combine sending, tracking, warmup, and sequences in one tool. Continue using HubSpot CRM (free) as the central record Note on Woodpecker: Previously mentioned at $49/mo, Woodpecker remains a solid option but pricing has fluctuated. Verify current pricing at woodpecker.co.
1D. Podcast Pitch Follow-Up Templates
First Follow-Up (5-7 business days)
Subject: Re: [Original Subject Line]
Hi [Host First Name],Just floating this back up -- I know podcast inboxes get buried.
Since I last reached out, [mention one new development -- a milestone, a
new feature, a user story, a press mention]. Figured that might add another
angle to the conversation.
Still happy to come on [Podcast Name] and talk about [primary topic angle].
I'm flexible on format and timing.
Let me know if there's interest -- or if this isn't a fit, no worries at all.
[Your Name]
Second Follow-Up (10-14 business days)
Subject: Re: [Original Subject Line]
Hi [Host First Name],Last follow-up on this -- I don't want to be that person who emails
forever.
The short version: I built an AI memory platform (Enovari), bootstrapped
and solo. Happy to talk about the product, the founder journey, or the
broader AI memory space on [Podcast Name].
If the timing isn't right or it's not a fit, totally understand. If it
is, I'm easy to schedule: [Calendly link or "just reply with a time"].
Either way, keep making great episodes.
[Your Name]
Third Follow-Up -- The Breakup Email (20-25 business days)
Subject: Closing the loop on [Podcast Name] guest pitch
Hi [Host First Name],I'll take the silence as a "not right now" -- completely fair. I'm going
to close the loop on this one.
If AI memory or the bootstrapped founder angle ever becomes relevant for
a future episode, my inbox is always open. I'll keep listening regardless.
All the best with [Podcast Name].
[Your Name]
https://enovari.ai
Note: The breakup email often gets the highest reply rate. People feel guilty and respond. Do not send a 4th email. Ever.
2. Blog/Publication Pitch Emails
2D. Blog/Publication Follow-Up Templates
First Follow-Up
Subject: Re: [Original Subject Line]
Hi [Editor First Name],Following up on my pitch for [article topic/product feature]. I know
editorial inboxes move fast.
Since I sent the original note, [mention one relevant development -- new
data point, relevant industry news, product update]. Happy to adjust the
angle if the original pitch doesn't quite fit.
I can also send a quick outline or draft to make evaluation easier --
just let me know.
[Your Name]
Second Follow-Up
Subject: Re: [Original Subject Line]
Hi [Editor First Name],Closing the loop on this pitch. If [article topic] doesn't fit
[Publication Name]'s current editorial calendar, completely understand.
If you'd ever want to revisit this or if a related angle comes up, I'm
easy to reach. I'll keep reading [Publication Name] either way --
consistently good coverage.
[Your Name]
https://enovari.ai
3. Newsletter Submission Emails
4C. LinkedIn Connection Message + Follow-Up
Connection Request (300 character limit)
Hi [Name] -- I follow your posts on [topic]. I'm building Enovari,
an AI memory platform (MCP-based). Would love to connect and share
what I'm learning about AI infrastructure.
Follow-Up After Connection Accepted (send within 24 hours)
Thanks for connecting, [Name].Didn't want to pitch you in a connection request -- that's obnoxious.
But since we're connected now: I'm [Your Name], solo founder of
Enovari. It's an AI memory platform that gives Claude, ChatGPT, and
Cursor persistent memory across sessions.
I've been following your content on [specific topic] and thought this
might be relevant to [specific reason -- e.g., "the AI tool stack
you've been writing about" or "the developer productivity workflow
you shared"].
Would you be interested in a free account to try it out? No obligation
to post about it -- genuinely curious what you'd think.
Either way, looking forward to your content in my feed.
[Your Name]
https://enovari.ai
Second Follow-Up (if no reply after 7 days)
Hey [Name] -- just bumping this in case it got buried in LinkedIn
notifications. The free account offer stands if you're interested.
If not, no worries -- happy to just be connected.
What to Customize Per Recipient
- Connection request -- must reference their specific content focus, not generic
- Follow-up -- tie Enovari to something they've recently posted about
- Tone -- LinkedIn allows slightly more professional tone than Twitter, but don't be stiff
- Connection request: Tuesday through Thursday, 8-10 AM in their timezone
- Follow-up message: within 24 hours of acceptance, during business hours
- Follow-up after acceptance: within 24 hours
- 2nd follow-up: 7 days after first message
- No further follow-ups on LinkedIn
Cross-promotion idea: Enovari + [Their Product]Helping each other's users: Enovari x [Their Product]Audience swap idea -- AI memory meets [their category]Partnership idea: let's share audiencesCross-promo proposal for [Their Product] and EnovariMutual audience growth: Enovari x [Their Product]Low-lift partnership: cross-promo between [Their Product] and Enovari
When to Send
Follow-Up Schedule
6B. Cross-Promotion Proposal
Subject Line Options
Email Body -- Formal Version
Hi [Name],I'm [Your Name], founder of Enovari (AI memory for Claude/ChatGPT/
Cursor). I think our products serve overlapping audiences with zero
competitive overlap -- which makes for a good cross-promotion.
Your audience: [describe their user base -- e.g., "developers using
AI coding tools" or "AI power users building workflows"]
My audience: Developers and power users who use AI assistants daily
and want persistent context across sessions.
Overlap: [Explain why these audiences would value each other's
products -- e.g., "Your users are already deep into AI tooling and
would benefit from memory persistence. My users are building AI
workflows and would benefit from [their product's value]."]
What I'm proposing:
Option A: Newsletter swap. I mention [Their Product] in my
communications; you mention Enovari in yours.
Option B: Social media co-promotion. We each create a post
highlighting the other's product and how they complement each other.
Option C: Bundle or discount. We offer each other's users a
discount or extended trial. [Their Product] users get [X] on Enovari;
Enovari users get [X] on [Their Product].
Option D: Joint content. We co-create a blog post, video, or
tutorial showing both products working together.
Happy to start small (Option A or B) and expand if the results are
there.
Interested in any of these?
[Your Name]
https://enovari.ai
Email Body -- Casual Version
Hey [Name],Our products serve overlapping audiences with zero competition --
that's cross-promo gold.
I'm [Your Name], built Enovari (AI memory for Claude/ChatGPT/Cursor).
Your users would dig persistent AI memory. My users would dig
[Their Product].
Simplest version: we each mention the other in a newsletter or social
post. Can scale from there if it works.
Interested?
[Your Name]
https://enovari.ai
Email Body -- Ultra-Short Version
Hi [Name],Cross-promo idea: Enovari (AI memory) x [Their Product]. Overlapping
audiences, zero competition. Newsletter swap or social co-promotion.
Worth exploring?
[Your Name]
https://enovari.ai
What to Customize Per Recipient
When to Send
Follow-Up Schedule
8D. Investor Outreach Follow-Up Templates
After a Warm Introduction
Subject: [Mutual Contact] suggested I reach out -- AI memory infrastructure
Hi [Investor First Name],[Mutual Contact] suggested I reach out. I'm [Your Name], founder of
Enovari -- an AI memory platform for Claude/ChatGPT/Cursor.
[Mutual Contact] thought you'd find the AI memory space interesting
because [specific reason tied to their investment thesis].
Quick context: bootstrapped, live product, paying users. Not raising
right now, but would value your perspective on [specific question].
Happy to send more detail or jump on a quick call -- whatever works
for you.
[Your Name]
https://enovari.ai
After Meeting at an Event
Subject: Great meeting you at [Event] -- AI memory follow-up
Hi [Investor First Name],Great chatting at [Event] about [specific topic you discussed]. Your
point about [something they said] stuck with me.
As promised, here's more context on Enovari: [1-2 sentences with the
most relevant detail based on your conversation].
Link: https://enovari.ai
Would love to continue the conversation. Free for a call [suggest
specific times]?
[Your Name]
9. Conference Organizer Pitches
9C. Conference Organizer Follow-Up Templates
After CFP Submission
Subject: Following up on [Conference Name] talk proposal -- AI memory infrastructure
Hi [Organizer First Name],Following up on my talk proposal for [Conference Name] ("[Talk Title]").
I submitted through the CFP on [date].
Since submitting, [mention one new development -- user milestone,
product update, relevant news]. Happy to adjust the talk scope or
angle based on your programming needs.
Let me know if you need any additional information.
[Your Name]
https://enovari.ai
After Speaking (Thank You + Future Pitch)
Subject: Thanks for [Conference Name] -- looking ahead
Hi [Organizer First Name],Thanks for having me at [Conference Name]. The audience response to
[specific thing -- Q&A engagement, demo reactions, post-talk
conversations] was great.
I'd love to come back for [next year's event / a related event].
A few topics I could cover next time:
[Topic 1 based on audience questions or feedback]
[Topic 2 based on product evolution]
[Topic 3 based on market developments] Keep me in mind for future programming. And thanks again for
running a great event.
[Your Name]
https://enovari.ai
10. Hackathon Sponsor Pitches
10C. Hackathon Follow-Up Templates
Post-Hackathon to Participants (User Acquisition)
Subject: Your Enovari access continues -- keep building
Hi [First Name],Thanks for hacking at [Hackathon Name]. Hope your project went well.
Your free Enovari access continues for [X more weeks]. If persistent
AI memory was useful during the hackathon, it's even more useful for
ongoing projects.
Your account: https://enovari.ai
Quick start docs: [link]
If you have feedback on the API or ran into issues during the hackathon,
I'd love to hear it -- just reply.
Happy building.
[Your Name]
Founder, Enovari
Post-Hackathon to Organizers (Relationship Building)
Subject: Thanks for [Hackathon Name] -- feedback + future events
Hi [Organizer First Name],Thanks for a great event. Quick stats from our end:
[X] teams used Enovari during the hackathon
[Notable project or winner in our category]
[Any feedback or metrics you have] I'd love to sponsor future events. Was the API-access + prize model
useful for your participants? Happy to adjust the package for next
time.
Keep me in the loop on upcoming events.
[Your Name]
https://enovari.ai
11. Academic Researcher Outreach
11D. Academic Outreach Follow-Up Templates
After Initial Contact (No Response)
Subject: Re: [Original Subject Line]
Dear Professor [Last Name],Following up on my note about a potential [research collaboration /
guest lecture]. I know academic schedules are demanding.
Since I last wrote, [one new development -- a relevant paper you
published, a product milestone, or relevant news in the AI memory
space].
Happy to work around your schedule. Even a brief email exchange
would be valuable if a call doesn't fit your availability.
Respectfully,
[Your Name]
https://enovari.ai
After a Research Meeting (Next Steps)
Subject: Next steps from our conversation -- Enovari research collaboration
Dear Professor [Last Name],Thank you for the conversation on [date]. To summarize what we
discussed:
[Key point 1]
[Key point 2]
[Agreed next steps] On my end, I'll [specific action items and timeline]. On your end,
[their action items if any].
I'm excited about the potential here. Looking forward to moving
this forward.
[Your Name]
https://enovari.ai
12. Best Practices & Playbook
12E. Follow-Up Cadence
The Master Follow-Up Schedule
| Follow-Up | Timing | Tone | Key Principle |
| 1st | 3-7 business days | Helpful bump | Add new value (new development, data, angle) |
| 2nd | 7-14 business days | Respectful check-in | Make it easier to say yes (offer outline, free account, etc.) |
| 3rd (if applicable) | 14-25 business days | Graceful close | The breakup email -- give them an easy out |
| Touch | Day | Content | Subject Line |
| Initial email | Day 0 | Full pitch (formal, casual, or ultra-short) | Original subject |
| Follow-up 1 | Day 5-7 | Add a new angle or development. 4-5 sentences. | Re: [Original] |
| Follow-up 2 | Day 12-14 | Offer flexibility (different format, topic, timing). 2-3 sentences. | Re: [Original] |
| Breakup | Day 20-25 | Graceful close. 2 sentences. | "Closing the loop on [Podcast Name] guest pitch" |
| Touch | Day | Content | Subject Line |
| Initial email | Day 0 | Problem + solution + CTA | Original subject |
| Follow-up 1 | Day 4 | Social proof or specific use case. 3-4 sentences. | Re: [Original] |
| Follow-up 2 | Day 9 | Final value add (link to demo video or tutorial). 2 sentences. | Re: [Original] |
| Touch | Day | Content | Subject Line |
| Initial email | Day 0 | Full partnership proposal | Original subject |
| Follow-up 1 | Day 7 | Simplify the ask (suggest smallest possible first step). | Re: [Original] |
| Follow-up 2 | Day 14 | New angle or updated value prop. | Re: [Original] |
| Breakup | Day 21 | Leave the door open. 2 sentences. | Re: [Original] |
| Touch | Day | Content | Subject Line |
| Initial email | Day 0 | Introduction + specific ask (advice, not money) | Original subject |
| Follow-up 1 | Day 7 | Share a specific insight or data point about the market. | Re: [Original] |
| Follow-up 2 | Day 14 | Offer to be a resource on AI memory space. | Re: [Original] |
| Tool | Free Tier | What It Tracks | Notes |
| Mailtrack (mailtrack.io) | Unlimited tracking for Gmail | Opens, click tracking | Chrome extension. Free tier adds a "Sent with Mailtrack" signature (paid at ~$5/mo removes it). Reliable open tracking. |
| Streak (streak.com) | 500 tracked emails/month | Opens, link clicks, reply tracking | Chrome extension + lightweight CRM. Good for solo founders. Free tier also includes basic pipeline management. |
| HubSpot Sales Extension | 200 notifications/month | Opens, clicks, meetings | Part of HubSpot free CRM. More powerful but heavier setup. |
| Mailspring (getmailspring.com) | Unlimited | Open tracking, link tracking | Desktop email client (not just Gmail). Open source. Works with any email provider. |
| Mixmax (mixmax.com) | Limited free tier | Opens, clicks, scheduling | Gmail focused. Free tier is very restricted (capped at a small number of recipients). Better on paid plans. |
| Tool | Free Tier | Notes | |
| Hunter.io | 25 verifications/month (also 25 email finder searches/month) | Also finds email addresses. Best for small-volume outreach. | |
| NeverBounce | Free trial credits (typically 1,000 verifications) | High accuracy. Pay-as-you-go after trial (~$0.008/verification). | |
| ZeroBounce | 100 free verifications/month | Good accuracy. Monthly free credits reset. Also offers email scoring. | |
| EmailListVerify | 100 free verifications (one-time) | One-time free credits, not monthly. Bulk pricing is competitive. | |
| MillionVerifier | 200 free verifications | Low cost at scale ($0.50/1,000). Worth knowing about for larger campaigns. | |
| Tool | Free Tier | Notes | |
| Warmup Inbox (warmupinbox.com) | 7-day free trial | Automated warmup by sending/receiving emails between real accounts. ~$15/mo after trial. | |
| Lemwarm (by Lemlist) | Included with Lemlist subscription (~$39/mo) | Not free but effective. Lemlist is a full cold email platform. | |
| Instantly.ai warmup | Included with Instantly plan (~$30/mo) | Instantly is a cold email tool with built-in warmup. Good all-in-one option. | |
| Manual warmup | Free | Send real emails to friends/colleagues who reply. Slower but costs nothing. See the detailed warmup schedule in section 12A. | |
| Tool | Free Tier | Notes | |
| GMass (gmass.co) | 50 emails/day free | Gmail-based. Simple mail merge with tracking. Good for getting started. Note: free tier adds a GMass footer. | |
| Yet Another Mail Merge (YAMM) | 50 emails/day | Google Sheets integration. Simple and effective. One of the easiest tools to start with. | |
| Woodpecker (woodpecker.co) | 7-day free trial (not a permanent free tier) | More sophisticated cold email tool with sequences and auto follow-ups. Starts at ~$49/mo. Worth evaluating when you're ready to invest. | |
| Instantly.ai | No free tier (starts ~$30/mo) | Cold email platform with warmup, sequences, and sending rotation. Worth noting for when you're ready to scale. | |
| Apollo.io | 250 emails/day on free plan | Prospecting + sending + CRM. The free plan is generous and includes email sequences. Worth evaluating. | |
| Trigger | Risk Level | What to Do | |
| No SPF/DKIM/DMARC | Critical | Set up all three before sending anything | |
| Brand-new domain | High | Warm up for 4-6 weeks | |
| High bounce rate (> 3%) | High | Verify all addresses before sending | |
| Spam complaints > 0.1% | High | Reduce volume, improve targeting | |
| URL shorteners (bit.ly, etc.) | Medium-High | Never use URL shorteners in cold emails | |
| Too many links (3+) | Medium | Stick to 1-2 links | |
| HTML-heavy formatting | Medium | Use plain text for cold outreach | |
| Image-heavy content | Medium | No images in cold emails | |
| Tracking pixels (from tools) | Medium | Use with caution; skip for high-value targets | |
| Certain words ("free," "guarantee") | Low-Medium | Minimize but don't obsess; context matters more than individual words | |
| All-caps subject line | Medium | Never use all caps | |
| Excessive exclamation marks | Low-Medium | One max per email, zero is better | |
| Sending from generic address (info@, team@) | Low | Always send from a personal address | |
| # | Template | Section | Primary Use Case |
| 1A | AI/Tech Podcast Pitch | 1A | Pitching AI-focused podcast appearances |
| 1B | Startup/Indie Hacker Podcast Pitch | 1B | Pitching founder-story podcast appearances |
| 1C | General Business Podcast Pitch | 1C | Pitching business-audience podcast appearances |
| 1D | Podcast Follow-Ups (1st, 2nd, 3rd) | 1D | Following up on podcast pitches |
| 2A | Guest Post Pitch | 2A | Pitching written articles to publications |
| 2B | Product Feature Pitch | 2B | Getting Enovari covered/reviewed |
| 2C | Technical Article Pitch | 2C | Pitching deep-dive technical content |
| 2D | Blog/Publication Follow-Ups | 2D | Following up on publication pitches |
| 3A | AI Newsletter Submission | 3A | Getting featured in AI newsletters |
| 3B | Tech Newsletter Submission | 3B | Getting featured in tech newsletters |
| 3C | Startup Newsletter Submission | 3C | Getting featured in startup/founder newsletters |
| 4A | YouTube Creator Pitch | 4A | Getting YouTube coverage/reviews |
| 4B | Twitter/X Influencer DM | 4B | Engaging Twitter influencers |
| 4C | LinkedIn Connection + Follow-Up | 4C | LinkedIn influencer/prospect engagement |
| 4D | Free Account for Review | 4D | Offering free access for honest reviews |
| 5A | Press Release Email | 5A | Distributing press releases to journalists |
| 5B | Story Pitch | 5B | Pitching feature stories to press |
| 5C | HARO/Connectively/Qwoted Response | 5C | Responding to journalist queries |
| 5D | Embargo Offer | 5D | Offering embargoed access to press |
| 6A | Integration Partnership | 6A | Proposing technical integrations |
| 6B | Cross-Promotion | 6B | Proposing audience-sharing arrangements |
| 6C | Co-Marketing | 6C | Proposing joint content/events |
| 7A | Cold Email -- Developers | 7A | Acquiring developer users |
| 7B | Cold Email -- Businesses | 7B | Acquiring business users |
| 7C | Referral Ask | 7C | Getting referrals from existing users |
| 7D | Testimonial Request | 7D | Collecting user testimonials |
| 8A | Angel/Micro-VC Introduction | 8A | Building investor relationships |
| 8B | Operator-Angel Outreach | 8B | Getting advice from operator-investors |
| 8C | VC Relationship-Building | 8C | Pre-raise VC relationship development |
| 8D | Investor Follow-Ups | 8D | Following up on investor conversations |
| 9A | Conference Speaker Pitch | 9A | Getting speaking slots at conferences |
| 9B | Conference Booth/Sponsor | 9B | Getting exhibitor presence at conferences |
| 9C | Conference Follow-Ups | 9C | Post-conference relationship building |
| 10A | Hackathon Sponsor Pitch | 10A | Sponsoring hackathons with API access |
| 10B | University Hackathon Pitch | 10B | Sponsoring student hackathons |
| 10C | Hackathon Follow-Ups | 10C | Post-hackathon user acquisition and relationship building |
| 11A | AI/ML Researcher Collaboration | 11A | Research partnerships with professors |
| 11B | PhD/Postdoc Outreach | 11B | Research partnerships with early-career researchers |
| 11C | Guest Lecture Pitch | 11C | Speaking in university courses |
| 11D | Academic Follow-Ups | 11D | Following up on academic outreach |
Document created: April 2026 Last updated: April 2026 Total templates: 50+ (with formal, casual, and ultra-short variants plus follow-ups) New sections added: Investor outreach, conference organizer pitches, hackathon sponsor pitches, academic researcher outreach, A/B testing guidance, deliverability deep dive, multi-touch follow-up sequences