Sales professionals who need polished proposals fast. Copy these prompts into ChatGPT, fill in your details, and get proposal sections that close deals.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
RFP Responses
You are writing the executive summary for a competitive RFP response.
Company: {prospect_company_name} Industry: {prospect_industry} RFP value: {contract_value} Key requirements: {top_three_requirements} Your differentiator: {unique_competitive_advantage} Implementation timeline: {project_duration} Decision maker: {primary_contact_name_and_title} Tone: {professional / consultative / confident}
Write a 400 to 500 word executive summary that opens with their business challenge, positions your solution as the strategic choice, and closes with next steps. Use concrete metrics where possible and avoid generic vendor language.
When to use it: When you’re facing 15 other vendors in a formal RFP and need to stand out in the first two paragraphs.
Pro tip: Lead with their pain point, not your capabilities. Decision makers scan for who understands their problem first.
You are responding to an RFP’s technical requirements section.
Solution: {product_or_service_name} Technical requirements: {five_key_technical_specs} Compliance standards: {regulatory_requirements} Integration needs: {existing_systems_to_integrate} Security requirements: {security_specifications} Your technical advantage: {technical_differentiator}
Write a 600 to 700 word technical response that addresses each requirement directly, demonstrates compliance, and highlights your technical edge. Use a requirement-by-requirement format with clear headings.
When to use it: When the technical team will score your response before it reaches the business decision makers.
Pro tip: Mirror their exact requirement language in your headers. Evaluators often use Control+F to find specific compliance points.
You are writing the pricing section for a multi-year RFP response.
Total contract value: {total_price} Payment structure: {monthly_annual_or_milestone} Included services: {core_deliverables} Optional add-ons: {additional_services_and_pricing} Implementation costs: {setup_and_training_fees} Discount offered: {percentage_or_dollar_discount}
Write a 300 to 400 word pricing section that presents value before cost, breaks down pricing clearly, and justifies the investment with ROI language. End with payment terms.
When to use it: When you need to position premium pricing against lower-cost competitors in the RFP evaluation.
Pro tip: Always lead with value delivered, then show pricing. Never start a pricing section with dollar amounts.
You are writing the implementation timeline section for a complex RFP.
Project duration: {total_timeline_weeks_or_months} Key milestones: {four_to_five_major_milestones} Client responsibilities: {what_they_need_to_provide} Risk factors: {potential_delays_or_challenges} Go-live date: {target_completion_date} Resource requirements: {team_size_and_expertise_needed}
Write a 400 to 500 word implementation section with a clear timeline, defined responsibilities, and risk mitigation strategies. Use a phased approach with specific deliverables for each milestone.
When to use it: When the RFP asks for detailed project management and the client has been burned by failed implementations before.
Pro tip: Call out their responsibilities explicitly. Most project delays come from unclear client obligations, not vendor issues.
You are writing case study proof points for an RFP response.
Similar client: {comparable_company_name_and_industry} Their challenge: {client_problem_you_solved} Your solution: {what_you_implemented} Results achieved: {specific_metrics_and_outcomes} Timeline: {how_long_implementation_took} Client contact: {reference_name_and_title}
Write a 250 to 300 word case study that demonstrates relevant experience, quantifies results, and builds credibility. Focus on outcomes that matter to this specific RFP.
When to use it: When you need social proof that you’ve solved exactly this problem before for a similar company.
Pro tip: Pick case studies from the same industry or company size. Irrelevant success stories hurt more than they help in RFPs.
Initial Sales Proposals
You are writing a proposal for a first-time buyer who requested pricing after a discovery call.
Prospect: {company_name} Contact: {decision_maker_name_and_title} Problem identified: {main_business_challenge} Current process: {how_they_handle_this_today} Proposed solution: {your_product_or_service} Investment: {total_cost_and_payment_terms} Timeline: {implementation_duration} Next step: {proposed_meeting_or_trial}
Write a 500 to 600 word proposal that connects their problem to your solution, presents clear pricing, and ends with a specific call to action. Use consultative language, not sales pitches.
When to use it: When a qualified prospect asks for a proposal after your first or second meeting but hasn’t seen pricing yet.
Pro tip: Reference specific details from your discovery call in the problem section. Generic proposals signal you weren’t listening.
You are creating a proposal for an enterprise client comparing multiple vendors.
Company: {prospect_company_name} Industry: {industry_and_company_size} Key stakeholders: {decision_makers_and_influencers} Business objectives: {what_success_looks_like} Current challenges: {pain_points_discovered} Competitive landscape: {known_competitors} Differentiators: {your_unique_advantages} Investment level: {budget_range_discussed}
Write a 700 to 800 word strategic proposal that positions you as the partner of choice, addresses enterprise concerns, and differentiates from competitors without naming them directly.
When to use it: When you’re in a competitive deal with enterprise buyers who will compare proposals side-by-side.
Pro tip: Address enterprise concerns like security, scalability, and support directly. Mid-market approaches don’t work at enterprise scale.
You are writing a proposal for a price-sensitive prospect who’s hesitating on budget.
Prospect: {company_name} Budget concern: {specific_pricing_objection} Current cost: {what_they_pay_for_status_quo} ROI opportunity: {financial_benefit_of_your_solution} Flexible options: {payment_plans_or_scaled_versions} Risk of inaction: {cost_of_not_solving_the_problem} Proposed investment: {recommended_package_and_price}
Write a 400 to 500 word value-focused proposal that justifies the investment, offers flexibility, and quantifies the cost of delay. Lead with ROI, not features.
When to use it: When a qualified prospect loves your solution but is stuck on price and needs financial justification for their boss.
Pro tip: Always compare your price to the cost of their current approach, not just present your price in isolation.
You are writing a proposal for a prospect who needs legal and compliance approval.
Company: {prospect_company_name} Industry: {regulated_industry_if_applicable} Compliance requirements: {regulatory_standards_they_must_meet} Security concerns: {data_protection_requirements} Contract terms: {specific_legal_requirements} Approval process: {who_needs_to_sign_off} Implementation safeguards: {risk_mitigation_measures}
Write a 600 to 700 word compliance-focused proposal that addresses legal concerns, demonstrates security measures, and provides documentation for their approval process.
When to use it: When selling into healthcare, financial services, or other regulated industries where compliance teams review every vendor.
Pro tip: Attach your security certifications and compliance documentation. Don’t make them ask for it later in the approval process.
You are writing a proposal for a startup or small business with limited resources.
Company: {startup_or_small_business_name} Stage: {early_stage_growth_stage_or_established} Resource constraints: {budget_time_or_staff_limitations} Growth goals: {what_they_want_to_achieve} Quick wins needed: {immediate_results_required} Scalability concerns: {how_solution_grows_with_them} Proposed package: {right_sized_solution_and_pricing}
Write a 350 to 450 word lean proposal that focuses on immediate impact, acknowledges resource constraints, and scales with their growth. Emphasize quick implementation and early ROI.
When to use it: When selling to resource-constrained buyers who need results fast and can’t afford lengthy implementations.
Pro tip: Offer phased implementations that start small and expand. Startups need to see value before they can justify bigger investments.
Proposal Follow-ups
You are writing a follow-up email for a proposal sent three days ago with no response.
Prospect: {contact_name} Company: {company_name} Proposal sent: {date_proposal_was_sent} Key value proposition: {main_benefit_highlighted} Decision timeline: {when_they_said_they_need_to_decide} Next step offered: {meeting_demo_or_trial_proposed} Potential concern: {likely_reason_for_delay}
Write a 150 to 200 word follow-up email that checks in professionally, highlights key value, and offers to address concerns. Include a clear call to action.
When to use it: When your proposal is sitting in someone’s inbox and you need to restart the conversation without being pushy.
Pro tip: Always assume they’re busy, not disinterested. Offer to address specific concerns rather than just asking for feedback.
You are writing a follow-up for a proposal that received initial feedback requesting changes.
Prospect: {contact_name} Original proposal date: {when_first_proposal_was_sent} Feedback received: {specific_changes_or_concerns_raised} Adjustments made: {how_you_modified_the_proposal} Additional value added: {new_benefits_or_concessions} Revised timeline: {updated_implementation_schedule}
Write a 300 to 400 word follow-up that acknowledges their feedback, explains changes made, and repositions the revised offer. End with next steps to move forward.
When to use it: When a prospect engages with your proposal but asks for modifications before they can move forward.
Pro tip: Frame changes as improvements, not concessions. Show how their feedback helped you create a better solution for them.
You are writing a follow-up for a proposal that’s been under review for two weeks.
Prospect: {contact_name} Company: {company_name} Proposal value: {total_contract_value} Review duration: {how_long_they’ve_had_it} Key stakeholders: {who_else_is_involved_in_decision} Competitor activity: {any_known_competitive_pressure} Urgency factor: {business_driver_for_quick_decision}
Write a 250 to 300 word strategic follow-up that creates appropriate urgency, offers decision support, and advances the deal. Balance persistence with patience.
When to use it: When a significant proposal has been in review longer than expected and you need to understand decision status.
Pro tip: Offer to present to additional stakeholders rather than just asking for a decision. Long delays usually mean more people got involved.
You are writing a follow-up for a proposal that lost to a competitor.
Prospect: {contact_name} Winning competitor: {competitor_name_if_known} Reason for loss: {feedback_on_why_you_lost} Relationship status: {how_to_maintain_connection} Contract duration: {how_long_competitor_contract_lasts} Future opportunities: {other_projects_or_renewal_timing}
Write a 200 to 250 word gracious follow-up that accepts the decision, requests feedback, and positions for future opportunities. Maintain the relationship professionally.
When to use it: When you lose a competitive deal but want to maintain the relationship for future opportunities or referrals.
Pro tip: Always ask what the winner did differently. This feedback improves your next proposal and shows you’re committed to improvement.
You are writing a follow-up for a proposal that was approved but implementation has stalled.
Client: {contact_name} Company: {company_name} Proposal approved: {date_of_approval} Implementation delay: {how_long_since_approval} Suspected blockers: {likely_reasons_for_delay} Project value: {contract_value_at_risk} Resources allocated: {team_or_budget_you’ve_committed}
Write a 300 to 350 word implementation follow-up that addresses potential blockers, reconfirms project value, and proposes solutions to move forward. Be supportive, not demanding.
When to use it: When a client said yes to your proposal but the project hasn’t kicked off within the expected timeframe.
Pro tip: Offer to help with internal change management or stakeholder alignment. Implementation delays are often about internal resistance, not vendor issues.
Competitive Response Proposals
You are writing a proposal to replace an incumbent vendor who’s underperforming.
Prospect: {company_name} Current vendor: {incumbent_vendor_name} Performance issues: {specific_problems_with_current_solution} Switching costs: {time_money_effort_to_change} Migration plan: {how_you_handle_transition} Improvement metrics: {specific_better_outcomes_you_deliver} Risk mitigation: {how_you_minimize_switching_risk}
Write a 600 to 700 word replacement proposal that acknowledges switching costs, demonstrates superior value, and provides a clear migration path. Focus on measurable improvements.
When to use it: When a prospect is frustrated with their current vendor but nervous about the effort and risk of switching.
Pro tip: Provide detailed transition support and guarantees. The fear of a difficult switch-over often keeps clients with underperforming vendors.
You are writing a counter-proposal after learning you lost to a lower-priced competitor.
Prospect: {contact_name} Competitor chosen: {winning_competitor} Price difference: {how_much_less_they_quoted} Value gap: {capabilities_you_offer_that_they_dont} Risk factors: {potential_problems_with_cheaper_option} Revised offer: {any_adjustments_you_can_make} Implementation timeline: {when_they_need_to_start}
Write a 400 to 500 word value-focused counter-proposal that acknowledges the price difference, highlights risks of the cheaper option, and repositions your superior value. Avoid directly attacking the competitor.
When to use it: When price was the deciding factor but you believe the cheaper option will create problems they haven’t considered.
Pro tip: Focus on total cost of ownership, not just upfront price. Include implementation risks, support costs, and opportunity costs of lower performance.
You are writing a proposal to win back a former client who left for a competitor.
Former client: {company_name} Departure reason: {why_they_originally_left} Time with competitor: {how_long_theyve_been_gone} Current challenges: {problems_with_current_vendor} Relationship history: {your_previous_track_record} Improvements made: {how_youve_addressed_original_issues} Win-back offer: {special_terms_or_pricing}
Write a 500 to 600 word win-back proposal that acknowledges past issues, demonstrates improvements, and offers compelling terms to return. Balance accountability with confidence.
When to use it: When a former client reaches out because they’re having issues with the vendor they chose over you.
Pro tip: Lead with how you’ve improved since they left, not how bad their current vendor is. They need to see you’ve evolved, not that they made a mistake.
You are writing a proposal defending against a new competitor trying to unseat you.
Client: {current_client_name} Relationship duration: {how_long_youve_worked_together} Competitor threat: {new_vendor_pitching_them} Their value proposition: {what_competitor_is_promising} Your track record: {results_delivered_for_this_client} Upcoming improvements: {enhancements_or_new_features_coming} Retention offer: {additional_value_you_can_provide}
Write a 450 to 550 word retention proposal that reinforces your partnership value, addresses competitive threats, and provides additional incentives to stay. Emphasize relationship and proven results.
When to use it: When you learn a competitor is actively trying to steal your client with promises of better service or lower prices.
Pro tip: Focus on the risk and cost of switching, not just defending your current performance. Proven relationships have value that new vendors can’t match.
You are writing a proposal for a prospect comparing you to a much larger, established competitor.
Prospect: {company_name} Large competitor: {enterprise_vendor_name} Their advantages: {resources_scale_brand_recognition} Your advantages: {agility_service_specialization_innovation} Client fit: {why_youre_better_for_their_specific_needs} Risk factors: {potential_downsides_of_large_vendor} Success stories: {relevant_wins_against_big_competitors}
Write a 550 to 650 word David vs. Goliath proposal that positions your size as an advantage, highlights big-vendor risks, and demonstrates how you’re a better fit for their specific needs.
When to use it: When you’re the smaller, more nimble option competing against industry giants with bigger brands and resources.
Pro tip: Position their size as a disadvantage for personalized service and decision-making speed. Enterprise vendors often move slowly and treat smaller clients poorly.
Frequently Asked Questions
How can ChatGPT improve sales proposal writing speed in 2026?
ChatGPT eliminates the blank page problem by generating structured first drafts from your input variables. Instead of spending hours writing from scratch, you get professional copy in 30 seconds that you can edit and customize for each prospect.
What’s the best way to customize AI-generated proposal content?
Always modify the output to match your company’s voice and add specific details about your solution. Replace generic language with your actual product names, metrics, and case study details. The AI provides the structure and flow, but your expertise provides the substance.
How do I avoid generic-sounding AI proposals that hurt my credibility?
Use specific input variables like actual company names, real pain points from discovery calls, and concrete metrics from your experience. The more specific your inputs, the more authentic your output. Never send AI-generated content without adding personal touches and real examples.