Who Supports the Software a Law Firm Runs On?

Three parties, and a firm gets hurt when nobody defines which one owns what. The software vendor owns the inside of the application, its features, its data, its bugs. Your IT partner owns everything the application depends on: servers or hosting, workstations, the network, backups, access, and performance. Your firm's power users own the workflow layer, how your people actually use the tools. The firms that never lose a filing day are the ones where those three lines are drawn in advance.

Ask this question after a document management outage on a filing day and the answers get expensive. A law firm’s practice runs on a stack of specialized software, practice management, document management, time and billing, e-filing tools, and the answer to “who supports it” is not one phone number. It is three parties with three distinct jobs, and the firms that avoid lost days are the ones that draw the lines before something breaks, not during.

Here is the layered model, the failure mode that burns firms, and what to ask each party when something goes wrong.

What are the three layers of legal software support?

Layer one: the software vendor owns the inside of the application. How the software behaves, what its error codes mean, how its data is structured, when a feature does not work as designed. You pay for this through your license or support agreement, and no IT company should pretend to replace it. A provider who claims deep expertise inside every legal application you run is telling you something, and it is not reassuring.

Layer two: your IT partner owns everything the application depends on. This is Braintek’s layer. It covers:

The servers or hosted environment where the applications and their databases live
The workstations attorneys and staff run the software on
The network connecting workstations to data, in the office and remotely
Performance, because “the software is slow” almost always traces to this layer
Backups of the matter files, databases, and documents behind the applications, actually tested, not assumed
Access and permissions, who can reach which matters, and offboarding when someone leaves
Coordinating updates, so a new version rolls out evenly instead of breaking half the office
The file shares, scanning, and printing that surround the applications, which legal work leans on heavily

Layer three: your firm’s power users own the workflow. Every firm has them: the paralegal who knows the document profiling conventions, the billing manager who knows how the time entries flow to invoices. Questions like “how do we set up this matter type” or “why did this bill calculate that way” are workflow questions. They belong to the people who know how your firm practices, sometimes with the vendor’s training resources behind them. An IT partner should know this layer exists and route questions to it, not guess at answers inside software they do not operate.

When each layer has an owner, most problems resolve at the first call. When they do not, you get the failure mode.

Why do the vendor and the IT company end up blaming each other?

Because most real problems can plausibly live in either layer, and neither party can see the other’s territory. The application freezes when opening documents. Is that the application, the server it queries, the network path, or the workstation? The vendor’s support desk checks their application and says it looks fine. The IT company reboots the workstation and says it looks fine. Both are telling the truth about their own layer, and the problem sits in the seam between them.

So the firm becomes the messenger. The office manager relays the vendor’s questions to the IT company, relays the IT company’s answers back, waits on hold twice per round trip, and personally project manages an outage while attorneys wait. Nobody is lying, nobody is accountable, and billable time drains away.

The fix is structural, not technical: one party has to own the diagnosis, and that party should be your IT partner. Their job is to work the problem to the vendor boundary, rule out the environment with evidence, and then get the vendor on the line with the diagnostic work already done. “The application is slow, please advise” gets a firm nowhere. “The same document opens in two seconds on one workstation and forty on another, here is what differs between them” gets an engineer. If your current IT company hands you the vendor’s phone number and considers the ticket closed, that is the arrangement to fix. What that ownership looks like day to day is covered on our law firm IT support page.

Where should legal software live, on premises or hosted?

Both, usually, and the mix matters more than the ideology. Legal software environments today are rarely all one thing: a firm might run document management on an office server, practice management on the vendor’s hosted platform, and email in Microsoft 365. Each placement decision has real trade-offs.

On premises means the application and its data sit on a server your firm owns. Speed is local and predictable, the data is physically yours, and nothing about your day depends on an internet connection except email and research. The costs are ownership costs: the hardware ages, the backups are your responsibility, the server needs patching and monitoring, and every five to seven years there is a replacement project. On premises also makes remote and multi-office work harder, since the data lives in one building.

Hosted or cloud means the vendor or a hosting provider runs the application, and your firm reaches it over the internet. The aging server problem disappears, remote work and second offices get dramatically simpler, and updates are largely the host’s problem. In exchange, your practice now depends on your internet connection and on the host’s performance during their busiest hours, and your data lives under someone else’s roof, which makes the questions about backups, export rights, and what happens if you leave worth asking before you sign, not after.

The unglamorous truth: even a fully hosted firm still needs the environment layer. Workstations still have to run well, the office network and internet still have to be sized for the traffic, access still has to be controlled, and the local files, scans, and email still need backing up. Moving to hosted changes what the IT layer covers; it does not remove it. A firm weighing this decision should make it application by application, with someone at the table who does not earn more from either answer. That conversation is what a discovery call is for.

What should you ask each party when something breaks?

When a problem hits, the right questions to the right layer cut hours off the resolution.

Ask your IT partner:

Have you ruled out the workstation, the network, and the server, and what did you check?
Is anyone else in the firm seeing this, or is it one machine or one user?
What changed recently, updates, permissions, hardware, that lines up with when this started?
If this is a vendor issue, will you get on the call with them, and what evidence are you handing over?

Ask the software vendor:

Is this a known issue in our version, and is there a fix or a workaround?
What exactly do you need from our IT partner, logs, versions, configuration, to diagnose this?
Can you join a call with our IT partner directly instead of routing everything through us?

Ask inside the firm:

Did our process change, a new matter type, a new template, a new person doing this task?
Is this the software failing, or the software doing exactly what it was told?

The pattern to notice: none of the questions ask the firm’s staff to diagnose anything. Their job is to report symptoms once, to one accountable party, and get back to practice. If the current setup requires more of them than that, the support model is the problem.

Who does this for law firms in Houston and DFW?

Braintek has supported Texas businesses since 2002 with local teams in Houston and DFW, including the servers, hosted environments, workstations, and file systems that legal applications depend on. We own the environment layer, coordinate with your software vendors so your staff never plays telephone between support desks, and plan updates as scheduled changes instead of Friday surprises. Fully managed support fits firms of roughly 10 to 50 people; larger firms with internal IT usually fit co-managed support, where your staff keeps the day to day and we cover security, projects, and escalations. Pricing runs $150 to $250 per device per month plus $15 to $35 per mailbox, shared mailboxes free and licensing separate, with the full structure on our pricing page.

If the current arrangement leaves your firm refereeing between a vendor and an IT company, that is the first thing worth fixing, and it is a structural fix, not a software purchase. Tell us what your firm runs and where it lives, and we will show you where the lines should be drawn.

Done playing telephone between your software vendor and your IT company?

Tell us what your firm runs, practice management, document management, time and billing, and whether it lives on an office server or a hosted platform. We'll look at the environment underneath it, show you where the finger pointing seams are, and put one accountable party in front of every problem.

FAQs

Our software vendor and IT company keep blaming each other. Who is supposed to own the problem?

Your IT partner should own the diagnosis, every time. Their job is to prove or rule out their own layers with evidence, workstation, network, server, permissions, and then bring the vendor a narrowed, documented question. If your current arrangement leaves a paralegal relaying messages between two support desks, the accountability structure is broken, not the software.

Does Braintek support our practice management or document management software directly?

We support the environment those applications depend on: the servers or hosted platforms they live on, the workstations they run on, the network between them, the backups behind them, and the access controls around them. Questions inside the application, its features, its templates, its data structures, belong to the vendor's support plan, and we coordinate with them directly so your staff is not stuck in the middle.

Who should we call first when the software breaks?

Your IT partner. Most problems that present as software problems start in the environment: a workstation update, a permissions change, a full disk on the server, a bad network path to the database. An IT partner can rule those out fast. If the problem is genuinely inside the application, you want the vendor receiving a specific, evidenced question rather than a vague complaint, because vague complaints go to the bottom of vendor queues.

The software has been slow for weeks and the vendor says everything looks fine on their end. Now what?

That answer is usually true and useless at the same time. The vendor checks the application; slowness typically lives underneath it, in the server it queries, the workstation running it, or the network in between. This is exactly the situation an IT partner should take over: measure where the time is actually going, fix what is theirs, and go back to the vendor only with evidence if the trail leads inside the application.

Should our legal software stay on our office server or move to a hosted platform?

It depends on your application mix and how your people work. Hosted platforms remove the aging server problem and serve remote and multi-office work well, but you take on dependence on your internet connection and the host's performance. On premises keeps control and speed local but means owning hardware, backups, and eventual replacement. Most firms land on a mix, and the honest way to decide is application by application, not all at once.

Do software updates really need IT involvement, or can we just click install?

Coordinate them. Legal application updates often want server components updated in step with workstations, and an update applied unevenly can lock users out or break integrations between your practice management, document, and billing systems. Handled as a scheduled, coordinated change with a rollback path, updates are routine. Clicked ad hoc on a Friday afternoon, they are how firms lose a Monday.

We are a small firm. Do we really need all three layers?

You already have them, whether or not anyone has named them. Someone answers workflow questions, someone owns the machines, and the vendor owns the application. In small firms the risk is that the office manager silently absorbs the first two layers on top of a real job. Naming the layers just means each problem goes to the party equipped to fix it.