The instinct in most sales conversations is to present your best case and hope the buyer doesn’t raise the hard questions. Chris Voss’s approach in Never Split the Difference runs the opposite direction: name the worst concerns yourself, out loud, before the buyer has a chance to bring them up. The accusations audit is one of the most counterintuitive and effective tools in high-stakes negotiation, and it translates directly to freelance proposals.
Why Naming the Worst Works
Concerns held in private accumulate emotional weight. A buyer sitting with “I’m worried this will go over budget” hasn’t said it yet, but it’s shaping how they read every line of your proposal. It makes your prices look worse, your timeline look less credible, and your enthusiasm look suspicious.
When you name that concern first, “You’re probably thinking this could balloon beyond the initial scope”, three things happen simultaneously.
First, the buyer feels understood. You knew what they were thinking. That accuracy creates a moment of trust even before you’ve addressed the concern itself.
Second, the concern’s emotional charge drops. Unspoken worries feel more powerful than voiced ones. The act of naming moves the concern from the private amplification loop into the shared space of the conversation, where it can be dealt with normally.
Third, the buyer no longer carries the burden of deciding whether to raise it. That burden generates friction, many buyers never raise their actual concern because they don’t want to seem difficult or because the moment doesn’t feel right. You’ve removed the friction by opening the door yourself.
The Exact Phrasing That Makes It Work
The language matters. There’s a meaningful difference between:
- “You might be concerned about price.” (Hedged, slightly patronizing.)
- “You’re probably thinking this is expensive.” (Direct, specific, matches internal language.)
The goal is to sound like you’re reading their mind accurately, not presenting a concern from outside. Use “you probably think” or “you’re probably wondering” rather than “some clients worry” or “you might have concerns about.” Generalized language creates distance; specific, personal language creates connection.
The full phrasing pattern: “You probably think [specific concern in their terms], and I want to address that directly.” Then address it, not defensively, but matter-of-factly. The audit is the opener; your response is what actually handles the concern.
The accusations audit works because buyers can’t argue with a concern you’ve already acknowledged. When you name their worry before they voice it, the conversation shifts from confrontation to collaboration, you’re both looking at the concern, rather than standing on opposite sides of it.
The Five Audits Every Freelancer Should Run
Audit 1, Price. “You’re probably looking at this number and thinking it’s more than you expected.” This is the audit that most directly prevents the price-shock reaction. Running it before they’ve had time to lock in on “too expensive” gives you the space to contextualize the investment rather than defending it after they’ve already made up their mind.
Audit 2. Reliability. “You’ve probably worked with contractors who disappeared after the contract was signed, communication drops off, you’re chasing for updates.” This one is particularly powerful because it directly acknowledges the most common bad experience buyers have with freelancers. You’re not just naming a concern; you’re demonstrating you understand the industry’s failure mode.
Audit 3. Communication. “You’re probably wondering what communication looks like during the project, whether you’ll be kept in the loop or left waiting.” Separated from reliability because the failure pattern is different. Reliability is about output delivery; communication is about the experience of working together. Both deserve their own audit.
Audit 4, Scope and Cost Growth. “You’re probably concerned about whether the final cost will match what we’re quoting, or whether things will keep getting added.” Budget certainty is one of the top anxiety drivers for clients buying a service for the first time or after a bad experience. Naming it opens the conversation about how you structure and document scope changes.
Audit 5. Fit and Expertise. “You’re probably wondering whether our experience applies to your specific situation, given that your industry is pretty particular.” This one is especially relevant for specialized industries, niche software, or unusual project types. Buyers often don’t raise fit concerns directly because they don’t want to seem presumptuous, so they just don’t hire you instead. The audit gives them permission to explore it.
When to Run the Audit: Before the Proposal, Not After
The timing of the accusations audit changes its effectiveness significantly. Run it before you reveal the investment, during your summary of their situation, as a bridge into the proposal, and you’re defusing the mines before you walk into the field. Run it after a price objection has already landed, and it reads as a defense rather than a move.
The optimal placement: after your summary of their situation (where you’ve built “that’s right” credibility) and before you present the investment. “Before I walk you through what this looks like and what the investment is, I want to name a few things you’re probably thinking…” then run two or three of the most relevant audits. By the time the price appears, those concerns are already on the table and partially addressed.
Calibrating the Audit to the Specific Buyer
Not every audit is appropriate for every buyer. A returning client doesn’t need an audit on reliability, you’ve already established that. A buyer who has explicitly said their budget is flexible doesn’t need an audit on price. The goal is to surface the concerns that are genuinely relevant to this buyer’s situation, not to run every possible concern and accidentally introduce ones that weren’t there.
The calibration comes from the discovery call. By the time you’re running the audit, you should have enough information about the buyer’s prior experiences, current constraints, and specific anxieties to select the two or three audits that will land most accurately. Those two or three, landed precisely, are worth more than five generic ones.
What the Audit Does to the Proposal Conversation
Proposals reviewed by buyers who’ve heard an accurate accusations audit beforehand behave differently in conversation. Rather than opening with objections, buyers tend to engage with the specifics, they ask clarifying questions rather than raising barriers. The adversarial energy that often accompanies proposal reviews is reduced because the buyer’s defensive guard came down during the audit.
The practical outcome: more honest conversations about what actually matters to the buyer, fewer ghosted proposals from buyers who were secretly concerned about something they never raised, and a clearer path to yes or no, either outcome being more useful than the ambiguous silence that follows an unaudited proposal.
Running the Audit on Yourself First
The preparation for an effective accusations audit is self-honesty. Before a call, write down the real concerns this specific buyer probably has, including the ones you least want to address. The temptation is to audit only the concerns you have good answers to. But the concerns that feel most uncomfortable to name are usually exactly the ones that are keeping buyers from committing.
If you’re newer and reliability is genuinely a reasonable concern, audit it and address it directly with your structure (milestone-based payment, check-in schedule, communication protocol). If your price is genuinely high, audit it and explain the value architecture rather than hoping the buyer won’t notice. The audit’s credibility comes from naming the real concerns, not the comfortable ones.
