Legal · Discovery Call
Discovery Call Questions for Legal: A 25-Minute Diagnostic for Law Firm Buyers
You have 25 minutes with a Litigation Chair who bills 2,200 hours a year and cleared this slot between a meet-and-confer and a partner comp meeting. He knows your one-liner. He is not going to be impressed that you work with 40 firms. What he will notice — inside the first ninety seconds — is whether you know that a matter is not a project, that a write-down and a write-off are different events, and that nothing in his shop gets bought without the risk committee, the technology committee, and one senior partner who can stall the whole thing by saying "I'd want to look at that more closely."
The surface problem he hands you in minute two will be something like "our associates are drowning in review" or "clients are pushing flat fees and we're guessing." That's worth almost nothing. The mechanism underneath it — 2,400 documents a day going to a contract reviewer, a second-pass privilege call by a third-year, a privilege log that eats three weeks, a billing partner who finds out at write-off time that the OCGs never allowed first-level review at associate rates — is the thing you have to earn. And the layer under that, the one that actually moves a deal, is political: whose origination credit is on the client, which partner has been complaining loudest about realization in the low 80s, and what the Managing Partner said out loud at the last partners' meeting about lockup.
This playbook gives you the clock, the layered question set, the legal-specific objections you will hear (ALSP pricing, a bad predictive-coding experience, Rule 1.6, "send it to the technology committee"), and a sample call with a buyer who is difficult in exactly the way law firm buyers are difficult. Run it as written. Drill it out loud before you dial.
The discovery call script
Say it in your own words. The structure is the part that matters.
- 1
0:00–2:00 — Frame (do not re-pitch)
"Thanks for holding the time — I know you've got a production date on the [X] matter, so I'll keep us to 25. When we spoke, you said the thing keeping you up is that first-level review on your big commercial matters is getting written down and the associates doing it are the ones leaving. That's what I want to dig into. Fair warning on how I run these: I'm going to ask questions for the first fifteen minutes and I'm not going to show you anything. I'd honestly rather tell you this isn't a fit for your practice than burn a demo slot on both of us. Still good for 25? And is there anything you want to make sure we get to, so I don't run us out of time?" [If they say "I mostly want pricing" — say: "You'll get it, and I want it to be a real number rather than a range. Give me ten minutes of questions first so I'm pricing your actual matter profile and not a hypothetical."]
- 2
2:00–6:00 — Layer 1 to Layer 2: get inside the matter
Pick ONE opener. Do not stack. - "Take me through how a document-heavy matter runs today, from the litigation hold to the privilege log. Where does it actually break?" - "Tell me about the last matter where review went sideways. What happened?" - "What's made this a now problem, versus last year?" Then three follow-ups on the same thread before you change subject: - "Who's making the privilege calls — contract reviewers, your own associates, or a mix?" - "Where does the second pass live? Is that a third-year or a senior associate?" - "What's the workaround the team's built? Every firm has one — spreadsheets, a shadow tracker, somebody's paralegal." - "Does that sit in your review platform or is it happening in Outlook and Excel between the platform and the DMS?" If they say "we use an ALSP," don't accept it as a closed door. Ask: "For first pass only, or are they touching privilege too? And who QCs their calls?" What you're listening for: the exact handoff where partner time or associate time gets consumed on work nobody will pay full rate for.
- 3
6:00–7:00 — When they ask "so what is it you actually do?"
This lands around minute six and it's fair. Thirty seconds, tied to what they just told you, then hand the ball straight back. "Short version — we take the first pass and the privilege-log build off your third-years so [name they used] isn't coding at 1am to hit 1,950. But I'd be guessing at whether that matters to your P&L until I understand one thing: on that last matter, how much of the review time survived the bill?" If they push a second time, give a clean 60 seconds — no slides, no logos — then: "Can I go back to the privilege log piece? That's the part I'm not clear on." They will almost always let you.
- 4
7:00–13:00 — Layer 3: the cost, in their metrics
Ask for numbers in the language the firm actually manages by. - "On that matter, what was cost per document by the time you counted your own QC pass?" - "Where's standard realization sitting for that practice group — are you at 90, or is it more like 83 to 88?" - "And on the review line specifically — how much of it gets knocked down before the bill goes out versus written off after the GC sees it?" - "What are your WIP days plus AR right now? Are we talking 90 days of lockup, 120?" - "First-through-third-year attrition — where'd you land last year?" Then the beat most reps skip: **"How do you know?"** "Is that coming out of the billing reports, or is that the number partners say to each other?" If they can't source it, that's a finding, not a dead end. Say: "Then part of what I'd want to do before we talk product is help you pull the actual realization by task code on two matters. If the number's fine, I'll go away." Then wait three seconds. Say nothing.
- 5
13:00–16:00 — Layer 4: the stake and the politics
This is the layer that makes a firm move. Ask it plainly. - "Who's feeling this most — is it you, the billing partner, or the COO looking at lockup?" - "Whose origination credit is on the clients where this hurts worst?" - "Has the Managing Partner said anything about it at a partners' meeting, or is this still a practice-group conversation?" - "When the client pushed back on that $60K invoice — who made that call, and how did it go?" - "Is anyone on the executive committee going to lose money if realization stays where it is?" And the one that separates a real deal from a nice chat: "If this is exactly the same twelve months from now — same write-downs, same attrition — what's the conversation you're having with your partners?" Three seconds of silence after that. The thing they weren't sure they'd say comes next.
- 6
16:00–20:00 — Qualify the path (never say "decision maker")
"If you decided this was worth doing, what actually happens next in your shop? Does it go to the technology committee, the risk committee, or both?" "Who chairs risk — is that your firm GC or the loss prevention partner? What's their default on a vendor that touches client data?" "Do you have a Director of Legal Operations or a Director of Legal Technology who'd own the evaluation, or does it land on a partner's desk?" "Have you tried to fix this before? What happened?" — the last failed project is your real competition. "What's forcing the timeline — a production date, an AFA bid, a panel review, the comp cycle?" If nothing is forcing it, you have a conversation, not a matter. Money, sized not interrogated: "Is this the kind of thing that comes out of an existing budget line — litigation support, KM, IT — or does it have to get created? And can any of it go on the client bill under their OCGs, or is it firm-side margin?" Do-nothing: "What happens if you just keep staffing it the way you do now?"
- 7
20:00–23:00 — Targeted relevance (90 seconds, only what they raised)
Not a demo. Not the tour. One mechanism, theirs. "Two things from what you described, and then I'll stop. One — the privilege log. You said that's three weeks and it's your third-years. That's the piece we build as review runs rather than at the end, so the log isn't a separate project with its own write-down. Two — the defensibility question you raised. You get a documented validation protocol and sampling report you can hand to opposing counsel, and it's designed to sit alongside a 502(d) order rather than replace it. I'm deliberately not showing you the interface, because the thing your risk committee will actually ask about is where the data sits. That's a different conversation and I'd want your CIO on it."
- 8
23:00–25:00 — Playback and the dated next step
Playback in their words, three sentences: "Let me make sure I've got it. First-level review and the privilege log are eating your first- and second-years, realization on that line is running low 80s and you're absorbing the difference, and the pressure's coming from [client name] renegotiating their OCGs before the next panel review in [month]. Did I miss anything, or get anything wrong?" Then prescribe: "Based on that, the useful next step isn't a demo to you. It's 45 minutes with you, your Director of Legal Operations, and whoever owns the security questionnaire — usually the CIO — where we walk one real matter: your document count, your cost per document, and what the review and log would look like handled our way. Bring the task-code detail on that matter if you can pull it. I've got Tuesday at 2, or Thursday at 8 before your court call. Which one?" Send the invite before you hang up. Confirm out loud: who's on it, what you'll show, what they're bringing.
- 9
CRM notes — their words, not yours
Write what they said, verbatim. "Kaplan's third-years did nothing but privilege review for eight months and two of them went in-house; he's had the same conversation at three exit interviews" beats "associate retention concerns" every time. Capture specifically: the matter name and document volume; the realization number and whether it was sourced or remembered; lockup in days; who chairs risk and tech committee; which partner holds origination on the pressured client; the date of the forcing event; and the exact objection language they used, because you will hear it again from the committee.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for the time — I know you've got the Verrano production date coming. When we spoke, you said the thing that's actually bothering you isn't the review volume, it's that you're writing most of it down anyway. That's what I want to get into. I'll ask questions for about fifteen minutes and I won't show you anything. Still good for 25?
Buyer
Twenty. I've got a meet-and-confer at three. And look, before we go too far — I've done this conversation four times in the last two years. Everyone says the same thing about review.
Rep
Then let's not do that conversation. Tell me about the last matter where review went sideways. What actually happened?
Buyer
Breach of contract, mid-eight figures. About 900,000 documents after de-duping. We had an ALSP doing first pass at twenty-eight an hour. Fine. The problem is the privilege calls came back inconsistent, so my third-years had to re-review the hits, and then the log took nineteen days. That's on our clock, at our rates.
Rep
Who owned the log build — one associate or a team?
Buyer
Two third-years and a senior paralegal. Nineteen days, nights included. One of them gave notice in March.
Rep
What did the client pay for those nineteen days?
Buyer
…Not all of it. Their outside counsel guidelines cap review staffing and they wouldn't pay associate rates for anything they characterized as first-level. We took a haircut. That's a fight I didn't want to have with their GC over a $60,000 line.
Rep
So where does standard realization land for the litigation group by the time that's all settled? Are you at 90, or is it more like 83 to 88?
Buyer
Group's at 84 and change. Firm-wide's better because transactional pulls it up. And before you ask, yes, the executive committee has noticed. But I'll tell you now — we tried predictive coding in 2019 and the protocol fight with opposing counsel cost us more in motion practice than the review saved. I'm not doing that again.
Rep
That's a real cost and I'm not going to argue you out of it. What was the fight actually about — the seed set disclosure, or the validation sampling?
Buyer
Seed set. They wanted our non-responsive training documents. Magistrate half-agreed with them. It was a mess.
Rep
That's the fight most firms got burned on, and the case law's moved a lot since. But here's the thing I'd separate: the seed set issue is a first-pass relevance problem. The nineteen days you just described was privilege log. Different workflow, different defensibility posture. Have you looked at those separately, or did 2019 close the door on both?
Buyer
Honestly? Both. Nobody wanted to bring it back to the technology committee. Look — send me something and I'll circulate it.
Rep
Happy to, and I want it to land rather than die in a queue. Who's on that committee, and who on it has actually felt this on a matter?
Buyer
Our COO, the CIO, two partners from corporate, and our loss prevention partner, who chairs risk and whose default answer to any outside vendor holding client data is no. Rule 1.6, malpractice exposure, the whole speech.
Rep
Fair speech. Two questions on that. Do you already run a hosted e-discovery platform or a cloud DMS? And do your clients' OCGs actually prohibit third-party processing, or do they require notice and written consent?
Buyer
We're on a hosted review platform, yes. And most of the guidelines are consent, not prohibition. I'd have to check the big three.
Rep
Then the conversation with your loss prevention partner isn't 'first cloud vendor,' it's 'another vendor under a standard you've already set.' That's a very different memo. Let me play back what I've got: privilege review and the log are landing on your third-years, you're at 84 realization in the group and eating the write-downs, one associate already walked, and the blocker isn't appetite — it's that nobody wants to carry it to a risk committee that says no by default. Anything I got wrong?
Buyer
The associate thing is worse than I said. That's three in eighteen months, all first-through-third year, and the exit interviews all say the same sentence. But no, that's about right.
Rep
Then the next step isn't a demo for you. It's 45 minutes with you, your Director of Legal Operations, and your CIO — where we take Verrano, your actual document count and cost per document, and lay out what the privilege log build looks like, plus I bring the security questionnaire so your risk chair has the four-week document in hand instead of a phone call. You get to be the person who brought it with the homework done. Tuesday at 2, or Thursday at 8 before your court call?
Buyer
Thursday at 8. Bring the questionnaire and don't bring a slide deck. And I want the cost-per-document comparison against twenty-eight an hour, fully loaded with our QC time.
Rep
Done. Invite's going out now — you, Legal Ops, CIO, 45 minutes, Verrano numbers and the security questionnaire, no deck. If you can pull the task-code detail on that nineteen-day log period before then, the comparison gets a lot sharper.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Client confidentiality — our risk committee will veto anything cloud-y.” | Then don't take it to them as a cloud product. Two questions first: what do your clients' outside counsel guidelines actually require — most say notice and written consent for third-party processing, not prohibition. And do you already run a hosted e-discovery platform or a cloud DMS? Most firms do, and that reframes this from 'our first cloud vendor' to 'another vendor under a standard we already set.' There's also a single-tenant and an on-prem option. Either way, let's get the security questionnaire in front of your CIO early — it's a four-week document, not a phone call, and your loss prevention partner will want it in hand before the meeting, not during it. |
| “Partners have practiced the same way for thirty years. Change here is glacial.” | Agreed, which is why I'm not asking for a firm-wide rollout. Which practice group has the most painful matter right now — usually litigation on a big production? Give me one matter, one partner who's already complaining about write-downs, and a defined scope. Firms adopt sideways: one group makes it work, it shows up in realization, and the executive committee follows the numbers rather than leading them. Nobody has to be convinced in the abstract. |
| “Our associates need those hours. If you cut review time you cut billables.” | You're not cutting billables, you're cutting write-offs. What's realization on the first-level review line right now? If clients are knocking 30% off it, those hours were never revenue — they were a subsidy. And on anything fixed-fee or capped, every review hour you don't spend is straight margin. The real question is whether those first- and second-years have higher-value work to move into. If they don't, that's a demand problem and technology won't fix it — but if they do, you're also fixing the exit interview where they say they did nothing but review for eight months. |
| “We tried predictive coding a few years ago. The court fight over the protocol wasn't worth it.” | Fair — TAR validation disputes with opposing counsel are a real cost, not a hypothetical one. Tell me what happened. In most cases the pain was seed set disclosure and negotiating the protocol, and the case law has moved considerably since then. It's also worth separating first-pass relevance from privilege review: the workflow burden and the defensibility questions are genuinely different, and firms who got burned on relevance usually never went back and looked at the privilege log side, which is where the nineteen-day write-downs live. |
| “We already use an ALSP for first-level review at $28 an hour. You can't beat that.” | That's the right comparison, so let's run it properly rather than on the headline rate. What's your total cost per document once you include your associates' QC pass and the privilege log build? And what's the turnaround when a production date moves up two weeks — can they staff that in three days? Most firms find the ALSP handles raw volume fine and the real cost sits in supervision and the second-pass privilege work that never leaves your people. Bring me one matter's numbers on Thursday and we'll do it fully loaded. |
| “Our clients' outside counsel guidelines don't allow us to pass technology costs through.” | Then it's a margin conversation, not a disbursement one — which is actually the better conversation for you. On hourly work this shows up in realization. On AFAs it's how you win the panel spot and still make money on it. Which of your top ten clients are pushing hardest on flat fees or phased budgets with caps? That's where it pays for itself first, and that's the client story your Managing Partner will care about. |
| “Send me something and I'll circulate it to the technology committee.” | Happy to — and I want it to land rather than sit in a queue. Who sits on that committee, and who on it has actually felt this on a live matter? A one-pager to a committee dies. What works is a short memo addressed to the concern each of them will raise: security and Rule 1.6 for the loss prevention partner, cost per document and lockup for the COO, defensibility for you. Can I get fifteen minutes with your Director of Legal Operations first, so the memo has a sponsor in the room when it comes up? |
Questions reps ask about this call
- What are the best discovery call questions for Legal buyers at a law firm?
The ones phrased in the firm's own accounting. "Where's standard realization for that practice group — 90, or low-to-mid 80s?" "What are your WIP days plus AR?" "What's cost per document once you count your own QC pass?" "From the client's first call to a signed engagement letter, is that 24 hours or five days?" Avoid generic efficiency questions — a Practice Group Leader has heard them and will give you a symptom and a polite goodbye. Anchor every question to a specific matter, because everything in a firm is conflicted, budgeted, and billed at the matter level.
- How do I get past the surface answer of "review takes too long"?
Follow up three times on the same thread before you change subject. Ask who's making the privilege calls versus the relevance calls, where the second pass sits (usually a third-year), and what the privilege log actually cost in days. Then go to money: how much of that time survived the bill? Then go to politics: whose origination credit is on that client, and did the billing partner have to call the GC about the invoice? Symptom, mechanism, cost, stake — you need layer three or four before minute sixteen.
- Who should actually be on a law firm discovery call?
You will usually start with one of three: a Practice Group Leader or Litigation Chair who feels the pain on a live matter, a Director of Legal Operations who owns process, or a COO who owns lockup and realization. Your job on the first call is not to collect all of them, it's to find out who chairs the risk committee (often the firm's General Counsel or loss prevention partner) and who owns the security questionnaire (the CIO or Director of Legal Technology). Ask "if you decided this was worth doing, what actually happens next in your shop?" rather than "are you the decision maker."
- How do I handle the risk committee objection without losing the deal on the first call?
Don't defend the cloud. Ask two diagnostic questions instead: what do the client's outside counsel guidelines actually require — notice and consent, or outright prohibition — and does the firm already run a hosted e-discovery platform or cloud DMS. Most firms do, which moves you from "first cloud vendor" to "another vendor under an existing standard." Then offer single-tenant or on-prem and get the security questionnaire to IT early. It's a four-week document; starting it in week one is a competitive advantage.
- The firm says associates need the billable hours. Is that a real objection?
It's real as a feeling and wrong as arithmetic, and you have to handle it that way. Ask what realization is on the first-level review line. If clients are knocking a third off it under their OCGs, those hours were never revenue. On capped or flat-fee work, every hour saved is margin. The honest follow-up is whether the first- and second-years have higher-value work to move into — if not, that's a demand problem, and saying so out loud buys you enormous credibility with a Managing Partner.
- What does a good next step look like after a legal discovery call?
Never "I'll send some information." Prescribe a named, dated session with named attendees and a specific artifact: 45 minutes with the Litigation Chair, the Director of Legal Operations, and the CIO, walking one real matter's document count and cost per document, with the security questionnaire delivered in advance. Ask them to bring the task-code detail for that matter. Get the invite out before you hang up and confirm out loud who's attending and what each side is bringing.