No prior relationship. No referral. The buyer had posted the job 14 hours earlier. I was the 23rd applicant. They closed everyone else and hired me on a $25K fixed bid. Here's exactly what I sent.
One cold proposal. $25K project. Everyone asks for the magic words. There aren't any.
What there is: a structure that respects the buyer's time and proves you read the job. Five sentences. No template. No "I have 8 years of experience." No "I'm passionate about your industry."
The proposal had 5 parts:
That was it. 7 sentences total. Sent at 11pm. Got a reply at 7am. Closed at $25K fixed.
You're trying to consolidate Mixpanel and your Postgres event tables into one source of truth, and you mentioned the team can't trust either right now. I rebuilt exactly this for a Series B SaaS last year — they had Segment + Snowflake + Postgres all telling slightly different stories. The first week, I'd audit your event taxonomy and write a single mapping doc. Anything that doesn't map gets killed or unified. If you don't have a clear plan by end of week one, you don't pay for it. One question: do you have any current dashboards that the leadership team actually trusts, or is everything suspect at this point?
That's 109 words. Most freelancers send 350-500 words. The buyer told me later that the average proposal he saw started with "I am a senior data engineer with..." and he stopped reading at sentence two.
"You're trying to consolidate Mixpanel and your Postgres event tables..." — paraphrased their problem in their own framing. This is the move that signals you read the post. It takes 30 seconds and almost nobody does it.
"I rebuilt exactly this for a Series B SaaS..." — one project, the closest one. Not "I've done analytics work for 50 companies." A buyer doesn't need range. They need the closest match. Range dilutes signal.
"The first week, I'd audit your event taxonomy and write a single mapping doc." — this is the move that separates you from "I'd discuss requirements and propose a solution." Buyers can picture you doing the work. They cannot picture "discuss requirements." A concrete first step is worth more than a 5-paragraph methodology.
"If you don't have a clear plan by end of week one, you don't pay for it." — buyers are scared of paying for nothing. This sentence tells them they can't lose. It works because I meant it. Don't write this if you're not willing to do it.
"Do you have any current dashboards that the leadership team actually trusts...?" — proposals end with "let me know if you're interested" or "happy to chat." Both die. A genuine question that requires their input opens a thread. They have to reply or feel rude.
The free Upwork Playbook has the exact template plus 4 worked examples across different niches. Free with email.
"I am a senior backend engineer with 8 years of experience..." Skip it. Background goes in line 7, if at all. The first sentence is about them.
Listing every framework you know. Listing every type of project you've done. The more you list, the less expert you sound. Pick one closest match. Trust the buyer to scroll if they want more.
"I'd be happy to discuss your requirements." "I can help you achieve your goals." Both are fillers. Replace with: "Week one I'd start by [specific action]."
"Let me know if you're interested" closes the door. End on a question they want to answer. Even a small one — "How are you tracking events today?" — gives them a reason to reply.
Use only jobs where you can write a one-sentence mirror without faking it. If you can't paraphrase the problem, skip the job.
Mirror, parallel project, first step, risk reversal, question. 100-150 words total. Send.
Don't write more proposals during this window. Notice the difference in reply rate vs. what you sent before.
Module 6 of High Earners is the proposal trainer. Paste your draft, get AI feedback against the same structure I used for the $25K message. Free assessment first if you want to see where you stand.
