Launch a Customer Engagement

{"category":"operations","description":"Use when one consultant, FDE, or delivery lead must convert a signed or nearly agreed customer engagement into a realistic initial delivery plan and an aligned kickoff. This covers mobilization through plan baseline, not ongoing weekly governance or detailed PoC evaluation. Treat contractual commitments and decision rights as source-controlled.","inputSchema":{"additionalProperties":false,"properties":{"constraints":{"description":"Known target dates, staffing, budget, and external dependencies.","items":{"type":"string"},"type":"array"},"engagement":{"description":"Engagement name or stable identifier.","minLength":1,"type":"string"},"intendedOutcome":{"description":"Customer outcome this engagement is expected to deliver.","minLength":1,"type":"string"},"scopeReferences":{"description":"Proposal, SOW, contract, internal handover, or related approved documents.","items":{"type":"string"},"type":"array"}},"required":["engagement","intendedOutcome"],"type":"object"},"schemaVersion":1,"steps":[{"expectedOutputs":[{"description":"Scope and acceptance baseline with contradictions and open approvals.","kind":"scope-baseline"}],"id":"4351","instructions":"Read the SOW, proposal, commitments made in sales, procurement/security terms and current customer expectations when available. Create a scope baseline separating signed deliverables, non-goals, assumptions, acceptance criteria, client dependencies and any ambiguous promise. Rank discrepancies by schedule or trust impact and direct unresolved contractual ambiguity to the responsible commercial owner; never reinterpret signed terms as settled fact. Gate: the kickoff can state accurately what has and has not been committed.","resourceHints":[],"title":"Reconcile the commercial promise with delivery reality"},{"expectedOutputs":[{"description":"Stakeholder map, responsibility assignments and dependency list.","kind":"responsibility-map"}],"id":"R581","instructions":"Map sponsor, day-to-day counterpart, business owner, technical/data owner, workstream leads, escalation contacts and those who approve deliverables. Create a concise responsibility map using accountable/consulted roles only where supported; unresolved ownership stays explicitly open. Inventory access, data, security review, procurement, resourcing, change freezes and supplier dependencies. Identify the earliest dependency that could prevent productive work. Gate: each critical deliverable has a proposed decision owner and blockers are visible.","resourceHints":[],"title":"Identify decision rights and delivery dependencies"},{"expectedOutputs":[{"description":"Milestones, owners, dependencies, initial risks and realistic dates.","kind":"mobilization-plan"}],"id":"0111","instructions":"Back-plan from acceptance outcomes rather than filling a calendar with generic tasks. Define work packages, milestone evidence, dependencies, estimates with confidence, review checkpoints, and customer-provided inputs. Highlight the critical path, slack, and early-warning indicators. Distinguish contractual dates from proposed internal targets; provide options if the desired date conflicts with evidence. Use the simplest project artifact that the team can maintain. Gate: plan assumptions are explicit and the first milestone can be started with available authority.","resourceHints":[],"title":"Build a realistic milestone-based workplan"},{"expectedOutputs":[{"description":"Kickoff agenda/materials and evidence-grounded decision notes.","kind":"kickoff-results"}],"id":"O4QU","instructions":"Prepare an agenda that addresses outcomes, scope, responsibilities, collaboration norms, reporting cadence, acceptance criteria, change control, immediate dependencies and unresolved decisions. Present a short pre-read when useful. Capture actual customer feedback, decisions and objections rather than assuming consensus; distinguish items that require legal or commercial approval. Gate: the stakeholders understand what is expected of each side and the kickoff produces explicit decisions or defined blockers.","resourceHints":[],"title":"Prepare and facilitate the kickoff"},{"expectedOutputs":[{"description":"Agreed or approval-ready charter, workplan, scope notes, and issue list.","kind":"engagement-plan"}],"id":"IAZ6","instructions":"Incorporate confirmed decisions into a versioned engagement plan. Show what changed from the proposal, who approved it, what remains contingent and which dependencies require an owner. Circulate or update systems only with authorization. Avoid manufacturing a new handoff ritual when the owner continues the work. Gate: the plan is executable, its approval status is honest, and critical ambiguities are escalated rather than hidden.","resourceHints":[],"title":"Baseline the agreed working plan"}],"title":"Launch a Customer Engagement"}