Podcast Blog Course
Tools AI Readiness Assessment KPI Dashboard Governance Framework Agentic Pricing Framework All tools →
About Subscribe
My Account Log Out

AI Governance Framework
for Mid-Market SaaS

A principles-based governance framework for PE-backed software companies navigating AI adoption.

1. Purpose & How to Use This Framework

Purpose

This framework provides a structured approach to AI governance for mid-market SaaS companies operating between $10M and $500M ARR. It is designed with particular relevance for PE-backed organizations navigating the pressure to adopt AI quickly while protecting the operational integrity and enterprise value that acquirers and investors scrutinize most closely. Governance here is not a compliance checkbox or a risk management tax on your engineering team. It is the infrastructure that lets you move faster with confidence — clear ownership, known risk tolerances, and repeatable controls that hold up when the board, a prospective acquirer, or a regulator asks how you govern AI in your business.

How to Use This Framework

This framework can be adopted as a complete governance program or used selectively by domain depending on where your organization has the most immediate exposure. If you are standing up governance from scratch, working through the domains in order provides a logical build sequence — policy and program management first, then risk, compliance, ethics, explainability, and vendor governance. If you already have partial governance in place, each domain is fully self-contained and can be read, assessed, and implemented independently without requiring the others.

Every domain follows the same seven-component structure to make adoption consistent and assessment straightforward: a Domain Statement that defines scope and intent; a Governing Principle that anchors the domain to a durable standard; a Maturity Model with five levels from ad hoc to optimized; a RACI Table assigning accountability across typical mid-market roles; Governance Indicators that signal whether controls are operating effectively; Industry Alignment mapping the domain to relevant frameworks (NIST AI RMF, ISO/IEC 42001, EU AI Act); and a PE Due Diligence Signal translating each domain into language and evidence that surfaces in M&A and growth equity processes. The number of RACI activities and governance indicators varies by domain — some domains have more distinct accountability surfaces than others — but the seven-component structure is consistent throughout.

Establish Your Baseline

Before working through the domains, the fastest way to establish your current state is to complete the JustKeenAI AI Readiness Assessment at assess.justkeenai.com. The assessment covers six dimensions of AI readiness; your Governance & Risk dimension scores map directly to maturity levels across all six domains, giving you a prioritized starting point rather than a blank slate.

Your Assessment Question Framework Domain
"Does your company have a formal AI governance policy?" Domain 1: AI Policy & Program Management
"How are AI-related risks (bias, hallucination, data privacy, regulatory) managed?" Domain 2: AI Risk Management
"Are there regulatory or compliance requirements in your industry affecting AI deployment?" Domain 3: Regulatory & Compliance Readiness
"Does your company have an AI ethics framework?" Domain 4: AI Ethics & Responsible Use
"How prepared is your organization to explain AI-driven decisions?" Domain 5: Explainability & Audit
"How does your organization govern AI vendors, sub-processors, and supply chain dependencies?" Domain 6: AI Vendor & Supply Chain Governance

2. Governing Principles

These seven principles underpin every domain in this framework. They are not aspirational values — they are the load-bearing assumptions that determine whether a governance control is real or cosmetic. When in doubt about a governance decision, test it against the applicable principle first.

Principle 1
Human accountability is non-delegable.

An AI system cannot be the accountable party. Every AI capability has a named human owner — a person with a title, a reporting line, and explicit responsibility for what the system does and the decisions it influences.

Why this matters: When an acquirer asks "who is responsible for this AI system?" the answer must be a person, not a team name or a model version. Diffuse or absent accountability is one of the most common findings in AI-related due diligence gaps.
Principle 2
Evidence over policy.

A governance control that cannot produce evidence of enforcement is a governance gap, not a governance control. The question is never "do you have a policy?" — it is "what evidence exists that the policy is followed?"

Why this matters: Policies that exist only in documents do not survive due diligence. Auditors and acquirers ask for training records, scan results, audit logs, and incident reports. A well-written policy with no evidence trail is worse than acknowledged absence, because it suggests the organization doesn't know the difference.
Principle 3
Governance scales with blast radius.

The rigor of oversight is proportional to what the AI system can do, spend, or break. A copilot suggestion that a human reviews before acting gets lighter governance than an agent with production write access or the ability to send communications on behalf of the company.

Why this matters: Over-governing low-risk tools kills adoption and drives shadow AI. Under-governing high-risk agents creates liability that doesn't surface until something goes wrong. Right-sizing oversight requires knowing the blast radius before deploying.
Principle 4
Shadow AI is a governance failure, not a user failure.

When employees adopt unsanctioned AI tools, the governance program has failed to provide a viable sanctioned path. The right response is not punishment — it is discovery, followed by either enablement or risk-justified prohibition with a supported alternative.

Why this matters: Prohibition without alternatives produces hidden risk, not safer behavior. The fastest way to reduce shadow AI is to give people sanctioned tools that are at least as capable as what they found on their own, with clear guardrails that don't require them to think hard about compliance.
Principle 5
AI incidents are distinct from cyber incidents.

Model hallucination, bias drift, prompt injection, agent misbehavior, and output toxicity require their own response playbooks. Cyber incident response plans are built for different failure modes and different stakeholders.

Why this matters: A cyber IR plan does not cover "our AI recommended a harmful action to a customer" or "our agent sent 10,000 emails before anyone noticed." Different failure modes require different ownership, different escalation paths, and different post-incident analysis. Conflating them produces slow, confused responses.
Principle 6
Vendor governance is supply chain governance.

AI providers — model APIs, fine-tuning platforms, inference infrastructure — are critical operational dependencies, not interchangeable SaaS utilities. Concentration risk, data residency, model versioning, and contractual exit provisions for AI vendors carry different risk profiles than typical software procurement.

Why this matters: A company whose entire AI capability runs through a single provider has a single-vendor dependency at the infrastructure layer. That is a board-level risk in any PE portfolio company, and it is the kind of risk that appears as a finding in a quality-of-earnings review if not proactively documented and managed.
Principle 7
Governance enables velocity.

The purpose of this framework is not to slow AI adoption — it is to make adoption sustainable. A well-governed AI program moves faster because teams have clear boundaries, approved tools, known risk tolerances, and incident playbooks ready before they need them.

Why this matters: Ungoverned AI programs do not move faster; they move faster until the first significant incident, then they stall while leadership decides what to do. The companies that will compound AI advantage over time are the ones that build governance infrastructure early, not the ones that sprint without guardrails and then stop to clean up.

3. Governance Domains

Each domain follows the same seven-component structure: Domain Statement, Governing Principle, Maturity Model, RACI Table, Governance Indicators, Industry Alignment, and PE Due Diligence Signal. Domains 1 and 2 are available below. Domains 3–6 are available with an Insider membership.

3.1  AI Policy & Program Management

Assessment link: "Does your company have a formal AI governance policy?"

Domain Statement

This domain covers the foundational policy infrastructure that makes every other governance domain enforceable. AI Policy & Program Management defines the organizational scope of AI governance, establishes acceptable-use boundaries across all AI systems, codifies approval workflows for new AI tool adoption, and sets a review cadence that keeps policy current as the technology and regulatory landscape evolve. Critically, this domain explicitly addresses shadow AI — tools adopted outside IT procurement — because an AI governance program that only covers sanctioned tools has a large, invisible blind spot.

Governing Principle

This domain enforces Principle 2: Evidence over policy. A governance control that cannot produce evidence of enforcement is a governance gap, not a governance control. The question is never "do you have a policy?" — it is "what evidence exists that the policy is followed?" Every component of Domain 1 is designed to generate auditable evidence, not just documentation.

Maturity Model

Level Description
1 — Absent No AI governance policy exists; the organization has not formally discussed who is responsible for AI oversight, and individual teams or employees are making AI adoption decisions entirely at their own discretion with no central visibility.
2 — Acknowledged AI governance has been recognized as a need at the leadership level, but no formal policy has been drafted, no owner has been designated, and no budget or timeline has been committed to closing the gap.
3 — Informal Informal guidelines exist — typically a Slack channel, a Confluence wiki page, or an all-hands slide — but they are not enforced, have no designated owner, have not been reviewed since they were created, and most employees are unaware they exist.
4 — Formal A written AI governance policy exists with a named owner, an explicit version number and effective date, org-wide communication of the formal versioned policy document (not an informal guideline or one-time awareness communication), a defined approval workflow for new AI tools, and a scheduled annual review cycle with an assigned reviewer.
5 — Optimized The policy is actively enforced with documented evidence: training completion rates are tracked, shadow AI discovery scans run quarterly with findings logged, the approval workflow produces an audit trail for every tool request, policy violations result in documented follow-up, and the review cycle incorporates feedback from engineering, legal, and security before each version is published.

RACI Table

Activity R (Responsible) A (Accountable) C (Consulted) I (Informed)
Draft AI governance policy CTO CEO CISO, Legal, CHRO Board
Maintain AI inventory (sanctioned + shadow) CISO CTO Engineering leads CEO
Annual policy review cycle CTO CEO All C-suite Board, PE sponsor
AI tool approval workflow CTO CTO CISO, Procurement Engineering leads
Employee training on AI policy CHRO CEO CTO, Legal Board
Shadow AI discovery scans CISO CTO Engineering leads CEO

Governance Indicators

  • Published AI governance policy with a version history showing at least one completed review cycle
  • AI tool inventory (sanctioned and shadow) with a documented last-refreshed date no older than 90 days
  • Shadow AI discovery scan results logged on a quarterly cadence, with disposition documented for each finding (approved, prohibited, or under review)
  • Policy training completion rates by department, with records showing who completed training and when
  • AI tool approval workflow audit log showing all requests, reviewers, and outcomes
  • Named policy owner with a title, reporting line, and explicit accountability documented in the policy itself

Industry Alignment

This domain maps to the NIST AI RMF GOVERN function, which establishes the organizational practices, culture, and processes necessary for responsible AI risk management. It also aligns with ISO/IEC 42001 Clause 5 (Leadership and AI Policy), which requires top management to establish an AI policy that is appropriate to the organization’s context, provides a framework for setting AI objectives, and is communicated and made available to relevant stakeholders.

PE Due Diligence Signal

PE Due Diligence Signal

An acquirer asks: "Can you show us your AI governance policy and tell us how you enforce it?" A governance posture that still has too many gaps sounds like a CTO opening a shared Confluence page last edited eight months ago, acknowledging that few engineers know it exists, and explaining that there is no formal enforcement mechanism — the acquirer notes a governance gap and flags it as a finding. A well-governed, risk-mitigated posture sounds like a CTO producing a versioned policy document with a review history, pulling up a dashboard showing training completion rates by department, sharing a quarterly shadow AI scan report with three tools flagged and dispositioned, and walking through the last five entries in the tool approval workflow audit log. The acquirer sees a governance program that has been exercised, not just written — and that distinction carries material weight in both the risk assessment and the negotiations.

3.2  AI Risk Management

Assessment link: "How are AI-related risks (bias, hallucination, data privacy, regulatory) managed?"

Domain Statement

This domain establishes the proactive infrastructure for identifying, assessing, and mitigating risks that are specific to AI systems — including model bias and fairness failures, hallucinated outputs that propagate into decisions or customer communications, data privacy exposure from model training or inference, adversarial manipulation through prompt injection or jailbreaking, and operational failures from agentic systems with real-world authority. These risk categories require a dedicated framework and cross-functional ownership; they cannot be adequately addressed by folding them into existing IT or cyber risk programs. This domain requires board-level visibility because the blast radius of a significant AI incident — reputational, regulatory, financial, or operational — can be material to enterprise value.

Governing Principle

This domain enforces Principle 3: Governance scales with blast radius. The rigor of AI risk oversight is proportional to what each system can do, spend, or break — and the core operational concept of this domain is blast-radius scoping: documenting the scope, privileges, and kill-switch ownership of every deployed AI agent. Principle 5 (AI incidents are distinct from cyber incidents) is also directly applicable here, particularly at maturity levels 4 and 5 where dedicated incident response playbooks and tabletop exercises are required.

Maturity Model

Level Description
1 — Unmanaged AI risks are not actively managed; the organization has no inventory of AI-specific risk categories, no process for assessing the risk of AI deployments before they go live, and no incident history because incidents are not distinguished from general IT failures.
2 — Acknowledged AI-specific risks such as hallucination, bias, and data exposure have been identified and discussed at the leadership level, but there is no formal risk register, no assigned ownership, and no systematic process for assessing or mitigating them before or after deployment.
3 — Siloed Individual engineering or product teams manage AI risks within their own systems on an ad hoc basis, producing inconsistent documentation and review practices across the organization, with no cross-functional framework to aggregate findings, no shared taxonomy, and no escalation path to leadership.
4 — Cross-functional A formal AI risk framework is in place with a shared risk register, defined risk categories, regular cross-functional review sessions (at minimum quarterly), assigned risk owners, and a documented escalation path to the CTO and CEO for high-severity findings.
5 — Board-visible The AI risk program operates with full organizational integration: the board receives a regular AI risk summary, every deployed AI agent has documented blast-radius scoping and a named kill-switch owner, adversarial testing (prompt injection, red-teaming) runs on a defined cadence with findings logged, a tabletop exercise has been completed in the last 12 months for an AI-specific incident scenario, and quantified risk metrics (e.g., hallucination rate, bias delta, incident count) are tracked over time.

RACI Table

Activity R (Responsible) A (Accountable) C (Consulted) I (Informed)
AI risk register maintenance CTO CEO CISO, Legal Board
Agent blast-radius documentation Engineering leads CTO CISO CEO
Prompt injection / adversarial testing CISO CTO Engineering leads CEO, Board
AI incident tabletop exercises CTO CEO CISO, Legal, Comms Board
AI-specific incident response plan CISO CTO Legal, Comms CEO, Board
Bias and hallucination rate monitoring Engineering leads CTO Product CEO

Governance Indicators

  • AI risk register with named risk owners, severity ratings, mitigation status, and a documented review cadence no less frequent than quarterly
  • Blast-radius documentation for every deployed AI agent, specifying the systems it can read or write to, the communications it can send, the maximum spend or action authority it holds, and the name and title of its kill-switch owner
  • Adversarial testing log showing prompt injection and red-team exercise cadence, scenarios tested, and findings with disposition
  • AI-specific incident response plan that is distinct from the cyber IR playbook, with its own escalation paths, role assignments, and communication templates
  • Tabletop exercise record showing an AI-specific scenario has been run in the last 12 months, with findings and follow-up actions documented
  • Quantified AI risk metrics tracked over time (e.g., hallucination rate per model, bias evaluation results, incident count by category)

Industry Alignment

This domain maps to the NIST AI RMF MAP and MEASURE functions, which together cover the identification of AI risks in context and the analysis and monitoring of those risks over the AI system lifecycle. It also aligns with the EU AI Act’s risk classification system (unacceptable, high, limited, minimal), which requires organizations deploying or integrating AI in the EU to assess risk tier before deployment and apply proportional conformity and monitoring requirements for high-risk applications.

PE Due Diligence Signal

PE Due Diligence Signal

The clearest signal in this domain is what happens when an acquirer asks the CTO to walk through every deployed AI agent: its purpose, what systems it can access, what it can do autonomously, and who owns its kill switch. A governance posture with too many gaps sounds like a pause followed by a partial list pulled from memory, with no documentation on agent scope and no certainty about what third-party APIs or internal systems each agent can reach — that pause is itself a finding. A well-governed posture sounds like a pre-built document produced in minutes, not hours, listing every agent, its blast radius (read vs. write access, communication authority, spend limits), its last security review date, and its named kill-switch owner by title. If that document doesn’t exist, the risk posture is undocumented — and undocumented risk is priced by acquirers as if it’s the worst case.

The framework continues with four additional governance domains: Domain 3 (Regulatory & Compliance Readiness), Domain 4 (AI Ethics & Responsible Use), Domain 5 (Explainability & Audit), and Domain 6 (AI Vendor & Supply Chain Governance) — each with full maturity models, RACI tables, governance indicators, and PE due diligence signals. The gated section also includes the four-quarter Implementation Roadmap, PE Value Creation & Due Diligence guidance, and the Industry Alignment Reference table mapping all six domains to NIST AI RMF, EU AI Act, and ISO/IEC 42001.

Put This Framework to Work

Start with your governance baseline, or license the framework for portfolio-wide implementation.

Assess Your Governance Baseline → License the Framework →