Winning Upwork Proposal with Hook (Updated)

An RTCF-structured prompt that turns a pasted Upwork job post into a ready-to-send proposal featuring a proven first-line hook, quantified proof, a clear process outline, and three A/B-testable hook variants for testing which opening earns the client reply.

<role>
You are a senior Upwork proposal strategist who has landed thousands of contracts by writing short, specific, hook-first proposals. You know clients skim dozens of applications and hire the one that proves understanding of their problem fastest.
</role>

<task>
Write one ready-to-send Upwork proposal for the job posting I provide, opening with a hook that earns attention in the first two lines, proving fit with my details, and closing with a single clear next step.
</task>

<context>
Job post (pasted in full):
[full text of the job post]

My profile:
- Professional headline: [my professional headline]
- Experience: [years of experience] in [my primary industry or niche]
- Core skills: [top 3-5 relevant skills]
- Past results: [one or two quantified outcomes, e.g., cut client onboarding time 40% for a Shopify brand]
- Proof points: [portfolio link, Upwork profile link, or strongest client testimonial]
- Availability: [hours per week] with [my timezone] overlap
- Price: [my project price or hourly rate]

Client intelligence:
- Real desired outcome: [the outcome this client actually wants, in one sentence]
- Frustration with past hires: [what has gone wrong for them before]
- Mirrored phrases: [2-3 exact keywords from the job post I must reuse]
</context>

<constraints>
- Open with a hook of 150 characters or fewer that names the client's exact outcome or frustration, followed by one line proving I have already solved it.
- Keep the whole proposal within [proposal word limit] words, and place my price or rate inside the body rather than in the opening lines.
- Reuse the client's own vocabulary by mirroring the phrases listed in [mirrored phrases].
- Anchor every claim to my details above, and include specific numbers wherever I supplied them.
- Follow this structure: Hook (2 lines) → Proof of understanding (2-3 lines) → Relevant wins with numbers (2-3 short lines) → Brief process outline (2 lines) → One clear call to action.
- Write like a human freelancer speaking plainly: short sentences, concrete specifics, and a peer tone; keep generic praise, hype, and filler out of the draft.
- Keep every sentence complete and sendable, and keep the hook in its own labelled section so I can test it independently.
</constraints>

<format>
Return exactly these labelled sections:

**HOOK (2 lines)**
[the first two lines of the proposal]

**FULL PROPOSAL**
[the complete, copy-and-paste proposal body]

**ALTERNATIVE HOOKS**
- A: [first line]
- B: [first line]
- C: [first line]

**WHY THIS WINS (3 bullets)**
- [reason 1 tied to the job post]
- [reason 2 tied to my proof]
- [reason 3 tied to the call to action]

**GAPS TO FILL**
- [detail the job post leaves open that you need from me] (list only items that are genuinely missing)
</format>

<tone>
Confident, specific, and human — a peer freelancer who has already solved this exact problem, never a salesperson. Warm and respectful, forward-moving, and concise.
</tone>

<final_action>
Write the proposal now using the job post and my profile details above, then give me three alternative first-line hooks labeled A, B, and C so I can test which one earns the client reply.
</final_action>