sales-skills/sales-deal-room
skills/sales-deal-room/SKILL.md
Designs a Qwilr deal room for complex multi-stakeholder B2B deals. Use when a deal has too many stakeholders to manage over email, buyers keep losing track of materials, there's no single source of truth for a complex deal, you need a mutual action plan to keep procurement on track, or an enterprise deal needs a polished hub for all parties.
$ install --global
skillsauthnpx skillsauth add sales-skills/sales sales-deal-roomInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 5:02 AM185.0s2 files scanned
SKILL.md
- name:
- sales-deal-room
- description:
- Designs a Qwilr deal room for complex multi-stakeholder B2B deals. Use when a deal has too many stakeholders to manage over email, buyers keep losing track of materials, there's no single source of truth for a complex deal, you need a mutual action plan to keep procurement on track, or an enterprise deal needs a polished hub for all parties.
- argument-hint:
- [describe the deal — type, stakeholders, stage, and what materials are needed]
- version:
- 1.0.0
- tags:
- [sales, proposal, deal-room, qwilr]
Design a Qwilr Deal Room
Help the user architect a Qwilr deal room — a multi-page digital sales room for complex B2B deals with multiple stakeholders, long sales cycles, and lots of moving parts.
When to use a deal room vs. a single proposal
| Scenario | Use |
|---|---|
| Simple deal, single decision-maker, straightforward pricing | Single proposal page (/sales-proposal-page) |
| Multiple stakeholders, complex evaluation, needs ongoing updates | Deal room (this skill) |
| Enterprise deal with procurement, legal, technical review | Deal room |
| Partner/channel deal with shared materials | Deal room |
| Expansion deal with existing customer needing executive buy-in | Deal room |
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
-
What type of deal is this?
- A) New logo — first time selling to this company
- B) Expansion — upselling/cross-selling existing customer
- C) Renewal — contract renewal with potential changes
- D) Partner/channel deal — working through a partner
- E) Other — describe it
-
Who are the stakeholders? (select all that apply)
- A) Executive sponsor (C-suite / VP)
- B) Economic buyer (budget holder)
- C) Technical evaluator (engineering/IT)
- D) End users / champions
- E) Procurement / legal
- F) External consultant or advisor
- G) Other — describe
-
What materials do you already have?
- A) Nothing yet — starting from scratch
- B) We have a proposal/quote
- C) We have a pitch deck
- D) We have case studies and technical docs
- E) We have most things, need to organize them
-
What's the deal timeline?
- A) Trying to close this month
- B) 1-3 month sales cycle
- C) 3-6 month enterprise cycle
- D) 6+ months
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Step 2 — Deal room architecture
Design the page-by-page structure. A deal room is a collection of Qwilr pages organized as a hub with linked sub-pages. The hub page is the "front door" that each stakeholder visits.
Recommended structure
Hub Page (the main deal room page — everyone starts here)
| Section | Block Type | Content | |---|---|---| | Welcome header | Splash | Personalized greeting, company logos, deal room title | | Navigation | Text + buttons | Links to each sub-page, organized by topic | | Key contacts | Text + Image | Your team's contacts with photos and roles | | Timeline snapshot | Text | High-level mutual action plan with key dates | | Latest updates | Text | What's new since last visit (keep this updated) |
Sub-pages (linked from the hub — create based on what the deal needs):
| Page | Who it's for | Content | |---|---|---| | Executive Summary | Executive sponsor | Business case, ROI, strategic alignment | | Technical Overview | Technical evaluator | Architecture, integrations, security, compliance | | Proposal & Pricing | Economic buyer | Interactive quote block, pricing options, terms | | Case Studies | All stakeholders | Relevant customer stories, metrics, testimonials | | Implementation Plan | Technical + Ops | Timeline, phases, resource requirements, dependencies | | Security & Compliance | IT / Legal / Procurement | Certifications, data handling, SLAs, DPA | | Mutual Action Plan | All stakeholders | Shared timeline with milestones, owners, and status | | FAQ & Objection Handling | Champions | Answers to common questions champions get asked internally |
Adapting for deal type
- New logo: Heavier on Executive Summary, Case Studies, and Security. Include a "Why Us" page if competitive.
- Expansion: Lead with "Results So Far" page showing value delivered, then expansion scope.
- Renewal: Lead with partnership recap, then changes/additions for the new term.
- Partner deal: Include a partner-facing page with co-selling materials and margin details.
Step 3 — Content briefs and hub page copy
Hub page draft copy
Write the actual content for the hub/navigation page:
Welcome section: "Welcome to the [Company] + [Your Company] Deal Room. This is your central hub for everything related to our partnership. Below you'll find the key materials organized by topic — click into any section to dive deeper."
Navigation section: Create a card-style layout linking to each sub-page with a one-line description:
- Executive Summary — The business case for [solution]: ROI, strategic fit, and expected outcomes
- Technical Overview — Architecture, integrations, security posture, and compliance details
- Proposal & Pricing — Interactive pricing with options to customize your package
- Case Studies — How companies like yours achieved [specific outcome]
- Implementation Plan — Timeline, phases, and what we need from each team
- Mutual Action Plan — Our shared roadmap to getting this live by [target date]
Key contacts section: List 2-3 people from your team with name, title, photo placeholder, email, and one line about their role in this deal.
Content briefs for sub-pages
For each sub-page, provide:
- Audience: Who this page is for and what they care about
- Key message: The one thing this page should communicate
- Structure: Section-by-section outline with recommended block types
- Tone: How formal/technical/executive the language should be
- CTA: What action the reader should take after this page
Step 4 — Mutual action plan
Design the timeline page with milestones and owners:
| Milestone | Owner | Target Date | Status | |---|---|---|---| | Discovery & scoping complete | Both | [date] | Done | | Technical evaluation | Buyer's IT team | [date] | In progress | | Security review | Buyer's security | [date] | Not started | | Proposal & pricing review | Economic buyer | [date] | Not started | | Legal / contract review | Both legal teams | [date] | Not started | | Executive sign-off | Executive sponsor | [date] | Not started | | Contract signed | Both | [date] | Not started | | Kickoff & implementation begins | Both | [date] | Not started |
Customize milestones based on the deal type and timeline. For faster deals, collapse steps. For enterprise deals, add procurement and compliance milestones.
Step 5 — Analytics strategy
Set up engagement tracking per stakeholder by configuring webhooks for the deal room pages:
Which events to watch per stakeholder
| Stakeholder | Watch for | What it means | |---|---|---| | Executive sponsor | Views Executive Summary page | They're engaged — or their EA is screening | | Technical evaluator | Views Technical Overview, time on security page | Doing due diligence — prepare for technical questions | | Economic buyer | Views Pricing page repeatedly | Evaluating cost — may need ROI reinforcement | | Procurement/Legal | Views Security & Compliance page | Deal is in procurement — prepare for contract negotiation | | New/unknown viewer | Views any page | Champion is sharing internally — the deal is expanding |
Webhook setup for deal room
curl -X POST https://api.qwilr.com/v1/webhooks \
-H "Authorization: Bearer $QWILR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-endpoint.com/qwilr-deal-room",
"events": ["pageFirstViewed", "pageViewed", "pageAccepted", "pagePartiallyAccepted"]
}'
Use view data to:
- Identify which stakeholders are engaged and which aren't
- Spot new stakeholders entering the evaluation
- Time your follow-ups to when people are actively reviewing
- Update your champion on who's looked at what
For full webhook and CRM automation setup, use /sales-qwilr-automation.
In Seismic
- Digital Sales Rooms (DSR): Create buyer-facing microsites for complex deals. Curate content by stakeholder role — executive summaries for C-suite, technical specs for evaluators, ROI calculators for finance.
- Per-stakeholder tracking: See which stakeholder viewed which content, how long they spent, and what they downloaded. Identify champions (high engagement) and blockers (no activity).
- Content recommendations: Seismic's AI (Aura) suggests relevant content for the deal based on CRM data, deal stage, and buyer persona.
- CRM integration: DSR activity syncs to Salesforce/HubSpot — engagement data appears on the opportunity record for deal reviews.
- Best practice: Create a DSR template per deal type (new business, expansion, renewal) with pre-loaded content for each stage. Customize per deal rather than building from scratch.
Gotchas
-
Don't create too many pages for simple deals. A deal room with 8 sub-pages for a $15k deal is overkill. Match complexity to deal size — small deals need 2-3 pages max (proposal + case study). Reserve the full structure for enterprise deals with multiple stakeholders.
-
Don't use the same content for every stakeholder. The whole point of a deal room is tailored content per role. An executive summary page full of technical specs fails the executive; a pricing page with no ROI context fails the CFO. Write for each audience.
-
Don't skip the mutual action plan. Claude often builds deal rooms with great content but no shared timeline. The MAP is what turns a deal room from a content dump into a collaboration tool. Always include one.
-
Don't forget the executive summary page. Even in a deal room with detailed sub-pages, the hub page needs a concise "why this matters" section. Executives won't click into sub-pages — they'll read the hub and decide if this is worth their time.
-
Don't treat the deal room as "set and forget." A good deal room is updated throughout the sales cycle — latest updates section, MAP status changes, new materials added. Mention this to the user.
-
Self-improving: If you discover something not covered here, append it to
references/learnings.mdwith today's date.
Related skills
/sales-proposal-page— Write a single proposal page (for simpler deals)/sales-proposal-analytics— Interpret engagement signals from deal room pages/sales-qwilr-automation— Automate deal room creation and CRM sync/sales-proposal-template— Create reusable deal room templates/sales-close— Closing strategies and mutual action plan tactics/sales-seismic— Seismic platform help including Digital Sales Rooms and content management/sales-do— Not sure which skill to use? The router matches any sales objective to the right skill. Install:npx skills add sales-skills/sales --skill sales-do
Related Skills
sales-skills/sales-upviral
tools
VerifiedTrustedCommunity
UpViral platform help — viral referral marketing and list-building platform (by Emarky) for viral sweepstakes, giveaway/reward campaigns, pre-launch waiting lists, and milestone referral programs, with REST API (app.upviral.com/api/v1/), callback-URL webhooks, PHP SDK, fraud detection (IP-based suspicious-referral flagging), A/B testing, smart leaderboards, unlockable incentives, and 30+ native ESP/CRM integrations (Mailchimp, ActiveCampaign, ConvertKit, AWeber, HubSpot, Klaviyo, Intercom) plus Zapier/Make/Pipedream/Integrately/Pabbly. Use when UpViral campaigns aren't tracking referral points correctly, deciding between Starter $79/mo annual (10K leads, 1 brand, NO API) vs Business $119/mo (25K, 2 brands, API + webhooks unlocked) vs Premium $319/mo (100K, 5 brands, dedicated account manager), the API returns errors because you're on the Starter tier where API/webhooks are gated, building an UpViral→CRM or UpViral→data-warehouse pipeline with add_contact / get_leads / get_leads_points / add_points / get_custom_fields / lists methods (uvapikey + uvmethod form-encoded POST), interpreting fraud flags where same-IP referrals get marked suspicious and you must manually activate/delete/blacklist, setting up the Callback URL (webhook) to fire on reward-unlock events, Zapier New Lead / New Reward Unlocked triggers not firing, ClickFunnels/Shopify/funnel-builder integration breaking, the drag-and-drop page builder showing broken widgets or limited customization, the setup feeling long and complicated for your first campaign, or picking UpViral over Viral Loops / KickoffLabs / Vyper / Prefinery / Gleam / KingSumo / ShortStack for a viral campaign. Do NOT use for general newsletter audience growth strategy across all platforms (use /sales-audience-growth), newsletter monetization (use /sales-newsletter), KickoffLabs-specific help (use /sales-kickofflabs), no-code merge-tag newsletter referrals (use /sales-referralkit), SparkLoop paid recommendations (use /sales-sparkloop), or full-stack multi-level Level-1/2/3 referral/affiliate tracking (use /sales-referralhero).
39SKILL.mdUpdated Jun 4, 2026
sales-skills/sales-referralhero
development
VerifiedTrustedCommunity
ReferralHero platform help — full-stack referral, affiliate, waitlist, contest, and NPS platform with subscriber API, webhooks, Zapier, Mailchimp/Kit/AWeber/Klaviyo/ActiveCampaign/SendLane connectors, coupon codes, multi-level referral tracking (Level 1/2/3), anti-fraud, and 5,000 calls/hour rate limit. Use when ReferralHero campaigns aren't tracking referrals correctly, deciding between PRO $199/mo (10K members, includes API + webhooks) and PREMIUM $399/mo (50K members, adds ReCaptcha + SMS verification), authentication is failing with no_token or X-API-Key header is being ignored, multi-level referral counts (Level 2/3) aren't appearing for downline subscribers, coupon group endpoints return 404 or coupon arrays max out, hitting the 5,000 calls/hour soft limit and getting too_many_calls 429s, the Mailchimp/Kit native integration is double-adding subscribers, webhook payloads aren't firing on confirmation events, importing Stripe customer IDs through transaction tracking, generating reward fulfillment when subscribers cross milestone thresholds (promote/unlock_promoted_reward), comparing ReferralHero against SparkLoop/ReferralKit/Viral Loops/GrowSurf/KickoffLabs for referral marketing, or routing referral data via add_bulk_transactions (500-transaction batch limit). Do NOT use for general newsletter audience growth strategy (use /sales-audience-growth), general newsletter monetization (use /sales-newsletter), no-code newsletter-only referral with merge-tag insertion (use /sales-referralkit), SparkLoop's paid recommendations or partner network (use /sales-sparkloop), or affiliate program strategy across many platforms (use /sales-affiliate-program).
39SKILL.mdUpdated Jun 4, 2026
sales-skills/sales-kickofflabs
tools
VerifiedTrustedCommunity
KickoffLabs platform help — viral marketing platform for pre-launch waitlists, bonus-entry giveaways, milestone-reward referral programs, leaderboard giveaways, and email opt-in bribes with REST API v1 + v2, server-side webhooks (in/out), KOL.js JavaScript library, AnyForm script for custom pages, fraud detection (duplicate_ip / bounced / duplidate_email flags), SMS verification add-on, native ESP integrations (Klaviyo, Mailchimp, ActiveCampaign, Brevo), website builders (Webflow, Wix, Squarespace, Weebly), Shopify, Facebook Audiences, Slack, Zapier. Use when KickoffLabs viral campaigns aren't tracking referrals correctly, deciding between Hobby $13/mo annual (500 leads/mo no A/B no reward emails) vs Premium $48/mo (2.5K + A/B + reward emails + tracking pixels) vs Business $99/mo (10K + custom email templates + custom domains + advanced reporting + 3 team) vs Enterprise $202/mo (25K + 5 team + SMS included), API key getting rejected because you embedded it in client-side JavaScript instead of server-side, can't decide whether to use v1 /subscribe vs v2 /tags/:TAG_ID/lead for lead creation, webhook payloads firing with `__fraudulent` flag and you need to interpret the duplicate_ip/bounced/duplidate_email reason codes (yes, duplidate is spelled that way in their docs), AnyForm script not posting to KickoffLabs vs native API endpoint, leaderboard endpoint returning more than 50 leads is not allowed, social_id (kid in share URLs) attribution chain breaking between v1 and v2, contest score vs lead count metrics in the webhook payload are confusing, SMS Verification only available on Premium+ as $50/mo add-on (Enterprise includes), per-month lead cap auto-upgrades at $8 per 1000 overage leads, picking between KickoffLabs and Viral Loops / UpViral / Prefinery / ReferralCandy / Voucherify for viral campaign type fit, or rate limit per tier (10-100 calls/minute) is hitting on bulk imports. Do NOT use for general newsletter audience growth strategy (use /sales-audience-growth), general newsletter monetization (use /sales-newsletter), no-code merge-tag-only newsletter referrals (use /sales-referralkit), SparkLoop paid recommendations + partner network (use /sales-sparkloop), or full-stack referral/affiliate with multi-level Level-1/2/3 tracking (use /sales-referralhero).
39SKILL.mdUpdated Jun 4, 2026
sales-skills/sales-do
development
VerifiedTrustedCommunity
Routes any sales, marketing, ad, or GTM objective to the right specialized skill and outputs the install command for that skill plus a ready-to-paste prompt packed with the user's context. Asks clarifying questions when the objective is ambiguous, then hands back a copy-paste-runnable next step. Covers prospecting, outbound cadences, deals, proposals, forecasting, deliverability, enrichment, intent, content, coaching, CRO, SEO, launch directories, newsletters, email/SMS/push marketing, chatbots, influencer marketing, social media, employee advocacy, media relations, reviews, data hygiene, B2B advertising, retargeting, affiliate, loyalty, digital products, memberships, webinars, checkout, and platform-specific help. Use when the user has a sales or marketing question and isn't sure which skill to use, or wants a multi-skill sequence with a batch install command. Do NOT use to solve problems directly — this skill only routes.
39SKILL.mdUpdated Apr 24, 2026