View
Project 01 — Lexx

Lexx

Product engineering + Brand identity + Art direction

Palette
14171A
3B4249
EDE7DC
DBD1BE
C2492D
Client
Lexx (self-initiated)
Year
2026
Role
Solo — product & brand
Sector
Legal technology

Software that tells you what it does not know is worth more than software that never admits it.

Lexx turns an uploaded case file into structured intelligence: a summary, the key issues, extracted facts, a timeline, and — the part every competitor omits — an explicit list of what is missing.

It is not a chatbot and it is not legal research. It is a processing engine with a controlled workspace on top, and every output is validated against a schema before a lawyer ever sees it.

  • 01Document processing engine and structured output schema
  • 02Secure AI workspace — scoped Q&A and draft generation
  • 03Naming, positioning and the campaign line
  • 04Identity system: wordmark, palette, type system
  • 05Environmental and print art direction

Building wraps — the claim at civic scale

Documents in. Structure out. You still decide.
Lexx — campaign line

Introduction

Lexx started as a build problem and turned into a positioning problem. The engine was straightforward: parse a document, send it to a model under a strict schema, validate the output against TypeScript types, never show a lawyer raw generated text. That part I knew how to do.

What I did not expect was that the hardest constraint would be a legal disclaimer. Every AI output has to carry “This is not legal advice. Attorney review required.” Every product in the category treats that line as a tax — set it in 10px grey, push it to the footer, hope nobody reads it.

That is what bothered me. The sentence they are all hiding is the only sentence their buyer actually wants to hear. A lawyer deciding whether to put privileged documents through software is not asking “is this smart?” They are asking “does this take the decision away from me?” Answering that plainly is not a compliance burden. It is the pitch.

Cheers,
C.D.

Phase 01The problem, in real units.

A junior associate reading into a new matter works through several hundred pages to produce the same five things every time: a summary, the key issues, the extracted facts, a timeline, and a list of what is missing. It is hours of work, it is billed to someone, and almost none of it is judgement — it is retrieval and ordering.

So Lexx does not answer legal questions. It produces those five artefacts and stops. The scope is deliberately narrow: a processing engine, not a chatbot and not research.

Phase 02The machine structures. The attorney decides.

That became the organising idea for the product and the identity at the same time. Architecturally it means output is always validated against a schema before it is stored, and never streamed to the interface as free text. There is no blank prompt box anywhere in the app — every AI action is a labelled button with a known output shape.

In the brand it became the line: Documents in. Structure out. You still decide. The same sentence, once enforced in the type system and once printed on a building.

Phase 03The identity, and what it refuses to look like.

The first build shipped with indigo and teal — the default palette of every AI product since 2021. In a category where the buyer is deciding whether to trust you with privileged material, looking like every other AI tool is not neutral. It is a liability.

The rebuild is warm archival paper and ink with one red that means something: the stamp on a filed document. The wordmark is geometric, and the two X letters overlap so their inner diagonals merge into one woven form — a cross-reference, which is exactly what the engine does when it links a fact in one document to a date in another.

One system idea carries into the interface: anything a person wrote is set in grotesk, anything the machine extracted is set in mono. A lawyer can tell at a glance what was asserted by software. It is the typographic form of the same promise.

Phase 04Limitations, honestly.

V1 stores everything as JSON files behind a single storage adapter interface. That is a deliberate trade — it made the product shippable without a database decision — but it does not survive concurrent users, and the swap to Postgres is a real migration, not the one-import change the architecture promises on paper.

Extraction is only as good as the document. Scanned filings go through OCR and degrade badly on poor scans, and the system is more confident than it should be about dates it has read wrong. Surfacing confidence per extracted field is the next thing that matters, and it is not built yet.

Closing remarks.

Every competitor in this category is quietly arguing that the software is smart enough to be trusted. Lexx argues the opposite and is more trustworthy for it: here is the structure, here is the page it came from, and the decision was never ours to make.

Fig 1: The campaign line is the disclaimer. Most legal-AI brands bury “attorney review required” in a footer; making it the headline is what a cautious buyer actually needs to hear.
Fig 2: “You still decide.” on a courthouse. The claim is about who holds authority, so it is placed where authority already lives.
Fig 3: Warm archival paper against cool terminal light. The palette is doing the differentiating before a single word is read.
Next projectSlate