Craft AIConsulting & AssessmentAI Governance Consult

ConsultingDelivery

AI Governance Consult

A cap that blocks before the call. A cost owner before the invoice.

Requests
Governance layer
Models

The cap blocks before the call. It doesn’t alert after the invoice.

1Inventoryowner, purpose and cost
2Layered caps
3Routing by task
4Context reuse
5Auditanomalous patterns trigger action
We measure
Caps block, not alert
% of calls to the frontier model
Cache hit rate
Assets with an owner: 100% · cost per resolution
Sound familiar?
  • Nobody can say who owns the AI cost. The invoice arrives weeks after the spend.
  • The model was chosen on prototype day and never touched again.
  • Someone can change the prompt in production today and it goes unrecorded.
“The AI bill doubled and I can’t say for which feature.”
What we do
  • Inventory: every AI asset (model, prompt, RAG base, fine-tune) with owner, purpose, criticality and cost.
  • Layered caps: per call, conversation, user per day, area per month. Cut before the call.
  • Routing by task: each task type gets an alias; the alias points to the smallest model that does the job.
  • Context reuse: what repeats is cached; cache reads cost a fraction of the price.
  • Audit and anomaly patterns: everything logged; volume, repetition and attempts to extract instructions trigger action.
Gateway · starts open source
An LLM gateway as the entry point, starting with open source. If you already run Bedrock or Azure APIM, the policy goes there.

Routing is an architecture decision by task alias, not a product. No platform of ours, no lock-in.

How it works
  1. AI invoice audit: 1 week.
  2. Layer in production: 4 to 10 weeks, fixed scope. Caps, aliases, cache and audit trail.
  3. Enterprise layer: policy per area and AI FinOps in your team.

Start with the 1-week AI invoice audit.

Scope and timeline agreed before you sign. You see the result of each step before deciding on the next.