The follow-up email is one of the most repeated and least systematised activities in a SaaS AE's workflow. Most reps write every follow-up from scratch, producing inconsistent quality, missing strategic elements, and taking far longer than the task requires. The best-performing reps — and the teams that coach them well — have frameworks for every follow-up scenario that are specific enough to produce high-quality output quickly and flexible enough to accommodate the real context of each deal.
This prompt pack gives SaaS AEs a complete set of AI prompts and writing frameworks for every follow-up scenario they encounter regularly. Each entry includes a prompt for AI-assisted drafting and the structural elements the email should contain.
---
In both cases, the output should sound like you. Edit anything that sounds like AI-generated marketing copy.
---
- The specific pain discussed: [description of pain in prospect's own words]
- The quantified business impact (if established): [number or range]
- The next step agreed on the call: [specific action, owner, and date]
- One relevant reference customer to include: [company type, use case, outcome]
The email should: confirm the understanding of the pain (in their words, not mine), state the specific outcome Brazn produces for this use case, reference the next step with full specificity, and include the reference customer. Maximum 200 words. No marketing language." Structural elements:- Specific opening referencing a detail from the call
- Pain confirmation in prospect's language
- One-line outcome statement (theirs, not ours)
- Reference customer (one sentence)
- Next step restated with owner, action, and date
- Brief close — no filler
---
- The specific use cases demonstrated: [list 2–3 specific capabilities shown]
- The positive reactions noted during the demo: [specific comments or moments of engagement]
- Open questions or concerns raised: [specific objections or questions that came up]
- The next step agreed: [specific action, owner, date]
The email should: personalise the opening to a specific moment in the demo, briefly recap the two most relevant capabilities against their specific use case, address the key concern raised directly (not defensively), confirm the next step. Maximum 200 words." Structural elements:- Opening referencing a specific demo moment
- Two capability → outcome statements (their use case, their metrics)
- Direct address of the primary concern raised
- Next step with specificity
- Low-friction close
---
- What was discussed at the executive level: [key topics relevant to the executive's priorities]
- The business impact framing: [ROI or strategic outcome most relevant to this executive's concerns]
- The next step agreed: [specific action]
The email should be: concise (under 150 words), peer-appropriate in tone (no deference, no over-enthusiasm), focused on the business outcome rather than the product, and clear about the next step. This executive hasn't been in previous calls — the email should stand alone." Structural elements:- Peer-level opening (no flattery)
- One paragraph: problem + outcome in their strategic language
- One supporting evidence point (reference or data)
- Clear next step
- Brief, direct close
---
- The specific value proposition established in discovery: [pain + outcome]
- The last committed next step that didn't happen: [what was agreed but not followed through]
- Any external context that adds relevance now: [company news, competitor development, market development — if any]
The email should: be direct and honest (not passive-aggressive), acknowledge that priorities shift, ask a specific diagnostic question to understand what has changed, and make a specific low-friction ask. No guilt, no pressure. Under 150 words." Structural elements:- Direct, honest opener (no "just checking in")
- One honest acknowledgement that priorities change
- One specific diagnostic question
- One low-friction ask (reply, not a meeting)
---
- What the proposal covered: [brief description — not the full proposal]
- The specific business case: [the ROI or outcome the proposal was built around]
- Any specific context or question worth raising: [a clarifying question or a new supporting point not in the original proposal]
The email should: not reference the proposal as the first sentence, add one piece of new value (a question, an insight, a relevant reference), and make a specific ask. No 'just following up.' Under 100 words." Structural elements:- Open with new value, not proposal reference
- One new piece of relevant information
- One specific question or ask
- Under 100 words
---
- The prospect's stated decision criteria: [their specific evaluation criteria]
- Where Brazn is stronger than [competitor] on those criteria: [specific, factual differentiation — not marketing claims]
- A relevant reference customer who came from [competitor] or evaluated [competitor]: [if available]
The email should: acknowledge the evaluation without appearing threatened, make one specific, evidence-based differentiation point directly tied to their stated criteria, offer one way to validate the differentiation claim (a reference call, a specific demo scenario, a technical proof point). No disparagement of the competitor. Under 175 words." Structural elements:- Confident, not defensive opening
- One specific, criteria-matched differentiation point
- One validation offer (reference, technical proof, specific demo)
- Brief close
---
- What the champion needs to accomplish in the presentation: [get EB approval, get budget confirmed, get legal process started]
- The key objections they're likely to face from [audience]: [specific concerns based on the audience's known priorities]
- The supporting materials available: [business case document, ROI calculation, reference customer, security documentation]
The email should: give the champion a clear, structured narrative for the presentation, pre-empt the most likely objections with specific responses, confirm the supporting materials they have and what each is best used for, and offer to be available for any last-minute questions before or after. Under 250 words." Structural elements:- Recommended presentation narrative (3-point structure)
- Pre-empted objections with specific responses
- Supporting materials guide
- Availability offer
---
- The stated reason for the decision: [competitor win reason or no-decision reason]
- The relationship quality with the champion: [strong / cordial / professional]
- Any relevant context about the decision that might change over time: [competitive product gap, budget constraint, timing issue]
The email should: thank them without grovelling, acknowledge the decision without contesting it, leave the door genuinely open without sounding like a follow-up sales email, and make a non-commercial ask if appropriate (feedback on what drove the decision). Under 125 words." Structural elements:- Genuine, gracious acknowledgement (no pressure, no reconsideration pitch)
- One non-commercial ask for feedback
- Door left open with specific, authentic framing
- Under 125 words
---
- Key outcomes achieved since implementation: [specific, quantified outcomes — use the customer's own metrics where possible]
- Usage and health: [account health summary — high usage / moderate / recovering]
- Expansion opportunity (if relevant): [specific use case or team that would benefit from expansion]
The email should: lead with outcomes (what has been achieved, in their metrics), propose a specific QBR or renewal planning conversation, surface the expansion opportunity naturally if one exists. Not a commercial pitch — a value review conversation invitation. Under 175 words." Structural elements:- Outcomes-first opening (their metrics)
- QBR / renewal conversation invitation
- Expansion framing (optional, if appropriate)
- Specific ask with proposed date
---
Brazn generates structured follow-up email drafts automatically after every call — extracting the pain summary, MEDDPICC elements, next step commitments, and objections from the transcript and populating the relevant prompt framework. For AEs managing 8–12 active deals, Brazn's automatic draft means every call has a high-quality follow-up sent within the hour — without the rep spending 20 minutes writing from memory. The prompts in this pack are the manual framework; Brazn is the automation layer that makes them instant.
---
Book a demo to see how Brazn AI fits into your sales stack.
About the Author
Alex Margarit, Sales AI Expert, SaaS Sales Leader, BMC, ServiceNow, Docusign — 25+ years in SaaS sales.