Ready-to-use ChatGPT prompts for sales reps who need follow-up emails written fast. Copy any prompt, fill in the variables, and get a polished email you can send immediately.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Immediate Post-Demo Follow Up
You are a sales rep writing a follow-up email immediately after a product demonstration.
Prospect company: {company_name} Attendees: {attendee_names_and_titles} Demo date: {demo_date} Key features shown: {three_main_features_demonstrated} Specific use case discussed: {their_primary_use_case} Questions they asked: {two_to_three_questions} Next step mentioned: {trial / meeting / proposal / pricing} Your name: {your_name}
Write a 150 to 200 word follow-up email sent within 2 hours of the demo. Open with appreciation for their time and attention. Reference one specific moment from the demo that showed engagement. Attach relevant resources. Close with a clear next step and timeline.
When to use it: Right after you finish a demo call while the conversation is still fresh in everyone’s mind.
Pro tip: Send this within 2 hours maximum. After 24 hours, prospects start forgetting demo details and your response rate drops 40%.
You are a sales rep following up after a technical demo where multiple stakeholders attended.
Company: {company_name} Technical contact: {technical_contact_name} Business contact: {business_contact_name} Other attendees: {other_attendee_names} Technical concerns raised: {specific_technical_questions} Integration mentioned: {existing_tools_they_use} Timeline they mentioned: {their_implementation_timeline} Your technical expert: {your_technical_person_name}
Write a 200 to 250 word email addressing both technical and business stakeholders. Acknowledge the technical questions raised and provide specific answers or resources. Offer a technical deep-dive call. Include next steps for both the technical evaluation and business decision process.
When to use it: After demos with multiple decision makers where technical integration was a major discussion point.
Pro tip: Always CC your technical team member in these emails so prospects know they have direct access to technical expertise.
You are writing a follow-up email after a demo where the prospect seemed very interested but didn’t commit to next steps.
Prospect name: {prospect_name} Company: {company_name} Positive signals during demo: {specific_engagement_signals} Feature they liked most: {feature_they_responded_to} Current solution they use: {current_tool_or_process} Pain point you addressed: {specific_problem_your_product_solves} Hesitation or concern: {any_objection_or_hesitation}
Write a 180 to 220 word email that reinforces the value without being pushy. Reference their positive reactions. Address any hesitation indirectly. Suggest a specific next step like a trial or pilot program. Include a case study or ROI example relevant to their situation.
When to use it: When prospects are engaged but fence-sitting after seeing your product in action.
Pro tip: Include a relevant case study attachment with similar company size and use case. Social proof works better than feature repetition.
You are following up after a demo where the prospect requested specific customization or asked about features you don’t have.
Prospect: {prospect_name} Company: {company_name} Requested customization: {specific_customization_request} Missing feature they need: {feature_gap_identified} Workaround you can offer: {alternative_solution} Timeline for potential development: {if_applicable} Their current process: {how_they_handle_this_now} Decision timeline: {when_they_need_to_decide}
Write a 250 to 300 word email that honestly addresses the gap without losing the deal. Explain available workarounds. If relevant, mention product roadmap plans. Focus on the 80% of needs you do meet perfectly. Suggest a trial period to test the workaround approach.
When to use it: When your product doesn’t perfectly fit their requirements but you can still deliver value.
Pro tip: Be upfront about limitations early. Prospects appreciate honesty and it builds trust for the features you do deliver well.
You are writing a follow-up after a demo to multiple time zones where some stakeholders couldn’t attend live.
Company: {company_name} Demo attendees: {who_attended} Missing stakeholders: {who_missed_it} Key demo highlights: {three_main_points_covered} Recording available: {yes_or_no} Specific questions for missing people: {questions_to_address} Timeline pressure: {any_urgency_mentioned}
Write a 200 to 240 word email to the original attendees that makes it easy for them to share with missing stakeholders. Summarize key points concisely. Provide shareable resources. Offer to do a brief recap call for the missing people. Include clear next steps that account for the expanded decision group.
When to use it: When you know important decision makers missed your demo due to scheduling conflicts.
Pro tip: Create a one-page demo summary PDF that attendees can forward easily. Long emails don’t get shared internally.
Value Reinforcement Follow-Ups
You are writing a follow-up email focused on ROI after a successful product demo.
Prospect company: {company_name} Contact name: {prospect_name} Current cost of their process: {what_they_spend_now} Time they waste monthly: {hours_or_days_wasted} Team size affected: {number_of_people_impacted} Your solution’s cost: {your_pricing} Potential savings: {calculated_savings} Implementation time: {how_long_to_get_value}
Write a 300 to 350 word email that builds a compelling ROI case. Use specific numbers from their situation. Calculate payback period. Include a simple before/after comparison. Avoid overwhelming with too many metrics. Close with an offer to build a detailed ROI analysis together.
When to use it: 2-3 days after a demo when prospects are evaluating the business case internally.
Pro tip: Use their actual numbers, not industry averages. A $5,000 monthly saving based on their real costs beats a $50,000 hypothetical saving.
You are following up with a prospect who saw a demo but works in a highly regulated industry with compliance concerns.
Company: {company_name} Industry regulations: {specific_compliance_requirements} Security concerns raised: {data_security_questions} Compliance certifications you have: {your_security_credentials} Data handling they need: {their_data_requirements} Risk tolerance: {conservative_or_flexible} Compliance officer name: {if_mentioned}
Write a 280 to 320 word email that addresses compliance proactively. Detail your security measures and certifications. Offer compliance documentation. Suggest involving their compliance team early. Provide references from similar regulated companies. Balance thoroughness with readability.
When to use it: Following up with prospects in finance, healthcare, government, or other heavily regulated sectors.
Pro tip: Lead with your strongest compliance credential in the subject line. These buyers prioritize risk reduction over features.
You are writing a follow-up that positions your solution against a competitor they mentioned during the demo.
Prospect: {prospect_name} Company: {company_name} Competitor mentioned: {competitor_name} Their experience with competitor: {what_they_said} Your key differentiator: {main_advantage_over_competitor} Specific capability gap: {what_competitor_lacks} Price difference: {higher_lower_similar} Implementation difference: {easier_harder_faster}
Write a 220 to 260 word email that differentiates without attacking the competitor. Focus on your unique strengths. Acknowledge the competitor’s legitimate strengths. Emphasize fit for their specific use case. Include a comparison resource if available. Suggest a trial to experience the difference firsthand.
When to use it: When prospects explicitly mention evaluating competitors during your demo conversation.
Pro tip: Never badmouth competitors. Focus on why you’re better for their specific situation, not why the competitor is bad generally.
You are following up after a demo where the prospect mentioned budget constraints or cost concerns.
Company: {company_name} Budget concern mentioned: {specific_cost_objection} Current budget range: {if_they_shared_numbers} Value they’re seeking: {main_outcome_they_want} Flexible pricing options: {payment_plans_available} Pilot program option: {smaller_scope_alternative} Cost of doing nothing: {what_happens_if_they_wait}
Write a 250 to 290 word email that addresses cost concerns constructively. Reframe around value and ROI. Offer flexible options like phased implementation or pilot programs. Quantify the cost of inaction. Avoid discounting immediately. Focus on finding a path forward that fits their constraints.
When to use it: When price was clearly a barrier during the demo discussion but they’re still interested in the solution.
Pro tip: Offer a smaller scope pilot instead of a discount. It lets them experience value without committing full budget.
You are writing a follow-up to a prospect who loved the demo but needs to get internal buy-in from senior leadership.
Your champion: {internal_champion_name} Decision maker: {senior_leader_name_if_known} Champion’s role: {their_position} Presentation format: {board_meeting_email_casual_chat} Key business metrics: {revenue_cost_efficiency_metrics} Implementation timeline: {when_they_want_to_start} Stakeholder concerns: {what_leadership_might_object_to}
Write a 300 to 340 word email that arms your champion for internal selling. Provide an executive summary they can forward. Include key talking points and objection responses. Offer to join their internal presentation. Focus on business impact language, not technical features. Make it easy for them to look good internally.
When to use it: When your primary contact needs to sell your solution up the chain after being convinced by the demo.
Pro tip: Create a separate one-page executive summary attachment. Champions need easy-to-forward materials, not long emails.
Technical Follow-Up
You are following up after a technical demo where integration requirements were a major focus.
Company: {company_name} Technical contact: {tech_person_name} Current tech stack: {their_existing_tools} Required integrations: {specific_systems_to_connect} API requirements: {technical_specifications_needed} Data migration scope: {what_data_needs_moving} Timeline constraints: {technical_deadlines} Your solutions engineer: {your_tech_person}
Write a 280 to 320 word technical follow-up email. Address specific integration points discussed. Provide technical documentation links. Offer a technical deep-dive session. Include implementation timeline estimates. Suggest a proof-of-concept for complex integrations. Balance technical detail with business impact.
When to use it: After demos focused on technical implementation and system integration capabilities.
Pro tip: Include actual API documentation links, not promises to send them later. Technical buyers evaluate based on real technical specs.
You are writing a follow-up after demonstrating advanced features to a power user who asked detailed functionality questions.
Power user name: {user_name} Advanced features shown: {specific_capabilities_demonstrated} Use case complexity: {their_sophisticated_requirements} Questions they asked: {technical_questions_from_demo} Current workarounds: {how_they_solve_this_now} Efficiency gains possible: {time_or_effort_savings} Learning curve concerns: {training_requirements}
Write a 240 to 280 word email that speaks to their expertise level. Answer their technical questions directly. Provide links to advanced documentation or training materials. Acknowledge the learning investment required. Focus on long-term productivity gains. Offer power-user references or case studies.
When to use it: Following up with highly technical users who need sophisticated functionality, not basic features.
Pro tip: Connect them with existing power users at similar companies. Peer validation matters more than vendor promises for advanced use cases.
You are following up after a demo where data security and privacy were primary concerns.
Company: {company_name} Industry: {sector_with_data_sensitivity} Specific data concerns: {privacy_security_requirements} Compliance standards: {GDPR_HIPAA_SOX_etc} Data residency requirements: {geographic_restrictions} Security certifications needed: {required_credentials} Risk assessment process: {their_evaluation_approach}
Write a 320 to 360 word email addressing data security comprehensively. Detail your security architecture and certifications. Explain data handling procedures. Offer security documentation and audit reports. Suggest involving their security team in evaluation. Provide contact information for your security specialists.
When to use it: When data security dominated the demo conversation and follow-up questions.
Pro tip: Attach your latest security audit report or SOC 2 compliance documentation. Security teams want proof, not promises.
You are writing a follow-up after demonstrating mobile and remote access capabilities to a distributed team.
Company: {company_name} Team distribution: {remote_hybrid_global_setup} Mobile requirements: {device_types_and_usage} Connectivity challenges: {bandwidth_or_access_issues} Security for remote access: {mobile_security_concerns} Current remote workflow: {how_they_work_remotely_now} Productivity gaps: {remote_work_challenges}
Write a 260 to 300 word email emphasizing mobile and remote capabilities. Address connectivity and security for distributed teams. Provide mobile app store links or download instructions. Offer a mobile-focused trial period. Include case studies from other distributed teams. Focus on productivity and collaboration benefits.
When to use it: After demos focused on mobile access and remote team collaboration features.
Pro tip: Suggest they test mobile functionality during the trial period, not just desktop features. Remote capabilities are proven through experience.
You are following up after a demo where scalability and growth planning were key discussion points.
Company: {company_name} Current team size: {number_of_current_users} Growth projections: {expected_team_growth} Scaling timeline: {when_they_expect_to_grow} Performance requirements: {speed_capacity_needs} Budget scaling concerns: {cost_growth_worries} Current system limitations: {what_breaks_as_they_grow}
Write a 290 to 330 word email addressing scalability directly. Explain how pricing and performance scale with their growth. Provide examples of customers who’ve grown successfully on your platform. Address infrastructure and support scaling. Offer growth planning consultation. Focus on reducing scaling risk and complexity.
When to use it: When prospects are rapidly growing and worried about whether your solution can scale with them.
Pro tip: Share metrics from customers who’ve scaled 5x or 10x on your platform. Growing companies need proof of scalability, not just promises.
Objection Handling Follow-Ups
You are writing a follow-up after a demo where the prospect expressed concerns about implementation complexity and time.
Company: {company_name} Implementation concern: {specific_complexity_worry} Current bandwidth: {their_team_capacity} Timeline pressure: {when_they_need_results} Resource constraints: {people_time_budget_limits} Success metrics: {how_they_measure_success} Support level needed: {hands_on_or_self_service}
Write a 280 to 320 word email that simplifies the implementation path. Break down the process into clear phases. Highlight your implementation support and resources. Provide realistic timelines with quick wins identified. Offer implementation planning session. Include customer success stories with similar constraints.
When to use it: When prospects love your product but worry about the effort required to implement and adopt it successfully.
Pro tip: Offer a pre-implementation planning call to map out their specific rollout. Concrete planning reduces implementation anxiety.
You are following up after a demo where the prospect questioned whether your solution was worth switching from their current process.
Prospect: {prospect_name} Current solution: {what_they_use_now} Switching costs: {time_effort_risk_of_change} Status quo benefits: {what_works_about_current_approach} Pain points: {what_frustrates_them_now} Switching timeline: {when_change_might_happen} Risk tolerance: {conservative_or_aggressive}
Write a 250 to 290 word email that justifies the switching cost. Acknowledge what works about their current approach. Quantify the pain points you solve. Calculate the cost of staying with status quo. Suggest a parallel trial to reduce switching risk. Focus on incremental value, not wholesale replacement.
When to use it: When prospects see value but question whether it’s worth changing from their current solution.
Pro tip: Propose running a pilot alongside their current solution instead of full replacement. It reduces switching anxiety significantly.
You are writing a follow-up after a demo where the prospect said they need to see more proof of results before committing.
Company: {company_name} Proof requirements: {specific_evidence_they_need} Success metrics: {how_they_measure_success} Industry relevance: {their_sector_requirements} Company size similarity: {size_stage_relevance} Timeline for decision: {when_they_need_proof} Current results baseline: {what_they_achieve_now}
Write a 320 to 360 word email providing comprehensive proof of results. Include specific case studies with metrics. Offer customer references and testimonials. Suggest a results-focused pilot program with clear success criteria. Provide ROI calculations and performance benchmarks. Focus on measurable outcomes over features.
When to use it: When prospects need more evidence of real-world results before making a purchase decision.
Pro tip: Offer to connect them with 2-3 existing customers in similar situations. Peer conversations carry more weight than case studies.
Closing and Next Steps
You are writing a follow-up email designed to move a post-demo prospect toward a buying decision.
Prospect: {prospect_name} Company: {company_name} Decision timeline: {when_they_need_to_decide} Budget approved: {yes_no_pending} Stakeholders involved: {who_makes_final_decision} Remaining questions: {any_outstanding_concerns} Competitor evaluation: {other_solutions_they_are_considering} Trial interest: {yes_no_maybe}
Write a 300 to 340 word email that creates appropriate urgency without being pushy. Summarize the value proposition clearly. Address any remaining concerns. Suggest specific next steps with timelines. Offer trial or pilot options. Include social proof and risk mitigation. Make the path to “yes” very clear.
When to use it: When prospects have seen your demo, understand the value, and need a gentle push toward a decision.
Pro tip: Include a specific timeline for your proposal validity. Deadlines create action, but make them reasonable and business-justified.
You are following up with a prospect who attended your demo but has gone silent despite initial interest.
Company: {company_name} Last interaction date: {when_you_last_heard_from_them} Interest level shown: {high_medium_low} Next step mentioned: {what_they_said_they_would_do} Potential reasons for silence: {budget_priorities_timing} Value proposition: {main_benefit_for_their_situation} Urgency factors: {seasonal_deadline_competitive_pressure}
Write a 200 to 240 word re-engagement email that’s helpful, not needy. Acknowledge the silence professionally. Provide new value or insight. Suggest a brief check-in call. Offer to pause outreach if timing isn’t right. Include a relevant case study or industry insight. Keep the door open without being persistent.
When to use it: When previously engaged prospects stop responding after your demo and standard follow-ups.
Pro tip: Offer to “pause outreach until Q4” or whenever makes sense. Permission-based pausing often re-engages prospects immediately.
You are writing a follow-up to a prospect ready to move forward but needing help with internal approvals and budget sign-off.
Internal champion: {champion_name} Approval process: {steps_they_need_to_complete} Budget cycle: {when_budget_is_available} Decision makers: {who_needs_to_approve} Proposal requirements: {formal_proposal_specs} Timeline for approval: {how_long_process_takes} Supporting materials needed: {what_helps_their_case}
Write a 340 to 380 word email that supports their internal approval process. Offer proposal assistance and executive summaries. Provide budget justification materials. Suggest stakeholder presentations or calls. Include implementation timeline and resource requirements. Make their internal selling easier with ready-to-use materials.
When to use it: When your champion wants to buy but needs help navigating their company’s approval and budget process.
Pro tip: Create a “business case template” they can customize for their internal presentation. Do the work for them, not with them.
You are following up with a prospect who wants to start with a smaller pilot program before a full implementation.
Company: {company_name} Pilot scope: {limited_team_or_use_case} Pilot duration: {timeframe_for_test} Success criteria: {how_they_measure_pilot_success} Full rollout potential: {scope_of_eventual_expansion} Pilot budget: {budget_for_test_phase} Stakeholders in pilot: {who_will_participate} Evaluation timeline: {when_they_decide_on_expansion}
Write a 280 to 320 word email that structures a successful pilot program. Define clear scope and success metrics. Provide pilot-specific onboarding and support. Include expansion planning for pilot success. Address pilot-to-full pricing considerations. Focus on setting up the pilot for obvious success and easy expansion decision.
When to use it: When prospects want to test your solution with a limited group before committing to full deployment.
Pro tip: Build expansion triggers into the pilot agreement. When they hit success metrics, expansion should be the obvious next step.
You are writing a final follow-up email to a prospect who has evaluated your solution thoroughly but hasn’t made a decision.
Prospect: {prospect_name} Evaluation duration: {how_long_they_have_been_considering} Decision factors: {what_they_are_weighing} Alternative options: {status_quo_or_competitors} Proposal validity: {when_your_offer_expires} Account value: {importance_of_this_deal} Relationship status: {warm_cold_neutral}
Write a 260 to 300 word professional closing email. Summarize the opportunity cost of delayed decisions. Restate your value proposition concisely. Set a clear deadline for response or proposal validity. Offer one final concession or value-add if appropriate. Thank them for their time and consideration. Leave the relationship positive regardless of outcome.
When to use it: As a final attempt with prospects who have been evaluating for an extended period without deciding.
Pro tip: Actually mean it when you say “final follow-up.” Respect their decision process and your own time investment limits.