AI Register · the as-is layer

Your AI Register, in a week.

Most firms can't name the AI they already run. Ansatz discovers your company-wide AI estate bottom-up — every agent, copilot, AI-enabled SaaS feature and shadow script — into one as-is register: what AI you run, who owns it, and what data it touches.
Bottom-up discovery — interviews, tool ingest, repo scan Discovery & advisory only — RDG-free, your data stays yours
ansatz · your-org · ai-registerdiscovered
AI estate · what you actually run
agentClaims FNOL triage agentendpoint
copilotM365 Copilot · Underwritingingest
saasSalesforce Einstein scoringingest
scriptReserving GPT macro (Excel)interview
agentBroker-email intake botrepo-scan
Provenance-tagged · confidence-scoredSee the full sample →
The honest anchors: GDPR Art. 30 ROPA AI-Act Art. 4 AI-literacy ISO 42001 NIST AI RMF · GOVERN 1.6
The blind spot

You can't govern, prioritise or verify the AI you can't even name.

Ask a regulated firm to list the AI it runs and you get the three or four official projects. The real estate is far larger — and most of it is invisible to the org chart: copilots switched on inside SaaS, models embedded in vendor features, and shadow AI living in browser tabs and Excel.

Browser tabs
Employees paste work into public chatbots all day — never logged, never reviewed, invisible to IT.
SaaS toggles
An AI feature flipped on inside a tool you already pay for is AI you now run — and nobody recorded it.
Excel & scripts
A spreadsheet macro calling a model is shadow AI — quietly making decisions with zero oversight.
Before any roadmap, any governance, any verification — there's a prior question almost no firm can answer: what AI do you actually run, and what does it touch? The AI Register answers it.
How the register is populated

Three discovery sources, cross-corroborated.

No single source sees the whole estate. We triangulate the deep human layer with what your tools already know and what your code reveals — every row tagged with where it came from.

The deep layer
1

Bottom-up employee interviews

The same adaptive agent behind the use-case map asks people what AI they actually reach for — the public chatbot in the browser, the copilot, the spreadsheet trick. This surfaces the shadow AI no scan can see.

→ interview
2

Ingest from tools you already run

Read-only pulls from the admin surfaces you control — SaaS licence and copilot usage, identity/SSO app lists, model-gateway logs — to enumerate the AI features quietly switched on across the estate.

→ ingest · endpoint
3

Repo & config scan

A scan of code and config for model SDKs, API keys to AI providers, prompt strings and agent definitions — catching the home-built bots and scripts that never appear in any licence or org chart.

→ repo-scan
Each system carries a provenance tag and a confidence dot — the more independent sources agree, the higher the confidence.
A discovered estate · sample

What an AI Register actually looks like.

Eight rows from a synthetic DACH-insurer estate — agents, copilots, embedded SaaS features and shadow scripts, each with its discovery provenance and a confidence read.

AI estate register · your-org · as-is 8 systems · 3 functions · 2 shadow
SystemKindFunctionData / PIIProvenanceConfidence
Claims FNOL triage agent
Routes first-notice-of-loss, drafts acknowledgement
agent Claims PII · health interviewendpoint high
Broker-submission intake bot
Extracts risk fields from broker emails → UW workbench
agent Underwriting PII repo-scaninterview medium
M365 Copilot · Underwriting
Drafting & summarisation inside Office
copilot Underwriting PII ingest medium
Salesforce Einstein lead scoring
Vendor model embedded in CRM
saas-feature Customer Service PII ingestendpoint high
Policy-wording Q&A assistant
Internal RAG over wordings & guidelines
agent Customer Service no PII repo-scaningestendpoint high
Fraud-flag classifier
Built with Ansatz advisory · pilot
model Claims PII manualinterview medium
Reserving "GPT macro" (Excel)
Shadow AI — actuary pastes into a public chatbot
script Actuarial PII interview low
Browser-based contract summariser
Shadow AI — public tool, never reviewed
script Broker Operations PII interview low
high — 3+ sources / endpoint-confirmed medium — two sources agree low — single source, uncorroborated Confidence is derived from cross-source corroboration — never asserted.
Synthetic demo data. A real register carries owner, business purpose, value hypothesis, model & endpoint per row — the full AISystem schema.
What the register feeds

One register. Two honest exits.

Each row forks by what it is. As-is systems feed an Ansatz roadmap. Live, non-conflicted agents can cross a one-way handoff to independent verification — Ansatz never inventories the agents it's paid to verify.

Exit 1 · stays with Ansatz

As-is row → transformation roadmap

Every system in the estate — its business purpose, owner, data classes and value hypothesis — becomes a row in the as-is map that feeds the Ansatz use-case roadmap: what to consolidate, what to retire, where the next AI opportunity actually is.

register rowvalue hypothesisprioritised roadmap

Advisory & discovery is Ansatz's lane. The full register — PII flags, advisory context and all — stays here.

Exit 2 · one-way handoff

Live agent → independent verification

A live, non-conflicted agent with a callable endpoint is eligible for a sanitised, one-way handoff to a separate assurance venture's behaviour-anchored agent register — for verification, on its own terms.

agent rowconflict-filtersanitised subset
The firewall. Only name · kind · endpoint · model · system-prompt? · line · function cross. Never PII, owner, advisory context, value hypothesis or secrets. Rows Ansatz built or advised carry a conflict flag and are excluded — so the verifier's independence stays visibly un-bought.
Why a register, honestly

Real anchors — no manufactured deadline.

An AI inventory is increasingly buyer-pulled and standards-shaped. Here's the honest case, separated into what already applies and what the market is asking for.

📑

GDPR Art. 30 — Records of Processing

In force

Your ROPA already has to list processing activities and the personal data behind them. An AI estate register that flags PII per system makes the AI slice of that record far easier to keep honest and current.

🎓

EU AI Act Art. 4 — AI literacy

Applies since 2 Feb 2025

Providers and deployers must ensure staff have a sufficient level of AI literacy. Knowing which AI systems your people actually use is the natural starting point for a credible, role-aware literacy baseline.

🧭

ISO/IEC 42001 — AI management

Buyer-pull

An AI management system expects you to maintain an inventory of AI systems in scope. Buyers and certifiers increasingly ask for it — the register is the artifact that answers the question.

🛡️

NIST AI RMF — GOVERN 1.6

Buyer-pull

The framework calls for an inventory of AI systems, maintained and resourced by risk. A living, provenance-tagged register is exactly that inventory — voluntary, but increasingly expected in diligence.

Honest framing: we don't claim a register makes you "compliant", and we cite no high-risk deadline — the EU Omnibus deferred high-risk obligations toward Dec 2027. A register is the as-is foundation that makes all of the above tractable.
Engagement · planning estimate

Start free. Get the register in a week.

An on-ramp by design: self-serve discovery is free, the full register is a fixed, fast engagement, and it pulls naturally into Ansatz's roadmap or independent verification. Figures are planning estimates, not quotes.

Step 0 · On-ramp

Self-serve discovery

Free self-serve
A guided scan + a short team questionnaire that returns a first-cut estate sketch — enough to see how much AI you're running that you couldn't name. The top of the funnel.
↳ first-cut estate sketch
The product
Step 1 · Register

Register in a week

~€5–15k est.
The full company-wide AI Register — interviews + ingest + repo scan, every row provenance-tagged and confidence-scored, mapped to the shared AISystem schema. Delivered in a week.
↳ full register · provenance · confidence
Step 2 · Downstream

Roadmap or verify

Pulls downstream
The register feeds an Ansatz transformation roadmap, or hands a sanitised live-agent subset to independent verification. The register is the on-ramp; the value compounds downstream.
↳ roadmap · or one-way handoff
All figures are planning estimates for mid-market DACH FS, labelled as such — final scope is set per engagement. Free discovery is the on-ramp; the register is the wedge; the roadmap and verification handoff are the downstream pulls.
⚡ FROM "WE DON'T KNOW" TO ONE REGISTER

Find out how much AI you're already running.

Start with the free self-serve discovery, or have us deliver the full company-wide AI Register in a week — provenance-tagged, confidence-scored, and ready to fork into a roadmap or independent verification.

Day 0 Ingest tool admin surfaces + run the repo scan Day 1–4 Interview the people who hold the shadow AI Day 5 Deliver the corroborated, provenance-tagged register