For sponsors, procurement and partners
A proposal should describe the work, participants, environments, delivery responsibilities and acceptance criteria it covers. Bring your procurement requirements so your sponsor, learning team, IT owners and partners can review the same scope.
Discuss commercial scope →Specify roles, learner starting levels, cohort size, regions, scheduling, simulations, practice content, assessments and feedback. The AI Bootcamp runs for 6–8 weeks. Agree customization and trainer responsibilities rather than assuming a fixed content or environment package.
Identify the practice environment, required capacity, access period and usage assumptions. Agree cloud and model usage budgets, limits, reporting, who monitors them and how changes are approved. Confirm what is included in the proposal and what is supplied or billed separately.
List approved applications and model services, who supplies licences or credentials, permitted data and relevant provider terms. Access to a model API does not by itself include an enterprise application licence. Existing customer tools may be used where the scenario and access requirements allow.
Scope LMS or SSO launch, reporting interfaces, integration testing, content signoff and change requests. For partners, agree branding, ownership, publication and customer reuse rights, along with each party’s delivery and commercial responsibilities.
Define acceptance evidence, delivery owners, environment support and escalation. Separate preparation from production implementation, agent operations and continuing support. Record any agreed support hours, service levels, review cadence and duration in the applicable agreement.
Assessment evidence describes the responsibilities assessed. Production acceptance and business impact depend on the customer’s implementation, approvals and operating conditions; they are not automatic consequences of purchasing preparation.
