Frequently Asked Questions About Moving to Matter-Centric Practice

I get versions of these questions on nearly every intro call, and the honest answers are more useful written down once than repeated one conversation at a time. These are the real questions, not the flattering ones a marketing FAQ would invent.

What does "matter-centric" actually mean, in plain terms

It means the matter, not the client, the document, or the task, is the container everything else attaches to. If someone asks where a matter stands, the answer exists as a fact you can look at directly, not a reconstruction performed from memory and three phone calls. Most practices are organized around something else by accident, a solo lawyer's inbox, a firm's document folders, and matter-centric practice is the deliberate correction of that accident.

Is this just rebranded case management software

No, and this is worth being precise about. Case management software is a category of tool. Matter-centric practice is an operating model, six named primitives, matter, actions, time, team, evidence, research, that a system either implements structurally or does not. Most case management software stores what a person already decided. A matter-centric system participates in the deciding, because the primitives were named deliberately rather than left as whatever fields a vendor happened to ship.

How long does it take to actually move a practice over

For one matter type, structured properly, thirty days is realistic if you follow a disciplined sequence: naming the process on paper first, building the spine, migrating live matters, closing the gaps you find. Covering an entire multi-practice-area firm takes longer, and I would tell any caller trying to do it all at once to slow down, because breadth before depth is the most reliable way to stall a build before it ships.

Do I have to replace my existing case management software

Not necessarily, and not always immediately. Some practices run a matter-centric layer alongside an existing system during a transition, especially where the existing system has real integrations, e-filing, accounting, that would be expensive to rebuild on day one. What has to happen eventually is that the matter-centric structure becomes where the truth lives, even if the old system keeps running in parallel for a while. A structure nobody trusts as the source of truth is not actually running the practice, regardless of what software it lives in.

Will this actually save money, or just feel more organized

Both, but the savings are specific rather than vague. Duration data, once you have it, lets you price fixed fees with confidence instead of fear, which is a direct revenue effect, not just a feeling of tidiness. Reduced intake friction and fewer missed deadlines are real financial effects too, not soft ones. "Feels more organized" is a real benefit and also the wrong thing to sell it on, because a practice that only feels more organized without a measurable change underneath has not actually moved yet.

What happens to my staff's jobs

The honest answer is that assembly work, the repeatable, low-judgment steps, gets easier to delegate, including to AI, once it is named clearly enough to delegate at all. Judgment work does not go anywhere, because judgment is the thing matter-centric structure is built to protect time for, not replace. In practice this usually means staff spend less time on data entry and status reconstruction and more time on the parts of the job that actually required a trained person, not fewer people employed doing meaningfully different work.

Can a solo practitioner do this, or is it only for firms

Solo practitioners are often the fastest movers, because there is exactly one person who has to agree the new structure is correct, and that person is you. The naming step is genuinely faster for a solo practice, and the whole sequence, name, systematize, automate, tends to compress from months to weeks when there is no partnership vote required at every stage.

Is AI required to do any of this

No. The plain structural pipeline, the six primitives named and organized, works and pays for itself before a single AI feature enters the picture. AI is what you add once the structure exists to grip it. I always build the structural version first for exactly this reason: a system that only works because AI is doing the organizing underneath it is a demo with a dependency, not a system.

What if my practice is too unusual for this to apply

I hear this more from practice areas with genuinely unusual procedural mechanics, not from practices that are simply reluctant to change. In nine years and roughly 200 systems across a wide range of practice areas, the six primitives have held up as a description of the underlying structure every time, even where the specific actions, deadlines and evidence types looked nothing alike from one practice area to the next. The primitives are the constant. The content poured into them is what varies.

Where do I actually start

On paper, naming your own process, before opening any software at all. If you want the structured version of that naming exercise rather than a blank page, MatterOS is built directly on this doctrine, agents running the first pass on intake, drafting and analysis, with you supervising every step, and the seven-day trial is the fastest way to see it running against a real matter rather than a demo.