The demo always looks easy. A salesperson clicks through a clean dashboard, generates a polished document in seconds and says you'll be up and running in a week. Then the account opens, and the real work starts: settings pages, template editors, custom fields, field codes, workflow rules and a help center with hundreds of articles. Somebody at the firm has to turn a general-purpose product into something that fits the way you practice. Usually that somebody is an attorney.
I've been on both sides of this. I ran a growing firm that lived inside packaged software every day, and I've since spent a lot of hours building and debugging templates inside commercial legal software as an engineer. Here's why the setup is so painful, and what a custom system does differently.
"Out of the box" means "built for nobody in particular"
A packaged product has to work for a solo immigration practice, a 40-lawyer personal injury firm and everyone in between. To do that, it ships as a toolkit: generic matter types, generic stages, generic fields and a template system flexible enough to do almost anything. That flexibility is real, but it comes at a price. The product doesn't do your work. It gives you parts to build your work out of.
So "setup" really means design: deciding how your matters should be structured, which fields you need, what each stage means and how documents should be assembled. That's a software design job, and it lands on people who were hired to practice law or run an office.
Where the hours go
Rebuilding every template
Your firm already has documents that work: engagement letters, pleadings, financial forms, settlement agreements. To automate them, each one has to be rebuilt inside the product's template editor. Every name, date and amount becomes a field code, and every "if there are children" or "if the client is the respondent" becomes a conditional block. A single complex document can take a full day to convert and test.
Learning a programming language that isn't called one
Template syntax is code. It has variables, conditions, loops for repeating items such as children or debts, and rules about formatting dates and numbers. It also has bugs. A misplaced bracket, a field nested inside a condition the engine doesn't handle, or a list that formats differently in one place can quietly produce a document with blanks where facts should be. The product gives attorneys the responsibility of a developer without a developer's tools.
Mapping fields that almost fit
The product's built-in fields never quite match your intake. You add custom fields, then discover they don't appear in the client portal, can't be used in a workflow rule, or don't carry into the template you need them in. Each workaround is another hour, and another thing only one person at the firm understands.
Configuring workflows by hand
Task lists, reminders and stage changes are set up rule by rule in settings screens. Getting them right means testing them on real matters and fixing what fires at the wrong time.
Waiting on support
When something doesn't work, you file a ticket, explain the problem, send screenshots and wait. Sometimes the answer is a fix. Sometimes it's a workaround. Sometimes it's that the feature works as designed, or that it's on the roadmap. Meanwhile, the firm is working around it.
What that setup really costs
Add it up for a typical firm: dozens of templates, a set of custom fields, a few workflows and the inevitable debugging. It's easily weeks of skilled time, and it usually comes from the people whose time is most expensive. Every hour an attorney spends nesting field codes is an hour not spent on clients. The subscription price is the smallest cost on the bill.
And setup is never finished. Forms change, the firm adds a practice area, a new paralegal needs a different view, the product ships an update that moves a setting. The firm keeps paying in time, indefinitely.
Why it's especially hard for attorneys
Lawyers are precise, detail-oriented and good at rules, which is exactly why they end up owning this work. But the skills that make someone good at drafting don't make template engines less finicky. The tools give little feedback when something breaks, test cases have to be built by hand, and there's no one to review the logic. Attorneys end up carrying the risk of a document that silently left out a fact, inside a tool they never wanted to learn.
What a custom system does differently
- Someone else does the setup. I convert your templates, build your fields and wire up your workflow. The firm reviews the results instead of building them.
- It starts from your work, not a toolkit. Intake questions, matter stages, documents and deadlines are designed around your practice from the start, so there's nothing to bend into shape.
- Documents are tested like software. Every template is generated against sample matters, including the unusual ones, before anyone relies on it. In the Florida family law platform, 50 court forms are generated from one intake and previewed on screen, with blank fields highlighted.
- One set of facts feeds everything. The same answers fill the forms, the deadlines, the client portal and the reports, so there's no field mapping to maintain.
- Changes are a request, not a project. When something needs to change, you describe it in plain English. With Claude built in, many changes can be drafted as a reviewed update the same day.
When packaged software is still the right answer
If your practice is simple, your documents are few and someone at the firm enjoys configuring software, a packaged product can work well. Custom pays off when setup and workarounds are eating real time, when documents are complex, or when the firm is growing and the cracks are starting to show. I wrote more about that decision in custom vs. off-the-shelf case management software.
Tired of being your firm's unpaid software administrator? Book an intro call and bring the template that gives you the most trouble.