This guide is for partners, chief operating officers and IT or innovation leads at small and mid-sized law firms, and for in-house legal teams that are choosing a legal software development company. It belongs to the industry platform playbooks and connects to Netbase's digital transformation consulting service.
In this guide
- Why is law firm software harder to build than ordinary business software?
- Which parts should a law firm build, and which should it buy?
- How do you brief a legal software development company?
- When should a law firm not build custom software?
- Where AI fits
- What delivery record exists, and what does not?
- Alternatives: other ways to get law firm software
- Limits of this guide
- Frequently asked questions
- Next step
Why is law firm software harder to build than ordinary business software?
Law firm software is harder because every record carries a professional duty, not only a business rule. A conflict check, a client file and a message to a client are each governed by the firm's regulator, so the software must show who saw what, when, and on whose authority. A leaked file is a breach of confidence, not an outage.
The SRA Code of Conduct for Solicitors in England and Wales shows the pattern. It forbids acting where there is a conflict of interest or a significant risk of one, it requires the affairs of current and former clients to be kept confidential, and it requires that clients get information they can understand about how their matter will be handled. Other jurisdictions word them differently, but they shape intake, storage and client communication almost everywhere.
Anti-money-laundering rules add a fourth constraint at intake. Under regulation 28 of the UK Money Laundering Regulations 2017, a firm in scope must identify and verify its customer and assess the purpose of the business relationship before it relies on it. Intake software that skips these checks moves a compliance task back onto a lawyer's desk.
Which parts should a law firm build, and which should it buy?
The matrix splits law firm software into six parts. "Buy" means a practice-management or document-management product configured for the firm; "build" means custom software, usually connected to that product.
| Part of the system | Default route | Duty it touches | Build it when |
|---|---|---|---|
| Intake, client checks and conflict search | Buy, then extend | Conflicts; client due diligence | Your conflict rules or intake questions differ by practice and the product cannot hold them |
| Matter workflow (tasks, deadlines, approvals) | Buy | Competent, timely service | A practice runs a repeatable process, such as high-volume claims, that no product models well |
| Document AI (reading, sorting, extracting) | Build on a product's storage | Confidentiality | Your documents, clause library or review checklist are the advantage, and the model must stay in your account |
| Knowledge search over precedents | Build | Confidentiality; supervision | Lawyers need answers from the firm's own work with the source cited, limited to matters they may see |
| Client portal | Buy, or build for one service line | Keeping clients informed | Clients need a self-service journey, such as status, documents and e-signature, tied to your matter data |
| Time, billing and client money | Buy | Safeguarding client money | Almost never; regulated accounts belong in a tested product |
The rule of thumb: the closer a part sits to money held for clients, the more it should be bought; the closer it sits to the firm's know-how, the more a custom build can pay back.
How do you brief a legal software development company?
You brief a legal software development company by putting the professional duties in writing before any design work starts. Each point turns a duty into a requirement bidders answer with a document.
-
A data map
List which client data each part will hold, where it is stored, and who may see it per matter, including ethical walls between teams.
-
Confidentiality in the design
Ask how access is checked on every record and how a lawyer who leaves a matter loses access the same day.
-
Conflict rules as configuration
Ask the partner to hold your conflict and intake rules as settings a risk partner can change, not as code that needs a release.
-
Hosting you control
Ask whether the system and any AI model can run in a cloud account the firm owns, in the jurisdiction it chooses.
-
Processor terms
If the partner touches personal data for the firm, Article 28 GDPR requires a contract that sets out the processing, and Article 32 asks for security measures such as encryption.
-
A rule for AI review
Ask which person reviews each AI output before it reaches a client or a court, and how the review is recorded.
-
An audit trail
Ask for a log of who opened, changed or shared each document and message, kept for as long as your file retention rules require.
-
Code and IP ownership
Ask who owns the code written for the firm and which parts are licensed products.
-
Exit and handover
Ask for repository access, documentation and a runbook, so another team can take over.
-
A stop point
Ask the partner to commit, in writing, to stopping after discovery if a product would serve the firm better.
A bidder that answers all ten with documents is safer than one that leads with features.
When should a law firm not build custom software?
A firm should not build when a practice-management product already fits its matters, its billing and its client portal with configuration alone. Custom software adds an owner, upkeep and a release process that a small firm with standard practice areas gains little from.
Three other cases argue against a build. One is a firm with no partner or operations lead who will own the workflow after launch. Another is client money and regulated accounts, where a tested product is the safer route. The last is data that an outside team must never reach, even for support; in that case, keep the build in house or limit the partner to code that never touches live client files.
Where AI fits
AI helps a law firm most where lawyers read, sort and search large volumes of documents. Document AI can classify incoming files, extract parties, dates and clauses into draft fields, and flag clauses that differ from the firm's standard. A retrieval-based assistant can answer questions from the firm's own precedents and know-how with a link to the passage it used, limited to the matters the user may see. A lawyer reviews every output before anyone relies on it.
The NIST AI Risk Management Framework gives a voluntary structure for that control through four functions: govern, map, measure and manage. Netbase works with the major commercial and open-source AI tools and models, chosen per project, so a firm can keep a model its risk team has already approved. The intelligent document processing page describes what Netbase builds, and the AI knowledge assistant covers search over a firm's own documents.
- In delivered work
Document AI
A document AI platform that reads and extracts business documents; the client is not named and it is not a law-firm project.
- In delivered work
Knowledge assistant
A retrieval-augmented (RAG) knowledge assistant; the client is not named and its sources are not published.
- Available capability
Clause review and matter triage
Clause comparison and routing of new matters for a lawyer to approve; not yet tied to a published legal-sector case.
What delivery record exists, and what does not?
Netbase has no legal-sector project on record, and this page claims none: no law-firm client, legal-tech product or regulator approval. What exists is adjacent delivery. Netbase has delivered projects for clients in travel and hospitality, healthcare, real estate, manufacturing and logistics, and events, and these clients are not named. Its delivered AI work includes RAG knowledge assistants, document AI and MLOps pipelines for clients who are not named.
Delivery follows a six-step lifecycle: discovery and strategic alignment; team assembly and architecture planning; agile execution with outcome-based milestones; modular and productized components; training, rollout and optimization; and ongoing support and co-building. Governance runs on weekly reviews, KPI dashboards and a dedicated account manager and project manager. Progress is tracked in Jira, Redmine, Trello or GitHub, where the client can check it at any time.
For custom development the client owns the IP created for it, while Netbase productized modules are licensed, not transferred. Most projects run on fixed-price contracts, with milestone-based, monthly team retainer and KPI-linked models also offered; engagement can be project-based, a dedicated team, on-demand support or fully managed delivery. After launch, Netbase runs, maintains and upgrades what it builds, remotely and alongside the client's team, under an agreed support scope with response targets set per contract.
Netbase's security practices include secure code review, TLS in transit and AES at rest, role-based access control, MFA for admin dashboards, vulnerability scanning, penetration testing and disaster recovery. Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations; neither extends to a firm's system or hosting.
Alternatives: other ways to get law firm software
Choose a route by who keeps control of client data and know-how after launch.
| Route | Choose it when | Watch for |
|---|---|---|
| Practice-management product, configured | Your matters, billing and portal fit a standard model | Features you need sit on a roadmap you do not control |
| Product plus custom extensions | One workflow or the document AI is your advantage | Integration upkeep when the product changes its API |
| Fully custom platform | Your service is itself software, such as a fixed-fee online legal service | Owning maintenance, security and releases for years |
| In-house developers | You can hire and keep engineers | Hiring time and a single point of knowledge |
| Remote development partner | You keep hosting, code and sign-off under your control | The ten brief points above |
The professional services industry page covers service firms broadly; two sibling guides apply the same split to other regulated work: the healthcare workflow platform requirements and e-government services with a remote partner.
Limits of this guide
- It is a general guide, not legal or regulatory advice; your regulator and counsel set the rules for your firm.
- It uses rules from England and Wales, the EU and a US framework as examples; your jurisdiction may differ.
- Netbase has no legal-sector record, so the delivery view comes from adjacent registered work only.
Plan the next step with a Netbase consultant
Frequently asked questions
Usually not. A small firm with standard practice areas is better served by a configured practice-management product, and it should build only one workflow or a document AI feature that gives it an advantage the product cannot.
It can, if the model runs in an account the firm controls, access follows the same matter permissions as the files, and a lawyer reviews every output. The contract with the developer should forbid using client documents for any other purpose.
Ask who owns the code, where client data and AI models will run, how access per matter is enforced, and whether the partner will stop after discovery if a product fits better. Written answers separate careful bidders quickly.
No. Netbase has no legal-sector project on record and names no law-firm client. It offers consulting, build and operation of document AI, workflow and portal software as a capability, backed by anonymised document AI and knowledge assistant delivery in other industries.
Next step
Send us the one workflow your firm wants to change and the products you use today, and we will review the build-or-buy split with you.
Related services and solutions
AI-enabled digital transformation consulting that ends in a delivery plan Netbase provides digital transformation consulting for mid-market companies that need a prioritized roadmap with a delivery path, not a deck. We rank every change by value and risk, including where AI removes manual work, and the same team builds it. According to CEO Huy Nguyen (David), Netbase has served 500+ businesses across 80 countries since 2012.
Learn More
AI knowledge assistant: answers from company knowledge, with sources and access control An AI knowledge assistant is an internal tool that answers employees' questions from your company's own documents and systems, cites the source behind every answer and shows each person only what they may see. Netbase offers it as a growth capability, designed with retrieval, evaluation and human review from the first pilot, and has delivered one for an unnamed client.
Learn More
Intelligent document processing with AI: from orders, invoices and forms to validated data Intelligent document processing is AI-driven intake that reads orders, invoices and forms, extracts the fields your systems need, validates them against business rules and routes each record to the right queue, with people reviewing anything uncertain. Netbase offers it as a growth capability built on its computer vision and automation work, including a document AI platform for an unnamed client.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.