Why the cheapest option in legal technology and legal services is almost never the best economic choice.
By Dan O’Day, CEO of ECFX
Nobody asks why a Porsche costs more than a Kia. Both are cars. Both will move you down the road. But one is engineered for sustained performance under stress. Sit in a 911 and close the door, and that dense, engineered thunk tells you everything. Turn the wheel and the car responds instantly, translating intention into motion without hesitation. The difference is not decoration. It is disciplined engineering. You do not need a spec sheet to understand the price. Your hands understand it.
The same need to invest in engineering is true of a commercial aircraft. In the world of mission-critical systems, quality announces itself through engineering and reliability. You may not see the redundancy built into the system. You may not witness the stress testing, the safety validation, or the layered controls. But when failure carries serious consequences, price and substance are linked by disciplined engineering. Of course, the more dependable system costs more. The evidence is in how it performs under pressure.
Enterprise software offers no such courtesy. You cannot run your fingers across a server architecture. You cannot hear the sound that a well-written codebase makes when it handles an edge case at two in the morning. The affordances that signal quality in software are invisible and buried in infrastructure decisions, monitoring systems, security frameworks, and the ten thousand small engineering choices that determine whether a platform works reliably or works most of the time, which in my industry is not the same thing at all.
I have spent more than thirty years building software, at companies large and small, and I now run ECFX, which makes what I believe is the best electronic court filing (ECF) notice processing platform available. It is also, I am regularly informed, the most expensive. I hear this on sales calls with some frequency, and I have come to welcome the conversation, because the answer to the question why does this cost more? is really an answer to a more important question: what does it take to build something you never have to worry about?
• • •
Let me explain what we do, because the stakes are less obvious than they might seem. When a case is active in any court or agency be it county, state, or federal email notices flow. Filing confirmations, scheduling orders, motions, rulings. These arrive electronically, often in volume, to email addresses monitored by paralegals or legal assistants whose job it is to sort, classify, and route them to the right attorneys and case team members. If a notice is missed, a deadline can be missed. If a deadline is missed, a default judgment can follow. If a default judgment is entered, someone is calling their malpractice carrier.
ECFX automates that process. We ingest court and agency email notifications, identify the relevant case and parties, and route the information to the correct people inside a firm or legal department. We integrate with docketing and case management systems. We handle the jurisdictional variations, the format changes courts introduce without warning, the edge cases that would quietly break a simpler system.
Described that way, it sounds straightforward. Something a talented developer could prototype in a few weeks. And that’s true - a prototype is not hard. In fact, I built the prototype for ECFX Notice in a few weeks without the help of AI! But the distance between a prototype that impresses in a conference room and a platform that law firms trust with their malpractice exposure is roughly the distance between a sketch of a bridge and a bridge you’d drive your family across. And that is for a single bridge to one provider of court notices. ECFX does this for thousands of different jurisdictions using over 300 different solutions providers, each one requiring a separate design specification to work correctly. I know how much investment it takes to design and build over 300 different bridges. We keep building more every day and will until we have every court and agency covered. Making that scale work seamlessly requires far more than code. It requires a deeply engineered platform that supports, monitors, and reinforces every connection behind the scenes. Building software has become less expensive. Operating software responsibly has not. Maintenance, resilience, data integrity, security, and uptime are where real complexity lives. Clients who have migrated from other systems understand this difference immediately. They’ve experienced what happens when integrations exist without infrastructure to support them.
That’s why I always welcome heavy involvement from IT teams during evaluations. They recognize the difference between software that simply works in a demo and a platform designed to work every day reliably, securely, and at scale.
• • •
Back to the Porsche for a moment. When Porsche prices a 911, the number reflects not just the materials in that particular car, but the engineering organization behind it—including the wind-tunnel testing, the decades of motorsport data, the metallurgists and the suspension engineers and the quality-control processes that ensure every car leaving Stuttgart performs the way the brand promises. You are not paying for a car. You are paying for the system that makes the car possible.
The same principle applies to what we build, even though you can’t sit in it and close the door. The price of ECFX’s software reflects the cost of redundant infrastructure, so that a server failure doesn’t mean a missed court notice. It reflects robust monitoring that catches anomalies before they reach a customer. It reflects security frameworks built to satisfy the most cautious general counsel, and compliance processes tested across dozens of jurisdictions. It reflects a support team staffed to respond when something unexpected happens, not within a business day, but in real time when it matters. And it reflects a continuous development cycle, because courts change their formats, firms expand into new jurisdictions, integrations multiply, and a serious platform has to keep pace with all of it.
You can reduce any of those inputs. Every one of them is a cost center that a more frugal operation might trim. But you cannot eliminate them without consequence, any more than Porsche could eliminate its wind tunnel and still produce the same car. If a product is meaningfully cheaper than the cost of building and operating it at a high standard, then something has been subtracted. The scope is narrower. The monitoring is lighter. The support model is thinner. The long-term development roadmap is shorter. That is not a criticism. It is arithmetic.
• • •
What I find interesting about this dynamic is that it applies with equal force to the profession our software serves. Lawyers face exactly the same conversation with their own clients, and the logic is identical.
When a partner at a top firm quotes a rate that makes a procurement department reach for their water glass, what is inside that number? Not just the partner’s time. The rate reflects what it took to build the institutional machinery that makes the partner effective: decades of accumulated expertise across thousands of matters. Institutional knowledge of specific judges, regulators, and opposing counsel. Internal quality-control processes including peer review, conflicts checks, compliance infrastructure that are maintained at enormous ongoing expense. Research platforms, litigation support technology, knowledge management systems that let an attorney locate the relevant precedent in minutes rather than days.
Think of it this way. A commercial aircraft costs what it costs partly because of the materials, but mostly because of the engineering. Decades of accumulated testing, redundancy planning, and safety validation that ensure it performs exactly as designed when it matters most. A seasoned litigator operates on the same principle. She has seen the fact pattern before. She knows which arguments tend to fail in front of which judges. She anticipates opposing counsel’s moves. She catches the issue buried in paragraph fourteen of a contract that a less experienced attorney reads right past. That accumulated judgment compresses uncertainty, shortens disputes, strengthens negotiating positions, and reduces the likelihood of the kind of catastrophic surprise that transforms a manageable legal problem into an existential one.
The client who selects counsel primarily on rate and who treats legal fees as a line item to minimize rather than a risk-management investment to optimize is making the same mistake as the legal department that selects technology primarily on subscription price. In both cases, the relevant question is not what the service costs. It is what it costs when it fails.
• • •
The false economy of cheapness persists because the savings are immediate and visible while the costs are deferred and probabilistic. Nobody writes a case study about the disaster that didn’t happen. But I have been in this industry long enough to see the pattern repeat. The firm that hires less experienced litigation counsel saves money on every invoice right up until someone misses a procedural deadline, overlooks a regulatory nuance, drafts ambiguous contractual language, or underestimates the exposure in a dispute. The cost of correcting those errors almost invariably exceeds the savings that produced them. Sometimes by orders of magnitude.
In software, the pattern is identical. The legal department that selects the cheaper notification platform saves money every month that is until a format change goes undetected, a notice is misrouted, a deadline is missed, and the cost of that single failure eclipses years of subscription savings. I have watched it happen. I do not enjoy watching it happen. We regularly get inquiries from law firms that have experienced these issues in other software. But it clarifies, in a way that no sales presentation ever could, what the price difference actually purchased. The old saying “buy cheap, buy twice” is as true in software as it is in anything that we rely on to work correctly.
You would not buy the cheapest parachute. You would not hire the cheapest surgeon. When I put it that way, people nod. But somehow, when the product is software or legal counsel (i.e., those situations when you cannot see or touch the quality differential) the instinct to economize reasserts itself. The intangibility of the product makes the value invisible, and invisible value is the first thing a budget process eliminates.
• • •
I want to be clear about what I am not arguing. I am not arguing that expensive automatically equals good. There are overpriced law firms. There are overpriced software platforms. And there are situations where the cheaper option is perfectly adequate—where the stakes are low enough and the use case forgiving enough that the marginal reliability of a premium solution is not worth the premium price. It is critical that the value delivered exceeds the price of what is purchased. That is a commitment I have made to every client. They will always get more value from ECFX than what we charge for the product.
In the specific markets where ECFX operates where a missed court notification can trigger a malpractice claim and for our law firm clients providing service to their own clients the calculus is different. The cost of building something genuinely dependable is high. The cost of accumulating the expertise required to practice law at the highest level is high. And when a price reflects those real costs, it is not a warning sign. It is, more often, the clearest signal available that someone has done the honest math on what excellence actually requires.
At ECFX, I have made a deliberate choice about where to operate on the cost-reliability spectrum. I have chosen the end where my clients do not have to worry. That choice is expensive to sustain. It requires serious engineering, serious infrastructure, serious accountability, and a serious, ongoing commitment to continuous improvement. I am not willing to take the risks that would come with cutting those investments, because they are not my risks to take. They are my clients’ risks. And my clients’ clients’ risks.
A Porsche costs more because the engineering has to be right. A commercial aircraft costs more because the engineering has to be right. ECFX costs more because I decided that the reliability had to be right. In each case, you are not paying for the surface. You are paying for the system behind it. And in all three cases, the price is not the point. The point is what the price made possible.
Dan O’Day is the CEO of ECFX, which provides electronic court filing (ECF) notice processing for law firms and corporate legal departments. He has spent more than thirty years in software development.
Learn more at ecfx.com.