Recipes / Mutual action plan from a deal record

Mutual action plan from a deal record

HubSpot + Notion

IntermediateAEs

Who it's for

AEs who want a mutual action plan with dated milestones and owners on both sides, built from what's already in the CRM, ready to share with the buyer. HubSpot can be swapped for Salesforce, Attio or Pipedrive. No Notion? Ask for the plan as text and paste it into your own doc.

What you get

A draft mutual action plan, before the Notion page is created. Sample output: every company and person in it is fictional.

Mutual action plan: Mossgate Labs (fictional) x Fernhill Software (fictional)
Target close: Dec 12
Deal: Mossgate Labs platform rollout, $64K, stage: Proposal

Owners
Mossgate Labs: Dana Okafor (VP Operations, sponsor), Alex Rivera (IT lead)
Fernhill Software: Jordan (AE), Sam Whitlock (Solutions Engineer)

Milestones (working back from Dec 12)
1. Oct 24: Technical review with IT. Owners: Alex Rivera, Sam Whitlock. Source: Oct 9 meeting note, "Alex wants a technical review before security."
2. Nov 7: Security questionnaire returned. Owner: Sam Whitlock
3. Nov 14: Pricing and terms agreed. Owners: Dana Okafor, Jordan
4. Nov 21: Contract to legal. Owner: Dana Okafor. Needs a name from Mossgate legal.
5. Dec 5: Legal redlines done. Owners: Mossgate legal (TBD), Jordan
6. Dec 12: Signature. Owner: Dana Okafor

Gaps to confirm with the buyer
- No legal or procurement contact on the deal yet.
- The two weeks for legal is a guess. Ask Dana how long their last vendor review took.

No Notion page created yet. Reply 'create' to make it under Deals > Mossgate Labs.

Time and cost

Estimate About 10–15 minutes, most of it fixing dates and owners.

Assumptions: One deal with three or four contacts and about 20 logged activities.

HubSpot: Reads only: the deal, its close date, associated contacts and recent activities. Credit use not confirmed by HubSpot.
Notion: One search for the parent page, plus one page created after you approve it. Credit use not confirmed by Notion.

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

HubSpot Up · auth

ClaudeChatGPTRead + writeCredits not confirmed
https://mcp.hubspot.com
Notion Up · auth

ClaudeChatGPTClaude CodeCursorCopilotRead + writeCredits not confirmed
https://mcp.notion.com/mcp

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 Notion 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 /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.
Notion: Sign in with OAuth in your client (run /mcp in 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"
    },
    "notion": {
      "url": "https://mcp.notion.com/mcp"
    }
  }
}

Step-by-step prompts

Find my HubSpot deal for {company}. Show me the deal stage, amount, close date, the associated contacts with their titles, and a list of activities and notes from the last 60 days. Don't change anything.
From those activities, list anything the buyer has already agreed to or asked for, such as a technical review, security review, legal or procurement step. Quote the note or activity for each one.
Draft a mutual action plan working back from the close date: dated milestones, an owner on each side for each milestone, and a list of gaps to confirm with the buyer. Only use contacts on the deal as buyer owners, and mark missing ones TBD. Show me the draft.
Find the Notion page {parent page} and create the plan as a new page under it, only after I approve the draft. Give me the link.

Run it on a schedule (optional)

This is a by-hand recipe. Run it once a deal reaches the stage where you'd share a plan, then again whenever the close date moves.
If you rerun it, have it compare the new draft with the existing Notion page and show you the changes. Update the page only after you approve them.
Notion supports org-level approval for MCP, so a workspace admin may need to allow the connection before your first run.

Where this goes wrong

Dates that can't work. Working back from the close date can squeeze legal and security into a few days. Have it flag any milestone with less than a week before the next one, and check those with the buyer.
Invented buyer owners. If no legal or procurement contact is on the deal, the model may name someone anyway. Only use contacts on the HubSpot deal, and mark every other owner as TBD.
A stale close date. A plan built from an old close date is wrong from day one. Show the close date and when it was last changed, and confirm it before drafting.
Internal notes in a buyer-facing page. Deal notes often hold pricing floors or competitor notes. Read the draft for anything internal before you approve it, and keep the page somewhere you control who sees it.

Gotchas

HubSpot only shows records the connected user can see, and non-admin users need a Super Admin to approve the connector first.
Notion admins can turn individual MCP tools off. If creating the page fails, ask your workspace admin whether page creation is allowed.
Notion's help center names ChatGPT Pro as the supported ChatGPT tier, so check your plan if you use ChatGPT.

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 mutual-action-plan-notion.md

Vendor sites: HubSpot. If we join an affiliate program, these links will be labeled as affiliate links.