DAGR hello@dagr.consulting

Digital Asset Governance & Risk

The risk is already on your servers.

Twenty years of records, half-documented systems, and data nobody ever classified — and now there's pressure to point AI at all of it.

DAGR maps what you actually hold, what you're obligated to keep, and what it's costing you to keep the rest. Then we give you something defensible in writing.

Start a conversation Scoping call, no charge · Remote or on-site

Signals

You already know if this is you.

  • ▸Legal asked for the current retention schedule and nobody could produce one.
  • ▸An AI pilot is queued against data whose provenance and licensing nobody has checked.
  • ▸A system the business runs on sits on a framework that stopped receiving security patches.
  • ▸Your data map is a spreadsheet someone maintained until they left.
  • ▸Your assistant works out of your account, so the audit log says every one of those actions was you.
  • ▸You are keeping everything forever because deleting anything feels riskier than storing it.

Engagements

DAGR‑400

Identity Delegation

Your assistant — human or AI — should not have to become you to do the work. Scoped access per task, held under their own identity, with written authority limits and a revocation procedure you have actually rehearsed.

Read the brief →
Typical
3–4 weeks
You get
Delegation map + scoped access design
DAGR‑100

AI & Data Governance

Provenance, licensing, and access review of the data behind your models. An internal AI use policy your counsel will actually sign. Documented approval paths, so the answer to "who signed off on this" is a record instead of a hallway conversation.

Typical
4–6 weeks
You get
Governance framework + risk register
DAGR‑200

Records & Retention

Current-state data map across the systems that actually hold records. A retention schedule by record series, defensible disposition you can execute without flinching, and e-discovery readiness before the hold letter arrives.

Typical
3–5 weeks
You get
Data map + retention schedule
DAGR‑300

Legacy System Risk

Assessment of unsupported .NET Framework, WinForms, and end-of-life dependency surface — with a modernization sequence that de-risks the business instead of stalling it. Written by someone who has done the migrations, not just costed them.

Typical
2–4 weeks
You get
Risk assessment + phased plan

Jared Henry

Principal · Tulsa, Oklahoma

Two decades inside line-of-business .NET systems — building them, maintaining them, and migrating them off frameworks that outlived their support windows. The kind of work where the documentation is the source code and the person who wrote it retired in 2014.

That's the vantage point DAGR brings to governance. Policy that ignores how the systems are actually built becomes shelfware. Every deliverable here is written to survive contact with the codebase and the audit.

Tell me what you're holding and what you're worried about.

A thirty-minute call is usually enough to tell whether there's an engagement here. If there isn't, I'll say so.

Email DAGR hello@dagr.consulting