Producing pitches and credentials at speed

It's 4:47 PM on a Thursday. A general counsel emails: "We're running an RFP for our global litigation panel. Submissions due Monday 9 AM." That's roughly 64 working hours to produce a pitch that reads like it took a month, covering matters across four practice groups and three continents. The firms that win this race aren't smarter. They have a system. The ones that lose spend Friday night hunting through old PowerPoints trying to remember which associate worked the Novartis matter.

This lesson is about building that system: a live credentials library and a modular pitch architecture, so business development (BD, the marketing function focused on winning new work and expanding existing clients) is assembling, not authoring, when the clock is running.

Why law firm pitching is structurally slow

Most professional services firms can template a proposal because their service is standardized. Law firms can't, fully, because every matter is confidential, partner-owned, and described differently depending on who wrote it up.

Three structural problems recur:

• Credentials live in people's heads and inboxes. A matter description written for a legal directory submission (like Chambers and Partners or *Legal 500*) sits in one associate's Word file. Nobody indexed it.
• Partners gatekeep their own client relationships. In most partnerships, a partner "owns" the contact, and BD cannot repurpose a matter description or use a client's name in a pitch without partner sign-off, sometimes without General Counsel sign-off too, given confidentiality and conflict concerns.
• Every RFP wants a different cut of the same experience. One wants "deals over $500 million in the last 24 months." Another wants "experience against Kirkland & Ellis as opposing counsel." If your credentials aren't tagged by variables like deal size, sector, jurisdiction, and opposing counsel, every pitch is a research project.

The fix is not "hire faster writers." It's building infrastructure before the RFP lands.

The credentials library: structure before speed

A credentials library is a searchable, tagged database of matter descriptions, kept current, that BD can query in minutes instead of asking partners to write from scratch.

Minimum viable structure, per matter entry:

1. One-paragraph description, pre-cleared for external use (client consented or matter is public record, e.g., court filings, announced M&A deals).
2. Tags: practice group, sector (using a fixed taxonomy, not free text), jurisdiction, deal/matter value band, role (lead counsel vs. supporting), date, key partner and associate names.
3. Confidentiality flag: public, nameable with consent, anonymized only ("advised a Fortune 500 pharmaceutical company").
4. Outcome/result line: what happened, quantified where possible ("secured dismissal," "closed in 45 days," "$1.2bn transaction value").

The practical build: most firms run this in their CRMCRMCustomer Relationship Management : logiciel et stratégie pour gérer et analyser les interactions clients tout au long de leur cycle de vie.Voir la définition complète → (customer relationship managementcustomer relationship managementCustomer Relationship Management : logiciel et stratégie pour gérer et analyser les interactions clients tout au long de leur cycle de vie.Voir la définition complète → system, e.g., Salesforce or Intapp) or a dedicated experience-management module, not a shared drive. The critical discipline is capture at matter close, not capture on RFP day. Firms that mandate a one-page "matter closure form" signed off by the billing partner within 30 days of matter completion have libraries that are actually usable; firms that rely on annual data calls (see the directories lesson in this module) end up with credentials that are 18 months stale by the time a pitch needs them.

A simple tagging schemaschemaUn schema est le plan formel qui définit comment les données sont structurées, nommées, typées et reliées entre elles au sein d'une base de données, d'un fichier ou d'un message.Voir la définition complète → in practice

Matter ID: 2025-EU-0417
Practice: Antitrust / Competition
Sector: TMT (Technology, Media, Telecom)
Jurisdiction: EU (European Commission), UK (CMA)
Value band: >€1bn
Role: Lead counsel, notifying party
Confidentiality: Nameable (client consented, deal announced)
Outcome: Unconditional clearance, Phase 1, 25 working days
Partner: [Name] | Associate: [Name]

Query this by sector + jurisdiction + outcome, and a associate can pull twelve relevant matters in the time it used to take to find one.

The modular pitch template

Once credentials are tagged, the pitch itself should be built from fixed modules, not written fresh:

• Firm overview module: one paragraph, one boilerplate slide, updated quarterly (headcount, offices, key rankings from Chambers/Legal 500).
• Team slide module: partner bios, pre-approved short and long versions, kept in the CRMCRMCustomer Relationship Management : logiciel et stratégie pour gérer et analyser les interactions clients tout au long de leur cycle de vie.Voir la définition complète →, not recreated per pitch.
• Relevant experience module: pulled directly from the credentials library query, not rewritten.
• Fee approach module: templated language on billing structures (hourly, fixed fee, capped fee, alternative fee arrangements or AFAs), with room to customize the number, not the framework.
• Differentiator module: the two or three sentences of "why us" that senior BD and the practice group leader agree on in advance, so nobody is improvising this under deadline.

The RFP response, then, is an assembly task: query the library, drop in the pre-cleared team bios, adjust the differentiator paragraph to the specific client ask, and route for partner approval. What used to take four days of drafting becomes a half-day assembly plus partner review.

The 48-hour workflow, concretely

1. Hour 0-2: BD lead reads the RFP, extracts the actual scoring criteria (RFPs almost always publish a weighting, e.g., "experience 40%, team 30%, fees 30%"), and queries the credentials library against those criteria.
2. Hour 2-8: Draft assembled from modules; gaps flagged (if the library has no matter matching "experience in Brazil," someone needs to ask around, fast).
3. Hour 8-24: Partner review, client-specific tailoring, general counsel-style "so what" added to each credential (why does this matter to *this* client).
4. Hour 24-40: Design/formatting pass, conflicts check (has the firm ever acted against this prospective client, or does taking this client create a conflict with an existing one), pricing sign-off.
5. Hour 40-48: Final partner sign-off, submission.

Note where the time actually goes: not writing, reviewing and tailoring. That's the point of the system.

Governance: who can say yes, fast

Speed dies without pre-agreed authority. Two governance rules make the 48-hour turnaround possible:

• Pre-cleared credential library means BD doesn't need fresh sign-off on matter language for entries already flagged "nameable." Only new or borderline entries go back to the partner.
• A standing pitch approval chain (practice group leader, then a BD director, then, above a revenue threshold, a partner-in-charge of business development or the firm's Chief Marketing Officer) with a same-day SLA (service level agreement, an internal commitment on response time) during active pitches. Many firms lose RFPs not on content quality but because a partner sat on an email for three days.

Measuring whether the system works

Track two things beyond "did we win": cycle time (hours from RFP receipt to submission, trending down as the library matures) and credential reuse rate (percentage of matter descriptions pulled from the library versus written fresh under deadline). A library at, say, 70 percent reuse rate is doing its job; one still at 20 percent after a year means capture discipline at matter close isn't happening.

🎬 [VIDEO: "How to Write a Winning RFP Response" — youtube.com — search for RFP response strategy walkthroughs from B2B sales/proposal management channels; the discipline of scoring-criteria-first drafting applies directly to legal pitches]

Key Takeaways

• Build the credentials library at matter close, not at RFP time; a 30-day matter closure form beats an annual scramble.
• Tag every matter by practice, sector, jurisdiction, value band, role, and confidentiality status so it's queryable, not just searchable by keyword.
• Modularize the pitch itself (firm overview, team, experience, fees, differentiator) so BD assembles rather than drafts under deadline.
• Pre-clear partner sign-off on nameable credentials in advance; build a same-day approval SLA for active pitches, since governance delay, not writing time, is the usual bottleneck.
• Measure cycle time and credential reuse rate, not just win rate, to know whether the system itself is improving.