Clio Duo is Clio's built-in AI assistant for UK and international law firms. It runs on top of large language models and operates on data already inside Clio Manage. The main capabilities are matter and conversation summarisation, first-draft document generation from templates, time entry suggestions based on activity, and inline writing assistance for client emails and file notes. It does not integrate with anything outside Clio's data model and is priced as an add-on to the core Clio subscription.

How much does Clio Duo cost in the UK?

Clio Duo in the UK is priced as an add-on to Clio Manage. Typical 2026 pricing is around £30-£60 per user per month for the Duo add-on, on top of Clio Manage seats which run roughly £55-£120 per user per month depending on tier. An 8-fee-earner firm on Clio Manage plus Duo is therefore looking at roughly £680-£1,440 per month all in for Clio, before other tools. Pricing varies by contract and region, always get a current quote.

What can Clio Duo not do?

The important gaps for small UK law firms: it does not integrate with AML providers like Smartsearch or Veriphy, it does not pull data from Companies House or Land Registry, it does not handle disbursement matching from supplier emails, it does not run cross-system workflows that touch your finance or billing stack, and it does not support specialised precedent libraries beyond Clio's built-in templates. Clio Duo operates on Clio's data boundary by design.

Is Clio Duo worth it for a small UK law firm?

Yes if your painful work happens inside Clio. File note drafting, matter summarisation, first-draft documents from Clio templates, inline writing help, time entry suggestions. The product is well-executed for those. No if your painful work is the cross-system admin: AML-heavy onboarding, disbursement tracking from supplier emails, court date management that touches external systems, specialised precedent drafting that needs custom library access. For those, you need either separate tools or a custom build.

Can a custom build replace Clio Duo?

Mostly yes for the data and workflow pieces, but the inline writing assistance inside the Clio UI is awkward to replicate and rarely worth replacing. Custom code can read and write to Clio over its REST API, can call Claude or GPT for drafting and summarisation, and can integrate with anything outside Clio. The pieces that make Clio Duo pleasant (the in-app buttons, the inline draft-as-you-type) require building inside Clio's UI and that isn't where most custom builds spend their budget. Most custom builds I do for UK law firms keep Clio Duo for in-Clio work and add custom for cross-system work.

When does a custom build pay back vs Clio Duo?

When a single workflow outside Clio's reach is costing the firm meaningful fee-earner hours. If your admin spends 5 hours a week chasing AML documents and matching disbursements across supplier emails, that's £150-£300 a week of cost that Clio Duo doesn't touch. A £15,000-£20,000 custom workflow that automates the work pays back in roughly 15-24 months on hours saved, and continues paying back at zero marginal cost as the firm grows. Multiple cross-system bottlenecks shorten the payback further.

Clio Duo vs custom build for UK law firms in 2026

Clio has been your practice management system for two years. You turned on Clio Duo when it launched and it genuinely helped. Matter summaries are quicker. First-draft documents come out cleaner. Time entries are less of a Friday-afternoon chore. You'd recommend it.

Then you look at the partner's time sheet at month-end and notice the same admin bleed you had before. AML refreshes still taking two weeks to close out. Disbursement matching still handled by your ops manager reading supplier emails one at a time. Court-date follow-ups still living in a partner's head. Clio Duo doesn't touch any of that.

That's the question this post answers. Where Clio Duo's line actually sits, and when a small UK law firm needs to add a custom layer alongside it. I'm Robin, I run Laires Labs, a solo AI engineering studio in London. Most of the law firm builds I do touch Clio, Actionstep, LEAP, or DPS at the practice management layer.

The short answer

Clio Duo is good at matter and conversation summarisation, first-draft document generation from Clio templates, time entry suggestions, and inline writing assistance inside the Clio UI. It is limited by design to data inside Clio. The highest-cost workflows in most small UK law firms (AML-heavy client onboarding, disbursement matching, court-date management, specialist precedent drafting) touch data outside Clio or require custom logic Clio doesn't expose. For those, a custom build that runs alongside Clio is usually the right answer. Most firms I work with keep Clio Duo for what it does well and add a custom layer for the rest.

What Clio Duo actually does well

The features that earn their keep in an 8-20 fee-earner UK firm:

Matter and conversation summarisation. Long email threads, attached documents, and scattered matter notes can be summarised on demand. Useful for picking up a matter you haven't touched in three months, or briefing a colleague taking over cover.

First-draft document generation from Clio templates. Clio Duo can fill a template with LLM-inferred content rather than straight merge variables. An engagement letter, a simple demand letter, a standard NDA can come out as a review-ready first draft rather than a skeleton.

Time entry suggestions. Clio Duo looks at the activity on a matter (emails sent, documents opened, calls logged) and suggests draft time entries in six-minute increments. For firms that chronically under-capture time at week-end, this is real revenue recovery.

Inline writing assistance. Drafting an email to a client or a file note, Clio Duo can suggest rewrites, tighten tone, or expand a bullet into a paragraph. The friction of writing drops materially for routine correspondence.

Matter search and natural-language query. Asking "what's the status of the Jones matter" or "who is the opposing solicitor on the Patel case" returns structured answers from the Clio database. Quality scales with how cleanly the firm runs Clio.

These are real features and Clio has executed them well. The use case is "make working inside Clio more efficient". Which is also where the product stops.

Legora legal AI homepage, an enterprise legal AI alternative to Clio Duo for UK law firms evaluating build vs buy.

Where Clio Duo stops

Clio Duo operates on data inside Clio. The workflows it doesn't touch:

AML and client onboarding. UK law firms are supervised under the Money Laundering Regulations. Every new client needs MLR checks, often via a specialist provider (Smartsearch, Veriphy, AMLCC, Credas). Clio Duo doesn't integrate with any of them. The onboarding chase (ID collection, refresh prompts, enhanced due diligence flags) happens outside Clio's data model.

Disbursement matching. Supplier emails arrive (search providers, experts, court fees). Your ops manager matches each to the right matter and posts to the Clio ledger. Clio Duo can help draft messages but cannot read external email outside Clio's own activity feed and cannot parse supplier invoices automatically.

External data sources. Companies House, Land Registry, HMRC, Office of the Public Guardian. Any workflow that depends on these is outside Clio Duo's reach.

Court-date management across external systems. If your firm uses a specialist court diary, a paralegal's tracking spreadsheet, or email-based court updates from chambers, Clio Duo doesn't see any of it.

Specialised precedent libraries. Clio has template support and Duo can draft from those templates. If your firm maintains a precedent library outside Clio (in a document management system, a Sharepoint folder, or a specialist tool like Contract Express or a firm-specific precedent store), Duo cannot read from it.

Cross-system dashboards. Partner reporting that pulls utilisation from Clio, billing from your accounting tool, and matter status from a practice group tracker requires reaching all three systems. Clio Duo sees only Clio.

Scheduled batch jobs. Monthly WIP analysis, quarterly matter-ageing reviews, weekly capacity checks. Clio Duo has no scheduler and cannot run jobs that produce outputs outside Clio.

None of this is a criticism. It's a vendor scoping its product. The marketing language around AI for law firms tends to leave buyers thinking Clio Duo covers broader ground than it does.

Five highest-ROI law firm automations: how Clio Duo fares

From my UK law firm buyer's guide, the workflows that pay back fastest. Here's how Clio Duo handles each.

1. Client intake and matter opening

Clio Duo: partial. Clio Grow handles intake forms and Clio Manage has matter templates. Clio Duo can draft the welcome email and suggest opening steps. AML integration, ID verification, engagement letter drafting with matter-specific paragraphs, and automatic cross-system setup on signature are not in Clio Duo's scope.

Custom build needed for: AML provider integration, LLM-drafted engagement letters with scope-specific paragraphs, DocuSign flow, automatic client and counterparty record population.

2. File note generation from calls

Clio Duo: partial-to-strong. If the call transcript is already in Clio (via a supported integration), Duo can summarise it into a file note. Raw audio from external sources (a softphone, voice memo app, Otter or Fathom recording) needs either a direct Clio integration or a custom bridge.

Custom build needed for: transcription services, LLM summarisation tuned to the firm's house style, Clio activity write-back, supervising-solicitor review queue.

3. Time capture from calendar and email

Clio Duo: strong for Clio-visible activity. Duo can suggest time entries based on activity it already sees in Clio. Weaker for time spent in external systems (court portals, specialist tools, email outside the Clio integration).

Custom build needed for: extending time capture to activity outside Clio's view (specialist external systems, non-integrated email clients, non-Clio document platforms).

4. Precedent and first-draft document generation

Clio Duo: strong for standard Clio templates, limited for specialised precedents.

Custom build needed for: firms with specialised precedent libraries (contract-heavy transactional firms, private client specialists, litigation practices with specialised pleading banks) where the precedent library lives outside Clio.

5. Disbursement matching

Clio Duo: none. Supplier emails and PDF invoices are not visible to Duo.

Custom build needed for: email parsing, matter reference extraction, Clio ledger write-back, exception review queue.

The pattern: Clio Duo covers workflow 4 well for standard matters, covers workflow 3 reasonably, partially covers workflow 2, does not help with workflows 1 or 5. Workflows 1 and 5 are typically the highest-cost cross-system burdens in small UK law firms.

When custom code is the right answer

Three signals that say a law firm has outgrown Clio Duo alone.

The painful work happens outside Clio. If your admin team, ops manager, or paralegals spend significant time in email parsing supplier invoices, in AML provider portals, on Companies House, or in spreadsheets tracking disbursements and deadlines, that time is invisible to Clio Duo and will stay that way.

You're hiring or considering hiring to handle workflow volume. If the next hire is a paralegal or admin for onboarding throughput or disbursement tracking, compare the full-year cost (£24,000-£40,000 in 2026 for a UK legal admin or junior paralegal) against a custom build that automates the same workflow.

You have a process specific to how your firm runs. Niche practice areas, specialised precedents, a particular compliance pack format, a custom client reporting cadence. Clio Duo is general-purpose by design and won't stretch to firm-specific logic. Custom code does.

How a Clio-plus-custom stack works in practice

The pattern I ship for UK law firm clients on Clio.

Clio stays as the system of record. Matters, contacts, documents, time, and trust ledger live in Clio. The custom layer reads from and writes to Clio over its REST API.

Clio Duo keeps doing what it does well. In-Clio drafting, summarisation, time entry suggestions, inline writing help. No replacement attempted.

The custom layer handles cross-system workflows. AML-heavy onboarding. Disbursement matching from supplier emails. External data-source integrations. Cross-system dashboards. Scheduled batch jobs. Specialised precedent drafting that reads from an external precedent store.

Outputs land in the right tool. Drafted documents and file notes go back to Clio as attachments and activities. Disbursement entries land on the right matter ledger. Reporting lives in Looker, Metabase, or a custom partner dashboard. The custom layer is a participant in the Clio workflow, not a replacement for it.

Most firm builds I ship on Clio are one or two workflows, total under £25,000. Larger firms commission more; the architecture is the same.

Cost over 2 years: Clio Duo alone vs Clio plus custom

For an 8-fee-earner UK law firm. Both paths keep Clio as the practice management system. The custom path adds a workflow layer for two workflows Clio Duo doesn't reach (AML-heavy onboarding, disbursement matching).

Clio Duo alone path

Clio Manage (8 fee earners): £85/seat/month × 8 × 24 = £16,320
Clio Duo add-on: £40/seat/month × 8 × 24 = £7,680
AML provider (Smartsearch): £150/month × 24 = £3,600
Call transcription (Otter Business or equivalent): £100/month × 24 = £2,400
LLM API costs (moderate, outside Clio Duo): £100/month × 24 = £2,400

2-year total: £32,400. The cross-system admin (AML chase, disbursement matching) continues to take ops or paralegal time. Estimate: 5-8 hours per week across the firm, roughly £15,000-£25,000 per year in fully-loaded staff cost depending on who absorbs it.

Clio plus custom path

Clio Manage (8 fee earners): £85/seat/month × 8 × 24 = £16,320 (same)
Clio Duo add-on: £40/seat/month × 8 × 24 = £7,680 (same; kept for what it does well)
AML provider (API direct): £150/month × 24 = £3,600 (same)
Call transcription: £100/month × 24 = £2,400 (same)
Render or AWS hosting for the custom layer: £40/month × 24 = £960
LLM API costs: £200/month × 24 = £4,800
Custom build: £18,000 one-off
Retained maintenance: £3,000-£6,000 across 2 years

Clio Duo alone versus Clio plus custom build 2-year cost comparison for an 8-fee-earner UK law firm.

2-year total: £56,760-£59,760. The custom path costs roughly £24,000-£27,000 more over 2 years. In return, the cross-system admin time (roughly £30,000-£50,000 of staff cost across 2 years) drops materially. Net position depends on whether the freed ops or paralegal time gets redeployed into billable work or into higher-value internal work. In most firms it does, and the custom path is positive across 2 years.

The argument for keeping Clio Duo inside the custom path: the inline writing assistance and time-entry suggestions are hard to replicate and cheap to keep. Pay the Duo fee for what it does well, build custom for what it doesn't reach.

When to skip the custom build

Three cases where Clio Duo alone is enough.

Firms under three fee earners. Custom economics don't work at this scale. Use Clio Duo, accept the cross-system friction, revisit when the firm grows.

Firms whose bottleneck really is drafting and summarisation. Some practices are genuinely bottlenecked on the document and communication side. If that's you, Clio Duo handles it and a custom build wouldn't help.

Firms mid-restructuring. Partner change, practice group merger, mid-systems-change. Settle the new shape of operations before committing custom engineering.

Book a call

If you're on Clio, Clio Duo is running, and you can tell that the painful workflows still aren't getting touched, that's the call to book. Twenty minutes, no pitch. Tell me the firm size, the two workflows your team complains about most, and how much of the admin burden sits outside Clio. I'll come back with a one-page write-up of what a custom layer alongside Clio would build, what it would cost, and which workflows I'd leave in Clio Duo's hands. Yours to keep whether you hire me or not.

Don't book if you're under three fee earners, if you're mid-restructuring, or if your painful work is genuinely all inside Clio already. Clio Duo alone is the right call in those cases.

Book a 20-minute call or read the full UK law firm buyer's guide if you're earlier in the decision.