A build ships with the scope its band defines, and the band sets which modules can join it later: the audit scopes the price, the price scopes the build, the build scopes the modules. When the practice grows, you add to it in fixed modules: one price each, written down here, with their own acceptance criteria and delivery times. Nothing is re-priced, nothing is re-audited, and nothing runs on an hourly meter.
Every module is built to the same standard as the original system, wired into the machine you already own, and accepted against criteria written into the order. The prices below are the prices; they do not move with your firm's size or your capacity number.
method: one price per module · written order · acceptance criteria per module · 30% on order, 70% on acceptance · never re-priced against your audit · no hourly meter
| module | price | what it includes | typical delivery |
|---|---|---|---|
| Additional document type | $1,250 | Template grounding, extraction schema, verification ruleset, test fixtures, reviewer training. Law-change refreshes covered under care from then on. | 1 week |
| Additional integration | $2,000 | A named external system wired in: permissions, audit trail, test fixtures. Slack, meeting capture, practice or document management, email, calendar. | 1 week |
| Additional jurisdiction pack | $1,500 | Jurisdiction rules, authority set, and law-change refresh coverage for the document types already in your build. | 1 week |
| Additional system | $4,500 | One of the six systems not yet in your build (Intake & Routing, Document Production, Verification Gates, Meeting Intelligence, Knowledge Layer, Follow-Through), built to the same standard and wired to the existing machine, with its own acceptance criteria. | 2 weeks |
| Additional named reviewer | No charge | Onboarding and training inside your care plan hours. | Care plan |
| Volume re-baseline | Inside care hours where they cover it; otherwise $1,500 | When your matter volume outgrows the level the build was tested to: evaluation fixtures, tuning, updated monitoring thresholds. | 1 week |
Thirty percent on the written order, seventy on acceptance against the criteria the order names. Nothing is built on an unquoted request, during the build or after it.
Change requests during a build follow the same path: quoted in writing at these prices before any work begins.
Your band's counts are ceilings. Scope your number bought but you chose not to build does not vanish; it converts to credit at the prices on this page.
Choosing a larger band at build time still costs less than adding the same scope as modules later. Credit exists so that a generous blueprint never becomes wasted money.
The line is simple. Anything that adds a capability the build did not have is a module. Anything that keeps the capabilities you have running well is care. Modules are fixed prices. Care is included hours, and anything beyond them is billed only with your written approval first.
| you want | it is | how it is priced |
|---|---|---|
| A document type the build does not draft yet | Module | $1,250, written order |
| A system not yet in your build | Module | $4,500, written order |
| A new external system wired in | Module | $2,000, written order |
| Your existing document types in another jurisdiction | Module | $1,500, written order |
| A correction, a tuning pass, a law-change refresh to what you already have | Care | Inside your monthly care hours |
| Another attorney or partner trained as a reviewer | Care | Inside your monthly care hours |
| A template refined, a workflow adjusted | Care | Inside your monthly care hours |
| More care hours in a heavy month | Care overage | $250 an hour, only with your written approval beforehand |
Care plans and their included hours are on Pricing. Care is optional and month to month; if it ends, the system keeps running and stays yours.
Because a quote invites a second audit, and the audit was the point of the first one. Each module carries one published price, its own acceptance criteria, and a typical delivery time. You can budget growth a year out, and nothing about your original price is reopened.
At build time. Choosing the next band up adds a system, a document type, an integration, and a reviewer together for less than the same modules cost separately afterwards. That is by design: the band the audit recommends is meant to be the rational purchase, a larger band is the rational upgrade, and modules exist for growth you could not have scoped on day one. The audit scopes the price, the price scopes the build, and the build scopes the modules.
No. Care covers monitoring, tuning, corrections, law-change refreshes to the document types you already have, template and workflow refinements, and reviewer onboarding. A new document type, system, integration, or jurisdiction is a module at the prices on this page. If modules raise your systems count into a higher care band, care moves to that band the following month.
During the build, yes. Your band's counts are ceilings, not obligations: scope your band includes but you choose not to build converts to credit at these prices, usable for twelve months after acceptance on any module, or traded across categories while the build is underway. Credit is not refundable and has no cash value.
More answers on Pricing and How It Works.
Existing clients order modules through their care channel and receive the written order back within two business days. New firms start where every build starts: a free Systems Audit, a written map of where the hours go, and a number fixed in writing.