I get a version of the same call at least twice a month.
A firm owner walks me through their Lawmatics setup — the pipelines, the automations, the intake forms. They’ve clearly put time into it. Then, somewhere in the middle of the conversation, they say it: “We’ve had it for eight months and it still doesn’t feel like it’s working.”
I always ask the same follow-up: “What were you expecting it to do?”
The answer tells me everything. And in most cases, what I discover has nothing to do with Lawmatics.
The Tool Usually Isn’t the Problem
When a firm says Lawmatics “isn’t working,” the assumption is that something is broken — the software, the setup, the training. So they submit support tickets. They hire someone to reconfigure the automations. They sign up for another onboarding session.
What they rarely do is ask: what process was this supposed to automate in the first place?
Lawmatics does what you design it to do.
If leads are slipping through, it’s because the routing logic wasn’t designed to catch them. If follow-ups aren’t going out, it’s because the trigger conditions don’t match how your firm actually works.
In 80+ implementations, I have almost never seen Lawmatics malfunction. What I have seen — constantly — is firms configuring a tool on top of a process that was never defined.
What No Process Actually Looks Like
Most firms believe they have a process. And they do — in the sense that things get done. Someone handles it.
“Someone handles it” is not a process. It’s a workaround that looks like one.
Here’s what I find in most intake audits:
The stages in the pipeline don’t match the real steps in the firm’s workflow. Leads sit in stages that don’t mean anything, and staff aren’t sure what “Consultation Scheduled” is supposed to trigger versus “Consultation Complete.”
Follow-up sequences run on timing, not behavior. A lead gets an email three days after intake — not because three days is the right moment, but because that was the default. Nobody designed the logic around what the lead actually did or didn’t do.
None of this is a Lawmatics problem. It’s a process problem that Lawmatics faithfully executed.
How to Tell the Difference
Open your pipeline right now. Pick any stage. Ask yourself: what has to be true for a lead to be here?
If different people on your team would answer it differently — you have a process problem.
Now ask: what’s supposed to happen next, and who’s responsible?
If the answer is “it depends” or “whoever notices it” — you have a process problem.
Lawmatics can be configured around almost any process. But it cannot invent the process for you.
What Changes When You Start With the Process
When a firm comes to MFA, we don’t open Lawmatics on the first call.
We start by mapping what actually happens — not what’s supposed to happen, but what really happens. Who touches a lead first? What does “scheduled” mean versus “confirmed”? What happens when someone doesn’t respond?
Most firms have never mapped this explicitly. It lives in the head of the person who’s been there the longest.
Once we have the real process documented, we build the Lawmatics configuration around it. Every stage has a definition. Every automation has a trigger that matches a real decision point. Every follow-up is tied to behavior, not just timing.
That’s what “Lawmatics working” actually feels like. And it’s available to any firm willing to do the process work first.
Before You Touch Another Setting
If you’re frustrated with your Lawmatics setup, try this before changing anything:
Pull up your intake workflow — not in Lawmatics, on paper. Map every step from the moment a lead comes in to the moment they sign. Be honest about who does what and how they know it’s their turn.
If you can’t draw that map cleanly, you’ve found the problem.
Lawmatics didn’t fail you. You asked it to automate something that wasn’t ready to be automated yet.
The good news is that’s fixable.
That’s exactly what we do at Matter Flow Advisors. We come in, map the real process, identify where the gaps are, and build the Lawmatics configuration around how your firm actually works — not how it’s supposed to work in theory. If you’ve been living with a setup that frustrates you, I’d be glad to take a look together.
→ Book a consultation with MFA
Have you ever blamed the tool when the real issue turned out to be the process underneath? I’d be curious what you found.
