The proposal you think is strong and the proposal that is actually strong are often different documents. The gap between them is invisible until a buyer fails to respond, and by then it’s too late to fix it. The proposal diagnostic score makes the gap visible before sending, 12 criteria, 12 minutes, and a number that tells you whether to send or revise. Sub-8 proposals should not be sent. They don’t close, and they teach buyers to have lower expectations of you.
The 12-Point Scorecard
Score each criterion as 1 (passes) or 0 (fails). The total is your diagnostic score.
Criterion 1: The buyer’s problem is stated in their language, not yours. Does the problem statement use exact phrases or numbers the buyer used in the discovery conversation, not a paraphrase? If the buyer said “we’re losing 30% of users in the first week,” does the proposal say that, or does it say “you’re experiencing onboarding challenges”? Score: 1 if buyer language is visible. 0 if the problem is restated generically.
Criterion 2: The problem statement is on the first page. A buyer who reads only the first page should understand what problem the proposal is solving. If the problem statement is buried after a bio, a company overview, or a service description, score 0. The buyer’s problem should be the first substantive content they encounter.
Criterion 3: Every deliverable specifies what, how many, what format, and when. Vague deliverables (“strategic recommendations,” “ongoing support”) fail this criterion automatically. Score 1 only if every deliverable is described with enough specificity that two readers would interpret it identically.
Criterion 4: The timeline includes specific dates and buyer responsibilities. “Week 1, Week 2” is not a timeline. A timeline with specific calendar dates and named responsibilities for both parties scores 1. Any less specificity scores 0.
Criterion 5: The proposal opens with buyer context, not freelancer biography. The first page should establish the buyer’s situation, not the freelancer’s credentials. Score 0 if the proposal opens with “About me” or “Our company.”
Criterion 6: At least one piece of Tier 1 proof appears in the first two pages. Tier 1 proof means a specific case study result: a named client type, a specific outcome, a specific timeframe. “I’ve helped many clients grow” does not pass. “Increased qualified pipeline by 43% for a B2B SaaS client in 11 weeks” does.
The six criteria above account for over 70% of the trust deficit in failing proposals. If your score is below 4 on just these six, stop and repair before scoring the rest.
Criterion 7: The methodology section is written in plain language, not jargon. Run the test: for each step in your process, ask whether a non-expert would understand what they receive at the end of that step. If any step sounds like “stakeholder alignment facilitation,” score 0 for this criterion.
Criterion 8: An outcome snapshot or ROI visual appears above the pricing. Is there a before/after, a 3-number summary, or a timeline outcome chart positioned between the methodology and the investment? If the proposal goes directly from methodology to price with no anchoring visual, score 0.
Criterion 9: The pricing page is clean and has a single primary number. Multiple line items, footnotes, and qualifying language on the pricing page increase anxiety. A clean page with one primary investment figure scores 1. A complex price breakdown without a summary total scores 0.
Criterion 10: The proposal cannot be shortened by removing any section without losing persuasive value. Read each section and ask: if this section were removed, would the buyer be less likely to say yes? If any section is padding, a company history no one asked for, a bio that runs three paragraphs, a general FAQ that doesn’t address this buyer’s situation, score 0.
Criterion 11: The next step is specific, owned, and dated. “Let me know if you have questions” scores 0. “I have us scheduled for a 20-minute call on May 14 at 2pm to walk through any questions” scores 1. The next step must be a named action, with a named owner, and a specific date.
Criterion 12: You would be comfortable if the buyer shared this proposal with three colleagues as their primary recommendation. This is the confidence criterion. Score honestly. If there is any section you’d be embarrassed by, any language you know is weak, any number that isn’t grounded in reality, score 0. If you’d send it to your own best client as an example of your best work, score 1.
Interpreting Your Score
10–12: Send as-is. The proposal reflects deliberate thinking about the buyer’s situation and strong execution on the key trust criteria.
8–9: Identify the failing criteria and repair them before sending. Most repairs take 10–20 minutes. The failing criteria are almost always visible in the score, go directly to them.
6–7: Two to three hours of substantive revision required. The proposal likely has structural issues, not just copyediting issues. Review criteria 1–6 first.
Below 6: Rebuild from the problem statement. A proposal scoring below 6 has fundamental misalignments that cannot be fixed by editing, the framing, structure, or specificity is fundamentally off.
The Time Cost of Not Running the Audit
A proposal that took 4 hours to write and 0 minutes to audit will lose to a proposal that took 3 hours to write and 30 minutes to audit, on the same scope and the same price.
The diagnostic adds 8–12 minutes to the proposal process. On a $10,000 engagement, improving from a score of 6 to a score of 10 typically improves close probability from 25% to 55%, a 30-percentage-point difference. The expected value of that improvement is $3,000 per proposal sent. The 12 minutes of audit time is the highest-ROI activity in the entire freelance sales process, and most freelancers skip it entirely.
Running the Audit as a Habit
The goal is for the 12-point audit to become automatic, run on every proposal, regardless of how confident you feel about it. The freelancers who score highest on the diagnostic are rarely the ones who feel most confident before running it. They are the ones who run it consistently enough to know which criteria they tend to fail and to fix those criteria before they become proposal-killers.
Build the scorecard into your proposal workflow: the last step before the delivery email gets sent is the diagnostic check. When the score is 10+, send the email. When it isn’t, fix what’s failing first.
