AI systems for regulated work
Agentware builds retrieval, proposal, and forecasting systems for teams that have to defend the output — to a client, an auditor, or a board. Each one shows the evidence it used.
What is our liability cap on the Meridian agreement?
Liability is capped at , with carve-outs for . The cap does not apply to .
Each party's aggregate liability shall not exceed the total fees paid in the twelve (12) months preceding the claim.
The limitation in §11.2 shall not apply to breaches of Section 9 (Confidentiality) or Section 13 (IP Indemnity).
Nothing herein limits liability for gross negligence, wilful misconduct, or fraud.
What we build
Each takes a corpus nobody can read end to end and returns something a person can act on — attached to the evidence that produced it. The habit is the same across all three: never assert without a citation.
DocumentsGrounded answers
Search across contracts, tickets, wikis, and PDFs that answers in sentences instead of returning ten links. Every claim carries the passage it came from.
RFPsDrafted responses
A 300-question security questionnaire, drafted against your real policies and every answer you have already won with. Your team edits instead of writing.
HistoryForecasts with intervals
Demand, load, spend, and headcount — projected with a range, not a single number. Planners see how much confidence the forecast actually deserves.
How we work
Most failed AI projects were never evaluated — they were demoed. We invert it: build small on your real data, grade it against a test set your experts wrote, then ship.
We start on your documents, not a demo corpus. By the end of the second week there is something you can put questions to and judge for yourself.
Out: a working prototype and a candid read on feasibility
We build a test set with your subject-matter experts and score against it. You see accuracy as a number you helped define, not a claim we make.
Out: an eval harness you keep and can re-run
Your cloud, your identity provider, your retention rules. Where data residency or model choice is constrained, that constraint shapes the design from the start.
Out: a deployment your security team has actually reviewed
Runbooks, retraining schedules, and a walkthrough with the people who will own it. The goal is that you stop needing us.
Out: documentation, handover sessions, no lock-in
What we build with
Contact
The useful first conversation is about a specific decision — which clauses put us at risk, which questionnaire is due Friday, how many units to hold in Q3. Tell us that, and we’ll tell you whether this is worth building.
Worth including
The link opens a draft with these as headings. Delete whatever doesn’t apply.