2 Adoption Models for GenAI
This chapter covers
- How SaaS, API, and self-hosted GenAI models shift control and risk
- What Agentic AI offers and which risks it introduces
- Key risk dimensions across deployment choices
- A primer on emerging Agentic AI
- MediAssist, a fictional use case moving through all three adoption models
Before setting up governance controls or assessing compliance needs, even before you decide which compliance requirements apply, you need to answer a simple question: How is your organization actually adopting GenAI?
It’s tempting to think the answer is obvious. After all, using these tools seems straightforward: type a prompt, get a response. But what happens behind the scenes can vary dramatically depending on the adoption path you choose. That choice determines how accountability may be assigned and how much oversight you must perform or demand.
We call this your GenAI posture; your operational stance toward generative AI. In practice, many organizations operate in more than one posture at the same time. Your marketing team might rely on ChatGPT (SaaS), engineering could integrate Claude via API, while data science fine-tunes a model in house. Each posture brings a different mix of control, complexity, and risk and none remove the need for governance.