Modules

Add to the machine. At published prices.

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 typical delivery estimates confirmed in the order. Nothing is re-priced or re-audited; module builds have no hourly meter. Optional care has agreed hours and preapproved overage. Applicable vendor charges remain separate.

§01The Catalog

Modules at published prices.

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. Development, regression, and acceptance tests use synthetic fixtures. Every band includes operating docs/runbook; each module updates the relevant scoped workflows and docs.

$1,250additional document type. Template grounding, extraction schema, verification ruleset, synthetic test fixtures, reviewer training, in up to two of your jurisdictions; each further jurisdiction for that type is $500. About a week.
$2,000additional integration. A named external system wired in: permissions, audit trail, synthetic test fixtures. About a week.
$1,500additional jurisdiction pack. Jurisdiction rules, authority set, law-change refresh coverage for every document type in your build, including one ordered with it. About a week.
$4,500additional system, one of the six not yet in your build. The full system to the build standard, its own acceptance criteria. About two weeks.

method: one price per module · written order · acceptance criteria per module · 30% on order, 70% on acceptance (the $500 further-jurisdiction line is paid on acceptance of its document type) · never re-priced against your audit · no hourly meter on module builds · typical delivery depends on access and readiness; the order confirms the schedule

modulepricewhat it includestypical delivery
Additional document type$1,250Template grounding, extraction schema, verification ruleset, synthetic test fixtures, reviewer training. Delivered in up to two of the jurisdictions in your build. Law-change refreshes covered under care from then on.1 week
Further jurisdiction for one document type$500The same document type extended to one more jurisdiction already in your build, beyond the two its module includes.With the document type
Additional integration$2,000A named external system wired in: permissions, audit trail, synthetic test fixtures. Slack, meeting capture, practice or document management, email, calendar.1 week
Additional jurisdiction pack$1,500Jurisdiction rules, authority set, and law-change refresh coverage for every document type in your build, including one ordered with the pack.1 week
Additional system$4,500One 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 reviewerNo chargeOnboarding and training inside your care plan hours.Care plan
Volume re-baselineInside care hours where they cover it; otherwise $1,500When your matter volume outgrows the level the build was tested to: synthetic evaluation fixtures, tuning, updated monitoring thresholds.1 week
§02Ordering and Credit

Written order. Written acceptance.

THE ORDERper module · fixed price
paid30/70

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.

  • ◆The order names the module, the price from this page, and its acceptance criteria
  • ◆Built to the same standard as your original system, wired into the machine you already own
  • ◆Synthetic fixtures for development, regression, and acceptance tests, not live client matters
  • ◆Accepted in writing; the balance is due only then
  • ◆New document types receive law-change refreshes under your care plan from then on
  • ◆If modules raise your systems count into a higher care band, care moves to that band the following month

Change requests follow the same written-order path at these prices. Operational activation is separately governed by the written agreement and client permissions. Approved integrations and providers must meet agreed data requirements before activation.

UNUSED SCOPEceilings · not obligations
12 months

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.

  • ◆Usable for twelve months after acceptance, on any module
  • ◆Tradeable across categories during the build: two document types for one integration, for example
  • ◆Not refundable, and it carries no cash value
  • ◆Written into your blueprint so both sides can read the balance

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.

§03What Is a Module, and What Is Not

Care keeps it sharp. Modules make it bigger.

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 covers monitoring, tuning, and corrections within agreed hours; overage is $250/hr only with your prior written approval. Work directly with the founder. Send care requests anytime. Routine requests receive a response within one business day. Business hours: Monday-Friday, 9 a.m.-6 p.m. Eastern Time (America/New_York), excluding U.S. federal holidays. System-blocking incidents take priority, with best-effort assistance outside business hours. A response acknowledges the issue and establishes the next step; it is not a resolution deadline. Resolution depends on the issue and any upstream provider. This is not a 24/7 staffing guarantee. Included care hours and prior written approval for additional work still apply. Software, cloud, and usage costs are separate, identified in the blueprint or module order.

you wantit ishow it is priced
A document type the build does not draft yetModule$1,250, written order
One document type in a third or later jurisdictionModule$500 with the document type
A system not yet in your buildModule$4,500, written order
A new external system wired inModule$2,000, written order
Your existing document types in another jurisdictionModule$1,500, written order
A correction, a tuning pass, a law-change refresh to what you already haveCareInside your monthly care hours
Another attorney or partner trained as a reviewerCareInside your monthly care hours
A template refined, a workflow adjustedCareInside your monthly care hours
More care hours in a heavy monthCare 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, cancellable with 14 days’ notice. Synapse Forge does not switch off the delivered system when care ends; applicable licenses, providers, usage payments, and an assigned operator remain necessary. Ending care does not cancel vendor bills.

FAQ

Modules, without the fog.

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 existing document types, template and workflow refinements, and reviewer onboarding within agreed hours. Work directly with the founder. Send care requests anytime. Routine requests receive a response within one business day. Business hours: Monday-Friday, 9 a.m.-6 p.m. Eastern Time (America/New_York), excluding U.S. federal holidays. System-blocking incidents take priority, with best-effort assistance outside business hours. A response acknowledges the issue and establishes the next step; it is not a resolution deadline. Resolution depends on the issue and any upstream provider. This is not a 24/7 staffing guarantee. Included care hours and prior written approval for additional work still apply. 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.

A jurisdiction pack extends every document type in your build to that jurisdiction, including one ordered with it. A new document type is delivered in up to two of the jurisdictions already in your build; each further jurisdiction for that type is $500. Spark and Forge builds never reach that line. Adding a type and a jurisdiction together is one module and one pack.

More answers on Pricing and How It Works.

MEMORANDUM · MODULE ORDERSSYNAPSE FORGE LLC

Already own the machine? Order in writing.

Existing clients request a written module order through their agreed contact channel; we confirm scope and timing. New firms start with a focused 30-minute Systems Audit. Your report arrives the same business day once the call and any agreed outstanding inputs are complete. No obligation to build. We reply to your inquiry to arrange the call, then provide a written systems recommendation and, if a build fits, a recommended band and price. Timing uses Eastern Time and business days, Monday-Friday excluding U.S. federal holidays. If both requirements are completed on a non-business day, delivery is the next business day. The initial reply is not the completed audit. Do not include client records or credentials in the contact form; an NDA is available before confidential discussion.