\r \r

Freelance Proposal Writer\r

\r

Why This Exists\r

Generic proposals waste connects. This skill crafts targeted proposals that lead with the client's problem, not your resume. 180-220 words that get responses.\r \r

Setup\r

\r Edit the MY_STACK section below to match your skills. This runs once:\r \r

MY_STACK:\r
- Frontend: [your frontend skills]\r
- Backend: [your backend skills]\r
- AI/Automation: [your AI/automation stack]\r
- Rate: [your rate range — e.g., $65-100/hr or project-based]\r
```\r
\r
## Process\r
\r
### Step 1: Extract Job Details\r
\r
From `$ARGUMENTS`:\r
- If URL: use WebSearch or Bash to fetch page content\r
- If pasted text: parse directly\r
\r
Extract:\r
- Client's stated problem (what they're asking for)\r
- Client's real problem (what they actually need — often different)\r
- Budget (hourly vs fixed)\r
- Timeline\r
- Tech stack specified or implied\r
- Client background (company type, size, spend history if visible)\r
\r
### Step 2: Score the Opportunity\r
\r
Quick fit score (skip if \x3C 6/10):\r
- Stack match: /3 (2+ = strong match)\r
- Budget viable: /2 (meets your floor)\r
- Client quality: /2 (some platform history, reasonable expectations)\r
- Problem solvable: /2 (not vague "build me a startup" type requests)\r
- Timeline realistic: /1\r
\r
If score \x3C 6: output `SKIP — [specific reason]` and stop.\r
\r
### Step 3: Identify the Hook\r
\r
The first line is everything. Find the client's most pressing pain:\r
- "You're losing users because [X]"\r
- "The bug you described is caused by [Y], here's the fix"\r
- "I've built exactly this for [similar context] — here's what I learned"\r
\r
Never start with "Hi, I'm [name]" or list your skills first.\r
\r
### Step 4: Write the Proposal\r
\r
Target: 180-220 words. Structure:\r
```\r
[HOOK — 1-2 sentences. Lead with their problem or a direct solution]\r
\r
[SOLUTION — 2-3 sentences. Concrete approach. Specific tech choices + why]\r
\r
[PROOF — 1-2 sentences. Closest relevant thing you've built. No fluff]\r
\r
[TIMELINE & CTA — 1-2 sentences. Realistic estimate + clear next step]\r
```\r
\r
Tone: confident, direct, no buzzwords. Write like texting a peer.\r
\r
**Avoid:** "I am a highly experienced developer", "I would love to help", "I am very passionate about", generic portfolio links without context.\r
\r
### Step 5: Output\r
\r
Produce:\r
1. The fit score with breakdown\r
2. The proposal text (ready to paste)\r
3. One optional follow-up question to add at the end (optional, if it would help)\r
\r
## Example Output Format\r
\r
```\r
FIT SCORE: 8/10\r
- Stack: 3/3 (Next.js + Supabase exact match)\r
- Budget: 2/2 ($75/hr = your minimum)\r
- Client: 2/2 ($5k spend history, US company)\r
- Problem: 2/2 (specific auth bug, clear scope)\r
- Timeline: 1/1 (2-week estimate is realistic)\r
\r
PROPOSAL:\r
[180-220 word proposal here]\r
\r
OPTIONAL QUESTION: "Are you open to a 1-hour paid discovery call to confirm the scope before the full project kicks off?"\r
```\r