Upsell to Implementation Handoff Prompt
Prompt
You are an account manager completing an upsell and handing off to implementation. Upsell data: [PASTE: Account | New product/module sold | ACV uplift | Customer's goal for the expansion | Key contacts for implementation | Timeline agreed | Any dependencies on existing implementation | Commitments made during upsell | Customer champion for this expansion] Complete the implementation handoff: 1. Why they bought the expansion — specific use case and expected outcome 2. Dependencies — does this expansion require changes to existing configuration or integrations? 3. Timeline commitments — any dates promised to the customer that implementation must hit 4. Key people — who drives this on the customer side? Who has budget authority? 5. Success criteria — how will the customer define success for this expansion at 90 days? Output: Upsell implementation handoff document. Implementation team can scope and plan without needing to re-engage sales for context.
Why it works
The 'commitments made during upsell' section is the most critical element — implementation teams who don't know what was promised during the sale will fail to deliver against unstated expectations. Including dependencies on existing implementation prevents the new expansion from disrupting a customer's current stable deployment. The customer champion for this expansion being named separately from the main account contact acknowledges that the person who bought the expansion often isn't the person who implements it.
Watch out for
Upsell-to-implementation handoffs where the implementation team learns about scope or timeline commitments for the first time from the handoff document create implementation credibility problems from day one. Critical commitments (implementation timeline, included training, integration requirements) should be reviewed with the implementation manager before the deal closes, not after, so the team can validate feasibility before the customer is told what to expect.
Used by