Private AI deployment
Design, pilot and deploy legal AI that runs inside your own perimeter: models you control, retrieval over your own documents with the permissions you already enforce, and an evaluation record built from your matters rather than a vendor's demo.
Why architecture beats assurance
A vendor's data-processing agreement limits what a supplier may do. It does not change the fact that client content leaves your systems. For firms with confidential, high-profile or regulated clients, that transfer is the problem — and the only complete answer is a model that runs where your documents already live.
- Open-weight models are now genuinely useful for focused legal tasks with retrieval
- Inheriting DMS permissions solves confidentiality structurally, not contractually
- An evaluation record built on your own matters is defensible; a vendor benchmark is not
Stated in advance, delivered as described.
Readiness and feasibility
What is in use today, what a private layer would replace, which hardware or private tenancy fits your size, and what it costs to run per month — in writing, before you commit to anything.
Architecture and build
Hosting, networking, key management, logging and matter walls, designed for your environment and documented for your IT lead and your insurer.
Model selection and licensing
Which open-weight family, which size, which quantisation — and a licence review so you know what you may do with it commercially, indefinitely.
DMS-scoped retrieval
Retrieval over precedents and matters that respects ethical walls and permissions rather than bypassing them. This is where most private AI projects succeed or fail.
Evaluation harness
Fifty to 150 tasks drawn from your own matters, scored by your fee-earners, with the results and failure modes documented.
Governance pack
DPIA, register entry, policy updates, vendor diligence notes and an incident runbook.
Training and handover
Fee-earner sessions, administrator runbooks and a named internal owner, so the capability outlives the project.
Four steps, no surprises.
Assessment
Ten working days to establish what is in use, what is feasible and what it costs. Fixed credited against a pilot if you proceed.
Pilot
Four to six weeks on a scoped document set: model chosen, retrieval wired, evaluation run with your fee-earners, security and DPIA documented.
Deployment
Six to ten weeks to production: full retrieval scope, access controls, monitoring, training and the governance pack.
Managed
Optional retainer a month: model updates with regression evaluation, quarterly re-testing, register upkeep and incident support.
Fixed numbers. The invoice matches the proposal.
| Engagement | Cost | Turnaround | What it covers | |
|---|---|---|---|---|
| AI readiness assessment | $3,000 – $4,000fixed · 10 working days | ~10 working days |
The honest starting point: what AI is actually in use, what data it touches, what it would take to run any of it privately, and what to fix first.
|
Contact us → Estimated range $3,000 – $4,000 · how quotes work |
| Private AI pilot | $12,000 – $18,000from · 4–6 weeks | 4–6 weeks |
A controlled pilot of a private model on your own matters, so the decision to deploy is made on evidence from your documents rather than a vendor demonstration.
|
Contact us → Estimated range $12,000 – $18,000 · how quotes work |
| Private AI deployment | $23,000 – $45,000from · 6–10 weeks | 6–10 weeks |
Design, build and hand over a private AI capability your firm owns: models inside your perimeter, retrieval scoped to your own precedents, and an evaluation record that satisfies a regulator or an insurer.
|
Book the free check → No charge, no obligation · findings yours either way |
| Managed private model | $1,900 – $3,500 / monthper month | Continuous |
We keep the deployment healthy and the governance current: model updates, evaluation re-runs, prompt and policy revisions, and a quarterly board note.
|
Contact us → Estimated range $1,900 – $3,500 / month · how quotes work |
Payment. 50% on booking, 50% on delivery unless the option says otherwise. Card payment through Stripe, or invoice with bank transfer. Card details never touch our servers. Larger deployments are billed to milestones agreed in writing before work starts.
- Firms with confidential or high-profile client bases where public tools are a hard no
- Firms whose AI use is currently blocked and needs to become possible
- Firms paying per-seat licensing for capability they could own
- Firms asked by a client or insurer where their data actually goes