When I was still running a full client load, I kept a sticky note on my monitor that read: “Free is a pricing strategy, not a gift.” It was a reminder I needed constantly, because every quarter I’d find another tool creeping into my overhead that I’d originally adopted because someone said it was free—or at least cheap.
Law firms bleed money in places that never show up cleanly on a P&L. Software is one of the worst offenders, and the damage is rarely in the line-item subscription cost. It’s in everything surrounding that cost.
The integration tax nobody budgets for
Here’s what typically happens. A firm adopts a per-seat case management platform. Then someone on the team realizes it doesn’t talk cleanly to the billing tool, so they bolt on a middleware connector. That connector needs occasional maintenance, and when the case management platform pushes a major update, the connector breaks—usually on a Tuesday afternoon when three deadlines are live.
Now you’re paying for:
- The platform subscription
- The connector subscription
- The hour (or four) of staff time troubleshooting the break
- The judgment call you made at 6 p.m. when you couldn’t pull an invoice
None of those last three appear on any vendor’s pricing page. I call it the integration tax, and in my experience it compounds quietly for years before anyone runs the real number.
The fix isn’t to avoid integrations entirely—that’s unrealistic at any firm size. The fix is to audit the friction cost of every connection in your stack before you sign, not after. Ask vendors specifically: what breaks when you push a major update, and who fixes it? If the answer is vague, price that vagueness in.
Switching costs are real, and they’re front-loaded
At some point every firm considers migrating off a platform it’s outgrown—or one that raised prices past the point of comfort. What people underestimate is that switching costs aren’t just the migration fee the new vendor quotes you.
They include:
Data export pain. Many platforms make importing easy and exporting hard. Before you commit to anything, test the export. Download your own data in a format you can actually use. If you can’t do that on the free trial, you’ve found your answer.
Retraining time. For a solo or small team, a week of reduced capacity while everyone learns new workflows is a manageable bruise. For a larger firm, that same week across multiple practice groups is a significant revenue event. Neither size gets to skip it—the math just changes.
Institutional memory loss. Your staff has workarounds, shortcuts, and tribal knowledge baked into the old system. Some of that is genuinely lost when you switch, not recovered. Budget for a discovery period post-migration that’s longer than you think you need.
I’ve watched firms spend six months researching a switch and then rush the actual transition in three weeks because a contract renewal was looming. That’s backwards. Negotiate the renewal timing or pay the overlap cost—it’s almost always cheaper than a rushed migration.
The “free” tier economics
Free tiers exist for one reason: to get your data and your habits inside a platform before the pricing conversation happens. That’s not cynical, it’s just business, and there’s nothing wrong with it—as long as you’re clear-eyed about it.
The pattern I see repeatedly: a firm adopts a free tier of a document tool or a client intake form builder. Usage grows organically. Staff starts depending on it. Then the vendor restructures its pricing, the features you actually use move behind a paywall, and you’re now negotiating from a position of dependency rather than choice.
The operational discipline here is straightforward: treat every free tool as if it costs what the paid tier costs, and decide whether you’d pay that. If you wouldn’t, don’t build workflows around it. Use it for something disposable, or don’t use it at all.
What an honest stack audit looks like
Once or twice a year, pull every recurring software charge—credit card statements are often more complete than budgets—and map each tool to three things:
- What does it actually do in our workflow?
- What breaks if it goes away tomorrow?
- What is the real cost, including staff time spent on it?
You’ll almost always find at least one tool that’s redundant with another, one that’s load-bearing in ways no one documented, and one that’s free but shouldn’t be trusted with anything important.
That exercise takes an afternoon. The savings, in time and money, tend to compound for years.
Q: How do I get my team to flag integration problems before they become emergencies? A: Build a lightweight log—even a shared notes document—where anyone can flag “this broke or slowed me down today.” Review it monthly. Patterns surface fast, and you’ll catch compounding friction before it becomes a crisis.
Q: Is it worth paying for a premium tier just to ensure better data portability? A: Often yes. Data portability is insurance. The premium tier cost is known and fixed; the cost of a forced migration from a platform that makes export difficult is neither.
Q: How should a growing firm think about standardizing its stack as it adds attorneys? A: Standardize around the workflows that touch every matter—intake, billing, file storage—and leave more flexibility at the edges. Trying to unify every tool at once as you grow creates the exact training and migration pain you’re trying to avoid. Pick the core, lock it in, then expand deliberately.