Law Firm Demand / Foundational essay
The Law Firm Demand System
Where do cross-practice pursuits stall? A working framework for examining decision authority, commitments and the transitions between teams.
Direct answer
Short answer
A Law Firm Demand System is a working framework for connecting client need, relationships, firm relevance, mobilization and action so potential work does not depend solely on individual memory or rainmaking.
Imagine a global firm advising a multinational on a proposed acquisition. The relationship partner sees a reason to involve specialists in several offices. Business development assesses the opportunity, tests the fit with the client’s needs and assembles relevant credentials. Each practice leader agrees that the client matters.
The client asks for an initial view of how the team would work together. No one can yet give a coherent answer.
In this hypothetical situation, one office is waiting for scope, another is uncertain about staffing, and the relationship partner expects the practice leaders to settle both. Everyone has contributed something. The client still lacks a response it can evaluate.
The CMO and practice leaders could interpret this as a need for stronger collaboration. A more useful diagnosis would identify the decision no one has authority or responsibility to make.
The unit of analysis is the transition
The Law Firm Demand System is a working framework for examining how a firm recognizes a client need, assembles relevant capabilities and participates in the client’s decision to engage counsel.
Its proposed contribution is to examine the transitions between those activities. A firm can have excellent research, respected specialists and committed relationship partners while still failing to connect their work.
In the acquisition example, identifying the relevant offices is not the same as agreeing who will integrate their advice. Providing credentials does not establish availability. Expressions of support do not resolve who can commit the team to a response.
For the CMO shaping the pursuit process and the practice leaders committing the team, the shared decision is whether a recurring transition needs a defined owner, an escalation route or a different allocation of authority. That is more specific than asking partners to collaborate more often.
Ownership without authority may leave the gap intact
Suppose the relationship partner accepts responsibility but cannot obtain a staffing commitment from the relevant practices. Naming an owner has made the problem visible; it has not solved it.
The firm may need a practice leader to resolve availability, a pricing professional to test the proposed scope or a conflicts determination before the response can proceed. The relationship partner should not have to simulate all those functions to keep an opportunity moving.
Conversely, allowing a central team to make commitments without the relevant partners could create promises the firm cannot deliver. The question is which decisions belong locally and which require escalation, and how people know when that boundary has been reached.
A useful operating model makes those dependencies explicit. The CMO can help define qualification, coordination and escalation; practice leaders must agree how staffing commitments will be resolved. Technology and knowledge leaders can make the supporting information accessible with appropriate permissions. Those responsibilities should be agreed locally, rather than inferred from a title. More recorded activity can otherwise disguise the same unresolved choice.
When planning a rollout, one practitioner worried that asking BD to support the process could lead lawyers to hand over the entire task. The intended support function could then become a bottleneck.
Anticipating that risk means agreeing what BD will prepare, what the lawyer must decide and what happens when the next commitment is unresolved. Naming a coordinator leaves those boundaries unsettled unless the team also agrees where responsibility sits.
Nine stages organize the investigation
The framework follows a situation from recognition to engagement and learning. The stages are prompts for reconstructing decisions, not mandatory approval gates.
| Stage | The leadership question |
|---|---|
| Recognition | Who became aware of the client’s need? |
| Relevance | What established the fit with our capability? |
| Prioritization | Why did this deserve scarce partner attention? |
| Ownership | Who could decide or escalate the next step? |
| Mobilization | Were the people, context and commitments available? |
| Action | What did the client actually receive? |
| Client selection | Why did the client choose or reject the firm? |
| Matter | What scope and commitments were agreed? |
| Institutional learning | What should change in the firm’s response? |
The acquisition response might stall at mobilization even though relevance and ownership are clear. In another situation, the firm might mobilize a large team before establishing that the client wants help. Moving further through the sequence is not inherently better.
Keep the model smaller than the process it explains
A diagnostic framework can become counterproductive if every stage creates a form, meeting or approval. A narrow client request should not acquire the machinery of a major cross-border pursuit.
Use the stages to inspect selected situations and locate recurrent friction. Introduce a new control only when there is evidence of a problem it can address. For a complex pursuit, that could mean a named integrating partner and a clear way to resolve competing staffing demands. A routine introduction may need only an accepted next step.
David Teece’s dynamic-capabilities framework examines how firms sense opportunities, seize them and reconfigure resources. It provides background for distinguishing assets from the ability to use them. Our nine-stage application to legal client decisions remains a proposal to test, rather than an established finding from that research.
Use the review to change one recurring decision
Ask a small group of relationship partners, practice leaders and business-development colleagues to reconstruct comparable pursuits: some won, some lost and some deliberately declined. Include client explanations where available. Separate what was known at the time from hindsight.
Locate the first consequential unresolved decision. Was the issue authority, information, capacity, economics or an unsuitable opportunity? Establish whether the same problem appeared in more than one case before redesigning the process around it.
If repeated staffing disputes delay credible pursuits, leadership can test an escalation arrangement and review whether it resolves commitments sooner without weakening delivery. If the real problem is poor fit, faster escalation will not help.
The original acquisition example does not necessarily call for a new platform or a firmwide committee. It calls first for an answer to who can assemble a credible team and resolve the commitments it requires. The framework earns its place if it makes that answer clearer.
Related reading: What Is Law Firm Demand? · What Is Demand Conversion? · The Conversion Window
Evidence note: Anonymized practitioner observations are paraphrased from commercial discovery or implementation conversations with Postilize. They are self-reported accounts, concerns or proposed uses, as indicated—not a representative study or proof of outcomes. The opening scenario remains hypothetical. Postilize has a commercial interest in this subject.
Canonical research concepts