These prompts help busy freelancers write compelling proposals without starting from scratch. Copy any prompt, fill in your project details, and get a polished draft in under a minute.
These prompts pair well with Jasper AI for Freelancers-specific tone control, or Copy.ai for fast iteration.
Initial Project Pitches
You are a freelance {your_specialty} responding to a project posting. Write a compelling initial pitch.
Client industry: {industry} Project type: {specific_project_description} Budget mentioned: {budget_range_or_not_specified} Your relevant experience: {two_to_three_specific_examples} Key differentiator: {what_makes_you_different} Client pain point you noticed: {specific_problem_from_posting} Tone: {professional / conversational / enthusiastic}
Write a 150 to 200 word pitch that opens with a question addressing their pain point, includes one specific example of similar work you’ve done with measurable results, and closes with a clear next step. No generic enthusiasm or “I’m excited about this opportunity” language.
When to use it: When you’re scrolling through Upwork or freelance job boards and need to respond to 5+ postings quickly without sounding templated.
Pro tip: Always reference something specific from their job posting in your opening question—a metric they mentioned, a tool they use, or a challenge they described.
You are a freelancer pitching a potential client who contacted you through your website or referral.
Your specialty: {specific_service_area} How they found you: {website / referral_from / LinkedIn / etc} Their business: {company_type_and_size} Project scope: {what_they_described_needing} Timeline: {their_deadline_or_urgency} Your availability: {when_you_can_start} Similar client win: {specific_example_with_outcome} Your process: {three_step_simplified_approach}
Write a 250 to 300 word response that acknowledges how they found you, restates their project to show you understood, shares one relevant case study with specific results, outlines your simple 3-step process, and suggests a 15-minute call. Professional but warm tone.
When to use it: When leads come to you directly and you need to strike while they’re interested, usually within 2-4 hours of their inquiry.
Pro tip: Mention their referrer by name if applicable—it reinforces the connection and builds immediate trust.
You are a freelancer responding to an RFP or formal project brief.
Project title: {official_project_name} Client organization: {company_or_organization} Key requirements: {three_main_deliverables} Success metrics they mentioned: {specific_goals_or_KPIs} Timeline: {project_duration_and_milestones} Your relevant credentials: {certifications_or_major_clients} Methodology you’ll use: {specific_framework_or_approach} Team size needed: {solo / small_team / specific_roles}
Write a 400 to 500 word formal proposal response structured as: Executive Summary (2 sentences), Understanding (restate their needs), Approach (your methodology), Qualifications (credentials + one detailed case study), and Next Steps. Use bullet points for deliverables section.
When to use it: When you’re competing against agencies for larger projects and need to sound professional without losing personality.
Pro tip: Mirror their language exactly when restating requirements—if they say “user acquisition,” don’t switch to “customer growth.”
You are following up on a proposal you submitted {timeframe} ago for a {project_type} project.
Original project: {brief_project_description} Proposal date: {when_you_submitted} Client name: {contact_person} Follow-up reason: {timeline_passed / checking_in / new_info} Additional value you can add: {recent_idea_or_insight} Your current availability: {still_available / booking_up} Alternative offer: {smaller_scope_or_trial_project}
Write a 100 to 150 word follow-up email that references your original proposal without being pushy, adds one new insight about their project you’ve thought of since, mentions your availability status, and offers a smaller trial project as an alternative. Subject line: “Quick follow-up: {project_name}”
When to use it: When you’ve heard nothing back after a week and want to re-engage without seeming desperate or annoying.
Pro tip: Always include one new insight or idea you didn’t mention originally—it shows you’re still thinking about their business.
You are a freelancer pitching a potential ongoing retainer relationship after completing project work.
Current project: {what_you_just_finished} Results achieved: {specific_outcomes_or_metrics} Client satisfaction: {feedback_they_gave} Ongoing need you see: {specific_recurring_work} Retainer scope: {monthly_deliverables} Your capacity: {hours_per_month_available} Retainer investment: {monthly_rate} Trial period: {30_days / 60_days / 90_days}
Write a 200 to 250 word retainer proposal that opens by celebrating the project win, identifies the ongoing need based on what you observed, outlines specific monthly deliverables, and proposes a trial period. Include a clear monthly investment figure and next step.
When to use it: Right after delivering a successful project when the client is happy and you’ve spotted recurring work they need help with.
Pro tip: Timing is everything—send this within 24 hours of their positive feedback while you’re top-of-mind.
Pricing and Value Justification
You are a freelancer explaining your project pricing to a client who said your quote is higher than expected.
Your specialty: {specific_service_area} Quoted price: {your_total_project_cost} Their reaction: {too_high / need_to_think / comparing_others} Project complexity: {specific_challenging_aspects} Your experience level: {years_and_notable_clients} Value you deliver: {specific_business_outcomes} Cheaper alternatives exist: {yes_acknowledge / not_really} Payment terms: {your_standard_terms}
Write a 300 to 350 word pricing justification that acknowledges their concern, breaks down what goes into your pricing without being defensive, explains the cost of getting it wrong, and offers one small concession (faster delivery, extra revision, bonus deliverable) without dropping your rate. Confident but understanding tone.
When to use it: When a client likes you but is sticker-shocked and you need to justify your rates without seeming desperate or negotiating against yourself.
Pro tip: Never defend your pricing by comparing hours—always focus on outcomes and the cost of poor execution.
You are a freelancer providing a detailed project quote after a discovery call or brief discussion.
Project scope: {specific_deliverables_discussed} Client budget: {mentioned_range / no_budget_given} Timeline: {their_deadline} Complexity factors: {technical_challenges_or_requirements} Your day rate: {standard_daily_rate} Estimated time: {days_or_hours_needed} Included revisions: {number_of_revision_rounds} Additional services: {optional_extras_they_might_need} Payment schedule: {upfront_percentage_and_milestones}
Structure as: Project Overview (2 sentences), Scope of Work (bulleted deliverables), Investment (total cost + payment terms), Timeline (key milestones), What’s Included/Excluded (clear boundaries), and Next Steps. 400 to 500 words total. Professional and comprehensive.
When to use it: After a good discovery conversation when you need to formalize everything discussed into a proper quote they can approve.
Pro tip: Always include “What’s Not Included” section to prevent scope creep conversations later.
You are a freelancer offering a package deal with three pricing tiers for a potential client.
Base service: {core_deliverable_everyone_needs} Client type: {startup / established_business / enterprise} Tier 1 scope: {essential_package_deliverables} Tier 2 scope: {tier_1_plus_additional_services} Tier 3 scope: {comprehensive_package_everything} Tier 1 price: {basic_package_cost} Tier 2 price: {mid_tier_cost} Tier 3 price: {premium_package_cost} Most popular: {which_tier_most_clients_choose}
Write a 350 to 400 word tiered pricing proposal with three clear packages: Essential, Professional, and Premium. Include what’s in each tier, highlight the most popular option, and explain who each package is best for. End with “Which option feels right for your current needs?”
When to use it: When you’re unsure of their budget or want to give them options to choose their level of investment.
Pro tip: Price the middle tier as your actual target—most clients avoid the cheapest and can’t justify the most expensive.
You are a freelancer explaining why you can’t work within a client’s stated budget.
Their budget: {what_they_can_spend} Your minimum rate: {lowest_you_can_go} Project scope: {what_they_need_done} Budget gap: {difference_in_dollars_or_percentage} Scope reduction options: {what_could_be_cut} Phased approach: {how_to_split_into_stages} Alternative solution: {different_approach_that_fits_budget} Referral option: {yes_you_know_someone / no}
Write a 200 to 250 word budget response that thanks them for sharing their budget, explains the gap without criticism, offers 2-3 alternatives (reduced scope, phased approach, or different solution), and mentions you can refer someone if none of those work. Helpful and professional, not defensive.
When to use it: When their budget is genuinely too low but you like the client and want to find a way to work together.
Pro tip: Always offer alternatives before saying no—sometimes they have more budget than they initially shared.
You are a freelancer requesting a budget increase mid-project due to expanded scope.
Original project scope: {what_was_initially_agreed} New requests: {specific_additional_work_they_want} Time impact: {extra_hours_or_days_needed} Original budget: {initial_project_cost} Additional cost: {extra_amount_needed} Project timeline: {how_this_affects_deadlines} Your relationship: {working_well / some_friction} Urgency: {they_need_it_fast / flexible_timing}
Write a 150 to 200 word scope increase request that acknowledges the additional requests, explains how they differ from original scope, provides clear additional cost and timeline, and asks for approval before proceeding. Include “I want to make sure we’re aligned before moving forward.”
When to use it: When scope creep happens and you need to address it professionally before resentment builds on either side.
Pro tip: Send this as soon as additional work is requested—waiting makes it harder to justify later.
Client Communication and Relationship Management
You are a freelancer sending a project kickoff message after a client signs your contract.
Project type: {specific_work_you’re_doing} Start date: {when_work_begins} First milestone: {initial_deliverable_and_date} Communication preference: {email / Slack / calls} Meeting schedule: {weekly_checkins / as_needed} Client point person: {main_contact_name} What you need from them: {specific_information_or_assets} Project timeline: {total_duration}
Write a 200 to 250 word kickoff email that confirms project details, sets expectations for communication, lists exactly what you need from them by when, and establishes the first milestone. Professional but excited tone. Subject line: “Let’s get {project_name} started!”
When to use it: Within 24 hours of contract signing when momentum is high and you want to keep things moving smoothly.
Pro tip: Be specific about what you need from them and by when—vague requests lead to project delays.
You are a freelancer delivering a project milestone or draft to a client for review.
Milestone: {what_you’re_delivering} Completion status: {on_time / slightly_delayed / ahead_of_schedule} Key decisions made: {important_choices_you_made_and_why} What to review: {specific_feedback_areas} Revision process: {how_they_should_provide_feedback} Next milestone: {what_comes_after_this} Questions for them: {specific_decisions_they_need_to_make}
Write a 175 to 225 word delivery email that presents the milestone professionally, explains key decisions, guides them on what feedback you need, and sets up the next phase. Include “Please review by {specific_date} so we stay on track.”
When to use it: Every time you deliver work for review—sets expectations and keeps projects moving forward.
Pro tip: Always tell them specifically what kind of feedback you need rather than asking for “general thoughts.”
You are a freelancer addressing a client concern or complaint about your work.
Their concern: {specific_issue_they_raised} Validity: {legitimate_issue / misunderstanding / scope_change} Your responsibility: {your_mistake / unclear_communication / outside_factors} Impact: {how_serious_the_problem_is} Solution: {how_you_will_fix_it} Timeline: {when_it_will_be_resolved} Prevention: {how_you’ll_avoid_this_going_forward}
Write a 150 to 200 word response that acknowledges their concern without being defensive, takes responsibility where appropriate, provides a clear solution and timeline, and explains how you’ll prevent similar issues. Professional and solution-focused tone.
When to use it: When a client raises a legitimate concern and you need to address it quickly before the relationship deteriorates.
Pro tip: Lead with the solution, not an explanation of what went wrong—they care more about fixes than blame.
You are a freelancer requesting feedback from a client on how the working relationship is going.
Project status: {current_phase_or_percentage_complete} Working relationship: {seems_to_be_going_well / some_friction} Communication frequency: {current_check_in_schedule} Your sense: {client_seems_happy / hard_to_read / some_concerns} Specific areas: {deliverables / timeline / communication / process} Future projects: {potential_for_ongoing_work} Timing: {mid_project / near_completion}
Write a 100 to 125 word check-in message that asks for honest feedback on how things are going, what’s working well, and what could be improved. Make it safe for them to share concerns. Close with “I want to make sure this is working well for you.”
When to use it: Halfway through longer projects when you want to course-correct before any issues become bigger problems.
Pro tip: Ask this question over a call, not email—you’ll get more honest feedback in real-time conversation.
You are a freelancer wrapping up a completed project and asking for a testimonial.
Project completed: {what_you_delivered} Results achieved: {specific_outcomes_or_metrics} Client satisfaction: {positive_feedback_they_gave} Working relationship: {smooth