# Marlow (marlow.legal)

> Practice software for small law firms. The whole practice in one console, with your lawyers at the head. Marlow is practice software: it gives no legal advice, is not a law firm, and signs nothing. Every act of legal judgment is a licensed lawyer’s own, and nothing in Marlow can commit past a lawyer’s refusal.

## Pages

- [The page](https://marlow.legal/): what Marlow is, the record, the console, the fees
- [Fees](https://marlow.legal/pricing): flat posted prices, the signing fee, and the rules that hold them
- [Join the first firms](https://marlow.legal/onboard): five short steps, native forms, ending on a sandbox workspace

## Machine faces

- [The partner memo](https://marlow.legal/?format=md): the page as markdown, each claim with its rule
- [Health](https://marlow.legal/healthz): a typed liveness probe

## The access sequence

Access runs as a sequence at GET /onboard: POST /onboard/1 (form-encoded firm, name, email) records the firm, and steps 2-5 enrich the same entry over the step cookie: role (managing-partner | firm-owner | practice-group-lead | another-firm-role) and firmSize (2-5 | 6-10 | 11-20 | another-size); areas (patent | trademark | corporate | litigation | another-area, repeatable) and software (clio | mycase | another-system | none); collab (slack | teams | neither) and suite (google | microsoft-365 | another-suite); posture (now | this-quarter | watching) with optional practice notes. A repeat with the same email updates the recorded details. Completing step 5 provisions a temporary anonymous sandbox workspace on api.lawyer (synthetic state, TTL-bound) and the sequence lands on GET /onboard/workspace, the live view of that grain; after expiry, POST /onboard/workspace provisions a fresh one.

## Proof

The engine Marlow runs on, api.lawyer, is graded in public: A+, 10 of 10 checks at api.qa/api.lawyer.

## Blog

Writing for the partners who run small firms. Every post also answers as markdown at its address plus .md, and llms-full.txt carries each one in full.

- [The Marlow blog](https://marlow.legal/blog): How a small firm keeps its matters, docket, documents and books, and what changes when new work arrives already opened.
- [The blog as markdown](https://marlow.legal/blog.md): every post with its date and dek
- [RSS](https://marlow.legal/blog/rss.xml) and [JSON Feed](https://marlow.legal/blog/feed.json): every post in full
- [llms-full.txt](https://marlow.legal/llms-full.txt): this file, then the partner memo and every post in full
- [What is legal docketing? Keeping every deadline from lapsing](https://marlow.legal/blog/what-is-legal-docketing): Docketing, calendaring and the tickler, defined; what the ABA’s malpractice data says about missed dates; and how a reminder ladder puts one named lawyer on every deadline.
- [Who owns the client file? What Rule 1.16(d) asks](https://marlow.legal/blog/who-owns-the-client-file): When a representation ends, what leaves with the client? The Model Rule, the entire-file and end-product approaches, Opinions 471 and 520, and what a portable file means for practice software.
- [What is a headless law firm?](https://marlow.legal/blog/what-is-a-headless-law-firm): Where the word headless comes from, what it means when the subject is a law firm, and why the head, a licensed lawyer’s judgment, never moves into the software.
- [Running new practice software beside Clio, without migrating](https://marlow.legal/blog/running-practice-software-beside-clio): How a parallel run works, what Clio’s own help center says an export contains, what to check before relying on any export, and what a portable client file should mean.