Onboarding kickoff pack: Notion page, kickoff link and intro email when a deal closes
HubSpot + Gong + Notion + Calendly
Who it's for
CS managers and onboarding leads who want each new customer's kickoff ready the day the deal closes, without chasing the AE for notes. HubSpot can be swapped for Salesforce or Attio, and Gong for Fireflies or Granola.
What you get
Handoff notes, Notion page draft and intro email waiting for approval. Sample output: every company and person in it is fictional.
Deal: Mossgate Labs (fictional), closed won Oct 14, $36K, AE Alex Rivera Contacts: Dana Okafor (VP Operations, economic buyer), Sam Whitlock (Ops Analyst, day-to-day admin) Handoff notes from the Gong deal brief: - Why they bought: weekly reporting took two analysts a full day - Success criteria: first automated weekly report live within 30 days - Promised in the sales process: SSO setup help and a data import session - Risk: Dana is out Nov 3–14, so kickoff should happen before then - Unknown: who owns the data import on their side. Ask Alex. Notion page (not created yet): 'Mossgate Labs (fictional): Onboarding' under Customers > Onboarding, with sections for goals, team, handoff notes, promises, open questions and the kickoff link. Calendly (not created yet): one single-use link for the '45 min Onboarding Kickoff' event type. Intro email (text only, not sent): Subject: Kicking off with Mossgate Labs Hi Dana, Sam, I'm Jordan, and I'll be your onboarding lead. Alex filled me in on your goal of getting the first weekly report automated within 30 days. Let's start with a 45-minute kickoff before Nov 3: https://scheduling-link.example/kickoff Talk soon, Jordan Reply 'create page', 'create link' or both.
Time and cost
Estimate About 15–20 minutes per new customer, most of it checking the handoff notes.
Assumptions: One newly closed deal with two contacts, one Gong deal brief, one Notion page and one scheduling link.
- HubSpot: Reads only: recently closed-won deals, then the deal, its owner and associated contacts for one customer. Credit use not confirmed by HubSpot.
- Gong: One generate_brief or ask_deal call for the deal. Each call uses Gong credits based on the calls and emails it analyzes. Every call uses credits. All three tools (ask_account, ask_deal, generate_brief) consume Gong credits based on the volume of calls and emails analyzed; briefs cost more per open-ended section. Same consumption as the equivalent API requests. Source: help.gong.io, checked 2026-10-16
- Notion: A search for the parent page, then one page created after you approve it. Credit use not confirmed by Notion.
- Calendly: One read of your event types, then one single-use scheduling link created after you approve it. Credit use not confirmed by Calendly.
Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.
MCP servers
Every server is confirmed in: ClaudeChatGPT
-
ClaudeChatGPTRead + writeCredits not confirmedNeeds admin or IT
https://mcp.hubspot.com -
ClaudeChatGPTRead onlyEvery call uses creditsNeeds admin or IT
https://mcp.gong.io/mcp -
ClaudeChatGPTClaude CodeCursorCopilotRead + writeCredits not confirmed
https://mcp.notion.com/mcp -
ClaudeChatGPTRead + writeCredits not confirmed
https://mcp.calendly.com
Set up in a chat app
Every server in this recipe is confirmed for Claude and ChatGPT. Connect each one, then paste the prompts below into one conversation.
- Connect HubSpot without code (Claude, ChatGPT)
- Connect Gong without code (Claude, ChatGPT)
- Connect Notion without code (Claude, ChatGPT)
- Connect Calendly without code (Claude, ChatGPT)
Developer setup
Auth setup and mcp.json for Claude Code and Cursor
- HubSpot: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token. - Gong: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token. - Notion: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token. - Calendly: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token.
Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.
{
"mcpServers": {
"hubspot": {
"url": "https://mcp.hubspot.com"
},
"gong": {
"url": "https://mcp.gong.io/mcp"
},
"notion": {
"url": "https://mcp.notion.com/mcp"
},
"calendly": {
"url": "https://mcp.calendly.com"
}
}
}
Step-by-step prompts
- Find HubSpot deals that moved to closed won in the last {days} days. For {company}, show me the deal amount, close date, owner and associated contacts with their titles. Don't change anything.
- Ask Gong for a deal brief on the {company} deal: why they bought, success criteria, key people, anything promised during the sales process, risks and open questions. Mark anything you're unsure of as unknown.
- In Calendly, list my event types and show me the one for {event_type} with its length and host. After I approve, create one single-use scheduling link for it.
- Draft a Notion onboarding page for {company} under {parent_page}: goals and success criteria, team on both sides, handoff notes, promises to keep, open questions and the kickoff link. Show me the draft, and create the page only after I approve it.
- Write a short intro email from me to the customer contacts: who I am, the goal we heard from them, and the kickoff link. Leave out internal notes. Show me the text only. Don't send it.
Run it on a schedule (optional)
- Run it by hand the day a deal closes, or once a week for all deals closed that week.
- In a scheduled run, stop at the drafts: list new closed-won deals and prepare the handoff notes, then create the page and link only after you approve.
- Gong and HubSpot both need an admin before anyone can connect. Test one manual run before you schedule it.
Where this goes wrong
- Promises that weren't made, or were made differently. A brief can turn 'we could look at SSO' into a commitment. Send the 'promised' list to the AE and get a yes on each item before it goes into the customer-facing plan.
- Missing context from private calls. Gong's MCP leaves out private calls, so the brief may miss things. Ask the AE what's not in Gong before the kickoff.
- The wrong deal. A customer can have an expansion or a second closed-won deal. Confirm the deal name, amount and close date before anything is drafted.
- Kickoff link on the wrong event type. Check the event type's name, length and host before the link is created, then open the link yourself before it goes in the email.
Gotchas
- Gong's setup needs an admin: a Gong tech admin must first create an MCP server integration. It needs a paid Gong seat and Gong credits. Gong's MCP is read-only and returns no raw transcripts.
- HubSpot's setup needs an admin: non-admin users need a Super Admin to approve the connector first.
- Calendly's tools can also book and cancel events and change availability. This recipe only creates one single-use link, so say so in the prompt.
- The intro email comes back as text to paste into your mail app. If you also connect Gmail, it can save it as a draft, but Gmail's MCP is in Google's Developer Preview and needs your own Google Cloud OAuth client.
- Using Salesforce instead? Use a SOQL query for closed-won Opportunities and their contacts. It needs Enterprise Edition or above and an admin-created External Client App, ChatGPT needs developer mode, and every tool call counts against the org's daily API request quota.
Download
Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.
Download onboarding-kickoff-pack.md
New recipe and breakage notes every week
Vendor sites: HubSpot · Calendly. If we join an affiliate program, these links will be labeled as affiliate links.