Service Activation and Delivery Arrangements
Customers hire Compound Leverage to complete assigned work. They do not have to purchase, deploy, or administer an AI Team. A THINK Strategist manages execution, quality, and delivery.
Select the appropriate delivery arrangement
| Question | CL-managed environment | Customer-controlled environment |
|---|---|---|
| Where is work performed? | In CL-managed infrastructure and approved tools | Within specifically approved customer infrastructure or systems |
| Who provides access? | CL manages its environment; customer authorizes any access to customer data/systems | Customer approves identities, credentials, permissions, and integration boundaries |
| Who manages assigned work? | THINK Strategist | THINK Strategist, under the customer’s agreed controls |
| What is delivered? | Finished artifacts, code, reports, or solutions | Finished artifacts, code, reports, or solutions in approved destinations |
| Is deployment included? | Only if explicitly scoped and authorized | Only if explicitly scoped and authorized |
Customer-environment delivery is engagement-specific. Technical feasibility and access must be confirmed; documentation of a deployment design does not mean that environment is already operational.
Activation checklist
- Agree on the objective, work types, deliverables, acceptance criteria, and deadline.
- Identify authorized requestors, approvers, and the THINK Strategist.
- Agree on email, meetings, or Customer Portal for intake.
- Confirm data sources, permitted tools, system access, and execution location.
- Identify human review gates and actions requiring explicit approval.
- Agree on delivery destinations, revisions, and any operational handoff.
Work lifecycle
Request → Scope and assign → Execute → Validate → Human review → Customer approval where required → Deliver
For software or automation assignments, validation may include automated tests, code review, configuration checks, and acceptance testing. Code authoring, repository changes, and production deployment must be separately scoped and authorized.
Related documentation
Managed Work Delivery Architecture · Work Execution Layer · Security and Governance · Work Orchestration · MCP and Integrations