Build and Handover
Implement an approved design with validation, operating documentation, and a defined handover.
Discuss this engagementWhen it fits
The design is accepted and the implementation needs agreed responsibilities, testing, change approvals, and an operating owner.
What changes
The contracted implementation, acceptance evidence, and the material the operating team needs to take ownership.
What you receive
- Implementation within the approved statement of work
- Versioned configuration or infrastructure code where applicable
- Test evidence, rollback procedures, and open issues
- Operating documentation and knowledge transfer
What we agree first
- An approved blueprint and implementation boundary
- Authorized access and change approvals
- Agreed acceptance tests and delivery responsibilities
Scope, fee, acceptance criteria, and timing are agreed before work starts.
Scope boundaries
Delivery capacity is confirmed during scoping. Production promotion requires separate authorization; unlimited operations and 24-hour support are not included.
View example deliverablesGrant Agent Authority One Level at a Time
Use the action-authority question from Microsoft's AI Decision Framework to decide whether an agent drafts, executes with approval, or acts alone, and what each level costs to operate.
What does your team need to settle?
Bring the system, the business goal, and the constraints. Scope, deliverables, and fee are agreed before work starts.
Discuss this engagement