The decision-support
layer.
Fixed scope, quoted from the audit. Your knowledge structured into a governed retrieval layer, the assistant in your workflows, evaluation baselines, and the full governance pack — cloud or on-premise.
A working system, not a deck.
The assessment tells you where work gets stuck. The build is the thing that unsticks it: a governed layer your people can ask, and put to work, inside the systems they already use.
Scope is fixed and quoted from the audit evidence. If the document estate is worse than the audit assumed, we change-order it — we do not eat a surprise data-cleaning project inside a fixed fee.
- 01A governed knowledge layerYour SOPs, policies, archives, and systems structured into one retrievable layer — with owners, access boundaries, and provenance.
- 02The assistant, in the workflowAsk and Act surfaces embedded where the work happens — not a chatbot off to the side. Humans approve anything that matters.
- 03Evaluation baselinesRelevance, groundedness, and citation accuracy scored before go-live. The harness is yours. Later changes get graded against the same instruments.
- 04The governance packAccess controls, human-approval thresholds, audit trails — aligned to NIST AI RMF and ISO/IEC 42001, designed to be operated, not filed.
- 05Cloud or on-premisePrivate cloud tenancy, or the full system on your servers. You own the data, the knowledge base, and every output — in machine-readable form.
Two typical builds. One fixed quote.
One domain, tightly held
A single knowledge domain, one or two sources, human-in-the-loop, and a basic governance pack. Typical duration: 4–8 weeks. Quoted from the audit.
Right when you want a first working layer the frontline will actually use.
Multi-source, production-ready
Multiple sources, citations, the evaluation pipeline, role-based access, and the full governance pack. Typical duration: 8–14 weeks. Quoted from the audit.
Right when the knowledge is spread across systems and the answers have to hold up to an auditor.
The people you meet are the people doing the work. Senior delivery, not a pyramid. The assessment fee is credited against a build signed from it.
Assess → build → run.
The readiness assessment
Fixed fee, two scopes. Ends with a scorecard, a friction map, and a 90-day roadmap — the evidence the build is quoted from.
See the two scopesYou are here
Fixed scope. Named artifacts. Evaluation and governance in the box, not as a follow-on.
The monthly operating rhythm
Not maintenance. A cadence: alignment, frontline work, one or two workflows shipped, training — scored on a board your team owns.
See how it runs