Your Favorite Legal Tech Company Hates You
Vibes & Verdicts — Issue #3
THE VIBE
Your Favorite Legal Tech Company Hates You
I need to talk about something that’s been bothering me since I started researching the legal tech market: the pricing.
Not in a “things are a bit expensive” way. In a “this is genuinely predatory and everyone has just accepted it” way.
Here’s what a typical mid-size law firm’s tech stack looks like in 2026: iManage or NetDocuments for document management ($30–60/user/month). Clio or PracticePanther for case management ($39–89/user/month or more depending on the tier). Separate billing software. Separate trust accounting. Separate eDiscovery tools when litigation heats up. An email integration that sort of works. A client portal that nobody likes (seriously — it’s universal).
For a 25-lawyer firm with support staff, you’re looking at $8,000–$15,000 a month. For tools that don’t talk to each other. That require separate logins. That store your data in separate silos. That you can’t leave because the migration cost is astronomical and they know it.
The per-seat model is the original sin of legal tech. It doesn’t charge you for value, it charges you for headcount. Hire a new associate? That’ll be another $150/month across your stack. Bring on a paralegal? More money. A temp for a big case? Hope you like per-seat overages.
It’s a business model that punishes growth. And the vendors have figured out that the switching costs are so high — migrating a document management system with 100,000 files and years of metadata is a genuinely miserable experience — that they can raise prices and degrade service and you’ll stay anyway.
I don’t say this as a neutral observer. I’m building a competitor, so I’m obviously biased. But I’m also a practicing attorney who has watched firms I’ve worked with hemorrhage money on tools that haven’t meaningfully improved in a decade. The bias comes from the frustration, not the other way around.
Here’s what I think the market is missing:
One platform, flat fee. Documents, matters, billing, trust accounting, client portal, eDiscovery — all in one system. $299 to $1699 a month depending on firm size. Not per seat. Not per feature. The whole thing.
Data portability as a feature, not a hostage negotiation. You should be able to export your entire dataset at any time in standard formats. If I can’t keep you by being better, I don’t deserve to keep you at all.
Architecture that actually integrates. Not “integrations” where you pay extra to connect two products that should have been one product. Built-together, same-database, shares-the-same-permission-model integration. When you upload a document, it’s immediately searchable, automatically tied to a matter, and accessible to everyone who should see it — because it’s all one system.
Is this ambitious? Absolutely. Am I building it alone with AI tools and a budget that wouldn’t cover one enterprise sales rep’s quota? Also yes. But the infrastructure costs for building software in 2026 are a fraction of what they were five years ago, and that changes the math on what’s possible.
The legal tech incumbents aren’t bad companies run by bad people. They’re mature businesses optimizing for revenue extraction from a captured market. That’s rational. But it creates an opening for someone willing to build something better and charge less for it.
I’m not the only one who sees this. I’m just the one dumb enough to try.
THE VERDICT
Quick Takes
If your software vendor makes migration painful on purpose, that’s not a feature. I’ve talked to firms who’ve stayed on terrible platforms for years because the migration estimate was $50K+. That’s a hostage situation, not loyalty. Any product that can only keep customers by making it expensive to leave is telling you something about its value.
The “best of breed” argument is over. For years, the pitch was “use the best tool for each job and integrate them.” In practice, this means six tools, six logins, six billing cycles, and an IT person whose entire job is keeping the integrations from breaking. All-in-one wins when the “one” is good enough. And “good enough” keeps getting better.
Bookkeepers think in ledgers, not UIs. Something I learned preparing for a trust accounting demo: when I built documentation showing pretty screenshots of the interface, the firm’s bookkeeper didn’t care. She wanted to know how data flows between accounts. She wanted to see the reconciliation math. The lesson: know your audience. Not everyone evaluates software the same way.
THE CONFESSIONAL
I Priced Batesly Wrong Three Times
First attempt: $99/month flat. Too cheap. People literally told me they wouldn’t trust legal software that costs less than their Netflix subscription. Pricing communicates value, and I was communicating “side project.”
Second attempt: Per-seat pricing to match the market. This lasted about 48 hours before I realized I’d become the exact thing I was building against. Hypocrisy speed run.
Third attempt (current): Tiered flat-fee. $299 for small firms, $599 for mid-size, $999 for larger firms, $1699 for enterprise. Unlimited users at every tier. This feels right.. but I do plan to increase each tier after the Big Launch (early adopters get the lower prices locked-in for life). It’s affordable enough to be a no-brainer upgrade, expensive enough to be taken seriously, and the flat-fee model is a genuine differentiator in a market addicted to per-seat.
Pricing is strategy. It took me three tries to figure out mine. If you’re building something and you’re agonizing over pricing, just pick something, put it out there, and listen to what people tell you. The market will teach you faster than any spreadsheet model.
Thanks for reading.
I’m Rachel — a practicing attorney building legal tech through vibe coding. Every week I share what I’m learning, what’s working, and what I probably shouldn’t admit publicly.
Next week: “I Deployed to AWS Without Knowing What a Docker Container Is” — The honest walkthrough of getting a real app onto cloud infrastructure as a non-engineer.
Know someone building without a CS degree? Forward this. They’ll thank you… maybe?