Automate the meeting-booked to CRM to onboarding handoff
Maps and automates every seam from calendar booking to onboarding kickoff: field-mapped CRM creation, automatic AE pre-meeting packages, no-show branches, same-day closed-won handoffs, and scheduled orphan checks at every stage. The leak-detection layer is the differentiator — handoffs fail silently, and this design makes silence detectable.
You are a revenue process designer who specializes in the seams between systems, because that's where deals leak: the meeting that booked but never hit the CRM, the AE who walked in cold because the SDR's notes lived in Slack, the closed deal that sat for nine days before onboarding noticed. Handoffs fail silently, so you design them to be observable. Design my handoff automation from meeting-booked through onboarding kickoff. Output: 1. STAGE MAP — every handoff moment: booking to CRM, SDR to AE, held-meeting to next step, closed-won to onboarding. For each: the trigger event, the data that must travel, the systems it touches, and the human who gets notified. 2. BOOKING FLOW — calendar event to CRM record: field mapping, deal or opportunity creation rules, source attribution preserved from the original campaign, and the pre-meeting package the AE receives automatically (enrichment summary, thread history, SDR notes) at booking and again one hour before. 3. NO-SHOW AND RESCHEDULE BRANCHES — automatic sequence enrollment for no-shows, rescheduling behavior, and when a human takes over from the automation. 4. CLOSED-WON HANDOFF — the trigger, the onboarding record created, the internal kickoff task with owner and SLA, and the customer-facing welcome that goes out same-day. 5. LEAK DETECTION — scheduled checks for orphans at every seam: meetings with no CRM record, held meetings with no logged outcome, closed deals with no onboarding started. Each check's cadence and where flags surface. Rules: every handoff needs an explicit owner on the receiving side — 'the team' owns nothing. Data travels with the record, never only in Slack. Every seam gets a leak check, because the failure mode of handoffs is silence. Before designing, interview me. Ask ONE AT A TIME, waiting for my answer each time: 1. Walk me through what happens today from booking to onboarding — where are the manual steps? 2. What scheduling tool, CRM, and sequencer are in play? 3. Who books meetings, who runs them, and who owns onboarding? 4. Which handoff has burned you most recently, and how was it discovered? 5. What does onboarding need on day one that sales usually forgets to pass along? Then produce the design with the leak checks specced.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer question 4 with the real story — the most recent burned handoff tells the design where to reinforce first.
- 3
Build the booking-to-CRM flow first, then leak checks, then the closed-won handoff; each ships independently.
- 4
Review the orphan flags weekly for a month — the volume of caught leaks is your before-and-after proof.
Best practices
Preserve campaign attribution through every hop; most attribution loss happens at handoffs, not at capture.
Send the AE package twice — at booking and one hour before — because the booking-time version is unread by meeting day.
Give every receiving owner an SLA with an escalation, or the handoff just moves where the waiting happens.
Ask onboarding quarterly what sales still forgets to pass along, and add it to the closed-won payload.
Example: what this looks like in practice
A sales leader at a 65-person managed-services firm discovers two booked meetings from last quarter that never became CRM records, and onboarding routinely starts a week late because closed-won news travels by hallway. The interview maps a Calendly-HubSpot-Smartlead stack with a two-person onboarding team. The design wires Calendly webhooks through n8n into HubSpot deal creation with source attribution, an automatic AE package assembling the Smartlead thread and Clay enrichment, a no-show branch enrolling prospects into a re-book sequence after 20 minutes, and a closed-won trigger creating the onboarding record with a same-day kickoff SLA. The Monday orphan check finds one leak in its first month — a rescheduled meeting whose deal never updated — caught in three days instead of discovered at quarter end.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Every major scheduler (Calendly, Cal.com, HubSpot Meetings) fires a webhook or native integration on booking. Route it into your CRM to upsert the contact, create or update the deal, and preserve the campaign source. The design details that matter are field mapping and attribution — a record created without source data is a record you'll misreport forever.
More automation & workflow design prompts
Build a system prompt for an AI cold email reply agent
Interviews you about your offer, booking flow, and voice, then generates a complete production system prompt for an AI reply agent — classification taxonomy, response rules, escalation conditions, and a strict JSON output contract an n8n or Zapier workflow can parse. You get the artifact teams pay thousands to have written, tuned to how you actually talk.
Turn a manual sales process into an automation blueprint
Converts a fuzzy 'we do this by hand every week' description into a structured blueprint with a detectable trigger, labeled steps, edge cases, human checkpoints, and failure alerts. It forces the design decisions people usually discover mid-build, so what you hand to n8n, Zapier, or an ops hire is assembly work, not archaeology.
Architect a Clay table before you burn the credits
Designs the Clay table before you build it: sources, column order, run conditions, waterfalls, outputs, and a credit estimate. Column ordering and gating are where most teams silently overspend, so the prompt enforces filter-first architecture and makes every paid column defend its run condition — typically cutting credit burn 40-70% versus enrich-everything builds.