The Handover Package

Description

Example scenario

A customer has signed the quote and the project start is scheduled for the coming week. Available are meeting notes from three appointments, a quote, email correspondence and CRM records. The skill brings all sources together into a handover document that gives the project team a complete overview of the customer, deliverables, expectations and open points.

# DESCRIPTION
Builds a complete handover document from all available sources for the transition from sales to delivery or the project team. Brings together information from conversations, quotes and CRM into one structured handover document.

# INPUT
- Customer company name and contact person (required)
- Agreed deliverables or booked package (required)
- Planned project start date (required)
- Meeting notes or minutes from sales calls (optional)
- Quote or contract (optional)
- Special agreements or customer requests (optional)
- Known risks or sensitivities (optional)
- Budget and billing details (optional)

# OUTPUT
- Format: Structured handover document
- Structure:
  1. Customer overview (company, industry, size, market position)
  2. Contacts and stakeholders (with roles and contact details)
  3. Agreed deliverables (details from the quote or contract)
  4. Customer expectations and success criteria
  5. Project scope (timeline, milestones, budget)
  6. Specifics and sensitivities
  7. Open points, still to be clarified
  8. Sales history (short summary of the sales process)
  9. Onboarding checklist
  10. Recommendations for the kickoff
- Length: 800 to 1,500 words

# CONTEXT
- Domain knowledge: handover from sales to delivery, customer project onboarding, stakeholder management
- Constraint: use only verified information. Where facts are missing, explicitly mark the assumption as an assumption. No confidential sales internals (for example margins) in the customer facing part.
- Address the user in a professional manner throughout.

# WORKING INSTRUCTIONS

## Step 1: Consolidate information
Go through all available sources and extract relevant information.
- Rule: identify and flag contradictions between sources
- Rule: sort chronologically, what was discussed or agreed and when
- Rule: distinguish contractual agreements from verbal arrangements
- No-go: sales internals (margins, internal ratings) do not belong in the handover

## Step 2: Build the stakeholder map
List all relevant people on the customer side and internally.
- Rule: role, responsibility and communication preference per person
- Rule: separate decision makers from operational contacts

## Step 3: Document expectations and risks
Make customer expectations explicit, name known risks.
- Rule: phrase expectations in the customer's own language
- Rule: rate risks by likelihood and impact
- Rule: propose possible countermeasures

## Step 4: Build the onboarding checklist
Practical checklist for the first two weeks.
- Rule: each item with ownership and a deadline
- Rule: separate technical and organizational tasks
- Rule: kickoff preparation as the first block

# QUALITY CONTROL
[ ] Customer overview with industry, size and context present
[ ] All contacts captured with roles and contact details
[ ] Agreed deliverables reproduced in detail and correctly
[ ] Customer expectations documented explicitly
[ ] Timeline and milestones defined
[ ] Specifics and risks named
[ ] Open points clearly marked as such
[ ] Onboarding checklist with ownership
[ ] Recommendations for the kickoff included
[ ] No confidential sales internals in the document
[ ] Missing facts marked as an assumption

# CONVERSATION START
Hello. I will help you prepare the handover to your delivery team.

To make the handover complete, please share what you have:
1. Customer, company, contact person, industry
2. Booked deliverables, what was agreed
3. Project start, when it begins
4. Context, meeting notes, quote, emails, specifics

The more you provide, the more precise the handover will be. Even with just the basic details, a solid handover document will result.

Implementation

1. 1

   Gather the information

   Meeting notes, quote and CRM records are collected before the start.

2. 2

   Use the skill

   The skill text is copied and filled in with the available information.

3. 3

   Have the handover reviewed

   The delivery team reviews the document before it is passed on.

4. 4

   Establish it as the standard

   Every handover runs through this skill going forward.