Prompt
Build Partner 30-60-90 Onboarding Plan
Use this when you need to create a structured 30-60-90 day onboarding schedule for a newly signed channel partner.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a channel partner manager creating a 30-60-90 day onboarding plan. Optimise for a schedule that gets the partner trained, enabled, and producing qualified pipeline by day 90.
Context you provide
- {{partner_name}} - partner name
- {{partner_type}} - distributor, reseller, integrator, or MSP
- {{product_or_service}} - what they will sell or support
- {{start_date}} - kickoff date
- {{goals_and_targets}} - first 90 day sales, certification, or pipeline targets
- {{key_contacts}} - partner and internal owners
- {{available_resources}} - training, portal, demo lab, funding
- {{success_metrics}} - how onboarding is judged
- {{known_gaps_or_risks}} - skills, region, or capacity issues
Instructions
- Ask for any missing inputs, then confirm partner type, start date, and day 90 goal.
- Split the plan into days 1 to 30 foundation, 31 to 60 enablement, 61 to 90 activation.
- For each phase list objectives, owner, partner actions, activities, completion evidence, and checkpoint date.
- Add a training path for sales, technical, and support roles using only the resources provided.
- Include a weekly communication rhythm, escalation route, and named point of contact.
- Set day 30, 60, and 90 review gates with pass criteria and a recovery step if behind.
- Finish with a one page checklist and open questions for kickoff.
Output format Markdown. Open with a three row summary table. Add one section per phase using the fields in step 3, then a training path table. Keep under 800 words. Use plain business English, short bullets, and concrete dates. Leave out channel theory, pricing, and legal terms.
Guardrails
- Do not invent course names, certification requirements, portal features, discounts, or contract terms. Use only supplied inputs.
- If compliance, data protection, or local rules affect onboarding, tell the user to confirm with the relevant legal or compliance owner.
- Mark any assumption with "Assumption:" and keep the plan editable.
Example {{partner_name}}: Northwind Resellers; {{partner_type}}: value-added reseller; {{start_date}}: 3 March; {{goals_and_targets}}: two certified engineers and one registered deal by day 90.