Home / Legal technology

Still the deepestroom in the building.

For law firms and corporate legal teams, we cover the full discovery lifecycle. This is where our method was built, and we never left.

SHA-256✓ verifiedASM-000001
EDRM coverageClick any stage
Mapped to EDRM 2.0 — public comment draft, June 2026

Foundation

Data acquisition

Use

Continuous

Foundation

Information Governance

The base the whole model now rests on. Retention schedules, classification, security and defensible disposal, built before a dispute rather than during one.

We do this: policy design, retention frameworks, data mapping, and governance programs that hold up under scrutiny.

Production simulation — one matter, end to end
Collected0
After dedupe0
Search hits0
Reviewed relevant0
Privileged, held0
Produced0

SHA-256✓ verifiedASM-000002
Why it matters hereContext

The Electronic Discovery Reference Model is the shared language of this field, and it is mid-revision. EDRM 2.0 opened for public comment on 30 June 2026, developed by roughly 150 practitioners across the global EDRM community.

The restructure matters. Information governance moves from a side box to the foundation the whole model rests on. Identification, preservation, collection and processing group into Data Acquisition. Disposition becomes a standalone phase. Analysis stops being a stage in the middle and becomes a continuous activity, increasingly informed by generative AI.

We mapped this page to 2.0 rather than the 2005 diagram because a litigation support manager can tell the difference in about four seconds.

SHA-256✓ verifiedASM-000003
Who does the workCredentials

Built where guessing wasn't an option.

Most process advice is written by people who never had to defend it. Ours came out of two decades in work where you did — enormous, messy datasets, deadlines that didn't move, and a standing requirement to explain every step you took and why. "Trust me" was never an acceptable answer.

That leaves a mark on how you work. You stop believing the org chart and start watching what people actually do. You measure before you recommend. You document as you build, because someone will ask how you got there and "I remember" isn't a method.

Learn the terrain before you touch anything. Assemble the fix from the right parts. Document it so it holds up. Then come back and keep it fitting.

Those habits turn out to have very little to do with the industry that produced them. The slow workflow, the data nobody trusts, the process held together by spreadsheets and one person's memory — that shape of problem is everywhere. We've been solving it for twenty years. The sector changed. The method didn't.

The founders

Two people, nearly twenty years

The two of us met almost twenty years ago, working on the kind of problems where being approximately right is the same as being wrong. We were not looking for a business partner. We were solving the same problem from different directions and kept arriving at the same answer.

That kept happening. Across different companies, different roles and different decades, we found we could hand each other a half-formed idea and get back something better built than what we started with. Neither of us has ever been interested in technology as the point. It's what the technology lets a group of people stop worrying about that makes it worth building.

Two decades of that produced a short list of things we won't bend on: learn the terrain before you touch it, prove what you claim, and leave people able to run what you built without you. Assembly Discovery is those habits with a name on the door.

SHA-256✓ verifiedASM-000004
Next
SHA-256✓ verifiedASM-000005