Write a Freelance Proposal
Most freelance proposals lose the job before the client finishes reading. This mission teaches you how to write proposals that get responses — using Gemini to research and Claude to write copy that feels personal, not generic.
Deliverable: A ready-to-send freelance proposal.
Read the job post and extract key pain points
Identify exactly what the client needs — not what they said, but what they actually want solved. Most job posts bury the real problem in the second or third paragraph.
- Highlight or copy the 2-3 sentences that describe their real problem
- Note any specific requirements they mention (deadline, budget, tools)
- Ignore generic filler in the post — focus on what they actually need solved
Research the client with Gemini
Spend 5 minutes learning about their business so your proposal feels tailored, not templated. Gemini can search the web in real time, so use it to find something specific to reference.
Prompt to use
“I'm applying for a freelance job with [client/company name, or paste the job post]. Search for information about this business — what they do, who their audience is, and anything recent (launches, posts, reviews). Summarize the 3 most useful details I could reference in a proposal.”
- If there's no company name, search the platform profile or portfolio link instead
- Look for one specific detail you can mention in your opening line
- Skip this step only if the post is fully anonymous
Draft your proposal with Claude
Use Claude to write a proposal that leads with the client's problem, not your credentials. Feed it both the job post and your research so it can write something specific.
Prompt to use
“Here's the job post: [paste job post]. Here's what I found about the client: [paste research from the previous step]. Write a freelance proposal that opens by naming their specific problem, briefly shows I understand it, and explains how I'd approach solving it — not a list of my credentials. Keep it under 200 words.”
- Ask Claude to cut the opening if it still sounds generic
- Request a version that opens with a question instead of a statement
- Keep your first sentence about them, not you
Add a specific offer and clear next step
End with exactly what you'll deliver, your rate, and one clear call to action. Vague proposals get vague responses — or none at all.
- State your rate or a price range, even if it's an estimate
- Name exactly what you'll deliver and by when
- End with one clear next step — a call, a question, or “ready to start Monday”
Review, personalize, and send
Read it as the client. Remove anything that sounds like everyone else's proposal — clients scanning 30 applications can spot a template instantly.
- Read it as if you were the client receiving 20 of these
- Delete any sentence that could apply to literally any other freelancer
- Double check the client's name and platform-specific formatting before sending
Mission Complete?
You now have a proposal built to get a response, not get ignored. Send it, then reuse this same workflow — research with Gemini, draft with Claude — for the next opportunity.