What is a headless law firm?

“Headless” is a software word that has started to travel. Applied to a law firm, it needs a careful definition, because the one part of a firm that can never be detached is the part that thinks like a lawyer.

Headless, defined for a law firm

A headless law firm runs the operating body of the practice in one console: its matters, its docket, its documents and its books. The head is the part that does not move. Licensed lawyers make every legal judgment, sign what gets signed, and refuse what should be refused.

The division is strict. The software runs operations. It is not a law firm, it gives no legal advice, and it signs nothing. In Marlow, nothing can commit past a lawyer’s refusal.

The term is new; the problem behind it is not. Many small firms still run their practice across separate tools. In the ABA’s 2024 Practice Management TechReport, 53 of every 100 respondents reported that case or practice management software was available at their firms, down from 63 in 2022. Among solo practitioners, the same report found reported use fell from 45 of every 100 in 2022 to 37 in 2024. For most solo practitioners, in other words, the practice runs without one.

Where the word comes from

In software, “headless” describes a system with the presentation layer taken off. A headless content management system, in Wikipedia’s description, is a back end that stores content without a built-in front end, so the same content can be shown anywhere.

In 2026 the idea moved into large business software. Salesforce launched Headless 360 on April 15, 2026, at its TDX developer conference, with the aim that customers could use the platform’s capabilities without logging into a browser or navigating its interface, according to TechWyse’s report. destinationCRM reported in August 2026 that Salesforce was expanding it across its portfolio. An a16z podcast in July 2026 asked the question directly, under the title “Is Software Losing Its Head?”, and discussed whether traditional software products are becoming systems of record rather than systems of engagement. A system of record, left to itself, only records; that is the argument Marlow makes about practice software in the problem.

Salesforce has also used the exact phrase. Its webinar “The Headless Law Firm” presents an “Invisible CRM” that sits inside Outlook and Teams, the tools partners already use.

In each of those uses, the head that comes off is a screen. For a law firm, the useful meaning is narrower, and it runs the other way. The operating body of the practice runs in one place, and the head, the legal judgment, stays exactly where the rules of professional conduct put it.

The head stays human

Two ABA Model Rules frame what a headless firm can and cannot be. Each jurisdiction adopts its own version, and that version governs.

Rule 5.4, professional independence. The Model Rule says a lawyer or law firm shall not share legal fees with a nonlawyer, outside narrow exceptions. A lawyer shall not form a partnership with a nonlawyer if any of its activities consist of the practice of law. A lawyer shall not let a person who recommends, employs or pays the lawyer to render legal services for another “direct or regulate the lawyer’s professional judgment.” Paragraph (d) bars practicing in a for-profit firm in which a nonlawyer owns an interest, serves as a director or officer, or has the right to direct or control a lawyer’s professional judgment.

Nothing in the headless model changes who may own a firm or direct a lawyer’s judgment. Those questions stay with Rule 5.4 and its local versions. Software that runs a firm’s operations is a tool the firm uses, not a participant in its judgment.

Rule 7.1, communications. A lawyer shall not make a false or misleading communication about the lawyer or the lawyer’s services. Under Comment [2], even a truthful statement can mislead if it is likely to lead a reasonable person to a conclusion with no reasonable factual foundation. That is why the word needs care in a firm’s own client-facing language. “Headless” describes how the firm runs, not who does the legal work, and any description that blurred the two would invite exactly the question Rule 7.1 asks.

One console: matters, docket, documents, books

The practical meaning of headless is that the firm’s operating record lives in one place instead of five. In Marlow’s console, that record has four parts:

• Matters. Each one carries its documents, its dates and its journal together.
• The docket. Reminders come 30, 14 and 7 days out, then daily in the final week, when one named lawyer acknowledges each day. A missed day is journaled as missed, never silent. A date with no owner shows as vacant. The reasoning is set out in what legal docketing is.
• Documents. Every version is kept, and none is overwritten.
• The books. The money, kept in the same console as the matters it belongs to.

The term is easy to confuse with older labels. This is how it compares.

The labels are not exclusive. A firm can be virtual and headless at once; one describes the office, the other the operating model.

Four questions that tell the difference

Whatever a firm calls itself, four questions show whether the head has stayed where it belongs:

1. Does the firm’s operating record (matters, docket, documents and books) live in one place?
2. Does a licensed lawyer make every legal judgment, with nothing in the software standing in for one?
3. Can anything in the software commit the firm past a lawyer’s refusal? In a headless firm, nothing can.
4. Can the complete client file leave whole when the client asks for it?

The first question is about operations. The other three are about the head, and they are the ones a client would ask.

Work that arrives opened

A headless firm still needs work. In Marlow, client demand from consumer services that Marlow’s maker runs arrives at the firm as opened matters: conflicts screened, the client’s signed consent on file, and every intake step on the record.

How much arrives, and when, depends on live demand, and nothing here promises a volume or a schedule. What it changes is the starting point. A matter that arrives opened begins with its record already kept, instead of with data entry about demand the firm found for itself. The reasoning behind that design is in the turn.

Signing acts at a flat fee, never a share of any fee

The same services produce documents that need a licensed lawyer’s judgment: reviews, attestations and reasoned refusals. Marlow routes those paid signing acts to the firm’s own lawyers.

Each act carries a flat fee, fixed before anyone takes it, and paid whole to the acting lawyer. A reasoned refusal is paid the same as a signature, so the fee never leans on the answer. Marlow’s own prices are flat and posted before anything is signed, $0 until the filing exists, and never scaled to any fee the firm earns. The details are under fees and on the pricing page.

Beside the system you already run

A headless firm does not have to start with a migration. Marlow installs nothing, migrates nothing and binds nothing. It runs beside the incumbent, and the firm keeps Clio for what Clio does. For a fair account of how a parallel run works, and of what Clio’s own documentation says its export contains, see running new practice software beside Clio.

Whatever runs the operations, the client file has to be able to leave whole. That obligation is the subject of who owns the client file.

Marlow is practice software, not a law firm. It gives no legal advice, and nothing in it can commit past a lawyer’s refusal. Managing partners who want the argument in one page can read the partner memo. Firms that want to see the console on synthetic matters can join the first firms: five short steps that end in a live sandbox workspace.