The capacity problem behind AI productivity tools

Consider a regional New Zealand law firm handling commercial, property and private client matters across several offices. The firm has strong demand, but profitability is under pressure because senior fee-earners are spending too much time on routine client-intake administration.

Lawyers and directors may be manually copying client details into templates, conducting initial conflict lookups, checking company information and assembling Anti-Money Laundering documentation. The work is important, but much of it is repetitive, structured and administrative rather than legal judgement.

Because the files still open and the work is completed, this capacity leak can remain hidden. Senior staff compensate through longer hours, while management sees the completed matter rather than the manual effort required to create it.

The temptation is to buy AI productivity tools immediately. However, automating an inconsistent or poorly understood workflow can make errors move faster. The safer starting point is to map the process, clarify responsibilities and identify which steps genuinely require professional judgement.

Define the legal client-intake workflow

The engagement begins by setting a clear boundary. In this example, the workflow starts when a prospective client requests a new legal matter and ends when a verified file is opened in the practice management system.

This keeps the review focused. Relevant context may include engagement-letter templates, intake emails, conflict-check procedures, identity-verification requirements, existing forms and the systems used by different offices.

New Zealand law firms must also consider their obligations under the Anti-Money Laundering and Countering Financing of Terrorism requirements for lawyers and conveyancers. Process improvement cannot remove required legal or compliance controls, but it can make the way those controls are completed more consistent and efficient.

Capture evidence before selecting AI productivity tools

Leanable uses structured, asynchronous stakeholder interviews to capture how the workflow operates in practice. A commercial partner, property lawyer, office administrator, compliance officer and practice manager can each explain their part of the process.

The interviews reveal where information arrives incomplete, which checks are duplicated, where partners use different intake methods and which tasks have shifted informally from administration to fee-earners.

This matters because software decisions should be based on evidence. The process-mapping guidance from business.govt.nz supports documenting the real sequence of work before attempting to improve or automate it.

Map the current state of legal onboarding

The Current State Process Map creates one view of the end-to-end workflow. It records how instructions arrive, what information is requested, who performs conflict checks, how identity evidence is handled, when engagement letters are drafted and who approves the file opening.

In the illustrative scenario, the analysis may reveal three different onboarding pathways based on the partner managing the matter. This variation leads to inconsistent information capture, repeated follow-up and unclear ownership.

The process map makes visible where senior legal staff are completing clerical tasks to prevent files from stalling. It also separates tasks requiring legal judgement from tasks that could be standardised, delegated or supported by automation.

Identify process waste and procedure gaps

The Pain Point Register groups issues by source, severity, frequency and commercial effect. Common findings may include incomplete intake emails, duplicate data entry, manual document assembly, repeated client chasing and fee-earners performing tasks that do not require legal expertise.

The SOP Gap Analysis compares the documented procedure with actual practice. It may show that the official process assigns identity checks to administrators, while bottlenecks have caused lawyers to take over these tasks informally.

This type of operational drift creates inconsistent service, unclear accountability and weakens the audit trail. It can also make it difficult to assess whether any proposed AI productivity tools will improve the process or simply add another layer of complexity.

Prioritise productivity improvements before automation

The Improvement Opportunity Register separates immediate process fixes from technology-dependent changes. Standardising the client information required at the start of the matter may deliver value before any AI tool is introduced.

Other improvements may include one digital intake form, clearer ownership for missing information, standard conflict-check handoffs and a defined point where legal review begins.

This evidence-based approach reflects good business analysis practice described by the International Institute of Business Analysis. The process, stakeholders and decision requirements are understood before a solution is selected.

Where AI productivity tools may add value

Once the future-state workflow is confirmed, the Automation Opportunity Assessment can identify bounded uses for AI productivity tools. Suitable opportunities may include extracting structured information from client emails, categorising matter types, pre-populating intake records and drafting first versions of engagement documents from approved templates.

AI may also help summarise missing information or route a matter to the correct administrative queue. However, conflict decisions, client acceptance, legal risk assessments and AML judgements should remain subject to human review and organisational policy.

Leanable treats AI output as draft support, not automatically correct or decision-ready. Four human approval gates allow the process owner to validate the current state, improvement opportunities, future-state design and automation assessment before delivery.

Seven deliverables for evaluating AI productivity tools

Leanable converts the stakeholder evidence and process analysis into seven professional deliverables that support operational decisions and responsible implementation.

Design a safer future-state workflow

The Future State Process Design standardises intake across offices. It may introduce a single digital capture step, one approved data structure and a clearer separation between administration, compliance review and legal judgement.

Routine information can be captured once and reused across approved systems and documents. Administrative staff can manage completeness and routing, while fee-earners focus on client acceptance, risk and legal work.

This design reduces variation before AI productivity tools are introduced. It also creates the controls needed to test whether the technology is producing reliable outputs.

Implement AI productivity tools in controlled stages

The Implementation Roadmap should begin with low-risk process changes. Standardising intake fields, ownership and templates can be completed before introducing automated extraction or drafting.

A later stage may pilot AI on a narrow matter type, with outputs reviewed by authorised staff. Accuracy, exception rates, time reduction and staff feedback can then be measured before wider rollout.

This approach protects live client work and avoids making a large technology commitment before the operational value is proven.

Potential capacity and commercial outcomes

Because this is an illustrative use case, actual results will depend on matter volumes, existing systems, compliance requirements, implementation quality and the tasks selected for automation. The intended outcome is to reduce repetitive administration while preserving legal and compliance oversight.

A better workflow may return several hours of weekly fee-earner capacity, reduce client chasing, improve consistency and create a clearer compliance audit trail. The commercial value comes from moving qualified staff back towards legal work rather than assuming that every administrative step should be automated.

A practical approach to AI productivity tools

AI productivity tools create the most value when they support a process that is already understood, standardised and governed. The first question should not be which tool to buy. It should be which workflow is consuming skilled time, why the waste exists and which decisions must remain human.

Leanable productises the analytical framework used by a senior business analyst and applies it through an eight-phase digital engagement. The AI does not replace the expertise. It operationalises it.