Skip to content

Legal technology consultancy

From buy to build to run.

We help law firms and legal teams choose the right technology, build what the market does not sell, and run it on infrastructure they control. We work in the open: BigLaw is free and open source, and our Documents intake is shown as a sample.

Our own work

Two things we built and give away.

They are how we work in public: the same verification-first approach we bring to client engagements. BigLaw is open source and free to run; Documents is shown as a sample walkthrough.

Sample walkthrough · Ontario

discover.legal Documents

A guided interview turns a client’s story into organized Ontario family-law drafts, in the vocabulary the court uses. Shown here as a scripted sample with a fictional client.

  • Interview once; every document fills from the same record
  • Every fact keeps the words it came from
  • A missing fact becomes a Draft note, never an invention
  • A recorded demo: no accounts, nothing sent, nothing saved
Explore Documents

Free · Open source · Experimental

BigLaw

An open-source legal AI platform: research, drafting, redlining, e-signatures, docketing and billing, orchestrated by a bench of agents with a verification protocol between every finding and the page.

  • Apache-2.0, self-hosted, one static Go binary
  • Runs on local models or your provider of choice
  • Human gate before low-confidence findings reach synthesis
  • Built for solos, boutiques and small firms
Explore BigLawSource on GitHub

How we work

The same rules for what we build and what we recommend.

Verification before output

Nothing an AI writes reaches a page without a check against the record. We build it that way, and we buy it that way.

Your data, your infrastructure

Client data stays in an environment you control. Open models and self-hosting are always on the table.

Open source where it counts

Our own platform is public and free. When we build for you, you own the code.

Fixed scope, written outcomes

Engagements end with something you can read and act on: a recommendation, a running system, or a roadmap.

Research

Questions we are testing in public.

Open experiments on how language models behave on legal tasks. Code, data pipeline and results are published as they exist, with their status stated plainly.

All research

Questions firms ask first.

Who is this for?
Law firms and in-house legal teams that are choosing, building or running technology, from a solo practice standardising intake to a firm replacing a vendor stack.
Can I use Documents today?
Not as a public product. It is shown here as a sample walkthrough with a fictional client: there are no accounts and nothing is saved. If you want intake like it for your firm, that is a Build engagement.
Is BigLaw really free?
Yes. BigLaw is open source under Apache-2.0. Paid work is the consultancy: selection, custom builds, managed services and advisory.
What does it cost?
Prices are on request. Every engagement is scoped in writing first, so you know what you get before anything is billed.
Do you resell software or take referral fees?
No. Selection work is independent. If we recommend a vendor, it is because it fits, and the contract we review is yours.
Can you run BigLaw for my firm?
Yes, as a managed service on your infrastructure. BigLaw is experimental and has not had an independent security audit, so a deployment starts with that review and authentication switched on.
Is any of this legal advice?
No. We are a technology consultancy, not a law firm. Nothing on this site or produced by our tools is legal advice.
How do we start?
Email us with the problem. We use a first conversation to understand it and come back with a scoped proposal.

Bring us the problem.

A vendor decision, a workflow nobody sells, a platform that needs running, or a roadmap that needs an owner. We come back with a scoped proposal.

Email us