Writing Proposals
Overview

Writing a Winning Proposal

Most applicants fail here. Master proposal writing to stand out.

The Brutal Reality

Proposal Quality Distribution:

Generic Proposals  ███████████████  50%
  (Copy-paste from ideas page)

Good Proposals     █████████        30%
  (Shows some thought)

Excellent Proposals ████             15%
  (Stands out immediately)

Outstanding        █                  5%
  (Gets accepted)

Only 5% of proposals are truly excellent.

What Mentors Think When Reading

Minute 0:15    "Is this person serious?"
Minute 0:45    "Do they understand the problem?"
Minute 1:30    "Can they actually do this?"
Minute 2:00    "Why this project? Why this person?"
Minute 2:30    "Decision made."

Yes or No. That's it.

Core Principle

Your proposal should answer:

  1. What are you building? (Clearly)
  2. Why does it matter? (Convincingly)
  3. How will you build it? (Realistically)
  4. Why you? (Specifically)

The Brutal Truth About Proposals

Distribution of proposals received by GSoC organizations:

Terrible Proposals      ███████████████████  45%
  ("I want to contribute")
  
Basic Proposals        ████████████         25%
  ("I'll implement feature X")
  
Good Proposals         ███████              15%
  ("Here's how I'd solve X")
  
Excellent Proposals    ███                  10%
  ("I understand the problem deeply")
  
Outstanding Proposals  █                    5%
  ("This proposal shows mastery")

Acceptance correlation:
- Terrible: 0% acceptance
- Basic: 5% acceptance
- Good: 25% acceptance
- Excellent: 60% acceptance
- Outstanding: 95% acceptance

Your goal: Get from 25% to 60%+ range.

The Proposal Journey

Understand the Problem (Week 1)

  • Read the project idea thoroughly
  • Study existing code related to it
  • Understand why it matters

Research the Solution (Week 2)

  • How have others solved this?
  • What's already implemented?
  • What are the gaps?

Plan Your Approach (Week 3)

  • Break work into realistic milestones
  • Identify potential blockers
  • Create detailed timeline

Write Draft (Week 3)

  • First draft should be rough
  • Get feedback from mentors
  • Incorporate guidance

Refine (Week 4)

  • Polish language and clarity
  • Add diagrams where helpful
  • Proofread thoroughly

Section Breakdown

This section covers:

  1. Understanding the Problem Statement
  2. Researching Existing Solutions
  3. Defining Clear Deliverables
  4. Creating a Realistic Timeline
  5. Technical Depth vs Buzzwords
  6. Writing Style Mentors Respect
  7. Common Mistakes to Avoid
  8. Proposal Review Checklist

Your proposal is your first impression. Make it count.