Tier 3 · scoped build
Vertical management system
The system of record for one regulated workflow, with retrieval and grounding native to it rather than bolted on afterwards.
Who this is for
An organization running one regulated workflow across spreadsheets, email and a general-purpose tool that was never built for it.
From
$35,000
- Typical
- $50,000 to $140,000
- Other currencies
- €31,900 · £26,900 · S$46,000
Thirty minutes with the engineer who would run the work, before any paperwork.
The work, stage by stage
In order, with what happens at each phase and what it produces. Phases rather than dates, because a build is scoped per engagement and the catalog deliberately publishes a price band instead of a duration.
One workflow, named and bounded
Phase 1
Matter management, claims intelligence or a compliance evidence workspace: one of them completely, rather than three partially. The scope decision is taken here and then held.
Model the records and the obligations
Phase 1
The entities, their states and the transitions between them, with the regulatory obligation attached to each state modeled as part of the record rather than left as a reminder in someone's calendar.
Build the system of record
Phase 2
The workflow, the permissions and the audit trail first, because a system of record that cannot evidence who changed what is not one.
Retrieval and grounding, native
Phase 3
Search and question-answering across the records and their attachments, citing the document and the passage, inside the same permission model as the records themselves. Retrieval that ignores record permissions is a data leak with a search box.
Evaluation and the release gate
Phase 4
The same groundedness gate a standalone retrieval build gets, because the AI half of this is a retrieval system and regresses like one.
Migration, deployment and handover
Phase 5
Existing records migrated with a reconciliation count, deployed in your environment, with the architecture document and the runbook.
Everything that arrives, listed
What is handed over at the end, and what you own of it. If something here would not be useful to you, say so before we start and the scope changes.
- The running system of record, deployed in your environment, with permissions and an audit trail
- Source code for the system written for you, which you own on payment in full under our terms
- A data model documenting entities, states, transitions, and the obligation attached to each state
- Native retrieval and grounded question-answering, inside the same permission model as the records
- The evaluation harness and CI gate for the retrieval half
- A migration with a reconciliation count, so you can prove nothing was lost
- An architecture document and a runbook, written for the team that will own it
What this covers, and who takes the rest
Stated up front, because scope is what derails an engagement in week two rather than at the proposal.
Inside this build
- One named workflow, modeled end to end, with its obligations part of the record
- Permissions, audit trail, and permission-aware retrieval
- Migration of existing records, with reconciliation
Handled separately
Named so you can plan and budget for it, whether we do it or somebody else does.
- Integrations with systems whose owners have to build the other half
- Ongoing operation after handover, which the Operate retainer covers
Start with a call, not a proposal.
Thirty minutes, straight to the engineer who would run the work. We will tell you if a smaller engagement answers your question, or if nothing here does.
Typical reply within one business day · Engagements start at $2,500
Scoped per engagement