How Managed Teams Work

Customers assign work in live meetings, by email, or through the optional Customer Portal. A THINK Strategist coordinates the Managed Team through the Strategist Portal and manages execution and quality. Customers receive notifications when work is ready for review or complete, can request revisions and approve deliverables, and receive finished artifacts through our systems or theirs.

Work lifecycle

Request → Assign → Execute → Review → Deliver

The customer chooses a convenient request channel. The THINK Strategist manages team execution. Finished documents, presentations, reports, research, solutions, or configured teams are delivered for review, revisions, and approval as applicable.

See Managed Capture Team, Managed Proposal Team, and Security and Governance.

Assign your first work item

Include	Example
Outcome	“Develop an opportunity assessment” or “Implement a repository integration”
Inputs	Opportunity link, files, source notes, or repository
Deadline	When the work is needed
Acceptance criteria	Required sections, tests, format, or business constraints
Review contact	Person who can confirm facts and approve deliverables
Delivery location	Email, portal, approved repository, or customer system

What happens next

Scope: The THINK Strategist clarifies deliverables and missing information.
Assign: The strategist coordinates the relevant Managed Team roles.
Execute: The team performs authorized research, drafting, development, or configuration.
Validate: Evidence, completeness, code tests, or other agreed checks are applied.
Review: Human reviewers resolve exceptions and consequential decisions.
Deliver: Finished work is returned through the agreed channel.

Two delivery environments

CL-managed delivery	Customer-environment delivery
CL operates approved tools and infrastructure	Work takes place within specifically approved customer systems
Customer supplies authorized inputs	Customer authorizes environment access and permissions
CL delivers reviewed artifacts or code	CL delivers or applies work within agreed boundaries

What if something changes?

Situation	Next step
Additional requirements	Send the change to the strategist for scope confirmation
Missing information	Provide approved source material or clarify assumptions
Revision needed	Identify the specific section, behavior, or result to revise
Production change needed	Confirm explicit deployment approval separately