A COO wants a single enterprise agent that can read CRM, ERP, and HR data and execute updates across all systems within six weeks. Compliance…

The constraints—tight deadline, strict compliance, no new connectors, and the need for quick value demonstration—make a "big bang" enterprise rollout infeasible. A phased pilot with KPI gates (D) is the best strategy. This approach de-risks the project by starting with a limited scope, allowing the team to prove value quickly and secure stakeholder buy-in. It respects compliance by tackling systems one by one, adheres to the "least privilege" principle, and allows for predictable cost management. Each phase's success, measured by KPIs, gates the investment for the next phase, ensuring alignment with business value.

A. An enterprise-first rollout is too high-risk, slow, and likely to violate the strict compliance and least-privilege access constraints from the start.

B. Choosing the lowest-cost model might not meet the complex cross-system requirements and could fail to deliver the value the COO expects.

C. Building a custom model in-house is time-consuming and expensive, directly contradicting the six-week timeline and predictable cost requirements.

1. Microsoft Cloud Adoption Framework for Azure. (2024). Strategy methodology. "Define motivations." This framework advocates for identifying business outcomes and starting with projects that can demonstrate value early to build momentum.

2. Microsoft Power Platform Adoption. (2023). Power Platform adoption maturity model. "Stage 2: Envision." This model emphasizes starting with pilot projects and defining success criteria (KPIs) to guide a phased and successful enterprise adoption.

3. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. Chapter 4, "An Agile View of Process," discusses the value of incremental delivery for managing complexity and stakeholder expectations.