These AI prompts generate complete sales proposals you can send within minutes. Built for working sales professionals who need polished drafts fast, not consultants building systems from scratch.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Initial Proposal Creation
You are a sales professional writing a comprehensive business proposal for a new prospect.
Company: {prospect_company_name} Contact: {decision_maker_name} at {prospect_company_name} Industry: {prospect_industry} Pain points discovered: {three_specific_pain_points} Your solution: {core_product_or_service} Proposed timeline: {project_duration} Budget range: {dollar_amount_or_range} Key differentiator: {main_competitive_advantage} Next step: {meeting_demo_trial_or_contract}
Write a 800-1200 word proposal following this structure: Executive Summary (2 paragraphs), Problem Analysis (3 specific pain points with business impact), Proposed Solution (features tied directly to their pain points), Implementation Timeline, Investment & ROI, Next Steps. Use a consultative tone that demonstrates deep understanding of their business challenges.
When to use it: When you’re responding to an inbound lead or following up after a discovery call where you’ve identified clear pain points and budget authority.
Pro tip: Include specific metrics from their industry in the Problem Analysis section. “Companies in {industry} typically lose 23% revenue when X happens” hits harder than generic statements.
You are responding to a formal RFP with strict requirements and evaluation criteria.
RFP title: {rfp_document_title} Issuing organization: {client_organization} Key requirements: {five_must_have_requirements} Evaluation criteria: {scoring_factors_like_price_experience_approach} Your company: {your_company_name} Relevant experience: {similar_projects_or_clients} Team members: {key_people_and_roles} Proposed approach: {methodology_or_process} Total investment: {dollar_amount}
Write a 1000-1500 word RFP response structured as: Executive Summary, Understanding of Requirements, Proposed Approach & Methodology, Team Qualifications, Timeline & Deliverables, Investment, References. Address each evaluation criterion explicitly. Use formal business tone with specific examples that demonstrate capability.
When to use it: When responding to government RFPs or large enterprise procurement processes with formal scoring matrices.
Pro tip: Mirror their exact language from the RFP requirements. If they say “vendor must provide scalable solutions,” use “scalable solutions” in your response, not “flexible offerings.”
You are writing a follow-up proposal after an initial rejection or “not right now” response.
Prospect: {company_and_contact_name} Original proposal date: {date_of_first_proposal} Reason for initial rejection: {budget_timing_features_or_other} What’s changed: {new_circumstances_or_information} Modified solution: {adjusted_offering_or_approach} New timeline: {revised_implementation_schedule} Revised investment: {updated_pricing} Urgency factor: {deadline_or_business_driver} Relationship status: {warm_cold_or_existing_contact}
Write a 400-600 word re-engagement proposal. Open by acknowledging the previous conversation and what’s changed. Present the modified solution as a response to their original concerns. Include a clear call-to-action with urgency. Use a confident but not pushy tone that respects their original position while making the case for reconsideration.
When to use it: When a qualified prospect said no 3-6 months ago, but their situation or your offering has evolved enough to warrant another approach.
Pro tip: Reference something specific from your original conversation to prove you remember their situation. “You mentioned the Q4 budget freeze” shows you were listening, not just following up on everyone.
You are creating a proposal for a complex multi-phase project requiring board approval.
Client: {company_name} Project scope: {comprehensive_description_of_work} Phase 1: {first_phase_deliverables_and_timeline} Phase 2: {second_phase_deliverables_and_timeline} Phase 3: {third_phase_deliverables_and_timeline} Total project value: {full_engagement_dollar_amount} Phase 1 investment: {first_phase_cost} Key stakeholders: {decision_makers_and_influencers} Success metrics: {measurable_outcomes} Risk factors: {potential_challenges_or_obstacles}
Write a 1200-1800 word strategic proposal formatted for executive presentation. Include: Strategic Overview, Phased Approach with Milestones, Resource Requirements, Investment & ROI Analysis, Risk Mitigation, Success Metrics. Emphasize business impact over features. Use data-driven language suitable for C-suite review and board presentation.
When to use it: When selling enterprise deals over $100K that require multiple stakeholder buy-in and formal approval processes.
Pro tip: Include a one-page executive summary at the beginning. Board members often read only the summary, so pack your strongest ROI arguments there.
You are pitching a premium solution to a prospect currently using a lower-cost competitor.
Prospect: {company_and_contact_name} Current vendor: {competitor_name} What they’re paying now: {current_cost_or_range} Your premium solution: {higher_end_offering} Your proposed investment: {premium_price_point} Key differentiators: {three_advantages_over_current_solution} Risk of status quo: {what_happens_if_they_dont_upgrade} Implementation effort: {time_and_resources_required} Decision timeline: {when_they_need_to_decide}
Write a 600-800 word premium positioning proposal. Structure as: Current State Analysis, Cost of Inaction, Premium Solution Benefits, Implementation Plan, Total Cost of Ownership Comparison. Focus on business risk and opportunity cost rather than feature comparison. Use confident tone that justifies the premium investment through measurable business outcomes.
When to use it: When competing against cheaper alternatives or trying to upsell existing clients to a higher-tier solution.
Pro tip: Calculate the cost per day of your premium solution versus their current spend. “$47 per day for enterprise-grade security” sounds more reasonable than “$17,000 annually.”
Pricing and Investment Proposals
You are presenting a custom pricing proposal after initial price objections.
Client: {company_name} Original quoted price: {initial_price_quoted} Their budget: {stated_or_implied_budget_limit} Modified scope: {adjusted_deliverables_or_timeline} New price: {revised_price_point} What’s removed: {specific_items_cut_from_original_scope} Payment terms: {payment_schedule_or_structure} Value maintained: {key_benefits_still_included} Upgrade path: {how_they_can_add_back_removed_items}
Write a 300-500 word pricing revision proposal. Open by acknowledging their budget parameters. Present the modified solution as a strategic fit, not a compromise. Detail what’s included and excluded clearly. Close with payment terms and upgrade options. Use collaborative tone that frames this as problem-solving, not concession.
When to use it: After a prospect says “we love it but it’s over budget” and you have flexibility to adjust scope or terms.
Pro tip: Always show the full original price crossed out, then your concession. This anchors them to the higher number and makes your revision feel like a win for them.
You are justifying premium pricing against a lower-cost competitor’s bid.
Your company: {your_company_name} Competitor: {competing_company_name} Your price: {your_quoted_amount} Their price: {competitor_quoted_amount} Price difference: {dollar_or_percentage_gap} Your advantages: {three_key_differentiators} Hidden costs in their bid: {what_competitor_likely_missed_or_charges_extra} Client’s risk tolerance: {high_medium_or_low} Project importance: {business_critical_or_routine} Decision criteria: {what_matters_most_to_this_client}
Write a 500-700 word price justification proposal. Structure as: Investment Comparison, Value Differential Analysis, Hidden Cost Revelation, Risk Assessment, Total Cost of Ownership. Acknowledge the price difference directly, then systematically justify it through superior value and lower total cost. Use confident, fact-based tone that educates rather than defends.
When to use it: When you’re 15-30% higher than the competition but offer demonstrably superior value or lower risk.
Pro tip: Create a comparison table showing “Apparent Cost vs Total Cost” where you add back all the extras they’ll charge for that you include.
You are proposing a payment plan to close a deal with budget timing issues.
Client: {company_name} Total project value: {full_amount_owed} Budget constraint: {cash_flow_or_approval_issue} Proposed payment schedule: {specific_payment_timeline} Deliverable milestones: {what_triggers_each_payment} Start date: {when_project_begins} Completion date: {final_delivery_date} Payment terms: {net_30_or_other_terms} Late payment terms: {consequences_of_missed_payments}
Write a 300-400 word payment plan proposal. Present the schedule as a solution to their cash flow challenge while protecting your interests. Tie payments to specific deliverables and milestones. Include clear terms for late payments. Use professional tone that treats this as standard business practice, not a special favor.
When to use it: When a qualified prospect wants to move forward but needs to spread payments across multiple budget periods or quarters.
Pro tip: Always tie payments to deliverables, never just calendar dates. “Upon completion of Phase 1 testing” is better than “30 days after contract signing.”
You are creating a multi-year contract proposal with annual price escalations.
Client: {company_name} Service: {ongoing_service_or_product} Year 1 price: {first_year_investment} Annual escalation: {percentage_increase_per_year} Contract length: {total_years} Scope changes: {how_scope_modifications_are_handled} Performance metrics: {success_measurements} Renewal terms: {automatic_or_manual_renewal} Termination clause: {how_either_party_can_exit}
Write a 400-600 word multi-year proposal. Structure as: Partnership Overview, Investment Schedule, Scope & Performance Standards, Contract Terms. Frame the escalation as standard business practice tied to inflation and service improvements. Emphasize the value of long-term partnership and price protection compared to annual negotiations. Use partnership language that positions this as mutually beneficial.
When to use it: When selling ongoing services like maintenance, support, or managed services where multi-year commitments benefit both parties.
Pro tip: Show the total savings over multiple one-year contracts. “3-year commitment saves $47,000 vs annual renewals” makes the escalation easier to accept.
You are proposing a performance-based pricing model tied to client results.
Client: {company_name} Base fee: {minimum_guaranteed_payment} Performance metrics: {specific_measurable_outcomes} Bonus structure: {how_additional_payment_is_calculated} Measurement period: {timeframe_for_evaluation} Baseline data: {starting_point_for_measurement} Maximum total fee: {cap_on_performance_payments} Reporting schedule: {how_often_results_are_reviewed} Dispute resolution: {how_measurement_disagreements_are_handled}
Write a 500-600 word performance-based proposal. Structure as: Base Investment, Performance Framework, Measurement Methodology, Reporting & Review Process. Emphasize shared risk and aligned incentives. Define measurement criteria precisely to avoid disputes. Use confident tone that demonstrates faith in your ability to deliver results while protecting both parties’ interests.
When to use it: When selling results-driven services like marketing, sales consulting, or operational improvements where success can be clearly measured.
Pro tip: Include a clause that lets you audit their data if results seem inconsistent. “Performance reviews include access to relevant client systems and data” prevents manipulation.
Objection Handling and Responses
You are responding to a “we need to think about it” objection after presenting your proposal.
Prospect: {company_and_contact_name} Proposal presented: {date_of_presentation} Stated objection: {specific_reason_for_hesitation} Real concern: {underlying_issue_you_suspect} Decision makers: {who_else_is_involved_in_decision} Timeline pressure: {any_deadlines_or_urgency_factors} Next step offered: {meeting_call_or_demo_you_want} Competitor threat: {other_vendors_they_might_be_considering} Value props: {three_strongest_benefits_for_them}
Write a 300-400 word follow-up proposal that addresses their hesitation. Acknowledge their need to deliberate, then provide additional information that makes the decision easier. Include a specific next step with urgency but no pressure. Offer to address any unstated concerns. Use helpful tone that positions you as an advisor, not just a vendor.
When to use it: 24-48 hours after a prospect says they need time to think, especially when you sense there’s an unstated concern.
Pro tip: Offer to speak with other decision makers directly. “I’m happy to present to your CFO directly” shows confidence and speeds up their internal process.
You are addressing a direct price objection with value reinforcement.
Client: {company_name} Objection: {their_specific_price_concern} Your price: {quoted_amount} Their expectation: {what_they_thought_it_would_cost} Cost of inaction: {what_happens_if_they_do_nothing} ROI timeline: {how_fast_they_see_payback} Competitive context: {how_your_price_compares_to_alternatives} Payment flexibility: {options_you_can_offer} Risk factors: {what_could_go_wrong_with_cheaper_options}
Write a 400-500 word price objection response. Structure as: Acknowledgment, Value Reframe, Cost of Inaction, ROI Demonstration, Risk Comparison. Never apologize for your price or immediately offer discounts. Instead, reinforce value and create urgency around the cost of delay. Use confident educational tone that teaches them how to think about the investment correctly.
When to use it: When a qualified prospect’s first reaction to your price is “that’s more than we expected” or “we can’t afford that.”
Pro tip: Ask “compared to what?” when they say it’s expensive. Often they’re comparing to something irrelevant, and this question reframes the conversation.
You are responding to a prospect who says they want to start with a smaller pilot project.
Prospect: {company_and_contact_name} Original proposal scope: {full_project_description} Their pilot suggestion: {smaller_scope_they_want} Pilot investment: {reduced_price_for_pilot} Full project value: {total_potential_deal_size} Timeline impact: {how_pilot_affects_full_rollout} Success metrics: {how_pilot_results_will_be_measured} Expansion criteria: {what_triggers_full_project_approval} Risk factors: {downsides_of_pilot_approach}
Write a 400-500 word pilot project proposal. Present the pilot as a strategic phase, not a compromise. Define clear success metrics and expansion criteria. Address how the pilot demonstrates value while building toward the full engagement. Include timeline for pilot completion and full project decision. Use collaborative tone that shows you understand their risk management while maintaining momentum toward the larger deal.
When to use it: When a risk-averse prospect wants to “test the waters” with a smaller engagement before committing to your full proposal.
Pro tip: Price the pilot at a premium per-unit cost compared to the full project. This creates financial incentive to move to the larger engagement after pilot success.
You are addressing concerns about your company size or experience in their industry.
Prospect: {company_name} Their concern: {specific_worry_about_your_capabilities} Your company size: {employees_or_revenue_range} Relevant experience: {similar_projects_or_industries} Key team members: {who_would_work_on_their_project} Success stories: {specific_results_youve_delivered} Risk mitigation: {how_you_reduce_client_risk} Support structure: {backup_resources_or_guarantees} Competitive advantage: {why_smaller_or_different_is_better}
Write a 400-600 word credibility-building response. Address their concern directly, then reframe your size or newness as an advantage. Provide specific examples and success metrics. Include risk mitigation measures and support structures. Use confident tone that acknowledges their concern while demonstrating why it’s actually beneficial to work with you.
When to use it: When prospects express concern about your company being too small, too new, or lacking specific industry experience.
Pro tip: Name specific team members who will work on their project and include brief credentials. Personal accountability beats corporate credentials for smaller firms.
You are responding to a request for references and case studies after initial proposal presentation.
Requesting company: {company_name} Similar client 1: {reference_company_name_and_industry} Similar client 2: {second_reference_company_and_industry} Similar client 3: {third_reference_company_and_industry} Relevant project: {specific_work_that_matches_their_need} Results achieved: {measurable_outcomes_from_reference_project} Timeline: {how_long_reference_project_took} Client contact: {reference_who_will_speak_to_them} Case study: {detailed_success_story_with_metrics}
Write a 500-700 word reference and case study response. Present three relevant references with specific context about why each is relevant to their situation. Include one detailed case study with measurable results. Provide contact information and suggest specific questions they should ask references. Use confident tone that demonstrates extensive relevant experience while making it easy for them to verify your claims.
When to use it: When a serious prospect asks for references, case studies, or proof points before making their final decision.
Pro tip: Brief your references before sharing their contact info. Send them the prospect’s situation and suggested talking points so they give strong, relevant testimonials.
Technical and RFP Responses
You are responding to a detailed technical RFP with specific functionality requirements.
RFP number: {official_rfp_identifier} Issuing organization: {client_organization} Technical requirements: {five_key_functional_specifications} Compliance standards: {regulatory_or_security_requirements} Integration needs: {systems_that_must_connect} Performance criteria: {speed_capacity_or_availability_requirements} Your solution architecture: {how_your_system_meets_their_needs} Implementation approach: {technical_rollout_methodology} Support structure: {ongoing_maintenance_and_support}
Write a 1000-1500 word technical response structured as: Executive Summary, Requirements Analysis, Technical Architecture, Implementation Methodology, Compliance & Security, Performance Specifications, Support & Maintenance. Address each requirement explicitly with specific technical details. Use precise technical language while remaining accessible to both technical and business stakeholders.
When to use it: When responding to government or enterprise RFPs that require detailed technical specifications and compliance documentation.
Pro tip: Create a requirements traceability matrix that shows exactly where in your response you address each RFP requirement. Procurement teams love this level of organization.
You are proposing a complex system integration project with multiple stakeholders.
Client: {company_name} Current systems: {existing_technology_stack} Integration scope: {systems_that_need_to_connect} Data migration: {what_data_moves_and_how} Timeline: {project_duration_and_key_milestones} Technical team: {your_technical_resources} Client technical contact: {their_technical_lead} Testing approach: {how_integration_will_be_validated} Rollback plan: {what_happens_if_integration_fails} Go-live strategy: {how_new_system_goes_into_production}
Write a 800-1200 word integration proposal. Structure as: Current State Analysis, Integration Architecture, Migration Strategy, Project Timeline, Testing & Quality Assurance, Risk Management, Go-Live Planning. Balance technical detail with business impact. Include specific risk mitigation strategies for complex integrations. Use technical but accessible language suitable for both IT and business stakeholders.
When to use it: When proposing to connect disparate systems or migrate data between platforms, especially when downtime risk is high.
Pro tip: Always include a detailed rollback plan. IT buyers need to know you can undo changes if something goes wrong during implementation.
You are responding to a security and compliance-focused RFP for a regulated industry.
Client industry: {healthcare_finance_government_or_other_regulated_sector} Compliance requirements: {specific_regulations_like_HIPAA_SOX_FedRAMP} Security standards: {required_security_frameworks} Data handling: {how_sensitive_data_must_be_managed} Audit requirements: {reporting_and_audit_trail_needs} Your certifications: {relevant_compliance_certifications_you_hold} Security measures: {specific_security_controls_you_implement} Incident response: {how_you_handle_security_breaches} Training requirements: {compliance_training_for_client_staff}
Write a 1000-1400 word compliance-focused proposal. Structure as: Regulatory Understanding, Compliance Framework, Security Architecture, Data Protection Measures, Audit & Reporting Capabilities, Incident Management, Staff Training & Certification. Demonstrate deep understanding of their regulatory environment. Use precise compliance language and cite specific regulations. Include your certifications and third-party security validations.
When to use it: When selling to healthcare, financial services, government, or other heavily regulated industries where compliance is a primary concern.
Pro tip: Include a compliance matrix that maps each regulation requirement to your specific control or process. This shows you understand their audit needs.
You are proposing a cloud migration project with hybrid architecture requirements.
Client: {company_name} Current infrastructure: {on_premise_systems_and_architecture} Migration scope: {what_moves_to_cloud_vs_stays_on_premise} Cloud platform: {AWS_Azure_GCP_or_multi_cloud} Hybrid requirements: {what_must_remain_connected_between_environments} Performance requirements: {latency_throughput_or_availability_needs} Security considerations: {data_sensitivity_and_access_controls} Migration timeline: {phased_approach_and_key_milestones} Business continuity: {uptime_requirements_during_migration} Cost optimization: {how_cloud_reduces_their_operational_costs}
Write a 1000-1300 word cloud migration proposal. Structure as: Current State Assessment, Target Architecture, Migration Strategy, Hybrid Connectivity, Security & Compliance, Performance Optimization, Business Continuity Planning, Cost Analysis. Balance technical architecture with business benefits. Include specific risk mitigation for each migration phase. Use cloud-native terminology while explaining