
All rights reserved, Habeas 2026
See our Privacy Policy
See our Privacy Policy

The in-house counsel role has always been a function of compression. One lawyer, sometimes two or three, holding the legal weight of an entire business. The work is broad rather than deep, the calendar is reactive rather than considered, and the tools available to in-house teams have historically been built for the opposite shape of practice, which is to say built for law firms where the economics reward depth and specialisation rather than coverage.
This is what makes the legal AI conversation different in-house, and it is also why most of the public discussion about legal AI misses the in-house case almost entirely. A partner at a BigLaw firm is asking how AI changes the leverage model that turns junior hours into partner profit, where a general counsel is asking something quite different: how does AI extend the bandwidth, productivity and day-to-day capacity of a team that has limited leverage to begin with, and that has been operating at the limit of its capacity for a long time.
The case for in-house AI adoption is about doing the work that a small team cannot realistically get to at all, which in most companies is a much larger category than the work actually being done. The contract review that gets a rubber stamp because there is no time for proper analysis, the policy update that lapses under the radar because nobody can dedicate the hours: these are the matters that AI efficiency benefits the most. The benefit, properly understood, rather than being a reduction in the in-house workload, which tends to be set by the size of the business rather than the size of the legal team, is instead an expansion in what the in-house team is actually able to cover with the resources it already has.
When coverage expands, the in-house function changes character. It stops being a bottleneck the business routes around and becomes something the business can rely on earlier in a decision, before a contract is signed rather than after a dispute emerges. The supplier agreement nobody had time to read closely, the privacy notice that no longer matched the product, the employment policy that drifted out of step with current law: these are the matters where small problems compound quietly into large ones. Closing that gap is a risk-posture argument as much as a productivity one, and it is the version in-house leaders should be putting to their boards.
The procurement decision in-house also looks meaningfully different from the law-firm decision, which is something legal AI vendors have been slow to internalise. Law firms buy legal AI to drive margin, which means feature comparisons and demonstrable ROI tend to dominate the evaluation process. In-house teams buy legal AI to manage risk and capacity, which puts data governance at the centre of every conversation.
The Law Society of the Australian Capital Territory has reminded practitioners that they must not input confidential, sensitive, or privileged information into public Gen AI tools, because these platforms may store or use submitted data in ways that compromise client confidentiality, and that guidance is not abstract for an in-house team whose entire workflow runs on confidential commercial information. For in-house, the security and data residency story is the threshold criterion that decides whether a tool can be used at all, and only after that threshold is met does the conversation turn to anything else.
A law firm that adopts the wrong tool has made a margin mistake it can correct at the next renewal. An in-house team that adopts the wrong tool has potentially exposed the commercial information of the entire business, and renewal cycles do not fix that. This is why in-house evaluations move slower, ask harder questions, and treat vendor assurances with a scepticism that law-firm buyers often do not need to apply.
The questions in-house teams should be asking when they evaluate legal AI tools follow directly from this:
A good vendor will have answers ready, because the same questions were asked internally long before any customer thought to ask them.
These are the questions Habeas was built to answer, and they are the questions we think every in-house team should be putting to every vendor that comes through the door. Habeas is an Australian-native legal AI platform, grounded on a curated corpus of Australian primary sources, built so that the security and data governance story holds up to the scrutiny an in-house team is right to apply. In-house counsel use it for strategy, research, analysis and drafting work daily.
If you are in-house and looking for tools that genuinely empower your everyday work rather than tools designed for a different shape of practice, it might be time to book a demo or start a 14-day free trial.
