Astralex Astralex

For in-house and fractional counsel

Your playbook, on every matter. Your time on the ones that need you.

A bespoke system that checks inbound contracts against your standing positions and drafts from them — built for in-house counsel and document-heavy practices, owned by you.

Book a free consult →

30 minutes. No deck.
Bring one document type you review often.

Master Services Agreement reviewed

§ 7.2 — Limitation of liability

…in no event shall either party's aggregate liability exceed the fees paid in the six (6) months preceding the claim.

Off-position POS-014

Your standing position floors the cap at 12 months' fees. Counter drafted from your language.

Runs in your environment. You own it outright — your playbook stays yours, never pooled.

What you get

A system that runs your playbook.

  1. 01

    Your playbook

    Your standing positions — what you accept, what you reject, what you fall back to — captured once. The durable asset of the engagement, and the source every review runs against.

  2. 02

    Review against your positions

    The system checks inbound and drafted work against your playbook and flags every deviation — with your standard counter pre-drafted. The same answer whoever is at the desk, and an audit trail for every call. Your attention goes to the exceptions, not the whole stack.

  3. 03

    Drafting from the same source

    Where work starts with you, the system drafts first-pass sections from the matter facts and your playbook, in your house style — outline first, you sign off, then sections fill.

  4. 04

    Continuous tuning

    Every edit you make sharpens the next pass. The system gets better at your practice, matter over matter — and that learning stays inside your system. It never trains a shared model or reaches another firm.

  5. 05

    Integration

    Wired into your DMS, your matter intake, your calendar. Work arrives where you already work; nothing new for your team to log into.

Yours to keep

Your data and your playbook stay yours.

The two questions every firm asks before trusting a system — answered the same way, in plain terms.

Your data

Your data stays yours

Your document store stays where it already is, on infrastructure you control — never copied up to a vendor's cloud. We store nothing of yours: the build runs under NDA, and at handover every working copy we used is destroyed.

Your playbook

Your playbook stays yours

The positions and refinements you build into the system are never pooled across firms or fed back to us. Your judgment compounds for you alone — not a product everyone else rents.

Where this lands

Built around the documents you handle most.

Every engagement starts from one document type that eats your time. One in full, three in sketch.

Featured · contract review

Every inbound contract, checked against the positions you already take.

The system reads the counterparty's paper, checks each term against your playbook, and flags every deviation — with your standard counter pre-drafted. You review the exceptions, not the whole document.

  • Your accept / reject / fallback positions, captured once and applied the same way every time.
  • Flags only what departs from your playbook — attention goes to the exceptions, not the boilerplate.
  • Every flag traceable to the position it failed and the fallback you would offer.

In · inbound contract

// vendor MSA · §8 Limitation of liability

"In no event shall Vendor's aggregate liability exceed the fees paid in the three (3) months preceding the claim."

Out · checked against your playbook

// §8 Limitation of liability

Flag · cap is 3 months' fees; your floor is 12 (LoL-004)

Counter drafted · "…the twelve (12) months preceding the claim."

// §11 Governing law

OK · Delaware — matches your standard

⤷ checked against playbook §commercial-terms

Illustrative output. Real engagements run against your own playbook and prior contracts.

NDAs, DPAs & vendor paper

The high-runners — reviewed against your positions or drafted from your standard — so routine inbound stops eating senior time and every redline reads the same.

Disclosure schedules & ancillaries

Schedules drafted from the data room and intake, ancillaries kept in lockstep with the SPA. A single fact change cascades through every related document — no reconciling Exhibit B against §4.7 the night before signing.

Pleadings & discovery, from intake

Complaints, answers, responses, and privilege logs built together from the structured fact file, cross-referenced and formatted to your court's rules. Your strategy drives the structure; the system handles the bookkeeping.

How it works

What happens between booking the call and Monday morning.

No pitch deck, no SaaS contract, no platform lock-in. Four steps, with an obvious off-ramp at each one.

  1. 01 On the call

    The 30 minutes

    You bring one document type that eats your time — a contract you review again and again, a motion you draft a lot. We sketch what a bespoke system could do, and what it could not, by end of the call.

  2. 02 Within 48 hours

    A one-page scope

    We send a short written scope: the agent, integration points, success criteria, a fixed fee, and a build window. You decide whether to proceed. No retainer.

  3. 03 Weeks 1–6

    Build, in your environment

    Two to six weeks, working with your real matter files (under NDA) and your tools. You see progress weekly. The lawyer who will use the agent shapes how it gets built.

  4. 04 On delivery

    Handover, fully owned

    Code, prompts, infrastructure, and documentation ship to your firm. Your team can run it, audit it, extend it. We stay on for support only if you want us to.

Why Astralex

Engineers who understand legal work, building tools lawyers want to keep using.

Most "AI for legal" is a feature list looking for a workflow. We work the other direction: pick one document type that costs your firm real hours and reads differently every time it leaves, build the smallest system that makes it consistent and owned, then expand only where it pays.

We do not ask your firm to change how it practices. We build the system around how it already does — your templates, your tone, your tools, your judgment at the centre. The system carries the repetitive pass; it does not replace the lawyer.

  • Built on Claude Code, end to end.

    We work in Claude Code daily and build with it as our primary tool. The agents we ship use the same patterns we use ourselves.

  • We sit with the lawyer who will use it.

    Discovery means watching how you actually review a contract or draft a motion, then designing the system to fit. Not the other way around.

  • You leave with a system, not a dependency.

    Code, prompts, and infrastructure ship to your firm. It runs in your environment and calls a model endpoint you control — your document store is never handed to a vendor, and the playbook you build is never pooled across customers or fed back to us. Documentation your team can read, extend, and own outright.

Before the call

The questions firms ask before they book.

We would rather answer these in writing than spend the consult on them. If something else is on your mind, it goes first on the call.

  • Do we own the system at handover, or are we renting it from you?

    Outright. At engagement end, the code, prompts, infrastructure configuration, and documentation ship to your firm. The system runs on your infrastructure thereafter — no Astralex licence, no per-seat fee, no remote killswitch. Your team can audit it, extend it, or hand it to another engineer to extend. Any follow-on work with us is optional and separately scoped.

  • Where do our documents live, and what actually gets sent to the model?

    Your documents stay where they already are, on infrastructure you control — we don't copy your document store up to a vendor's cloud the way the hosted AI assistants people are trying do. The system runs in your environment and sends only the specific text each step needs to Anthropic, under your own account and on commercial terms you set — no training on your data, retention you control. The model is a service you point at, not a workspace we host for you. Nothing of yours is stored on our servers, build happens under NDA, and at handover every working copy we used is destroyed.

  • Does our use of the system improve a shared product, or feed anything back to Astralex?

    No. The playbook you build — your positions, your prompts, the refinements you make matter after matter — is yours alone. It ships to you at handover and runs only in your system; nothing you teach it flows back to us or into another customer's system. With the hosted assistants, every customer's edits sharpen one product everyone rents — here, your judgment compounds for you. We store nothing of yours: the build happens under NDA, and at handover every working copy we used is destroyed.

  • What does an engagement actually look like — timeline, our involvement, cost?

    Two to six weeks, fixed fee, no retainer. The lawyer who will use the system sits with us during discovery — a few hours up front, then a weekly check-in of about thirty minutes through the build. We work in your environment with real matter files, under NDA. Scope, deliverables, and price are written into a one-page brief before any work begins; you decide whether to proceed.

  • When the system gets something wrong, who catches it?

    The lawyer signs; the system does not. Every draft or flag is traceable to the fact or position that produced it. Citations are surfaced for check, not buried. The review pass flags its own uncertainty rather than hiding it. Where partner gates sit in the workflow is a decision we make with you during build — Astralex produces first-pass work product, and final responsibility stays with the lawyer who signs.

Book a consult

Find out, in 30 minutes, what one document type would cost to automate.

Bring a document you draft often. We'll scope what an agent could realistically do, what it would take to build, and whether it's worth doing. No pitch deck.

Book a free consult →