Freelance Proposal Writer

Creates winning freelance proposals tailored to specific project briefs with precise scope definition, strategic pricing, portfolio highlights, and client-specific persuasion hooks. This skill analyzes the client's brief, identifies their pain points, and generates proposals that stand out on platforms like Upwork, Fiverr, Toptal, and direct client outreach via email or LinkedIn.

Supported Platforms & Integrations

Platform	Integration Type	Features
Upwork	Proposal format	Cover letter, milestones, connects optimization
Fiverr	Gig response	Buyer request responses, package pricing
Toptal	Screening format	Technical depth, experience-first structure
Freelancer.com	Bid format	Competitive bid positioning, milestone breakdown
LinkedIn	Direct pitch	InMail-optimized proposals for enterprise clients
Email	Direct outreach	Full SOW-style proposals with attachments

When to Use This Skill

• Use this when responding to a client job posting on any freelance marketplace

• Use this when a potential client sends you a project brief and expects a formal proposal

• Use this when you need to define scope and pricing for an ambiguous project description

• Use this when you want to differentiate yourself from dozens of competing proposals

• Use this when transitioning from hourly to project-based pricing and need to structure fixed-fee proposals

• Consider alternatives when writing long-form contracts with legal terms (use a contract template)

• Consider alternatives when you need ongoing client management rather than initial proposals

• Consider alternatives when pricing enterprise deals above $50K (use a sales proposal tool)

Quick Start

Copy
# proposal-config.yml
proposal:
  platform: "upwork"
  freelancer:
    name: "Casey Morgan"
    specialty: "Full-Stack Web Development"
    hourly_rate: 85
    years_experience: 6
    portfolio_highlights:
      - "E-commerce platform for a DTC brand (React + Shopify)"
      - "SaaS dashboard with real-time analytics"
  client_brief: |
    Need a developer to build a customer portal for our B2B SaaS.
    Must integrate with Stripe billing and our existing REST API.
    Timeline: 6 weeks. Budget: $8K-12K.
  pricing_strategy: "value-based"

First run example:

> Write a proposal for this Upwork project: B2B customer portal with Stripe integration, 6-week timeline, $8-12K budget.

Generated Proposal:
- Personalized opening (references their specific product)
- Understanding of requirements (rephrased to show comprehension)
- Proposed approach (3-phase delivery plan)
- Relevant portfolio examples (2 matching projects)
- Pricing: $10,500 fixed-price with milestone breakdown
- Timeline: 6-week Gantt with deliverables per week
- Risk mitigation and communication plan

Advanced Configuration

Copy
# Upwork-specific
upwork:
  cover_letter_max: 600
  include_questions: true
  boost_connect: false
  profile_link: true

# Direct client proposals
direct:
  include_sow: true
  payment_terms: "50-25-25"
  revision_rounds: 2
  contract_type: "fixed-price"

Parameter	Type	Default	Description
platform	string	"upwork"	Target platform: upwork, fiverr, toptal, direct, email
pricing_strategy	string	"competitive"	Options: competitive, value-based, premium, budget
tone	string	"professional"	Options: professional, casual, consultative, technical
proposal_length	string	"medium"	Options: short (200w), medium (400w), long (800w)
include_timeline	boolean	true	Add a phase-by-phase timeline breakdown
include_portfolio	boolean	true	Include relevant portfolio examples
payment_structure	string	"milestone"	Options: milestone, hourly, retainer, 50-50
upsell_maintenance	boolean	false	Include ongoing maintenance upsell option
competitive_analysis	boolean	false	Position against likely competitor proposals
revision_policy	string	"2-rounds"	Define revision/change request policy
guarantee	string	"none"	Options: none, satisfaction, money-back, results

Core Concepts

Concept	Description
Mirror & Expand	Restate the client's requirements in your own words to prove understanding
Value Anchoring	Frame your price against the business value delivered, not hours worked
Social Proof	Reference specific past projects that match the client's industry or tech stack
Risk Reversal	Reduce client anxiety with guarantees, milestones, or trial periods
Scope Fence	Clearly define what is and is not included to prevent scope creep

+------------------+     +-------------------+     +------------------+
| Client Brief     | --> | Brief Analyzer    | --> | Pain Point       |
| (raw project     |     | (extract reqs,    |     | Identifier       |
|  description)    |     |  budget, timeline)|     | (what they need) |
+------------------+     +-------------------+     +------------------+
                                                          |
                                                          v
+------------------+     +-------------------+     +------------------+
| Final Proposal   | <-- | Pricing Engine    | <-- | Solution Builder |
| (formatted for   |     | (strategy-based   |     | (approach, tech, |
|  platform)       |     |  price calc)      |     |  timeline)       |
+------------------+     +-------------------+     +------------------+

Workflow Examples

Scenario 1: Upwork Cover Letter

Input: "Client needs a mobile app for their restaurant chain. React Native, push notifications, online ordering. Budget $15-25K."
Output:
"Hi [Client] — I read through your brief and the mobile ordering flow you described is exactly what I built for [Restaurant Group], where online orders increased 40% in the first month after launch.

Here is how I would approach your project:
Phase 1 (Week 1-2): UI/UX design, menu integration, Stripe payments
Phase 2 (Week 3-4): Push notifications, order tracking, kitchen display
Phase 3 (Week 5-6): Testing, App Store/Play Store submission

Investment: $19,800 (3 milestones of $6,600)
I can start next Monday. Happy to jump on a quick call to discuss."

Scenario 2: Value-Based Direct Proposal

Input: "E-commerce client losing $50K/month to cart abandonment. They want checkout optimization."
Output: Proposal framed around ROI — "A 20% reduction in abandonment = $10K/month recovered. My fee of $8,000 pays for itself in 25 days." Includes A/B testing plan, heatmap analysis, 3 checkout redesign concepts.

Scenario 3: Fiverr Custom Offer

Input: "Buyer wants a WordPress site with WooCommerce, 10 product pages, basic SEO. Quick turnaround."
Output: 3-tier package response:
- Basic ($500): 5 pages, starter theme, basic SEO
- Standard ($900): 10 pages, custom theme, full SEO, WooCommerce
- Premium ($1,400): 15 pages, custom design, advanced SEO, speed optimization, 30-day support

Best Practices

Open with proof you read the brief. Reference something specific from their posting — a feature they mentioned, a problem they described, their company name. The majority of freelance proposals on marketplaces are generic templates. One specific sentence immediately puts you in the top 10% of applicants.

Price based on value, not time. When a client's project will generate $100K in revenue, charging $10K is a bargain regardless of whether it takes you 40 hours or 80. Frame your pricing around the outcome they receive. Use phrases like "your investment" rather than "my fee" and always connect the price to a business result.

Structure with milestones, not lump sums. Breaking a $12K project into 3 milestones of $4K reduces the perceived risk for the client. Each milestone should have a clear deliverable — "working prototype," "feature-complete beta," "production launch." This also protects you from doing all the work before getting paid.

Include what is NOT in scope. The fastest path to a bad client relationship is an ambiguous scope. Explicitly list 3-5 items that are not included — hosting setup, content creation, third-party API costs, ongoing maintenance. This prevents scope creep and sets professional expectations from day one.

Close with a low-friction next step. Do not end with "let me know." End with a specific action: "I am available for a 15-minute call Tuesday or Thursday afternoon — which works better for you?" A clear next step doubles your response rate compared to an open-ended closing.

Common Issues

Problem: Proposals get no responses on Upwork. Ensure your opening line is personalized and not generic. Avoid starting with "Dear client" or "I am a skilled developer." Use the client's name or company name if visible. Also verify your Upwork profile is complete with a professional photo, portfolio, and at least 3 reviews — clients often skip proposals from incomplete profiles.

Problem: Clients say the price is too high. Shift the conversation from cost to value. If a client balks at $8K, ask what the problem is costing them monthly. Show the math: "If cart abandonment costs $50K/month and I reduce it by 20%, the project pays for itself in 25 days." If they still cannot afford it, offer a reduced-scope starter package.

Problem: Scope keeps expanding after the proposal. This means the initial scope fence was too vague. Use the skill with revision_policy set explicitly and include a "Change Request Process" section in your proposal. State that changes beyond the original scope will be quoted separately with a 48-hour turnaround on estimates.

Privacy & Data Handling

• Local processing: All proposal content is generated locally within your Claude Code session. Client briefs and your portfolio details are never sent to freelance platforms or third parties.
• Data retention: Proposal drafts exist only during the active session. Save completed proposals to your local files for reuse and tracking.
• Export options: Output as plain text, markdown, PDF-ready format, or platform-specific formatting (Upwork cover letter length, Fiverr package structure).
• Sensitive data: The skill does not access your freelance platform accounts, payment information, or client communication history.
• Pricing confidentiality: Your rate information and pricing strategies remain local. No competitive data is collected or shared.