Design a Sales Onboarding Program for New Reps
ChatGPT Prompt
Design a 30/60/90-day onboarding program for a new {role} selling {product}. For each phase define: what they must be able to do by the end (demonstrated, not attended), the certification that proves it, the shadowing and reverse-shadowing schedule, and the ramped quota. Week 1–2 covers product and ICP with a recorded pitch certification; week 3–4 covers discovery with two live calls under supervision; days 31–60 add demo certification and first self-sourced pipeline; days 61–90 target first closed deal. List the ten artefacts they need on day one, the named owner for each phase, and the leading indicators that predict a rep will miss ramp so a manager can intervene in week 4 rather than month 6.
💡 Pro Tip: Replace placeholders in [BRACKETS] with your specific information for best results.
How to Use This Prompt
- 1Click the copy button above to copy the prompt to your clipboard
- 2Open ChatGPT, Claude, or your preferred AI assistant
- 3Paste the prompt and replace any [PLACEHOLDER TEXT] with your specific details
- 4Review the AI's response and iterate if needed for better results
Related Tags
Related Prompts
Employee Handbook Template
Draft an employee handbook for a {company_size} company in {jurisdiction}. Cover: welcome and how the company actually makes decisions, employment basics, working hours and flexibility, compensation and review cycle, leave of every type with accrual rules, expenses, conduct and anti-harassment with a reporting route that has real anti-retaliation protection, IT and acceptable use, confidentiality and IP, health and safety, and how someone leaves well. Write it in plain language an employee will read rather than legal boilerplate they will not, but keep the clauses that carry legal weight intact. Flag every section where the requirement varies by jurisdiction, and note that it needs review by qualified employment counsel before issue.
Technical Documentation Template
Create a technical documentation template for {project_type}. Structure it for someone arriving via search who will read exactly one page, not the whole site. Cover: what this is and what problem it solves in two sentences, when to use it and when not to, a quickstart that works end to end in under five minutes, core concepts with the vocabulary defined once, task-based how-to guides, an API or configuration reference, troubleshooting organised by the symptom the user observes rather than the underlying cause, and an architecture section for contributors. Specify which sections are mandatory, how code examples are kept runnable and tested, the review trigger that catches documentation drifting from behaviour, and the ownership model that stops it rotting.
Design a Sales Presentation
Design a 12-slide sales presentation for {product} aimed at {buyer_role} at {company_type}. Open on the prospect's problem, not your company. Slide plan: the shift in their market, the cost of the status quo in their numbers, the specific gap that creates, your approach in one sentence, how it works in three steps, proof from a comparable customer with a measured result, what changes in their first 90 days, pricing anchored to the cost of inaction, implementation timeline, risk reversal, and a single explicit ask. For each slide give the headline as a full assertion (not a label), the one visual that carries it, and the sentence the presenter says out loud. Cap body text at 20 words per slide.
Create a Discovery Call Question Framework
Design a 30-minute discovery call framework for selling {product} to {buyer_role}. Structure it in five blocks with timings: rapport and agenda (2 min), current-state mapping (8 min), problem quantification (8 min), decision process and buying committee (7 min), and mutual next steps (5 min). Give 4–6 open questions per block, ordered so each one earns the right to ask the next. Include the specific follow-up probe for every question, the numbers a rep must leave the call holding (cost of the current process, timeline, budget owner), and three disqualification signals that should end the call early rather than book a second one.
Write Follow-Up Email Templates for Every Deal Stage
Write follow-up email templates for {product} covering seven moments: after a first discovery call, after a demo, after sending pricing, after a champion goes quiet for 7 days, after a verbal yes with no signature, after a loss, and a 90-day re-engagement. Each under 80 words, each adding new information rather than 'just checking in' — a relevant benchmark, a customer story, an answer to a question they did not ask yet, or a deadline that is genuinely real. Give each a subject line, the ideal send delay, and the one signal that means you should call instead of email.
Develop a Closing Strategy for Enterprise Deals
Build a closing strategy for a {deal_size} enterprise deal for {product} with a buying committee of {committee_size}. Map every role — economic buyer, champion, technical evaluator, legal, procurement, security review — with what each one needs to say yes and what each is personally risking. Produce a mutual action plan working backwards from the target signature date with owners and dates for security review, legal redlines, procurement onboarding and budget approval. Add: how to arm a champion to sell internally when you are not in the room, the three questions that reveal whether your champion actually has power, and the concessions to hold back for the final week rather than spending early.