I Pointed Claude at Upwork: 33 Jobs, 1 Prototype, 1 Proposal
My Upwork profile had zero jobs and zero reviews. A profile like that loses to established freelancers on almost every post, however good the cover letter is. So I changed the question from “how do I write a better proposal?” to “what can I show a client that a CV can’t?”
The answer was a working prototype of their job, built before I apply.
The pipeline
Section titled “The pipeline”I set it up as four stages with two points where I decide:
- Scout: Claude searches Upwork for Claude, agent and MCP server work through Upwork’s official MCP server.
- Qualify: each job is scored out of 100 on fit, whether a demo is buildable in about two hours, client quality, budget and competition.
- I pick which jobs to pursue.
- Build: Claude builds a small working version of what the post asks for.
- Pitch: Claude drafts a short proposal that leads with the prototype.
- I approve the proposal before it is sent.
Claude does the searching, reading and building. I keep the two decisions that cost money or carry my name.
The first run
Section titled “The first run”Four searches returned 40 posts, 33 once duplicates were removed. Nine passed my filters for the last 48 hours. Most of the rest were full-time roles, plain web design, or rates at or under $10 an hour.
The first thing the numbers showed: Claude jobs fill up fast. Eight of the nine shortlisted posts already had more than 50 proposals within hours of going live. A demo helps, but being early matters as much.
The job I chose
Section titled “The job I chose”I went for a $500 fixed-price setup: connect a retailer’s Google Ads, Merchant Center and GA4 to Claude using Google’s official MCP servers, strictly read-only.
It scored well because the scope was clear, the client had a real hiring record, and nobody had been interviewed yet. It was not a perfect fit: they asked for proven Google Ads API experience, and I have used Google Ads but never shipped an API project. I said exactly that in the proposal.
What the prototype turned up
Section titled “What the prototype turned up”I installed Google’s official Ads MCP server to build the setup kit, and listed the tools it exposes. Four of its seven default tools write to the account: asset creation, video upload and two for labels.
For a client whose first requirement was “everything must be read-only”, that is the most useful thing I could tell them. The kit disables those tools, and includes a script that starts the server and fails if any write tool appears. I wrote the details up in How to Make the Google Ads MCP Server Truly Read-Only.
The proposal
Section titled “The proposal”Under 200 words, in this order:
- Their problem in their own words.
- What I already built and the write-tool finding.
- My honest experience, price, timeline, security approach and the exact access I would need.
- One question about their setup.
It went out with the kit attached, no boost, for 18 Connects.
What I’m watching
Section titled “What I’m watching”One proposal proves nothing yet. The measure I care about is the reply rate after ten proposals, and which scoring criteria predicted the replies. I’ll update this post when I have those numbers.