--- title: "Email Templates" description: "Sales email templates for AINative Studio — cold outreach, follow-up, trial conversion, enterprise upgrade, and partner proposals" canonical: "https://docs.ainative.studio/docs/sales/email-templates" last-updated: "2026-11-02T18:12:43.468Z" --- # Email Templates Source: https://docs.ainative.studio/docs/sales/email-templates > Sales email templates for AINative Studio — cold outreach, follow-up, trial conversion, enterprise upgrade, and partner proposals # Email Templates **Version**: 1.0 **Last Updated**: 2026-06-18 **Refs**: #4201 --- ## How to Use These Templates - **Personalization tokens** are marked `{{LIKE_THIS}}` — always fill them before sending - **Send timing** is based on observed reply rate patterns; adjust to your sequence cadence - All emails are written for plain-text first; HTML formatting is optional - Subject line A/B variants are provided for each template --- ## Template 1 — Cold Outreach to AI Startups **Use Case**: First touch to a prospect who has an AI product or is building with LLMs. **Send Timing**: Tuesday–Thursday, 8–10am recipient local time. Do not send Monday AM or Friday PM. **Subject Lines** (A/B test these): - `A: Your AI agent doesn't remember anything — here's why that matters` - `B: How {{COMPANY_NAME}} can ship agents in <60 seconds` - `C: The infrastructure problem behind 95% of failed AI pilots` --- **Body**: ``` Hi {{FIRST_NAME}}, I noticed {{COMPANY_NAME}} is building {{PRODUCT_DESCRIPTION}} — {{PERSONALIZED_OBSERVATION_ABOUT_THEIR_AI_USE_CASE}}. Quick question: when your agent finishes a session, does it remember what happened? Most teams we talk to hit the same wall: they've got the model working, but the agent forgets everything when the session ends. They either build a custom memory layer (takes 2–3 months and someone always owns it forever) or ship without memory (and the product feels brittle). We built ZeroDB specifically for this. It's agent-native memory — not pgvector bolted onto Postgres, not a Redis hack. Sub-second cold-start, episodic-to-semantic consolidation, 91.5% on the full LoCoMo memory benchmark (one of the highest published scores). We also route across 100+ AI models automatically — so when Cerebras is 10x cheaper for a task, your agent uses Cerebras. When you need OpenAI quality, it routes there. You don't think about it. 7,270 teams are using AINative today. 24x growth in 6 weeks, zero paid marketing. Worth a 20-minute call to see if it fits what you're building? — {{SENDER_NAME}} AINative Studio | ainative.studio ``` **Personalization Tokens**: - `{{FIRST_NAME}}` — Prospect's first name - `{{COMPANY_NAME}}` — Their company - `{{PRODUCT_DESCRIPTION}}` — One-line description of what they build (from LinkedIn/website) - `{{PERSONALIZED_OBSERVATION_ABOUT_THEIR_AI_USE_CASE}}` — Something specific you noticed (e.g., "you mentioned agent memory is your Q3 focus in your last blog post") - `{{SENDER_NAME}}` — Your name **Follow-Up Cadence**: - Day 0: Send this email - Day 3: Follow-up #1 (Template 2 variation — shorter, add value) - Day 7: Follow-up #2 (bump thread, add a new proof point) - Day 14: Break-up email ("I'll stop reaching out, but the door is open") --- ## Template 2 — Follow-Up After Demo **Use Case**: Prospect attended a demo, went quiet. Re-engage with specifics from the demo. **Send Timing**: 2–3 business days after demo. If no reply, follow up again at day 7. **Subject Lines**: - `A: Following up — {{SPECIFIC_USE_CASE_FROM_DEMO}}` - `B: Next steps for {{COMPANY_NAME}}'s agent memory` - `C: The ZeroDB setup we discussed (+ a shortcut)` --- **Body**: ``` Hi {{FIRST_NAME}}, Thanks for the time on {{DEMO_DATE}}. I wanted to follow up on a few things we discussed. You mentioned {{SPECIFIC_PAIN_POINT_FROM_DEMO}} — here's what I'd suggest as a starting point: 1. **ZeroDB Free** — spin it up today, no credit card. Your agent has persistent memory in an afternoon. → npx zerodb-cli init {{COMPANY_NAME_LOWERCASE}}-agent 2. **Inference Router** — you mentioned you're currently going direct to {{MODEL_THEY_MENTIONED}}. Our router handles fallback, cost optimization, and rate limit spreading across 100+ providers automatically. 3. **MCP connectivity** — {{SPECIFIC_TOOL_THEY_MENTIONED}} connects in about 10 lines of JSON config. I can send you the exact snippet. I've also attached a one-pager on how {{SIMILAR_COMPANY_TYPE}} teams typically start with us. Two questions: - Is there a specific timeline you're working toward for {{USE_CASE_DISCUSSED}}? - Who else on your team should be looped in before you move forward? Happy to do a shorter follow-up call (15 min) to answer any remaining questions, or I can just send over the technical docs and let your team evaluate async. — {{SENDER_NAME}} AINative Studio | ainative.studio/docs ``` **Personalization Tokens**: - `{{FIRST_NAME}}` — Prospect's first name - `{{DEMO_DATE}}` — Date of the demo (e.g., "Thursday") - `{{SPECIFIC_PAIN_POINT_FROM_DEMO}}` — The main problem they articulated during the call - `{{COMPANY_NAME_LOWERCASE}}` — Lowercased company name for the CLI command - `{{MODEL_THEY_MENTIONED}}` — The model provider they're currently using - `{{SPECIFIC_TOOL_THEY_MENTIONED}}` — Tool or integration they asked about - `{{SIMILAR_COMPANY_TYPE}}` — Category description (e.g., "B2B SaaS", "dev tools startup") - `{{USE_CASE_DISCUSSED}}` — Their specific use case from the demo - `{{SENDER_NAME}}` — Your name **Notes**: - Do not attach anything on the first follow-up — keep it action-oriented - The two-question close is intentional: it surfaces urgency and decision-makers simultaneously - If they reply to the demo with "send me pricing," skip this template and go straight to the enterprise pitch --- ## Template 3 — Trial Expiration (Convert to Paid) **Use Case**: User has been on Free tier, is approaching the token limit or has been active for 14+ days. Prompt conversion to Pro. **Send Timing**: Day 14 of trial OR when they hit 80% of Free tier token limit. Send at 9am UTC. **Subject Lines**: - `A: You've used {{USAGE_PERCENT}}% of your AINative free tokens` - `B: Your agents are going to hit a wall soon — here's how to avoid it` - `C: {{FIRST_NAME}}, quick question about your AINative usage` --- **Body**: ``` Hi {{FIRST_NAME}}, You've been building with AINative for {{DAYS_ACTIVE}} days — and based on your usage, you're doing real work. Quick heads-up: you've used {{USAGE_PERCENT}}% of your free tier allocation. When you hit 100%, your agents will queue (not crash — but you'll notice latency). To keep things running without interruption: **Pro — $49/month** - 10M tokens/month ({{MULTIPLIER}}x your current usage headroom) - Priority model routing (lower latency during peak) - Dedicated ZeroDB storage (no shared pool) - Email support Upgrade takes 30 seconds: ainative.studio/settings/billing If you're hitting limits faster than expected, it usually means one of two things: 1. Your agent is calling the model on every keystroke (we can help tune this) 2. You're actually doing more volume than you realized — which is a good problem Either way, reply here and I'll take a look at your usage patterns with you. — {{SENDER_NAME}} AINative Studio P.S. If you're a student or working on an open-source project, reply and let me know. We have a program for that. ``` **Personalization Tokens**: - `{{FIRST_NAME}}` — User's first name - `{{DAYS_ACTIVE}}` — How long they've been on Free (pull from user record) - `{{USAGE_PERCENT}}` — Percent of free token allocation used - `{{MULTIPLIER}}` — How many times their current usage fits in Pro (e.g., "5x") - `{{SENDER_NAME}}` — Support or sales sender name **Notes**: - The P.S. about students/OSS is intentional — it shows good faith and reduces churn from users who would otherwise just abandon - Do NOT send this email until day 7 minimum — users who are still in setup should not feel pushed - If usage is low but 14 days have passed, use a different angle: "We noticed you haven't explored X feature yet — here's how it works" --- ## Template 4 — Enterprise Upgrade Pitch **Use Case**: Pro user at a company with 5+ seats or signs of high-volume usage. Pitch Enterprise. **Send Timing**: When a Pro user has had 3+ active users on the account for 30+ days, OR when they open a support ticket about rate limits or team access. **Subject Lines**: - `A: {{COMPANY_NAME}} is outgrowing Pro — here's what Enterprise unlocks` - `B: Team access + 10M org token pool for {{COMPANY_NAME}}` - `C: Quick question about your team's AI usage, {{FIRST_NAME}}` --- **Body**: ``` Hi {{FIRST_NAME}}, I was looking at {{COMPANY_NAME}}'s usage and noticed {{USAGE_OBSERVATION}} — which tells me you're past the "experimenting" phase and into real production. When teams get to this point, they usually run into three things: 1. **Token contention** — individual seats fighting for pool space 2. **Access management** — you want your whole team to have access without sharing credentials 3. **Priority support** — when something breaks at 2am, you need a response, not a ticket queue Enterprise solves all three: **Enterprise — $999/month** - 10M org token pool shared across your team - 1M tokens per user (individual guarantees) - 10 seats included - $0.50 per 1M tokens overage (predictable, not punishing) - Priority support with SLA - Dedicated account manager - Custom ZeroDB retention policies - SOC 2 documentation on request For context: if you're paying $49/mo per seat across 5 developers, you're already at $245/mo. Enterprise is $999/mo but gives you 10 seats + the org pool + priority support. The math usually works out at 5+ active users. Want me to run the numbers for your specific usage? I can pull your current consumption and model what Enterprise would look like. — {{SENDER_NAME}} AINative Studio | Enterprise Sales P.S. We're offering a 30-day Enterprise trial for accounts that qualify. If you want to test drive it before committing, let me know. ``` **Personalization Tokens**: - `{{FIRST_NAME}}` — Prospect's first name - `{{COMPANY_NAME}}` — Their company name - `{{USAGE_OBSERVATION}}` — Specific observation (e.g., "your team has made 47,000 API calls this month" or "you've added 4 new team members in the last 2 weeks") - `{{SENDER_NAME}}` — Enterprise sales rep name **Notes**: - Never send this cold — it requires account data to be credible - The P.S. Enterprise trial offer has a high conversion rate; use it liberally - If they're a developer asking about Enterprise for a client, pivot to the reseller/agency angle --- ## Template 5 — Partner / Integration Proposal **Use Case**: Reaching out to a tool, framework, or platform company about an integration partnership or co-marketing. **Send Timing**: Tuesday–Thursday, 9–11am recipient local time. Reach the CTO or DevRel lead, not sales. **Subject Lines**: - `A: {{THEIR_PRODUCT}} + AINative: native integration proposal` - `B: {{FIRST_NAME}} — 7,270 developers who might want {{THEIR_PRODUCT}}` - `C: Co-marketing idea for {{THEIR_PRODUCT}} × AINative MCP` --- **Body**: ``` Hi {{FIRST_NAME}}, I'm {{SENDER_NAME}} from AINative Studio — we build AI infrastructure for developers: ZeroDB (agent memory), 100+ model routing, MCP server hosting, and Agent Cloud. We have 7,270 developers on the platform, with 511,000 API requests/day and 24x growth in 6 weeks. I'm reaching out because {{THEIR_PRODUCT}} + AINative is a natural integration. {{SPECIFIC_INTEGRATION_RATIONALE}}. What I'm proposing: **Technical integration**: {{SPECIFIC_INTEGRATION_DESCRIPTION}} - Timeline: 2–3 weeks engineering effort on our side - What we need from you: {{WHAT_WE_NEED_FROM_THEM}} - Result: {{WHAT_USERS_GET}} **Co-marketing** (optional, separate from the technical work): - Joint blog post / tutorial - Feature in AINative docs + newsletter (7,270+ subscribers) - Listing in our MCP server catalog We've done this with {{EXAMPLE_PARTNER_CATEGORY}} teams and the integrations consistently drive qualified signups to both platforms. Does this fit anything on your roadmap for {{CURRENT_QUARTER}}? Happy to set up a 30-minute call with your team. — {{SENDER_NAME}} AINative Studio | ainative.studio ``` **Personalization Tokens**: - `{{FIRST_NAME}}` — Recipient's first name - `{{THEIR_PRODUCT}}` — The partner company/product name - `{{SENDER_NAME}}` — Your name - `{{SPECIFIC_INTEGRATION_RATIONALE}}` — Why this integration makes sense (e.g., "developers using LangChain want persistent memory, and ZeroDB is the natural fit") - `{{SPECIFIC_INTEGRATION_DESCRIPTION}}` — What the integration actually does - `{{WHAT_WE_NEED_FROM_THEM}}` — API access, docs, a technical contact - `{{WHAT_USERS_GET}}` — The user-facing benefit - `{{EXAMPLE_PARTNER_CATEGORY}}` — A category of existing partner (e.g., "developer tool", "framework") — do NOT name specific companies unless you have permission - `{{CURRENT_QUARTER}}` — Current or next quarter (e.g., "Q3 2026") **Notes**: - Lead with their audience, not ours — "here's what your users get" before "here's what we get" - Do not mention revenue share in the first email — it signals you're transactional, not strategic - If they have an open-source project, star the repo before sending this email - Target DevRel or CTO for framework companies; BD or Partnerships for SaaS companies --- ## General Sending Guidelines | Rule | Why | |------|-----| | Always fill every `{{TOKEN}}` | Templated emails with unfilled tokens are an immediate delete | | Personalize the first sentence | Generic openers halve reply rates | | One clear CTA per email | Multiple CTAs create decision paralysis | | Keep to under 200 words when possible | Shorter emails have higher reply rates at cold stage | | Follow up 2–3 times before giving up | 80% of replies come after the first follow-up | | Never send from a shared alias | Replies need to land in a real person's inbox | | Test subject lines | A/B at 50/50 split for the first 100 sends, then lock in the winner | | Track open rates, not just replies | Low opens = subject line problem; low replies = body problem |