Table of contents11
Two years ago I sent 31 proposals in a single month and won exactly one project. One. I remember staring at my laptop at 2 a.m., rewriting the same sentences for the tenth time, wondering if I was just not good enough at this freelancing thing. I had real skills. I could build a fast, clean WordPress site in my sleep. But my proposals were getting opened and ignored, and I had no idea why.
I’ve since sent more than 200 proposals and won a steady stream of projects from small businesses, agencies, and startups. The difference wasn’t my portfolio or my rates. It was the proposal itself. I rebuilt it from scratch, tested every section, and kept what got replies. Most proposals get decided in the first three seconds — the client’s eyes land on your first line and either keep reading or move to the next bidder. That scared me at first. Now it excites me, because it means the fix is smaller than you think.
In this guide I’m giving you the exact six-part proposal structure I use for every WordPress project, plus the pricing trick and follow-up script that doubled my replies. It’s written for freelance WordPress developers and designers who are tired of being ghosted after doing good work on paper. Ready? Let’s get started.
You don’t need to be the cheapest bidder or the most experienced developer to win. You need the proposal that makes the client feel understood in the first 30 seconds. Clients hire the freelancer who proves they get the problem — not the one with the longest list of skills.
Table of Contents: What You’ll Learn Here
- Why your proposals get ignored (the 3-second filter most never pass)
- The six-part anatomy of a proposal that gets real replies
- How to open with a line that proves you actually read the brief
- How to price with two options so clients choose between yes and yes
- The follow-up script that revives proposals you thought were dead
- Mistakes that silently kill even strong proposals
- FAQs and my pre-send checklist
Ready? Let’s get started.
Why Most WordPress Proposals Fail Before Page Two
Here’s the deal: clients don’t reject your proposal because you’re not good enough. They reject it because it reads like everyone else’s.
The first time I lost a project I really wanted, I asked the client why. I expected her to say the winner had a better portfolio. She said something worse: “Your proposal looked fine, but I honestly couldn’t tell what you’d actually do differently.” Fine. That word stung for weeks.
Most proposals fail for three reasons, and all three are fixable today. First, they open with the freelancer, not the client — “Hi, I’m a WordPress developer with 8 years of experience.” The client already knows they need a WordPress developer. That’s why they posted the job. Second, they describe services instead of outcomes — “I will build a 5-page responsive website.” The client hears: blah blah blah. What they need to hear is what changes for their business. Third, they end with a whimper — “Looking forward to hearing from you.” That’s not a next step. That’s a hope.
One freelance writer who tested proposal openings across 83 bids found something striking: proposals that opened with a project-specific reference got a 22.4% reply rate, while generic greetings got only 6.1%. Same freelancer, same projects, same prices. The opening line was the only difference. That research (from codepressacademy.com) matched exactly what I saw in my own inbox data: the moment I stopped introducing myself and started naming the client’s problem, replies came back.
The 3-second filter is real. Clients scan your first two sentences like a headline. If those lines could have been written by any of the other 40 bidders, you’re done. The rest of this guide is about making sure your proposal survives that filter — and then closes the deal.
The Six-Part Anatomy of a Proposal That Gets Replies
Now: the structure. Every proposal I send now has exactly six parts, in this order. Nothing extra. No fluff paragraphs about my philosophy. Each part does one job, and the jobs stack: attention, trust, confidence, clarity, choice, and action.
1. The project-specific opening line. One sentence that proves you read the brief. This is the hardest-working sentence in the entire proposal. It names their exact problem, not your title. I’ll show you how to write it in the next section.
2. One sentence of credibility. Not a paragraph. Not a life story. One sentence with a specific, measurable result that connects to their project. Numbers and outcomes beat adjectives every time.
3. Your approach in 2–3 sentences. This is the part most freelancers skip, and it’s the part that separates a proposal from a brochure. You tell the client how you would actually do the work — the steps, the order, the method. Clients are buying a thinking process, not just hands.
4. Scope and deliverables. Exactly what’s included, exactly what isn’t, in plain bullet points. This is where you protect yourself from the “I thought that was included” conversation later. If you’ve ever delivered a theme install and had the client assume SEO and copywriting were in the package, you know why this section exists. (By the way, if you want a repeatable process for that part of delivery, my guide on [how to install a WordPress theme the right way](https://hyperdaf.com/how-to-install-a-wordpress-theme-the-right-way) shows the checklist I run on every build.)
5. Two pricing options. Never one number. Two options change the question in the client’s mind from “should I hire this person?” to “which package fits me better?” I’ll break this down fully below.
6. One clear next step. A single, easy action. Not “let me know.” Something like: “Reply YES and I’ll send the contract and invoice within 24 hours.” Make saying yes effortless and saying nothing the awkward choice.
That structure works for a one-page email proposal and for a polished multi-page PDF. The parts don’t change — only the polish does. Memorize this order and you’ll never stare at a blank proposal again.
How to Open With a Line That Proves You Read the Brief
Let me tell you about the worst opening line I ever wrote. It was on Upwork, for a restaurant owner who needed online ordering. I wrote: “Hello, I am an experienced WordPress developer specializing in restaurant websites.” I might as well have written nothing. Every other bidder wrote some version of the same sentence. I never heard back.
Here’s what I write now. Before I type a single word of the proposal, I re-read the job post and hunt for one of four details: a specific technology (“WooCommerce”, “Elementor”), a specific problem (“checkout keeps failing on mobile”), a specific constraint (“must handle 200 orders a day”), or a specific goal (“rank for bakery in Chicago”). That detail becomes my first sentence.
Bad opening: “Hi, I am a WordPress and WooCommerce expert with 6 years of experience. I can help you with your website.” Good opening: “Checkout abandonment at the payment step is almost always a plugin conflict or a theme issue on mobile — I’ve fixed this exact problem on four WooCommerce stores this year.”
See the difference? The good one names the pain and shows pattern recognition. The client thinks: this person already understands my problem better than I do. The good opening never mentions your experience. It doesn’t have to — the knowledge proves it.
Write your opening in this order: their problem first, your proof second, yourself never. After the hook, add your single credibility sentence: “I rebuilt a slow WooCommerce store that now loads in under 2 seconds and handles holiday traffic without crashing.” Specific. Measurable. Done. Then move on to your approach before the reader’s attention fades.
Bonus Tip: If the client included a website link, spend five minutes actually looking at it before you write the opening. Mention one thing you noticed — “your contact form redirects to a 404 page” — and your proposal instantly jumps ahead of every copy-paste bidder. Five minutes of looking beats five years of adjectives.
Describe Your Approach Like an Expert, Not a Vendor
This is where most proposals turn into brochures. “I offer web design, SEO, and maintenance services.” That’s a vendor talking. Clients pay more to experts, and experts describe their thinking.
Compare these two. Vendor version: “I will build your WordPress site with a modern theme, contact form, and blog.” Expert version: “First I’ll audit your current setup and remove the plugins slowing it down. Then I’ll rebuild the homepage around your booking form — since that’s where your customers actually convert. Finally I’ll test everything on mobile before launch, because that’s where most of your traffic comes from.”
The expert version tells a story in three acts. It shows sequence, priority, and reasoning. The client can picture the work happening. And notice: it also quietly proves the freelancer diagnosed something (slow plugins) that the client might not have known. That’s the moment a client decides they’d be dumb to hire anyone else.
Keep it to 2–3 sentences. More than that and it reads like a project plan, which belongs in the contract, not the proposal. End this section with a line that points forward: “Once I see your current setup, I’ll confirm the exact timeline — but projects like this typically take two weeks.”
Price With Two Options and Watch “Maybe” Turn Into “Yes”
I used to send one price. One number, one take-it-or-leave-it. Then a mentor asked me a question that changed everything: “What happens in the client’s head when they read a single price?” The answer: they compare your price against doing nothing, or against the cheapest bidder. That’s a fight you often lose.
Now I always offer two options, and it changed the question entirely. The client stops asking “should I hire this person?” and starts asking “which package is right for me?” That mental shift is worth more than any discount.
Here’s how I structure it. Standard: the core deliverables, cleanly defined. “5-page WordPress site, mobile-tested, speed-optimized, launch support included — $1,800, delivered in 3 weeks.” Premium: standard plus 2–3 meaningful additions, priced about 30% higher. “Everything in Standard, plus blog setup with 3 launch articles, on-page SEO configuration, and 30 days of post-launch support — $2,400, delivered in 3 weeks.”
The premium option needs to feel like a genuinely better fit for an ambitious client, not a forced upsell. I pick additions the client would probably ask for later anyway — SEO basics, extra support, content help. When clients choose Premium (and many do), I make more and they get more. When they choose Standard, I still win the project. The only outcome this structure eliminates is “let me think about it.”
One rule I never break: never present three options in a proposal. Three options feel like a pricing page, and pricing pages feel impersonal. Two options feel like a recommendation from someone who understood the project. And always name the total as an investment figure with the timeline attached — “$1,800, delivered in 3 weeks” — because price without timeline is just a number floating in the air.
Note: I’m not a lawyer or an accountant, and this is pricing strategy, not financial advice. Your rates should reflect your costs, your market, and your experience level. The structure works at $500 or $15,000 — only the numbers change.
Follow Up Like a Professional, Not a Stalker
Here’s an uncomfortable truth: most of my won projects didn’t close on the first message. They closed on the follow-up. Clients are busy. They read your proposal between meetings, mean to reply, and forget. Silence is usually not rejection — it’s distraction.
My mistake for years was either never following up (leaving money on the table) or following up like a needy ex: “Just checking if you saw my proposal?” That sentence helps nobody. It reminds the client they owe you a reply and gives them nothing new. Of course they ignore it.
The follow-up that works gives the client something. My standard one goes out 3–4 days after the proposal: “Hi [name], while reviewing your site I noticed your homepage images are slowing mobile load times — fixing that alone usually improves bounce rates. Happy to include it in the project if we move ahead. Still interested?” That’s value, not begging. It shows I’m already thinking about their business. About half of these get a reply, and many turn into signed contracts.
My follow-up rules: one follow-up after 3–4 days, a second (shorter) one after 10 days, then stop. Two follow-ups is persistence; three is pressure. Never follow up on the same day you sent the proposal. And every follow-up must contain something new — an observation, a question, a small win — never just “checking in.”
If a client explicitly says no, thank them and ask one question: “Would you mind telling me what decided it?” Most won’t answer, but the ones who do give you the most valuable feedback of your career. One “your proposal was great but we went with someone local” taught me to add a line about time-zone overlap to every proposal. Tiny fix, real results.
Mistakes That Silently Kill Even Strong Proposals
I keep a running list of these because I’ve made every single one. Here are the killers that undo an otherwise good proposal:
- Sending a wall of text. Dense paragraphs get skimmed or skipped. Short paragraphs, bullet points, and white space make your proposal readable on a phone at midnight — which is when many clients read them.
- Talking about yourself more than the client. Count the “I/me/my” versus “you/your” in your draft. If “I” wins by a lot, rewrite. The proposal is about them.
- Vague deliverables. “A beautiful, modern website” means nothing. “Homepage, about page, services page, contact page, and blog — all mobile-tested” means everything. Specifics are trust.
- Hiding the price. Some freelancers avoid stating price, hoping to “discuss on a call.” Clients read that as “this will be expensive and awkward.” Name your number confidently.
- No next step. Ending with “I look forward to hearing from you” puts all the work on the client. End with one simple action instead.
- Typos in the client’s name or business. Nothing kills credibility faster. I once sent a proposal addressed to the wrong company name. I got a polite no. Read the proposal out loud before sending — your ears catch what your eyes miss.
The pattern here is simple: every one of these mistakes makes the client work harder. Your proposal’s job is to make everything easy — easy to read, easy to understand, easy to say yes to.
My Pre-Send Checklist (Steal This)
Before I send any proposal now, I run through this checklist. It takes 90 seconds and has saved me from more embarrassments than I can count.
- ☐ First sentence names the client’s specific problem (not my title)
- ☐ One credibility sentence with a real, specific result
- ☐ Approach described in 2–3 sentences with clear steps
- ☐ Deliverables listed as bullets — included AND excluded
- ☐ Two pricing options with timelines attached
- ☐ One clear next step at the end
- ☐ Client’s name and business spelled correctly (read out loud!)
- ☐ Under one page for email proposals, or cleanly formatted PDF for formal ones
The excluded-items line deserves emphasis. I write things like: “Not included: logo design, copywriting, ongoing monthly maintenance (available separately).” This one line has prevented more arguments than any other sentence I write. Clients respect clarity. What they don’t respect is discovering mid-project that something they assumed was included costs extra. If you want a deeper look at keeping projects clean, my guide on [how to customize WordPress without breaking it](https://hyperdaf.com/how-to-customize-wordpress-without-breaking-it) covers the delivery discipline that makes clients come back.
Frequently Asked Questions
How long should a WordPress proposal be? For platform bids (Upwork, Fiverr), keep it to 5–7 short paragraphs — that’s all a client reads before deciding. For direct clients and formal RFPs, a clean 2–4 page PDF works, but the six-part structure stays the same. Length never wins; clarity does.
Should I include my portfolio in the proposal? Yes, but as 2–3 linked examples of relevant work, not a full gallery. Pick projects that resemble the client’s project. A restaurant owner doesn’t care about your SaaS dashboard. Relevance beats volume every time.
What if the client asks for a discount? Don’t discount the price — adjust the scope. “I can do $1,400 if we drop the blog setup and launch articles” keeps your rate intact and teaches the client that price and scope are connected. Discounting your number without touching the scope just trains clients to haggle.
How fast should I send a proposal after the first contact? Within 24 hours, ideally the same day. Speed signals enthusiasm and competence. But never rush so fast that you skip reading the brief properly — a fast generic proposal loses to a thoughtful one sent six hours later.
Do I need a designed PDF, or is email fine? Email is fine for most projects under $3,000. A clean PDF with your branding helps for bigger projects and corporate clients. The structure matters 10x more than the format. I won a $6,000 project with a plain-text email because the opening line nailed the client’s problem.
Final Thoughts
I still remember that month of 31 proposals and one win. It felt like the market was telling me I wasn’t good enough. It wasn’t. It was telling me my proposals weren’t doing their job — they were talking about me when they should have been talking about the client.
If you take one thing from this guide, let it be this: the first sentence does the heaviest lifting. Name their problem before you name yourself. Everything else — the structure, the pricing, the follow-up — amplifies that one moment of recognition where the client thinks, “finally, someone who gets it.”
You did the hard part already by reading to the end. Now open your last rejected proposal, rewrite just the opening line using what you learned here, and feel the difference. I’d love to hear how it goes — drop a comment below and tell me what changed in your replies. And if you want to tighten the delivery side too, read my checklist on [how to install WordPress plugins safely](https://hyperdaf.com/how-to-install-wordpress-plugins-safely) — because winning the client is only half the job.
