A Claude Skill that takes an account ID and outputs a fully populated Notion deal-room: account snapshot, stakeholder map, MEDDPICC scorecard, competitive landscape, mutual close plan template. Replaces the two hours an AE spends prepping for a renewal kickoff.

What you’ll need

Salesforce with read access to Accounts, Contacts, Opportunities, and Activities
Notion with a deal-room template database and an API integration token
Claude.ai or Claude Code
Your team’s MEDDPICC or qualification doc as project knowledge

Setup

Install the Skill. deal-room.skill exposes pull_account_context, build_stakeholder_map, score_qualification, and render_notion_doc.
Wire Salesforce. API user with read scope. The Skill pulls the parent account, all related opportunities, the contact list, and the last ninety days of activity.
Wire Notion. Add the integration to the deal-room database. Pass the database ID to the Skill. Each generated doc lands as a new row with the account name as the page title.
Drop in the template structure. A Notion template page with the section headers your team uses. The Skill fills them in; the structure stays consistent.
Test on one account. Pick an account you know cold. Spot-check the stakeholder map and MEDDPICC scoring. Tune the prompt for your vocabulary.

How it works

The Skill runs four steps. First, it pulls account context from Salesforce, including the contact list with titles. Second, it asks Claude to build a stakeholder map: who are the likely champions, the economic buyer, the technical evaluator, the blockers. This is inferred from titles, activity history, and the account’s industry. Third, it scores the deal against your qualification framework, surfacing gaps as questions for the AE. Fourth, it renders into the Notion template.

The stakeholder map is the most useful piece. AEs typically build it in their head; rendering it explicitly forces the question “who is missing.” Claude will literally say “no champion identified” when the activity history shows zero engagement with anyone outside procurement.

Watch-outs

Title-based inference is shallow. A “Director of Operations” might be your buyer or your blocker depending on the company. The Skill flags inference confidence per stakeholder; do not treat the map as ground truth.
Activity history quality. If reps do not log anything in Salesforce, the stakeholder map collapses to “the people on the opportunity contact role.” Garbage in.
Notion API rate limits. Each section is a block creation call. A populated deal-room can be fifty calls. The Skill batches and backs off, but very large templates will hit limits.
Refresh cadence. Deal-rooms go stale fast. Add a refresh function or schedule a weekly re-run that updates the doc in place.

Stack

Salesforce — account, contact, and activity context
Notion — destination doc layer
Claude — stakeholder inference, qualification scoring, narrative generation