ai-on-saas-combined-methodology

name	ai-on-saas-combined-methodology
description	Use when one proposal must integrate multi-tenant SaaS delivery with RAG, copilots, agents, or AI analytics across shared phases and gates; use SaaS implementation methodology when the scope contains no AI feature.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

AI-on-SaaS Combined Methodology

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use When

• The deliverable is a multi-tenant SaaS product that contains AI features built into the product.
• The buyer expects investor-grade or board-grade rigour: AI ROI that survives a sceptical CFO, eval evidence that survives a sceptical CTO, procurement answers that survive a sceptical CISO.
• The Methodology section must demonstrate simultaneous SaaS literacy (control plane, tenant isolation, cost attribution) and AI literacy (eval harness, model gateway, hallucination SLO, red-team).
• The engagement faces AI-specific regulators (EU AI Act, Kenya NCAIS, Nigeria NAIS, South Africa AI policy, Uganda NITA-U guidance, Rwanda AI Policy, sectoral rules).
• A generic SaaS implementation methodology or a generic AI methodology will not pass evaluator scrutiny.

Do Not Use When

• The engagement is a SaaS implementation with no AI features — use saas-implementation-methodology instead.
• The engagement is generic AI strategy or AI proof-of-concept with no SaaS / multi-tenant layer — use ai-transformation-proposal instead.
• The engagement is a pure consulting assignment without software delivery.

Required Inputs