Notes from the workspace.

On the Enterprise plan the firm uses its own AI account. This is every step, from opening the account to the first check inside Avantwerk: about ten minutes, no technical knowledge needed.

The honest answer is: it depends entirely on where the data goes. Here is the line that separates an AI tool you can safely put a privileged file into from one you can't.

We're pre-launch and we say so. The capabilities page lists every concrete action with its real status, checked against the code, and roadmap items aren't dressed up as done. Where the product is now, and what's next.

Flat per seat, a generous monthly allowance, a managed key with no setup, bring-your-own-key at the top, and none of the scarcity games. The philosophy behind the pricing: figures live on the pricing page.

A populated demo that takes a fictional matter through the whole product in a few minutes: no card, no commitment. We would rather show you than tell you.

The architecture that lets one engine serve several markets without ever bleeding one jurisdiction into another, and how we opened new markets on the same core without translating anything.

A product should get better the more a firm uses it, but not by quietly harvesting matter content. Our self-learning layer is off by default, opts in explicitly, and never lets matter content leave the firm.

Translating one market's legal product into another's language produces something that reads plausibly and gets the law wrong. We build each jurisdiction to its own frame instead: here is what that costs and what it buys.

Solicitors live in Word, Outlook and Excel: not in a browser tab. So we put the agent fleet inside those tools: a Word ribbon, an Outlook task-pane that matches an email to a matter, and an Excel batch counterparty lookup.

HMCTS court forms and pleadings, native to England and Wales: the N-series, the workflows that chain them, and a litigant-in-person mode, all pre-populated from the matter you already have open.

A comparison of three client-account balances the firm enters, issued-invoice age, recorded time, a historical settlement base rate and UK invoice files, in the same system where the matters already live. It reads no bank or accounting system and makes no compliance finding.

On the Enterprise tier you bring your own AI-provider key. Your usage is billed by your provider, at their rates, never marked up by us. Your contract for the model is with the provider, not with us.

A matter is not a list of documents. It is a shape: a chronology, a set of relationships, a caseload with deadlines. So we built four ways to see that shape, not just scroll a file list.

An HMAC-authenticated, chain-linked record of events successfully written on covered paths, exportable in one click. It is tamper-evident when checked with the firm-held key; the export alone is not independent proof.

A running register of the matter's risks, limitation, deadlines, conflicts, exposure, that moves when the matter moves. Because it is built from the same structured case the rest of the product writes to, it does not wait for someone to remember to update a spreadsheet.

On the attended registry path, 10 consequential registered drafting, filing and signing skills pause for confirm, reject or modify; unattended review is refused. Direct and unregistered paths are outside that guarantee.

Click a compliance check on a live matter and get a read grounded in the SRA Code of Conduct: tied to what actually happened on that matter, not a generic template. The record is built from real activity, so it holds up when someone asks.

Case citations and legislation do not clear the same check. UK case citations are queried against Find Case Law; statutory references remain for the solicitor to confirm from the official legislation source. Unresolved items hold the export unless a named override is recorded.

Click 'run adversary pass' on a draft and the tool argues the other side's case against yours across a set of critique angles, procedure, evidence, limitation, quantum and more, each finding anchored to the statute, rule or authority it relies on. You read your own weaknesses before opposing counsel does.

Click 'prepare case' on a matter and the tool marshals what the file already contains, parties, claims, evidence, authorities, the date spine, into a typed skeleton. You start from a prepared position rather than a blank page, and edit the judgement calls yourself.

Type a counterparty name and get a structured intel card built from public UK registers, Companies House, the SRA register, OFSI, AML sources, with every fact linked back to the register entry it came from. No opaque summary; a card you can verify line by line.

On covered structured-text requests, recognised identifier classes are replaced in the browser before egress. Image-only or scanned content and the names or vocabulary intentionally supplied to AI-assisted dictation are documented exceptions. This is reversible pseudonymisation, not anonymisation.

A new matter arrives as an email thread, a contract, or a chaotic Word file. We built the intake to read those papers and propose a structured matter, parties, dates, issues, value, with every fact linked back to the paragraph it came from, for the fee-earner to confirm.

Our client onboarding module does not hand you a to-do list. It produces the SRA and UK GDPR compliance pack itself, privacy notice, data-handling policy, DSAR workflow and more, as drafts, mapped to live regulator guidance, ready for review and sign-off.

The first module we built: drop in the client, scope and fee basis, and get a jurisdiction-correct engagement letter draft in your firm's voice. A draft you review and sign: not a filing, and never machine-translated.

The architecture behind the product: your case file lives in an encrypted vault your firm controls, not in a database we run. Here is what leaves it for an AI step, and through where.

How the privilege gate works: on the attended UK AI path, protected or unknown material triggers a per-request warning; a decline or no answer refuses the request. Other market routes can hard-block.

The founding post in our build log. A tool that processes your matter remotely has to receive the privileged file first. We started from the opposite decision (the matter stays under your control) and built everything else around it.