Clio Grow vs Lawmatics

A firm at the end of this shortlist is asking two questions: what will this cost, and where does the matter end up once intake is finished. Neither vendor's published material answers the first. Both answer the second, and they answer it differently. That difference, rather than any feature list, is what this page is about.

20 claim records·8 sections·every figure attributed to a dated capture·no first-party testing

What follows is built from each vendor's own pages, captured on dated snapshots, plus one practitioner discussion. It contains no independent test of either product, because none exists in this research. Where a vendor states a capability, the sentence says which vendor stated it and when it was captured. That is the whole method, and the closing section says plainly where it runs out.

The first question: what does an intake-capable configuration cost?

Neither vendor publishes the answer. They withhold it in different ways, and the difference is worth understanding because it changes what you have to do to get a number.

Clio publishes a floor, and the floor is not the intake price. Clio states that its plans start at 49 US dollars per user per month and that there are four plans to choose from, named Starter, Core, Signature and Elite. On the same pricing page, Clio states that Clio Grow, its client intake and CRM product, is included in the Elite and Elite Work plans and is available as a paid add-on for the Core and Signature plans. The add-on price is not published anywhere on that page. So the 49 dollars is real, and it is the price of a plan that does not include the intake product. All three statements were captured 2026-08-16, and each was found again word for word in a fresh capture of the same page taken on 2026-08-19.

There is a smaller oddity in those two sentences worth naming, because a buyer reading the page will hit it. The plan count and the plan names come from Clio's own FAQ, which lists four. The Grow packaging line names the plans that include Grow as Elite and Elite Work. Elite Work is not one of the four the FAQ lists, and it is not one of the four columns in the plan comparison table on the same page. This page does not know what Elite Work is or what it costs, and neither does the pricing page.

Lawmatics publishes no figure at all. Lawmatics states that it offers tailor-made pricing plans for law firms of all sizes and asks the visitor to supply information for a custom quote. No plan on that page carries a price. Captured 2026-08-16, and the same page was captured again on 2026-08-19 with an identical content hash, so nothing on it had changed. The same claim records that the page also references credit-based pricing for an AI lead-routing capability, so an eventual quote may combine a subscription with a usage component; neither is quantified on the page.

Where intake sits in each plan structure is also different, and it is not an inversion. Both products gate intake. They gate it differently, and describing them as opposites would be wrong in a way that matters to a buyer.

Lawmatics lists client intake, lead management, custom forms and e-signature in the included list of Essential, the lowest of its three named plans. Intake is not withheld from the entry plan. It is metered there: that plan caps automations at 10 against unlimited above it, contacts at 500 against 10,000, conflict checking at Basic against Advanced, and e-signatures at 50. Both captured 2026-08-19.

Clio's arrangement is the availability kind rather than the metered kind: Grow is included in two named plans and sold as a separately priced add-on for two others. A firm on Core or Signature does not get a smaller version of intake. It gets none until it buys the add-on, at a price the page does not state.

One further caution on the Lawmatics side, and it is the vendor's own footnote rather than our reading. On the plan cards both contact figures carry a numbered footnote marker, and the page defines three numbered footnotes beneath them; the marker on the contact figures is the first, which reads that additional contacts are sold separately. The entry plan's included list opens with the words "Everything in Basic", naming a fourth tier that the page does not show and for which nothing is captured here.

The bottom row is the finding. Two products, two different packaging philosophies, and the same outcome for a buyer trying to build a budget: you cannot get the number from either page. What differs is the work required to get it. On the Clio side you need one figure, the Grow add-on price, and you already know the plan price it sits on top of. On the Lawmatics side you need the whole quote, and the page tells you a qualification step comes first.

This page computes nothing from those numbers. There is no ratio between the two products' tiers here and there will not be one: the tiers are not comparable units, one product publishes no price to put in a denominator, and a derived figure spanning them would carry authority it has not earned.

What each plan table can and cannot be read for

The Lawmatics table is readable. The collector capture contains the same Compare Plans table twice. In the first rendering the non-text cells drop out and the surviving values lose their columns, which is the rendering this project read and drew its conclusions from. In the second, every cell is present in column order across the three plans shown, and the tick and dash cells survive as distinguishable image addresses rather than vanishing. The four metered measures quoted above were re-read directly from that second rendering before this page was published, and each carries one value per plan: automations 10, Unlimited, Unlimited; contacts 500, 10,000, 10,000; conflict checking Basic, Advanced, Advanced; e-signatures 50 followed by two tick cells.

What this page still does not do is transcribe the rest of that table. Those cells have not been compiled into claims in this research, and a figure without a claim does not ship here. That is a limit of the work done, not a limit of the capture, and it is a smaller and more honest statement than the one this page made before.

The Clio table is readable too, except in one block. Eighty of its rows carry a label and one value for each of the four plans, and can be read straight off. The reading breaks only in the Add-ons block at the end, where twelve rows carry a single value and the online client intake forms row carries three: No, "Contact your sales representative for pricing." and Included, against a header that names four plans.

Three values against four plan columns means one column has no value of its own, and the capture does not say which. Our research records that row as listing intake forms unavailable on the entry plan, requiring a sales conversation on the middle plans, and included on the highest. That reading is the only one consistent with the unambiguous prose above the table, and it is a reconciliation rather than a direct reading. The packaging statement is what carries the weight here, not the row.

The second question: where does the matter go?

This is where the two products actually diverge, and it is the half of the decision that a feature comparison tends to miss.

Lawmatics states that matter data syncs from Lawmatics, on lead conversion, to nine named case-management products made by other companies: 8am MyCase, CARET Legal, Clio, Filevine, LEAP, PracticePanther, Rocket Matter, SmartAdvocate and Smokeball. Captured 2026-08-19. That count is the set of destinations carrying the same lead-conversion sync sentence on the captured page; the same page names further destinations under different verbs or triggers, and those are deliberately excluded from the nine.

Destinations publish their own half too. Clio's app-directory page for Lawmatics states that once intake is completed in Lawmatics the matter can be synced automatically to Clio Manage, and that on conversion the matter syncs together with custom fields, documents, notes and relationships. Captured 2026-08-19. Clio is the one this research has compiled into a claim, and it is not the only one that does this: MyCase's own integrations page, captured 2026-08-16, describes the same crossing from the receiving end and names the same trigger, a lead converting to a client. An earlier version of this paragraph called Clio's publication unusual. It is not, and that sentence was written from what this project had compiled rather than from what it had captured, which is the exact failure the wiki exists to prevent.

Clio Grow's own documented handoff points inward. Clio states that once client intake is complete, documents, notes, events, intake form details and related contacts transfer into Clio Manage. Captured 2026-08-15. That is a crossing between two products made by the same company.

So the shape of the answer is this. Lawmatics publishes a crossing out to nine case systems made by other companies. Clio Grow publishes a crossing into Clio Manage. If your firm already runs one of those nine case systems and intends to keep it, the two products are not offering the same thing, and the published evidence says which one has documented the crossing you would need.

That is close to what the original poster in the one practitioner discussion we hold actually did, and the difference in wording is worth keeping. The firm ran Clio Manage, chose Lawmatics for intake, and said it would keep Clio Manage, which it twice calls its CRM rather than its case system. The vocabulary in this market does not settle, which is itself part of the problem a buyer faces. One firm, four years ago, is not a pattern. It is one worked instance of the decision this section describes.

Every statement in this section is a vendor describing an integration it is a party to. None of them establishes that a sync works, how completely it maps fields, what it costs, or whether any particular field survives the crossing. A listed integration is a statement of availability. The only way to find out what arrives is to move a real intake with your own fields and compare the resulting matter against the intake record, field by field.

What the one practitioner discussion actually contains

Our practitioner evidence for this comparison is a single discussion thread in a law firm forum, supplied as a browser transcript because the platform refuses the collection tooling used here. The platform displayed its age as four years at capture. It is among the oldest transcripts in this research, though not the oldest: another displays five years. Both products have changed since, and nothing in it describes current packaging or current pricing.

It holds six accounts, and the single most important thing about it is that only one of them had used both products. They are listed below rather than summarised, so that any statement made about the thread can be checked against it.

Read that table before you read any summary of this thread, including ours. Four of the six accounts contribute no claim to this research at all, and the five claims we do draw come from the other two: the original poster supplies three and Dingbatdingbat supplies two.

The one durable thing in it is the tradeoff Dingbatdingbat names, and it survives the staleness better than any product detail does, because it is about what the buying firm has to supply rather than about what either product shipped in a given year. A configurable automation product costs internal analyst time before it costs subscription money, and nothing on either vendor's captured pages mentions that cost. The original poster's three-month setup expectation and setup fee sit in the same territory, and no Lawmatics pricing page captured in this research mentions a setup fee of any kind. Another vendor's captured pricing page does list a one-time onboarding fee without pricing it, so an implementation charge is not unheard of in this category; it is simply not something Lawmatics publishes.

All five practitioner claims are recorded here as unverified hypotheses at low confidence. The accounts are pseudonymous, their descriptions of their own practices cannot be checked, and a community source can never establish prevalence, a benchmark, causality, or a product capability.

Conflict and duplicate search, described and left there

Both products say something in this territory and the two statements are not the same kind of statement, so they are reported separately and compared on nothing.

Clio states that firm-wide searches across Clio Manage and Clio Grow can find a conflict of interest or duplicate contacts. Captured 2026-08-15. Lawmatics does not describe a capability in the material captured here; what it publishes is a tier boundary, listing conflict checking as Basic on its entry plan and Advanced above it. Captured 2026-08-19. Nothing captured here defines what either word covers.

That is the whole of what the evidence supports. This page does not say which is better, does not say what either capability discharges, and states nothing about who at a firm may perform, approve or delegate any part of this step, or whether any of it may be automated. Those are questions for your own counsel, and no qualified reviewer has read this page.

The rest of what each vendor states about intake

These are the remaining capability statements in our research for these two products. Each is the vendor describing its own product on a dated capture, and none is tested here.

Clio states that intake forms can be shared on a website or sent by email or SMS, with submitted contact and matter information captured in Clio; that reusable intake form templates can be created in several named languages, including English, Spanish, French, German and Portuguese; and that its scheduling and payment products combine to book consultations and accept payment for them online. All three captured 2026-08-15.

Lawmatics states that its law firm software spans client intake through marketing automation, and presents an integration marketplace for legal technology applications. Both captured 2026-08-16. A marketplace listing establishes that a connection is offered and nothing about its depth.

Both products, and thirteen others, are set out with their captured evidence in the intake software directory, which also maps where intake breaks as a workflow rather than as a feature list.

What this page does not establish, and where its evidence falls short