revops
Design and optimize systems connecting marketing, sales, and customer success into a unified revenue engine.
sales-deal-room
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 enterpr...
Full skill instructions
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.
| 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 |
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
What type of deal is this?
Who are the stakeholders? (select all that apply)
What materials do you already have?
What's the deal timeline?
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.
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.
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 |
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:
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.
For each sub-page, provide:
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.
Set up engagement tracking per stakeholder by configuring webhooks for the deal room pages:
| 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 |
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:
For full webhook and CRM automation setup, use /sales-qwilr-automation.
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.md with today's date.
User says: "We're 4 months into a new-logo deal with a 2,000-person fintech. There's a VP sponsor, a head of engineering, a security/IT team, and procurement just got pulled in. The thread is a mess and people keep asking for the same docs. Help me build a Qwilr deal room."
Skill does:
Result: A page-by-page deal room blueprint plus ready-to-paste hub copy, a procurement-aware action plan, and an engagement-tracking plan — the buyer gets one source of truth instead of a tangled email thread.
User says: "Existing customer, want to upsell a second product line, but I need a VP we haven't worked with to sponsor it. Closing target is this quarter."
Skill does:
Result: A lean expansion deal room that opens with proof of value and routes a new executive to a concise business case, with a timeline matched to the close date.
Cause: Too many sub-pages for the deal size — an 8-page structure built for a small or simple deal buries the few things that matter.
Solution: Match page count to complexity. For small deals use 2-3 pages max (proposal + case study) and reserve the full hub-and-sub-page structure for enterprise deals with multiple stakeholders. Make sure the hub page itself carries a concise "why this matters" summary, since executives decide from the hub without clicking in.
Cause: The same generic content is reused across pages, so an executive hits technical specs and a CFO hits pricing with no ROI context — the per-role tailoring that justifies a deal room is missing.
Solution: Write each sub-page for its specific audience using the content-brief fields (audience, key message, tone, CTA). Keep the Executive Summary strategic and outcome-focused, give the Technical Overview the depth evaluators want, and pair pricing with ROI framing for the economic buyer.
Cause: The webhook subscription is missing the relevant events, the endpoint isn't reachable, or the auth token is wrong.
Solution: Confirm the subscription includes pageFirstViewed, pageViewed, pageAccepted, and pagePartiallyAccepted, that the Authorization: Bearer $QWILR_TOKEN header is valid, and that your endpoint returns 2xx. For full webhook delivery and CRM-sync setup and debugging, use /sales-qwilr-automation.
/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-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-doDesign and optimize systems connecting marketing, sales, and customer success into a unified revenue engine.
Strategic planning and optimization for email capture offers and gated content.
Directory submissions: the foundation layer of distribution that passes backlinks and discovery surface area into your marketing pages.
Sequence and choreograph multi-step animations with precise timing control and nested timelines.
Structured framework for planning product launches, feature announcements, and go-to-market strategies.
Upload files to Google Drive with automatic MIME type detection and metadata.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
firecrawl lead gen
firecrawl lead research
firecrawl demo walkthrough
Team leadership persona with standup coordination, meeting prep, task delegation, and team communication.
Identify large Google Drive files consuming storage quota.
Revolutionize Video Creation with AI-Generated Avatars and Voices
Social media on autopilot
Design custom logos instantly with AI.
Text-heavy marketing and design images
Boost Your SEO with Content and SEO Silos
Revolutionize Your Marketing with AI-Powered MarketingBlocks!
10X faster & free AI content creation for 100+ use cases
Tribescaler | Make Your Tweets Go Viral