Key takeaways
- The real objection is usually financial timing, not technology. Investment hits this year's distribution, benefits arrive later.
- Never lead with the technology. Lead with a specific problem partners already complain about.
- A fixed price removes the objection that a partnership finds hardest to overcome: open-ended cost.
- Your sponsor needs authority, not enthusiasm. Those are different people in most firms.
The pattern is familiar to anyone who has tried. Someone in the firm does the work, builds a sensible case, presents it to the partnership, and receives a response that is neither approval nor refusal. Interesting, worth exploring, perhaps a small trial, let us come back to it next quarter. Six months later nothing has happened and nobody has said no.
This is not indecision. It is a governance structure doing exactly what it was designed to do, and it responds to a specific kind of proposal.
Name the money problem out loud
Here is what is actually happening in the room, and it is rarely said.
In a partnership, a spending decision is a decision to reduce this year's distributable profit. The money does not come from a corporate budget that exists somewhere abstract. It comes out of the pockets of the people voting, this year, in a way each of them can calculate during the meeting.
Meanwhile the benefit is described in terms of capacity, efficiency and positioning over two to three years. For a partner five years from retirement, that arithmetic is straightforward and unfavourable. They pay all of it and see a fraction of it. They will not say this, because it sounds self-interested, so instead they will raise a series of reasonable-sounding questions about risk, client confidentiality and whether the technology is mature.
Those questions cannot be answered, because they are not the objection.
What to do about it: make the number small enough that the calculation stops mattering. A fixed cost in the low thousands, stated plainly, does not require anyone to weigh their retirement horizon against the firm's five year positioning. Large open-ended programmes trigger the arithmetic. Small defined ones do not.
Lead with their complaint, not your solution
The second failure is presenting AI as a subject. Partners have heard about AI, have opinions about AI, and will happily spend forty minutes discussing AI in general while approving nothing.
What gets approved is a proposal about a problem they already complain about, which happens to have this solution. The difference is entirely in the framing:
- Not "we should adopt AI" but "our associates spend a day a week on document summarisation and we are turning away work".
- Not "AI improves efficiency" but "proposals take three days to turn around and we lost two pitches last quarter on timing".
- Not "competitors are investing" but "the client asked us in the panel review and we did not have an answer".
- Not "this is the future of professional services" but "we are paying for four separate personal subscriptions on expenses and nobody controls the client data in them".
Each of those is a problem with a cost, in the firm's own language, that a partner has personally experienced. The technology then arrives as the answer to something rather than as a topic in itself.
The four objections and what is underneath them
| What is said | What is meant | What answers it |
|---|---|---|
| The technology is not mature enough yet | I do not want to spend money this year | A small fixed cost, and a defined end date |
| Client confidentiality is too big a risk | I do not understand what happens to the data | The specific contractual position, in one paragraph, with the setting evidenced |
| Our work is too bespoke for this | You are implying my expertise is replaceable | Be explicit that it touches the drafting layer, not the judgement |
| Let us do a small pilot first | I would like this to go away politely | Accept, but with a defined scope, a date and a decision criterion attached |
The fourth row is the one to handle carefully, because it looks like progress. A pilot with no end date, no success criterion and no committed decision point is how proposals are declined without anyone having to decline them. If you accept a pilot, insist on three things in the same sentence: what it will test, when it ends, and what happens on that date.
The sentence that converts a pilot into a decision: we will run this with the corporate team for six weeks, and on the fifteenth of the month the partnership decides to extend it firm-wide or stop it. Without that, the pilot runs indefinitely and quietly becomes the answer.
Choose the sponsor for authority, not enthusiasm
Every firm has someone who is genuinely interested in this, reads about it, and has been experimenting. They are valuable and they are usually the wrong sponsor.
Enthusiasm gets a trial approved. What it cannot do is tell a senior fee earner that the firm now works this way, allocate someone's time to the rollout, or defend the decision when it is questioned six weeks in. That requires standing.
The right sponsor is the managing partner, the operating partner or whoever actually controls the firm's operational decisions. The enthusiast becomes the person who makes it work. Separating those two roles solves a problem most firms discover only after the rollout has already stalled.
The one page paper
Length is a signal. A twelve page proposal with appendices tells the partnership that this is complicated and needs proper consideration, which is a request to be deferred. One page tells them it is a straightforward operational decision, which is what you want it treated as.
Seven things, in this order:
- The problem, in the firm's own numbers. Hours, turnaround times, lost pitches, expense claims.
- What is proposed, in two sentences with no jargon.
- The cost, fixed and total, including licences for the first year.
- Who does the work, and confirmation that it is not partner time.
- What changes for fee earners, stated honestly including anything uncomfortable.
- The confidentiality position, in one paragraph.
- The decision requested and the date it needs to be made by.
Anything else goes in an appendix that exists so you can say it exists.
Answer the billing question before it is asked
In any time-based practice, someone will eventually ask what happens to realisation if the work takes less time, and a proposal that has not anticipated this looks unconsidered.
You do not need to solve it in the paper. You need to show you have seen it, and to name the options the firm can choose between: absorb the efficiency as capacity, move affected work to fixed fees, or reinvest the time. Proposing that the partnership decide this at the same meeting is usually a mistake, because it is a bigger conversation. Proposing that it be decided within the first quarter of the rollout is reasonable and shows judgement.
Frequently asked questions
Why does the partnership keep deferring the decision?
Usually because the spending comes out of this year's distributable profit while the benefit arrives over several years, and partners near retirement carry all the cost and little of the gain. Nobody says this because it sounds self-interested, so it emerges as unanswerable questions about maturity and risk. A small fixed cost removes the arithmetic.
How should the proposal be framed?
As the answer to a problem partners already complain about, not as a proposal about AI. Turnaround times, capacity, a question you failed to answer in a panel review, or four personal subscriptions on expenses with client data in them. Specific, costed, in the firm's own language.
Who should lead it?
Someone with operational authority, not the firm's technology enthusiast. Enthusiasm gets a pilot approved but cannot direct how a senior fee earner works. Pair a managing or operating partner as sponsor with the enthusiast as the person who makes it happen.
Should we agree to a small pilot?
Only with a scope, an end date and a decision criterion attached in the same sentence. A pilot without those is how a partnership declines something politely. State what it tests, when it finishes, and that the partnership decides to extend or stop on a named date.
Take a fixed number to the partnership
We produce the business case in your firm's own numbers, with a fixed cost, a defined end date and the confidentiality position written out, then run the implementation ourselves so it does not consume partner time. Live in 30 days or less.