Objection Response Library
Part 1: Plaintiff Attorney Objections
These are the objections adjusters will face most frequently — usually over the phone, in writing, or at mediation. The goal is never to "win" the argument, but to redirect the conversation back to data and keep the negotiation moving.
1.1 "Your offer is insultingly low."
What's really being said: "I need to signal to my client that I pushed back hard, and I want to see if you'll panic and move."
Response Strategy: Don't apologize and don't move. Acknowledge the reaction, then redirect to the package. The offer isn't your opinion — it's the data's conclusion.
Sample Script:
"I understand the number feels low relative to your demand, and I want to make sure we're working from the same set of facts. That's exactly why I sent the written package — it walks through the specific liability factors, the venue data, and the medical analysis that got us to this number. Can we walk through any section of it together? I'd rather address your specific concerns directly than just trade numbers."
1.2 "My client has suffered enormously. The damages are real."
What's really being said: "I'm going to anchor this in emotion because I know it works."
Response Strategy: Validate the human element — never dismiss it — then pivot to the framework. The question isn't whether the damages are real, it's what the legal environment says they're worth.
Sample Script:
"No one is disputing that your client was injured — that's not what's at issue here. What the package addresses is the probable outcome if this goes to trial in [venue]. Based on comparable cases in this jurisdiction, the realistic range for this injury type and these liability facts is [X–Y]. That's not our opinion — that's the verdict data. We want to get your client compensated fairly, and we believe this offer reflects what a jury in this county would actually award."
1.3 "The AI generated this — I don't have to take it seriously."
What's really being said: "I'm looking for a reason to dismiss the package without engaging with the substance."
Response Strategy: Don't get defensive about the technology. Separate the tool from the output. Every fact, data point, and argument in the package is real and verifiable — the AI drafted it, a human reviewed and approved it.
Sample Script:
"I hear you, but let me push back on that framing. The package was drafted using AI as a tool — the same way your firm might use EvenUp to build your demand packages. Every fact in it came from the file. Every data point is sourced from actual verdict data in this jurisdiction. I reviewed and approved it before it went out. If there's a specific fact or argument you think is wrong, I'm happy to address it directly. But 'it was drafted with AI' isn't a rebuttal to the substance."
1.4 "You're not accounting for my client's pain and suffering."
What's really being said: "I want to shift the conversation to the most subjective, hardest-to-quantify element of damages."
Response Strategy: Acknowledge it's in the package, then point to the specific section. Synthesizer packages include non-economic damage analysis — use it.
Sample Script:
"Pain and suffering is actually addressed in Section [X] of the package. What the data shows is that for this injury type, in this venue, non-economic damages in comparable verdicts have ranged from [X to Y]. Our offer accounts for that range. If your client's circumstances are meaningfully different from those comparables, walk me through what makes this case an outlier — I'm listening."
1.5 "We have a strong liability case against your insured."
What's really being said: "I think you're underweighting our chances of winning on liability."
Response Strategy: You've already addressed liability in the package. Point to the specific section and invite a specific rebuttal, not a general assertion.
Sample Script:
"Liability is addressed in detail in the package — specifically [section/page]. Our analysis accounts for [X liability factors]. If there's evidence or witness testimony we haven't factored in, I want to know about it. A specific rebuttal to our liability analysis will move this conversation forward faster than a general disagreement about strength."
1.6 "I need more time / my client isn't ready to settle."
What's really being said: "I'm not ready to have this conversation yet" — or — "I need to manage my client's expectations and this package is going to help me do that."
Response Strategy: This is actually a good sign. The package is now in their hands and will do work for you. Don't chase — set a clear next step.
Sample Script:
"That's completely fine. The package isn't going anywhere — take the time you need to review it with your client. I'd ask that you share it with them directly, because a lot of what's in there is information that's useful for their decision, not just yours. Can we put a 2-week follow-up on the calendar so we have a defined window to revisit?"
1.7 "I've gotten much higher verdicts in this county."
What's really being said: "I have anecdotal data I'm going to use to counter your statistical data."
Response Strategy: One verdict is not a trend. The Analyzer data represents the full distribution of outcomes — including the cases that didn't go your opponent's way.
Sample Script:
"I don't doubt that — outlier verdicts happen, and I'm sure you've had wins. But a negotiation should be based on what's probable, not what's possible. The data in the package shows the full distribution of outcomes for this injury type in this venue — including the median, the range, and the cases that settled well below demand. One high verdict doesn't change the probability-weighted picture. Would it help if I walked you through how the venue analysis was constructed?"
Part 2: Defense Counsel Objections
These objections typically arise when you're asking defense counsel to incorporate Synthesizer packages into their workflow, or when there's friction about who controls the negotiation narrative.
2.1 "I prefer to handle negotiations my own way."
What's really being said: "This feels like a challenge to my authority or expertise."
Response Strategy: Position the package as support for their strategy, not a replacement for it. They're still the pilot — Synthesizer is the navigator.
Sample Script:
"This isn't meant to change how you negotiate — it's meant to give you better ammunition. The package captures the defense strategy you've already built and puts it in a format that travels well. You control what goes in, you review it before it goes out, and you decide when and how to deploy it. Think of it as a leave-behind that does the heavy lifting after the call ends."
2.2 "The AI might misrepresent the facts of our case."
What's really being said: "I'm worried about accuracy and professional liability."
Response Strategy: This is a legitimate concern — acknowledge it directly. The review step is non-negotiable and should be reinforced, not minimized.
Sample Script:
"That's exactly why your review is a required step before anything goes out — not optional. AI can draft quickly but it can get details wrong, and you'd catch that. What we've found in practice is that the package gets 90% of the way there, and counsel's edits are usually refinements rather than corrections. But you're the check — that's by design, not an afterthought."
2.3 "This adds work to my plate."
What's really being said: "Show me the ROI before I change my process."
Response Strategy: Lead with the time savings data. The HelpScout content cites 4–5 hours of prep time saved per file. That's a direct billing reduction — and that's the number that gets attention.
Sample Script:
"I hear you — the last thing we want to do is add to your workload. What the data from our pilot programs shows is that using a Synthesizer package before mediation saved defense counsel an average of 4 to 5 hours of preparation time per file. That's not our estimate — that came from counsel tracking their own hours. The package essentially drafts your mediation brief. You edit, you approve, it goes out. Net time is almost always less than doing it from scratch."
2.4 "I don't want opposing counsel to know we're using AI."
What's really being said: "I'm worried about optics or perceived fairness challenges."
Response Strategy: Normalize it. Plaintiff firms are already using EvenUp and similar tools. This levels the playing field — it doesn't create an unfair one.
Sample Script:
"Plaintiff firms have been using AI to build demand packages for a couple of years now. EvenUp alone is in hundreds of firms. This isn't a secret weapon — it's table stakes. Using Synthesizer doesn't need to be disclosed any more than they disclose using EvenUp. The package is reviewed, approved, and signed off by you. It's your work product."
Part 3: Mediator Objections and Concerns
Mediators aren't adversaries, but they can be skeptical of packages that feel one-sided or that make their job harder. The goal here is to position the Synthesizer package as something that makes the mediator's job easier.
3.1 "This package feels very one-sided."
What's really being said: "I need to be neutral, and I'm not sure I can use this as a tool."
Response Strategy: Acknowledge the mediator's role and reframe the package as a factual document, not advocacy. The data is neutral even if the framing favors the defense.
Sample Script:
"You're right that it's written from the defense perspective — that's intentional. But the underlying data — the verdict trends, the venue analysis, the medical comparables — that's objective. What we've found is that mediators find it useful specifically because it gives them specific talking points and numbers to use in the other room. You're not endorsing our position; you're using our evidence to have a more grounded conversation with the plaintiff."
3.2 "The plaintiff's attorney is going to object to this."
What's really being said: "I don't want conflict in my mediation session."
Response Strategy: Normalize pre-mediation packages as standard practice, and point out that plaintiff counsel sends detailed demand packages all the time.
Sample Script:
"Plaintiff counsel sends detailed demand packages to mediators regularly — this is the defense equivalent. If they object to us presenting our evidence and data in writing, that's worth noting. In our experience, the initial reaction fades quickly once counsel starts engaging with the substance. Would it help to share the package with plaintiff counsel in advance so there are no surprises in the room?"
3.3 "I've already reviewed the file. I don't need more materials."
What's really being said: "I don't want more reading."
Response Strategy: Position the package as a replacement for reading, not additional reading. It synthesizes what's already in the file into a format the mediator can use actively.
Sample Script:
"I completely understand — and this isn't meant to add to your prep. Think of it as the opposite: it distills the most relevant facts, liability arguments, and financial data from the file into one document. Rather than cross-referencing your notes in the session, you'd have the defense's full position on one page. Mediators who've used it in our pilot have said it actually shortened their prep time, not extended it."
3.4 "The AI data about this venue might not be accurate."
What's really being said: "I know this jurisdiction and I'm skeptical of data I can't verify."
Response Strategy: Invite scrutiny — the data should hold up. And even if a mediator disagrees with one data point, the overall picture still anchors the conversation.
Sample Script:
"That's a fair challenge, and I'd encourage you to push on it. The venue data comes from [source — actual verdict database]. If you've seen outcomes in this jurisdiction that look different from what the package shows, I'd genuinely like to understand why — it either means there are specific factors in this case we haven't accounted for, or there's a data gap worth knowing about. Either way, it's a better conversation than trading gut feelings about what a jury might do."