AI RFP Responses for Law Firms: Faster Answers, Better Questions, Fewer Fabrications

Greg Siskind, founder of Siskind Susser, put the question in ABA Law Practice in March 2026: “If a firm determines it has an eight percent chance of winning a proposal that will cost $35,000 in partner time, should they proceed?” Most firms never run that arithmetic. They run the pitch. AI RFP responses for law firms start there, with a decision, not a draft.

The volume makes the decision urgent. QorusDocs’ 2025 benchmark found 67% of firms reporting rising pitch and RFP volume and average RFP turnaround up from six days in 2022 to nine in 2025. The savings figures, by contrast, are vendor case studies (Ikaun reports GRSM cutting proposal turnaround by 50% in four months; Harvey reports a 48-hour urgent response at Lynn Pinker Hurst & Schwegmann), so measure your own baseline first. What the independent data shows is a pitch machine slowing down as demand rises.

The economics: $35,000 pitches at 8% win rates

One number explains the slowness and the risk. Ikaun, a proposal-software vendor, reported in 2026 that only 27% of firms actively use AI in proposals and that 74% lack a single source of truth for matter experience. If experience lives in nine partners’ heads, every pitch starts from a blank page, and a model asked to fill it will oblige with matters that never happened.

Build the bid/no-bid use first: give the model three years of proposals with outcomes, the new RFP and the partner hours a comparable bid consumed, and ask for a win-probability range with reasons.

Siskind’s ten RFP uses

One caution frames all ten: drafting RFP responses “using public LLMs that train on the data the law firm inputs is an absolute no-no”.

From the attached RFP, extract every requirement, question, deadline, format rule, mandatory clause and evaluation criterion into a matrix: Ref | Requirement (quoted) | Type (mandatory / scored / informational) | Weight | Verified precedent answer available? (Yes / No / Partial) | Owner | Risk.
Then list every outside-counsel-guideline term (billing, travel, staffing, data security, indemnity, AI use) and classify each Standard / Needs review / Deal-breaker against <terms>.
Finally a bid/no-bid summary: fit with <experience_index>, win-probability drivers, estimated partner hours by section, and three questions to ask the client before we decide.
Do not draft answers. Do not infer experience we have not listed.

Building the answer library the draft comes from

The library is the product. A Claude Project or custom GPT holding anonymised winning answers, current bios, matter descriptions with a “verified by / date” field and the firm’s standard terms is what makes a 70-80% draft safe; the Projects and custom GPTs guide covers the set-up.

Using only the answer library in <library> (each entry carries a matter reference, a verification date and an owner), draft responses to the RFP questions in <matrix>. Where a verified precedent answer exists, adapt it to this client's wording and cite the entry; where only part exists, draft that part and mark the gap [NEEDS PARTNER INPUT: what is missing]; where nothing exists, write [NEEDS PARTNER INPUT] with three bullet prompts for the partner. Never create a matter, client, result, award or credential that is not in the library. List every entry you relied on.

The client’s new questions about AI

In the ACC/Everlaw 2025 survey of 657 in-house professionals, 59% did not know whether their outside counsel used generative AI, 80% neither required nor encouraged it, and only 3% collaborated with their firms on it. Axiom’s July 2026 report found 92% of in-house teams expecting or negotiating AI-related rate cuts. Citigroup’s global head of legal, Adam Meshel, quoted by the Financial Times and the New York Post on 1 September 2026, says Citi now asks bidding firms to disclose AI savings: “our expectation is for costs to come down significantly per transaction.”

So RFPs now carry AI sections lifted from outside counsel guidelines. Poppy Legal’s sample clause requires disclosure of “the tool, provider, use case, categories of data involved, applicable retention and training settings, planned human review, and any proposed charge”; Layer3Labs’ five standard provisions add approved and prohibited tools (many OCGs ban “free public chatbots for any client work”), no client data into public models, billing for actual time with no charge for learning general tools, and mandatory human review. Answer specifically: Law.com’s Amit Dungarani notes that a bare claim to use AI “reveals nothing about the maturity, security, or value delivered”. The OCG clause guide walks through each term.

One r/legaltech commenter described “increasing client pressure to have some sort of ‘name brand’” AI; another put it more bluntly: firms’ “primary need is to be able to tell their clients their using AI”. The answer is not to buy a logo but to explain what you do, because, as Seward & Kissel’s CFO Anton Levchik put it, “If you can’t explain to your clients what you’re doing in AI space, your clients will assume that you are overpriced.”

Pricing answers: AI-assisted fee structures

The ethics floor is fixed. ABA Formal Opinion 512 says lawyers billing hourly may “only bill for their actual time”, and that “a fee charged for which little or no work was performed is an unreasonable fee”, which is the trap for a flat fee left unchanged after AI has cut the work. Above the floor, Thomson Reuters’ 2026 report on AI strategy gives the pitch a script: what changed about the work, what changed for the client, what value was created, how pricing should reflect it. Its warning: “Firms leading with price concessions risk training clients to expect discounts rather than pay for capability.”

The academic debate is worth one line in a pitch meeting: Georgetown’s Jonah Perlin argues in “How the Billable Hour Can Survive Generative AI”, via his “CHRGE equation” and Jevons Paradox, that fewer hours need not mean less revenue, while Rapoport and Tiano’s “Fighting the Hypothetical” reaches the opposite conclusion. The billable-hour guide has both sides.

Prepare one page of talking points on how we use AI on [client]'s matter types and how it affects pricing, in this order: what changed about the work; what changed for the client; what value that created; how pricing should reflect it. Include where AI saves time on these matters and where it does not; our verification commitment; our billing rule (actual time only; no charge for learning tools; no reconstructed "equivalent time"); and two fee options (fixed fee for [matter type]; capped hourly for [matter type]). Lead with value, not concessions. Use only <matter_data>.

The fabrication trap: invented matter experience

The quieter version is the upgrade: models asked to harmonise five partners’ contributions turn “leading” into “the leading”. Tone consistency therefore needs a rule that no factual claim, name, number, date or credential changes, and every altered sentence is listed.

The attached proposal was written by five partners. Rewrite it in one consistent voice matching <style_guide>, without changing any factual claim, name, number, date, result or credential. Then produce a change log listing every sentence whose meaning you altered (there should be none) and every factual claim that lacks a source, for BD to verify.

Review workflow and sign-off

Four steps before submission: the compliance check against the matrix (every mandatory item addressed, every format rule met, page limits kept); the change log from the harmonisation prompt, worked through by BD; every success story, award and bio traced to its source; and the responsible partner reading the final text and signing the AI disclosure. Siskind on that disclosure: “You should disclose that AI provided some assistance, but make sure the client understands that it was done with the firm’s close oversight.”

Confidentiality runs underneath all four: the RFP is the client’s document and your library holds win rates and pricing, so use a tier that does not train on inputs (the ChatGPT confidentiality guide explains which) and keep the library anonymised.

A pitch-prep sequence you can run this week

Day one: requirements matrix and bid/no-bid summary in the morning, committee decision, then a draft from the library only, with [NEEDS PARTNER INPUT] items sent to partners. Day two: partner input in, harmonise with a change log, BD verifies every flagged claim. Day three: compliance check against the matrix, pricing talking points, partner sign-off.

AI Lab for Lawyers runs for teams as well as individuals (Maven for Teams and private cohorts), its business-development edition covers pitch preparation, and the answer library is the kind of Project a BD professional and a pitch partner can build side by side. The prompts above are in the prompt library.

Where to go next: the business-development pillar for the rest of the BD workflow, the in-house guide for the client’s chair, and the disclosure guide for when AI use must be declared. The whole cluster is in the business-development hub.