Structure · Rep Onboarding & Ramp
Build a Week-One Onboarding Checklist
Produce a day-by-day week-one checklist that gets a new agency rep accounts provisioned, contexted, and shadowing within 5 working days.
managerBeginner⏱ 2-3 hours
When to use
Use the Friday before a rep starts so HR, IT, and sales ops all have the same checklist. Best when you're hiring more than once a quarter and want week one to feel structured (not chaotic). Pair it with a Loom-walkthrough library so the rep can self-serve outside of live time.
The prompt
You are a sales enablement lead at a digital marketing agency who has run week-one onboarding for 30+ new hires and refuses to let a rep "figure it out." Agency: [AGENCY_NAME] — services [SERVICES] | New rep: [NEW_REP_ROLE], start date [START_DATE] | Tech stack to provision: [TECH_STACK] | People they must meet: [KEY_INTROS] | Office model: [REMOTE_OR_HYBRID] Build a day-by-day week-one onboarding checklist (Mon–Fri) that ensures the rep is fully provisioned, briefed on services and ICP, has shadowed live work, and can pass a Friday exit ticket. - Structured by day with three tracks: Systems (accounts, tools), People (intros, 1:1s), Knowledge (services, ICP, POV). - Every day must include at least one practical exercise (Loom walk-through, mock task, shadow session) — not just slack-message-someone. - Friday must end with an exit-ticket assessment the rep submits to their manager. - Assign an owner to each line item (Manager, Ops, IT, Buddy). - Total time per day capped at 6 hours of structured work — leave room for absorption. Markdown checklist grouped by Day (Mon–Fri), each day showing three sub-sections (Systems / People / Knowledge) with checkboxes, owner, and time estimate. End with a "Friday Exit Ticket" section listing 8–10 self-assessment questions.
Variables
- [AGENCY_NAME] — Your agency name
- [SERVICES] — Service lines the rep will be exposed to in week one
- [NEW_REP_ROLE] — SDR, AE, strategist, etc.
- [START_DATE] — First day on the job
- [TECH_STACK] — Tools to provision (CRM, dialer, Loom, Gong, Slack, etc.)
- [KEY_INTROS] — People the rep must meet (founders, SEO lead, paid lead, head of delivery)
- [REMOTE_OR_HYBRID] — Remote, hybrid, or in-office
Example input
Agency: Loop & Co — services SEO + content + Webflow | New rep: SDR, starts Mon June 2 | Stack to provision: HubSpot, Apollo, Aircall, Gong, Loom, Slack, 1Password | Intros: Mara (founder), Devin (SEO lead), Sasha (head of delivery), Wes (buddy AE) | Hybrid (Tue/Thu in office)
Example output
MON — Systems: HubSpot, Apollo, Slack, 1Password provisioned (IT, 1h). People: 30-min welcome with Mara, Wes assigned as buddy. Knowledge: Watch "Loop & Co services overview" Loom (45 min). Exercise: Post intro in #team-sales. WED — Systems: Aircall + Gong, first 10 prospect records assigned. People: 1:1 with Devin on SEO POV. Knowledge: Read 3 past won-deal call summaries. Exercise: Write a 1-page POV on mid-market Webflow buyers (Manager review). FRI — Exit Ticket: (1) Name 3 services and one differentiator per service. (2) Who do you escalate a technical SEO question to? (3) Walk through Apollo → HubSpot lead handoff. (4) What's our ICP firmographic? (5) What's the cadence template called? (6) Who owns proposal pricing? (7) Demo logging an activity in HubSpot. (8) One thing you'd improve about this week.
Pro tips
- Assign a buddy AE — separate from the manager — so the rep has a low-stakes channel for dumb questions.
- Pre-load week one in your project tool (Asana / Linear / Notion) so the rep sees a real backlog on day one.
- Track week-one exit-ticket scores by hire — patterns in misses tell you what your enablement is weak on.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts