The law office is an information system.

Legal work is not just documents. A case is people, deadlines, money, memory, judgment, and time — all moving at once.

Most firms scatter that information across tools. Apple Calendar holds the dates. Google Drive holds the documents. Dropbox holds what Drive doesn't. A sticky note holds the rest. Each one holds part of the truth, and none of them know about the others.

That gap between systems is where work goes to drift.

What the gap costs

Nothing in that arrangement is responsible for the case. A person is — reassembling it from four places, from memory, several times a day.

An hour worked on Tuesday and not entered on Tuesday exists in one place: someone's recollection of Tuesday. By Friday it is gone. It was earned, it was owed, and it was never invoiced. Firms notice missed deadlines because the consequence arrives with a court's name on it. Unbilled time leaves nothing behind at all.

The cost of tool sprawl is not the subscriptions. It is the reconciling, and the things that fall between.

The case is the unit

Legal work should be organized around the case, not around the disconnected tools that happen to touch it. The case is the thing every document, date, note, message, and invoice has in common — so the case is where they belong.

Contacts, calendar, documents, notes, messages, billing, tasks, and the client portal all attach to the case. Nothing floats.

Context over storage

A document is more useful when it knows the case, client, date, task, note, message, and invoice it belongs to. Storage keeps a file. Context keeps its meaning.

The software does not guess

Thistle records what a firm tells it and shows it back, in order, when it is needed. It does not summarize, predict, or generate.

This is a permanent constraint, not a stage the product is passing through. Legal work carries consequences that arrive with a court's name on them. Software that infers is software that can be wrong quietly.

Trust is architecture, not assurance

The client portal is a separate system with its own restricted data model — not a filtered view of staff tooling. Access is default-deny. Inbound client messages are held for review before they reach the case file. Every action is logged. Only a firm's own client can be issued a portal login; opposing parties, opposing counsel, guardians ad litem, and children on a case cannot.

Security architecture and a public changelog are published because they are the product, not because they reassure.

Built inside a working law office

Thistle is designed in daily use in an operating firm — not from specifications, and not from feature lists. What is slow, what gets skipped, and what people work around is visible immediately, and gets fixed.

Not for every firm

A system built around how legal work actually runs will not fit a firm that wants something else. Thistle is for whole firms — attorneys and staff in the same cases, in the same record, where no one has to ask anyone what happened.