Legal

What legal apps are worth building?

The useful zone is education and organisation, not representation. A clause explainer, a deadline tracker for a notice period, a checklist of what to bring to a hearing, and a glossary that turns a lease into plain words all help a person understand their situation and prepare for it. Each one should state what it is not: it does not decide the outcome of a dispute, it does not predict what a court or regulator will do, and it does not replace a qualified lawyer. Those statements belong on the first screen, not in a footer.

Three kinds of idea recur. Comprehension tools translate a document the reader already holds, such as a lease, a terms page or a contract from a client. Record and deadline tools keep track of dates, notices and evidence, which people often lose during a dispute. Compliance checklists tell a small business which obligations usually apply to its kind of activity, with a note that the rules depend on the place and the facts. Each of these is narrower than a legal advice service, and each is easier to build honestly, because the output can be checked against the source.

A fourth shape, the self-serve form that produces a document for a court, is the one to be most careful with. It is closer to drafting than to explaining, and the rules on who may prepare such documents differ between places. Treat it as a question for a qualified person before you write any code.

Who uses legal apps, and how do you reach them?

The clearest need sits with people who cannot pay for a lawyer for every question: renters with a deposit dispute, freelancers reading their first client contract, sole traders registering a business, and people holding an official letter about a debt or a benefit they cannot make sense of. These users are often under time pressure and often frightened, which means a plain answer with a clear next step is worth more to them than a long explanation. Professionals form a second group. Paralegals, advice centres and small firms can use intake tools that prepare paperwork, provided their own professional rules on tools and client data are met.

Reach people where the problem starts, not where lawyers advertise. A person who has just received a notice searches for the notice. The first version should be a page that answers that search directly and then offers the next step, such as a question to ask a landlord or a form to check. Test it by watching whether people finish the task or leave for a lawyer, and treat either outcome as information. Do not buy legal-sounding keywords to reach people who are not yet in a dispute, because the people you reach that way are the least likely to be ready for the answer.

What makes a legal idea good?

• It names the document or event. “Understand a lease” is vague. “Find the clauses in a residential lease that set when a deposit can be kept” is something a builder can scope and a tester can check.
• It has a visible boundary. The tool can say what a clause means in ordinary language. It does not say whether the clause is fair, enforceable or worth challenging in the user’s case.
• Every explanation names its source. The statute, regulator page or line of contract it comes from should be shown next to the summary, so the reader can check it.
• It works without an account. Legal problems are stressful and private. Asking for sign-up before the first answer loses people, and storing a dispute history creates a record nobody needs.
• It says “ask a professional” at the right moment, with a reason. A fixed disclaimer at the bottom is not enough. When the answer depends on facts the tool cannot see, the result should say which facts and why they matter.

A good test for an idea is to write the sentence the tool must never say. If you cannot name it, the boundary is not yet designed.

What does a first version look like? A worked example

Hypothetical example for a freelancer who has been sent a client contract. The reader pastes the contract text, and the tool finds the clauses on payment, ownership of work, cancellation, liability and governing law. For each one it quotes the sentence it found, gives a one-line plain-English summary, and says “not located” when a clause is absent. It does not say whether a clause is fair or what to negotiate.

Build a one-page web app. Input: a text area for pasted contract text. No file upload in version one. Find clauses on: payment terms, late payment, ownership of work, cancellation, liability cap, governing law. For each, return the exact quoted sentence, a one-sentence plain-English summary of what it says, and the words “not located” if it is absent. Never say whether a clause is fair, enforceable or good for the user. Show this line above every result: “General information only. This is not legal advice.” Do not store the pasted text after the page is closed.

To test it, give the tool ten contracts that a qualified person has already reviewed, and compare each summary with that reviewer’s notes. Count the errors and sort them. A summary that is slightly vague is a design problem. A summary that misses a termination date, or puts a liability cap in the wrong category, is a failure, and the first version is not ready to show anyone until those are fixed.

What are the pitfalls specific to legal apps?

The central pitfall is unauthorised practice of law. In many places, giving specific advice on a person’s legal problem is reserved to licensed people, and software can cross that line even when no human is involved. Whether a given tool does so depends on the jurisdiction, the wording and the facts, and this page cannot settle it. Get a qualified opinion before you launch anything that gives case-specific answers, and treat the rules as something to verify, not something you can assume.

• Confident wrong answers. Law changes and differs between places. A summary built from an old version of a rule, applied to someone in another region, can be wrong in a way that costs money. Show the place and the date of every source.
• Disclaimers that do no work. A footer that says “not legal advice” under a result that tells someone to withhold rent does not change what the result is. Remove the instruction. A disclaimer cannot repair it.
• Sensitive records. Disputes involve names, addresses, income, and sometimes health or immigration details. Process pasted text in the browser where you can, keep no copy, and say so plainly.
• Tools that imitate a lawyer. Avatars, titles such as “legal assistant”, and claims about likely outcomes make people trust a result more than the result deserves.
• Duplicating a free service. Before building, check whether a free information service already covers the same document in the place you intend to operate. A second copy of a good free guide adds little.

Where to start: live ideas and editorial reading

Two ideas in this category were on the board when this page was written. Duolingo, but for knowing your rights sits on the comprehension side. Its risk is that a quiz reads as advice, so the boundary has to be designed in from the first screen. Which cookie banner do you actually need? is narrower: a short questionnaire about what a website does with visitor data, where each branch names the rule it depends on. Have the rules checked by a qualified person before the questionnaire goes live.

Have a different document or deadline in mind? Post it and name the notice, form or date the tool would cover. Before anyone builds it, validate the idea with people who are holding that paper right now, not with people who find law interesting.