Hand us the AI question that keeps coming back. We answer it in writing.
Do the juniors get AI or not? Build or buy? What should the AI policy say? You hand us one question. We sharpen it, work it out from the legal side and the technical side, and come back with a decision you can defend.
Why the question keeps going back on the list.
It comes up in a partner meeting, everyone agrees it matters, and it goes back on the list. Answering it takes focused work and a view across law and technology. Nobody in the room has both the view and the time.
Meanwhile the decision gets made by default. The licence renews, the pricing stays as it was, and the associates use whatever they already use.
The kind of question a Strategy Deepdive answers
Examples from the questions legal teams bring us.
Do the juniors get AI?
Whether juniors learn the work first or learn it with AI changes how they are trained, how their work is reviewed and what their first years look like.
Buy, build or both
Which work belongs in the platform you already pay for, and which is worth building and owning yourself on frontier models.
What the AI policy says
What may go into which tool, who reviews what the model wrote, and what you tell a client who asks.
Pricing when drafting takes less time
How to price work when AI takes over much of the first draft, and what that changes in the client relationship.
Which vendors, and how to stay free to leave
Which legal AI vendors deserve a serious look, and how to keep your workflows and data portable if you move.
What AI use costs
What the tools cost per team and per matter, and who keeps an eye on it.
How it works
We sharpen the question
A first brief often holds two or three questions. Together with you we find the one that needs answering.
We choose the shape
Some questions need quiet research. Others start with workshops with your leadership to gather the angles.
We work out the legal and the technical side
So the answer holds up legally and can be built, bought or written into policy.
We test the thinking with you
Before it is final, your leadership hears it and pushes back.
We write it down and present it
A conclusion, a framework or a stated decision, with the reasoning, to whoever asked.
What you get
A written answer
In the form the question needs: a report, a decision framework or a stated decision.
The reasoning behind it
Written so the decision still stands when the next person asks why.
A presentation
To whoever asked, in the room, with time for their questions.
Frequently asked questions
Isn't this what we pay a strategy house for?
A strategy house will answer it too, and on some questions you should ask one. We take the questions where the legal work and the technology have to be understood together, and we know what it takes to build what we recommend.
Couldn't we answer it ourselves?
You have the people who know the organisation. What they lack is time free of client work and a place outside the debate. An answer from outside can be read on its merits by both sides of the room.
Won't our platform vendor tell us what to do?
On questions about their product, ask them. Whether to build alongside it, how to price, or what the policy should say are questions about your organisation, not their product.
What happens after the answer?
If the answer is to build something, Discovery scopes it. If it ends in a policy or a vision, it stays with you, and we step back.
More in this track
Send us the question in a sentence.
A paragraph is fine too. If it needs no engagement at all, or the question really covers the whole organisation and an AI Transformation Scan fits better, you hear that first.