Configured, not coded.
Most legal software is a stack of separate products — one for injury-plaintiff work, one for insurance defense, another for corporate legal — each hard-coded, each maintained by its own team, each priced to carry that maintenance (per seat, forever). LexSteward is built the opposite way.
One platform · flat per firm, never per seat · adapts in days, not quarters
A set of universal engines, configured for your firm.
LexSteward is a small set of universal engines — a matter engine, a billing engine, a docket/deadline engine, a compliance engine, and a client-acquisition engine — that are configured for your firm’s practice, your side of the “v.”, and your jurisdiction. A plaintiff firm’s version, a defense firm’s version, and a fractional GC’s version are the same engines configured differently — not different products. Adding a practice area, a side, or a jurisdiction is a configuration change, not a coding project.
Five engines. One system.
Every LexSteward firm runs on the same engines. What changes between firms is how they’re configured — not which product you bought.
The matter engine
Matters, parties, documents, and a system of record that runs a file the same way whatever the caption says — plaintiff, defense, or an internal legal request.
The billing engine
Time, invoices, and client payments — configured to contingency, flat-fee, hourly, or an internal cost-center model, on one flat per-firm price.
The docket & deadline engine
Court-rule and calendar-based deadlines computed for your jurisdiction and matter type, so nothing slips wherever you practice.
The compliance engine
Disclaimers, data residency, tracking consent, and an approval gate that turn on by configuration for your practice and region — conservative by default.
The client-acquisition engine
Get-found tools and intake, configured to how your kind of firm actually wins work. Live today for consumer/plaintiff lead-gen; the defense and in-house configurations are in design.
One platform serves plaintiff, defense, and in-house.
That’s the whole point of building it this way: the firm across the table and the internal legal team run on the same engines you do — configured for their side, their billing model, and their jurisdiction.
A plaintiff firm
Get-found calculators and consumer intake on top of the matter, billing, and docket engines — configured for contingency work.
Explore →A defense firm
The same matter, billing, and docket engines run the defense docket; acquisition is configured for authority and referral, not consumer lead-gen.
Explore →A fractional / in-house team
The engines configured to manage outside counsel and control legal spend — a cost-center billing model, not client billing.
Explore →Configuration, not a coding project.
The usual model funds a separate hard-coded product for every practice and every side, then charges per seat — forever — to keep each one alive. Configuring one platform doesn’t carry that cost, so the price is flat per firm and a change ships in days, not quarters. To be clear about what that does and doesn’t mean: the system does the research and drafting — you’re not handed a blank builder to run yourself, and you’re not doing the legwork. But you’re the licensed attorney, so you review and approve the configuration it proposes; nothing legal goes live until you approve it. The win is speed and cost, with the correctness call staying yours.
Straight answers.
So can I configure the system myself?
You don’t have to, and you don’t start from a blank builder. The system does the legwork — it researches your practice area, your side of the “v.”, and your jurisdiction and drafts a proposed configuration. But you’re the licensed attorney, so you review and approve what it drafts; nothing legal goes live until you sign off. The benefit is speed and cost, with the correctness call staying yours — not do-it-yourself, and not something we decide for you.
What actually changes between a plaintiff, defense, and in-house setup?
The engines are the same; the configuration differs — which get-found tools are switched on, the billing model (contingency, hourly, or an internal cost center), the intake flow, and the jurisdiction rules that drive deadlines. It’s one platform configured three ways, not three different products.
Why does “configured, not coded” make it cheaper?
The usual model builds a separate hard-coded product for each practice and each side, then charges per seat, forever, to fund the engineering that keeps each one alive. One configurable platform doesn’t carry that cost — so the price is flat per firm instead of per seat, and you’re not funding a company just to keep a hard-coded system running.
How fast can a new practice area or jurisdiction go live?
Because adding a practice area, a side, or a jurisdiction is a configuration change rather than an engineering project, the system can draft it in days, not quarters. It assembles the proposed configuration; then you — the licensed attorney at your firm — review and approve it before anything legal goes live, so “fast” never means “unchecked,” because you’re the one checking it. We don’t staff attorneys for your jurisdiction; the review that counts is yours.
One platform, configured for the way you practice.
Plaintiff, defense, or in-house — the same engines, set up for your side and your jurisdiction, flat per firm.