chore: import upstream snapshot with attribution
This commit is contained in:
wehub-resource-sync
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"name": "sales",
|
||||
"version": "1.3.0",
|
||||
"description": "Prospect, craft outreach, and build deal strategy faster. Prep for calls, manage your pipeline, and write personalized messaging that moves deals forward.",
|
||||
"author": {
|
||||
"name": "Anthropic"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,64 @@
|
||||
{
|
||||
"mcpServers": {
|
||||
"slack": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.slack.com/mcp",
|
||||
"oauth": {
|
||||
"clientId": "1601185624273.8899143856786",
|
||||
"callbackPort": 3118
|
||||
}
|
||||
},
|
||||
"hubspot": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.hubspot.com/anthropic"
|
||||
},
|
||||
"close": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.close.com/mcp"
|
||||
},
|
||||
"monday": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.monday.com/mcp"
|
||||
},
|
||||
"clay": {
|
||||
"type": "http",
|
||||
"url": "https://api.clay.com/v3/mcp"
|
||||
},
|
||||
"zoominfo": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.zoominfo.com/mcp"
|
||||
},
|
||||
"notion": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.notion.com/mcp"
|
||||
},
|
||||
"atlassian": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.atlassian.com/v1/mcp"
|
||||
},
|
||||
"fireflies": {
|
||||
"type": "http",
|
||||
"url": "https://api.fireflies.ai/mcp"
|
||||
},
|
||||
"apollo": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.apollo.io/mcp"
|
||||
},
|
||||
"outreach": {
|
||||
"type": "http",
|
||||
"url": "https://api.outreach.io/mcp/"
|
||||
},
|
||||
"google calendar": {
|
||||
"type": "http",
|
||||
"url": ""
|
||||
},
|
||||
"gmail": {
|
||||
"type": "http",
|
||||
"url": ""
|
||||
},
|
||||
"similarweb": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.similarweb.com/mcp"
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,22 @@
|
||||
# Connectors
|
||||
|
||||
## How tool references work
|
||||
|
||||
Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~CRM` might mean Salesforce, HubSpot, or any other CRM with an MCP server.
|
||||
|
||||
Plugins are **tool-agnostic** — they describe workflows in terms of categories (CRM, chat, email, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works.
|
||||
|
||||
## Connectors for this plugin
|
||||
|
||||
| Category | Placeholder | Included servers | Other options |
|
||||
|----------|-------------|-----------------|---------------|
|
||||
| Calendar | `~~calendar` | Google Calendar, Microsoft 365 | — |
|
||||
| Chat | `~~chat` | Slack | Microsoft Teams |
|
||||
| Competitive intelligence | `~~competitive intelligence` | Similarweb | Crayon, Klue |
|
||||
| CRM | `~~CRM` | HubSpot, Close, Monday | Salesforce, Pipedrive, Copper |
|
||||
| Data enrichment | `~~data enrichment` | Clay, ZoomInfo, Apollo | Clearbit, Lusha |
|
||||
| Email | `~~email` | Gmail, Microsoft 365 | — |
|
||||
| Knowledge base | `~~knowledge base` | Notion | Confluence, Guru |
|
||||
| Meeting transcription | `~~conversation intelligence` | Fireflies | Gong, Chorus, Otter.ai |
|
||||
| Project tracker | `~~project tracker` | Atlassian (Jira/Confluence) | Linear, Asana |
|
||||
| Sales engagement | `~~sales engagement` | Outreach | Salesloft, Apollo |
|
||||
+202
@@ -0,0 +1,202 @@
|
||||
|
||||
Apache License
|
||||
Version 2.0, January 2004
|
||||
http://www.apache.org/licenses/
|
||||
|
||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
|
||||
1. Definitions.
|
||||
|
||||
"License" shall mean the terms and conditions for use, reproduction,
|
||||
and distribution as defined by Sections 1 through 9 of this document.
|
||||
|
||||
"Licensor" shall mean the copyright owner or entity authorized by
|
||||
the copyright owner that is granting the License.
|
||||
|
||||
"Legal Entity" shall mean the union of the acting entity and all
|
||||
other entities that control, are controlled by, or are under common
|
||||
control with that entity. For the purposes of this definition,
|
||||
"control" means (i) the power, direct or indirect, to cause the
|
||||
direction or management of such entity, whether by contract or
|
||||
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
||||
outstanding shares, or (iii) beneficial ownership of such entity.
|
||||
|
||||
"You" (or "Your") shall mean an individual or Legal Entity
|
||||
exercising permissions granted by this License.
|
||||
|
||||
"Source" form shall mean the preferred form for making modifications,
|
||||
including but not limited to software source code, documentation
|
||||
source, and configuration files.
|
||||
|
||||
"Object" form shall mean any form resulting from mechanical
|
||||
transformation or translation of a Source form, including but
|
||||
not limited to compiled object code, generated documentation,
|
||||
and conversions to other media types.
|
||||
|
||||
"Work" shall mean the work of authorship, whether in Source or
|
||||
Object form, made available under the License, as indicated by a
|
||||
copyright notice that is included in or attached to the work
|
||||
(an example is provided in the Appendix below).
|
||||
|
||||
"Derivative Works" shall mean any work, whether in Source or Object
|
||||
form, that is based on (or derived from) the Work and for which the
|
||||
editorial revisions, annotations, elaborations, or other modifications
|
||||
represent, as a whole, an original work of authorship. For the purposes
|
||||
of this License, Derivative Works shall not include works that remain
|
||||
separable from, or merely link (or bind by name) to the interfaces of,
|
||||
the Work and Derivative Works thereof.
|
||||
|
||||
"Contribution" shall mean any work of authorship, including
|
||||
the original version of the Work and any modifications or additions
|
||||
to that Work or Derivative Works thereof, that is intentionally
|
||||
submitted to Licensor for inclusion in the Work by the copyright owner
|
||||
or by an individual or Legal Entity authorized to submit on behalf of
|
||||
the copyright owner. For the purposes of this definition, "submitted"
|
||||
means any form of electronic, verbal, or written communication sent
|
||||
to the Licensor or its representatives, including but not limited to
|
||||
communication on electronic mailing lists, source code control systems,
|
||||
and issue tracking systems that are managed by, or on behalf of, the
|
||||
Licensor for the purpose of discussing and improving the Work, but
|
||||
excluding communication that is conspicuously marked or otherwise
|
||||
designated in writing by the copyright owner as "Not a Contribution."
|
||||
|
||||
"Contributor" shall mean Licensor and any individual or Legal Entity
|
||||
on behalf of whom a Contribution has been received by Licensor and
|
||||
subsequently incorporated within the Work.
|
||||
|
||||
2. Grant of Copyright License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
copyright license to reproduce, prepare Derivative Works of,
|
||||
publicly display, publicly perform, sublicense, and distribute the
|
||||
Work and such Derivative Works in Source or Object form.
|
||||
|
||||
3. Grant of Patent License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
(except as stated in this section) patent license to make, have made,
|
||||
use, offer to sell, sell, import, and otherwise transfer the Work,
|
||||
where such license applies only to those patent claims licensable
|
||||
by such Contributor that are necessarily infringed by their
|
||||
Contribution(s) alone or by combination of their Contribution(s)
|
||||
with the Work to which such Contribution(s) was submitted. If You
|
||||
institute patent litigation against any entity (including a
|
||||
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
||||
or a Contribution incorporated within the Work constitutes direct
|
||||
or contributory patent infringement, then any patent licenses
|
||||
granted to You under this License for that Work shall terminate
|
||||
as of the date such litigation is filed.
|
||||
|
||||
4. Redistribution. You may reproduce and distribute copies of the
|
||||
Work or Derivative Works thereof in any medium, with or without
|
||||
modifications, and in Source or Object form, provided that You
|
||||
meet the following conditions:
|
||||
|
||||
(a) You must give any other recipients of the Work or
|
||||
Derivative Works a copy of this License; and
|
||||
|
||||
(b) You must cause any modified files to carry prominent notices
|
||||
stating that You changed the files; and
|
||||
|
||||
(c) You must retain, in the Source form of any Derivative Works
|
||||
that You distribute, all copyright, patent, trademark, and
|
||||
attribution notices from the Source form of the Work,
|
||||
excluding those notices that do not pertain to any part of
|
||||
the Derivative Works; and
|
||||
|
||||
(d) If the Work includes a "NOTICE" text file as part of its
|
||||
distribution, then any Derivative Works that You distribute must
|
||||
include a readable copy of the attribution notices contained
|
||||
within such NOTICE file, excluding those notices that do not
|
||||
pertain to any part of the Derivative Works, in at least one
|
||||
of the following places: within a NOTICE text file distributed
|
||||
as part of the Derivative Works; within the Source form or
|
||||
documentation, if provided along with the Derivative Works; or,
|
||||
within a display generated by the Derivative Works, if and
|
||||
wherever such third-party notices normally appear. The contents
|
||||
of the NOTICE file are for informational purposes only and
|
||||
do not modify the License. You may add Your own attribution
|
||||
notices within Derivative Works that You distribute, alongside
|
||||
or as an addendum to the NOTICE text from the Work, provided
|
||||
that such additional attribution notices cannot be construed
|
||||
as modifying the License.
|
||||
|
||||
You may add Your own copyright statement to Your modifications and
|
||||
may provide additional or different license terms and conditions
|
||||
for use, reproduction, or distribution of Your modifications, or
|
||||
for any such Derivative Works as a whole, provided Your use,
|
||||
reproduction, and distribution of the Work otherwise complies with
|
||||
the conditions stated in this License.
|
||||
|
||||
5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||
any Contribution intentionally submitted for inclusion in the Work
|
||||
by You to the Licensor shall be under the terms and conditions of
|
||||
this License, without any additional terms or conditions.
|
||||
Notwithstanding the above, nothing herein shall supersede or modify
|
||||
the terms of any separate license agreement you may have executed
|
||||
with Licensor regarding such Contributions.
|
||||
|
||||
6. Trademarks. This License does not grant permission to use the trade
|
||||
names, trademarks, service marks, or product names of the Licensor,
|
||||
except as required for reasonable and customary use in describing the
|
||||
origin of the Work and reproducing the content of the NOTICE file.
|
||||
|
||||
7. Disclaimer of Warranty. Unless required by applicable law or
|
||||
agreed to in writing, Licensor provides the Work (and each
|
||||
Contributor provides its Contributions) on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
||||
implied, including, without limitation, any warranties or conditions
|
||||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
||||
PARTICULAR PURPOSE. You are solely responsible for determining the
|
||||
appropriateness of using or redistributing the Work and assume any
|
||||
risks associated with Your exercise of permissions under this License.
|
||||
|
||||
8. Limitation of Liability. In no event and under no legal theory,
|
||||
whether in tort (including negligence), contract, or otherwise,
|
||||
unless required by applicable law (such as deliberate and grossly
|
||||
negligent acts) or agreed to in writing, shall any Contributor be
|
||||
liable to You for damages, including any direct, indirect, special,
|
||||
incidental, or consequential damages of any character arising as a
|
||||
result of this License or out of the use or inability to use the
|
||||
Work (including but not limited to damages for loss of goodwill,
|
||||
work stoppage, computer failure or malfunction, or any and all
|
||||
other commercial damages or losses), even if such Contributor
|
||||
has been advised of the possibility of such damages.
|
||||
|
||||
9. Accepting Warranty or Additional Liability. While redistributing
|
||||
the Work or Derivative Works thereof, You may choose to offer,
|
||||
and charge a fee for, acceptance of support, warranty, indemnity,
|
||||
or other liability obligations and/or rights consistent with this
|
||||
License. However, in accepting such obligations, You may act only
|
||||
on Your own behalf and on Your sole responsibility, not on behalf
|
||||
of any other Contributor, and only if You agree to indemnify,
|
||||
defend, and hold each Contributor harmless for any liability
|
||||
incurred by, or claims asserted against, such Contributor by reason
|
||||
of your accepting any such warranty or additional liability.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
APPENDIX: How to apply the Apache License to your work.
|
||||
|
||||
To apply the Apache License to your work, attach the following
|
||||
boilerplate notice, with the fields enclosed by brackets "[]"
|
||||
replaced with your own identifying information. (Don't include
|
||||
the brackets!) The text should be enclosed in the appropriate
|
||||
comment syntax for the file format. We also recommend that a
|
||||
file or class name and description of purpose be included on the
|
||||
same "printed page" as the copyright notice for easier
|
||||
identification within third-party archives.
|
||||
|
||||
Copyright [yyyy] [name of copyright owner]
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
+146
@@ -0,0 +1,146 @@
|
||||
# Sales Plugin
|
||||
|
||||
A sales productivity plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Helps with prospecting, outreach, pipeline management, call preparation, and deal strategy. Works with any sales team — standalone with web search and your input, supercharged when you connect your CRM, email, and other tools.
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
claude plugins add knowledge-work-plugins/sales
|
||||
```
|
||||
|
||||
## Commands
|
||||
|
||||
Explicit workflows you invoke with a slash command:
|
||||
|
||||
| Command | Description |
|
||||
|---|---|
|
||||
| `/call-summary` | Process call notes or transcript — extract action items, draft follow-up, generate internal summary |
|
||||
| `/forecast` | Generate a weighted sales forecast — upload CSV or describe your pipeline, set quota, get projections |
|
||||
| `/pipeline-review` | Analyze pipeline health — prioritize deals, flag risks, get weekly action plan |
|
||||
|
||||
All commands work **standalone** (paste notes, upload CSV, or describe your situation) and get **supercharged** with MCP connectors.
|
||||
|
||||
## Skills
|
||||
|
||||
Domain knowledge Claude uses automatically when relevant:
|
||||
|
||||
| Skill | Description |
|
||||
|---|---|
|
||||
| `account-research` | Research a company or person — web search for company intel, key contacts, recent news, hiring signals |
|
||||
| `call-prep` | Prepare for sales calls — account context, attendee research, suggested agenda, discovery questions |
|
||||
| `daily-briefing` | Prioritized daily sales briefing — meetings, pipeline alerts, email priorities, suggested actions |
|
||||
| `draft-outreach` | Research-first outreach — research the prospect, then draft personalized email and LinkedIn messages |
|
||||
| `competitive-intelligence` | Research competitors — product comparison, pricing intel, recent releases, differentiation matrix, sales talk tracks |
|
||||
| `create-an-asset` | Generate custom sales assets — landing pages, decks, one-pagers, workflow demos tailored to your prospect |
|
||||
|
||||
## Example Workflows
|
||||
|
||||
### After a Call
|
||||
|
||||
```
|
||||
/call-summary
|
||||
```
|
||||
|
||||
Paste your notes or transcript. Get a structured summary, action items with owners, and a draft follow-up email. If CRM is connected, offers to log the activity and create tasks.
|
||||
|
||||
### Weekly Forecast
|
||||
|
||||
```
|
||||
/forecast
|
||||
```
|
||||
|
||||
Upload a CSV export from your CRM (or paste your deals). Tell me your quota and timeline. Get a weighted forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis.
|
||||
|
||||
### Pipeline Review
|
||||
|
||||
```
|
||||
/pipeline-review
|
||||
```
|
||||
|
||||
Upload a CSV or describe your pipeline. Get a health score, deal prioritization, risk flags (stale deals, past close dates, single-threaded), and a weekly action plan.
|
||||
|
||||
### Researching a Prospect
|
||||
|
||||
Just ask naturally:
|
||||
```
|
||||
Research Acme Corp before my call tomorrow
|
||||
```
|
||||
|
||||
The `account-research` skill triggers automatically and gives you company overview, key contacts, recent news, and recommended approach.
|
||||
|
||||
### Drafting Outreach
|
||||
|
||||
```
|
||||
Draft an email to the VP of Engineering at TechStart
|
||||
```
|
||||
|
||||
The `draft-outreach` skill researches the prospect first, then generates personalized outreach with multiple angles.
|
||||
|
||||
### Competitive Intel
|
||||
|
||||
```
|
||||
How do we compare to Competitor X?
|
||||
```
|
||||
|
||||
The `competitive-intelligence` skill researches both companies and builds a differentiation matrix with talk tracks.
|
||||
|
||||
## Standalone + Supercharged
|
||||
|
||||
Every command and skill works without any integrations:
|
||||
|
||||
| What You Can Do | Standalone | Supercharged With |
|
||||
|-----------------|------------|-------------------|
|
||||
| Process call notes | Paste notes/transcript | Transcripts MCP (e.g. Gong, Fireflies) |
|
||||
| Forecast pipeline | Upload CSV, paste deals | CRM MCP |
|
||||
| Review pipeline | Upload CSV, describe deals | CRM MCP |
|
||||
| Research prospects | Web search | Enrichment MCP (e.g. Clay, ZoomInfo) |
|
||||
| Prep for calls | Describe meeting | CRM, Email, Calendar MCPs |
|
||||
| Draft outreach | Web search + your context | CRM, Email MCPs |
|
||||
| Competitive intel | Web search | CRM (win/loss data), Docs (battlecards) |
|
||||
|
||||
## MCP Integrations
|
||||
|
||||
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).
|
||||
|
||||
Connect your tools for a richer experience:
|
||||
|
||||
| Category | Examples | What It Enables |
|
||||
|---|---|---|
|
||||
| **CRM** | HubSpot, Close | Pipeline data, account history, contact records |
|
||||
| **Transcripts** | Fireflies, Gong, Chorus | Call recordings, transcripts, key moments |
|
||||
| **Enrichment** | Clay, ZoomInfo, Apollo | Company and contact data enrichment |
|
||||
| **Chat** | Slack, Teams | Internal discussions, colleague intel |
|
||||
|
||||
See [CONNECTORS.md](CONNECTORS.md) for the full list of supported integrations, including email, calendar, and additional CRM options.
|
||||
|
||||
## Settings
|
||||
|
||||
Create a `settings.local.json` file to personalize:
|
||||
|
||||
- **Cowork**: Save it in any folder you've shared with Cowork (via the folder picker). The plugin finds it automatically.
|
||||
- **Claude Code**: Save it at `sales/.claude/settings.local.json`.
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Your Name",
|
||||
"title": "Account Executive",
|
||||
"company": "Your Company",
|
||||
"quota": {
|
||||
"annual": 1000000,
|
||||
"quarterly": 250000
|
||||
},
|
||||
"product": {
|
||||
"name": "Your Product",
|
||||
"value_props": [
|
||||
"Key value proposition 1",
|
||||
"Key value proposition 2"
|
||||
],
|
||||
"competitors": [
|
||||
"Competitor A",
|
||||
"Competitor B"
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
The plugin will ask you for this information interactively if it's not configured.
|
||||
@@ -0,0 +1,287 @@
|
||||
---
|
||||
name: account-research
|
||||
description: Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
|
||||
---
|
||||
|
||||
# Account Research
|
||||
|
||||
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ ACCOUNT RESEARCH │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ ALWAYS (works standalone via web search) │
|
||||
│ ✓ Company overview: what they do, size, industry │
|
||||
│ ✓ Recent news: funding, leadership changes, announcements │
|
||||
│ ✓ Hiring signals: open roles, growth indicators │
|
||||
│ ✓ Key people: leadership team from LinkedIn │
|
||||
│ ✓ Product/service: what they sell, who they serve │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + Enrichment: verified emails, phone, tech stack, org chart │
|
||||
│ + CRM: prior relationship, past opportunities, contacts │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
|
||||
Just tell me who to research:
|
||||
|
||||
- "Research Stripe"
|
||||
- "Look up the CTO at Notion"
|
||||
- "Intel on acme.com"
|
||||
- "Who is Sarah Chen at TechCorp?"
|
||||
- "Tell me about [company] before my call"
|
||||
|
||||
I'll run web searches immediately. If you have enrichment or CRM connected, I'll pull that data too.
|
||||
|
||||
---
|
||||
|
||||
## Connectors (Optional)
|
||||
|
||||
Connect your tools to supercharge this skill:
|
||||
|
||||
| Connector | What It Adds |
|
||||
|-----------|--------------|
|
||||
| **Enrichment** | Verified emails, phone numbers, tech stack, org chart, funding details |
|
||||
| **CRM** | Prior relationship history, past opportunities, existing contacts, notes |
|
||||
|
||||
> **No connectors?** No problem. Web search provides solid research for any company or person.
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
```markdown
|
||||
# Research: [Company or Person Name]
|
||||
|
||||
**Generated:** [Date]
|
||||
**Sources:** Web Search [+ Enrichment] [+ CRM]
|
||||
|
||||
---
|
||||
|
||||
## Quick Take
|
||||
|
||||
[2-3 sentences: Who they are, why they might need you, best angle for outreach]
|
||||
|
||||
---
|
||||
|
||||
## Company Profile
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Company** | [Name] |
|
||||
| **Website** | [URL] |
|
||||
| **Industry** | [Industry] |
|
||||
| **Size** | [Employee count] |
|
||||
| **Headquarters** | [Location] |
|
||||
| **Founded** | [Year] |
|
||||
| **Funding** | [Stage + amount if known] |
|
||||
| **Revenue** | [Estimate if available] |
|
||||
|
||||
### What They Do
|
||||
[1-2 sentence description of their business, product, and customers]
|
||||
|
||||
### Recent News
|
||||
- **[Headline]** — [Date] — [Why it matters for your outreach]
|
||||
- **[Headline]** — [Date] — [Why it matters]
|
||||
|
||||
### Hiring Signals
|
||||
- [X] open roles in [Department]
|
||||
- Notable: [Relevant roles like Engineering, Sales, AI/ML]
|
||||
- Growth indicator: [Hiring velocity interpretation]
|
||||
|
||||
---
|
||||
|
||||
## Key People
|
||||
|
||||
### [Name] — [Title]
|
||||
| Field | Detail |
|
||||
|-------|--------|
|
||||
| **LinkedIn** | [URL] |
|
||||
| **Background** | [Prior companies, education] |
|
||||
| **Tenure** | [Time at company] |
|
||||
| **Email** | [If enrichment connected] |
|
||||
|
||||
**Talking Points:**
|
||||
- [Personal hook based on background]
|
||||
- [Professional hook based on role]
|
||||
|
||||
[Repeat for relevant contacts]
|
||||
|
||||
---
|
||||
|
||||
## Tech Stack [If Enrichment Connected]
|
||||
|
||||
| Category | Tools |
|
||||
|----------|-------|
|
||||
| **Cloud** | [AWS, GCP, Azure, etc.] |
|
||||
| **Data** | [Snowflake, Databricks, etc.] |
|
||||
| **CRM** | [e.g. Salesforce, HubSpot] |
|
||||
| **Other** | [Relevant tools] |
|
||||
|
||||
**Integration Opportunity:** [How your product fits with their stack]
|
||||
|
||||
---
|
||||
|
||||
## Prior Relationship [If CRM Connected]
|
||||
|
||||
| Field | Detail |
|
||||
|-------|--------|
|
||||
| **Status** | [New / Prior prospect / Customer / Churned] |
|
||||
| **Last Contact** | [Date and type] |
|
||||
| **Previous Opps** | [Won/Lost and why] |
|
||||
| **Known Contacts** | [Names already in CRM] |
|
||||
|
||||
**History:** [Summary of past relationship]
|
||||
|
||||
---
|
||||
|
||||
## Qualification Signals
|
||||
|
||||
### Positive Signals
|
||||
- ✅ [Signal and evidence]
|
||||
- ✅ [Signal and evidence]
|
||||
|
||||
### Potential Concerns
|
||||
- ⚠️ [Concern and what to watch for]
|
||||
|
||||
### Unknown (Ask in Discovery)
|
||||
- ❓ [Gap in understanding]
|
||||
|
||||
---
|
||||
|
||||
## Recommended Approach
|
||||
|
||||
**Best Entry Point:** [Person and why]
|
||||
|
||||
**Opening Hook:** [What to lead with based on research]
|
||||
|
||||
**Discovery Questions:**
|
||||
1. [Question about their situation]
|
||||
2. [Question about pain points]
|
||||
3. [Question about decision process]
|
||||
|
||||
---
|
||||
|
||||
## Sources
|
||||
- [Source 1](URL)
|
||||
- [Source 2](URL)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Execution Flow
|
||||
|
||||
### Step 1: Parse Request
|
||||
|
||||
```
|
||||
Identify what to research:
|
||||
- "Research Stripe" → Company research
|
||||
- "Look up John Smith at Acme" → Person + company
|
||||
- "Who is the CTO at Notion" → Role-based search
|
||||
- "Intel on acme.com" → Domain-based lookup
|
||||
```
|
||||
|
||||
### Step 2: Web Search (Always)
|
||||
|
||||
```
|
||||
Run these searches:
|
||||
1. "[Company name]" → Homepage, about page
|
||||
2. "[Company name] news" → Recent announcements
|
||||
3. "[Company name] funding" → Investment history
|
||||
4. "[Company name] careers" → Hiring signals
|
||||
5. "[Person name] [Company] LinkedIn" → Profile info
|
||||
6. "[Company name] product" → What they sell
|
||||
7. "[Company name] customers" → Who they serve
|
||||
```
|
||||
|
||||
**Extract:**
|
||||
- Company description and positioning
|
||||
- Recent news (last 90 days)
|
||||
- Leadership team
|
||||
- Open job postings
|
||||
- Technology mentions
|
||||
- Customer base
|
||||
|
||||
### Step 3: Enrichment (If Connected)
|
||||
|
||||
```
|
||||
If enrichment tools available:
|
||||
1. Enrich company → Firmographics, funding, tech stack
|
||||
2. Search people → Org chart, contact list
|
||||
3. Enrich person → Email, phone, background
|
||||
4. Get signals → Intent data, hiring velocity
|
||||
```
|
||||
|
||||
**Enrichment adds:**
|
||||
- Verified contact info
|
||||
- Complete org chart
|
||||
- Precise employee count
|
||||
- Detailed tech stack
|
||||
- Funding history with investors
|
||||
|
||||
### Step 4: CRM Check (If Connected)
|
||||
|
||||
```
|
||||
If CRM available:
|
||||
1. Search for account by domain
|
||||
2. Get related contacts
|
||||
3. Get opportunity history
|
||||
4. Get activity timeline
|
||||
```
|
||||
|
||||
**CRM adds:**
|
||||
- Prior relationship context
|
||||
- What happened before (won/lost deals)
|
||||
- Who we've talked to
|
||||
- Notes and history
|
||||
|
||||
### Step 5: Synthesize
|
||||
|
||||
```
|
||||
1. Combine all sources
|
||||
2. Prioritize enrichment data over web (more accurate)
|
||||
3. Add CRM context if exists
|
||||
4. Identify qualification signals
|
||||
5. Generate talking points
|
||||
6. Recommend approach
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Research Variations
|
||||
|
||||
### Company Research
|
||||
Focus on: Business overview, news, hiring, leadership
|
||||
|
||||
### Person Research
|
||||
Focus on: Background, role, LinkedIn activity, talking points
|
||||
|
||||
### Competitor Research
|
||||
Focus on: Product comparison, positioning, win/loss patterns
|
||||
|
||||
### Pre-Meeting Research
|
||||
Focus on: Attendee backgrounds, recent news, relationship history
|
||||
|
||||
---
|
||||
|
||||
## Tips for Better Research
|
||||
|
||||
1. **Include the domain** — "research acme.com" is more precise
|
||||
2. **Specify the person** — "look up Jane Smith, VP Sales at Acme"
|
||||
3. **State your goal** — "research Stripe before my demo call"
|
||||
4. **Ask for specifics** — "what's their tech stack?" after initial research
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **call-prep** — Full meeting prep with this research plus context
|
||||
- **draft-outreach** — Write personalized message based on research
|
||||
- **prospecting** — Qualify and prioritize research targets
|
||||
@@ -0,0 +1,258 @@
|
||||
---
|
||||
name: call-prep
|
||||
description: Prepare for a sales call with account context, attendee research, and suggested agenda. Works standalone with user input and web research, supercharged when you connect your CRM, email, chat, or transcripts. Trigger with "prep me for my call with [company]", "I'm meeting with [company] prep me", "call prep [company]", or "get me ready for [meeting]".
|
||||
---
|
||||
|
||||
# Call Prep
|
||||
|
||||
Get fully prepared for any sales call in minutes. This skill works with whatever context you provide, and gets significantly better when you connect your sales tools.
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ CALL PREP │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ ALWAYS (works standalone) │
|
||||
│ ✓ You tell me: company, meeting type, attendees │
|
||||
│ ✓ Web search: recent news, funding, leadership changes │
|
||||
│ ✓ Company research: what they do, size, industry │
|
||||
│ ✓ Output: prep brief with agenda and questions │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + CRM: account history, contacts, opportunities, activities │
|
||||
│ + Email: recent threads, open questions, commitments │
|
||||
│ + Chat: internal discussions, colleague insights │
|
||||
│ + Transcripts: prior call recordings, key moments │
|
||||
│ + Calendar: auto-find meeting, pull attendees │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
|
||||
When you run this skill, I'll ask for what I need:
|
||||
|
||||
**Required:**
|
||||
- Company or contact name
|
||||
- Meeting type (discovery, demo, negotiation, check-in, etc.)
|
||||
|
||||
**Helpful if you have it:**
|
||||
- Who's attending (names and titles)
|
||||
- Any context you want me to know (paste prior notes, emails, etc.)
|
||||
|
||||
If you've connected your CRM, email, or other tools, I'll pull context automatically and skip the questions.
|
||||
|
||||
---
|
||||
|
||||
## Connectors (Optional)
|
||||
|
||||
Connect your tools to supercharge this skill:
|
||||
|
||||
| Connector | What It Adds |
|
||||
|-----------|--------------|
|
||||
| **CRM** | Account details, contact history, open deals, recent activities |
|
||||
| **Email** | Recent threads with the company, open questions, attachments shared |
|
||||
| **Chat** | Internal chat discussions (e.g. Slack) about the account, colleague insights |
|
||||
| **Transcripts** | Prior call recordings, topics covered, competitor mentions |
|
||||
| **Calendar** | Auto-find the meeting, pull attendees and description |
|
||||
|
||||
> **No connectors?** No problem. Just tell me about the meeting and paste any context you have. I'll research the rest.
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
```markdown
|
||||
# Call Prep: [Company Name]
|
||||
|
||||
**Meeting:** [Type] — [Date/Time if known]
|
||||
**Attendees:** [Names with titles]
|
||||
**Your Goal:** [What you want to accomplish]
|
||||
|
||||
---
|
||||
|
||||
## Account Snapshot
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Company** | [Name] |
|
||||
| **Industry** | [Industry] |
|
||||
| **Size** | [Employees / Revenue if known] |
|
||||
| **Status** | [New prospect / Active opportunity / Customer] |
|
||||
| **Last Touch** | [Date and summary] |
|
||||
|
||||
---
|
||||
|
||||
## Who You're Meeting
|
||||
|
||||
### [Name] — [Title]
|
||||
- **Background:** [Career history, education if found]
|
||||
- **LinkedIn:** [URL]
|
||||
- **Role in Deal:** [Decision maker / Champion / Evaluator / etc.]
|
||||
- **Last Interaction:** [Summary if known]
|
||||
- **Talking Point:** [Something personal/professional to reference]
|
||||
|
||||
[Repeat for each attendee]
|
||||
|
||||
---
|
||||
|
||||
## Context & History
|
||||
|
||||
**What's happened so far:**
|
||||
- [Key point from prior interactions]
|
||||
- [Open commitments or action items]
|
||||
- [Any concerns or objections raised]
|
||||
|
||||
**Recent news about [Company]:**
|
||||
- [News item 1 — why it matters]
|
||||
- [News item 2 — why it matters]
|
||||
|
||||
---
|
||||
|
||||
## Suggested Agenda
|
||||
|
||||
1. **Open** — [Reference last conversation or trigger event]
|
||||
2. **[Topic 1]** — [Discovery question or value discussion]
|
||||
3. **[Topic 2]** — [Address known concern or explore priority]
|
||||
4. **[Topic 3]** — [Demo section / Proposal review / etc.]
|
||||
5. **Next Steps** — [Propose clear follow-up with timeline]
|
||||
|
||||
---
|
||||
|
||||
## Discovery Questions
|
||||
|
||||
Ask these to fill gaps in your understanding:
|
||||
|
||||
1. [Question about their current situation]
|
||||
2. [Question about pain points or priorities]
|
||||
3. [Question about decision process and timeline]
|
||||
4. [Question about success criteria]
|
||||
5. [Question about other stakeholders]
|
||||
|
||||
---
|
||||
|
||||
## Potential Objections
|
||||
|
||||
| Objection | Suggested Response |
|
||||
|-----------|-------------------|
|
||||
| [Likely objection based on context] | [How to address it] |
|
||||
| [Common objection for this stage] | [How to address it] |
|
||||
|
||||
---
|
||||
|
||||
## Internal Notes
|
||||
|
||||
[Any internal chat context (e.g. Slack), colleague insights, or competitive intel]
|
||||
|
||||
---
|
||||
|
||||
## After the Call
|
||||
|
||||
Run **call-follow-up** to:
|
||||
- Extract action items
|
||||
- Update your CRM
|
||||
- Draft follow-up email
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Execution Flow
|
||||
|
||||
### Step 1: Gather Context
|
||||
|
||||
**If connectors available:**
|
||||
```
|
||||
1. Calendar → Find upcoming meeting matching company name
|
||||
- Pull: title, time, attendees, description, attachments
|
||||
|
||||
2. CRM → Query account
|
||||
- Pull: account details, all contacts, open opportunities
|
||||
- Pull: last 10 activities, any account notes
|
||||
|
||||
3. Email → Search recent threads
|
||||
- Query: emails with company domain (last 30 days)
|
||||
- Extract: key topics, open questions, commitments
|
||||
|
||||
4. Chat → Search internal discussions
|
||||
- Query: company name mentions (last 30 days)
|
||||
- Extract: colleague insights, competitive intel
|
||||
|
||||
5. Transcripts → Find prior calls
|
||||
- Pull: call recordings with this account
|
||||
- Extract: key moments, objections raised, topics covered
|
||||
```
|
||||
|
||||
**If no connectors:**
|
||||
```
|
||||
1. Ask user:
|
||||
- "What company are you meeting with?"
|
||||
- "What type of meeting is this?"
|
||||
- "Who's attending? (names and titles if you know)"
|
||||
- "Any context you want me to know? (paste notes, emails, etc.)"
|
||||
|
||||
2. Accept whatever they provide and work with it
|
||||
```
|
||||
|
||||
### Step 2: Research Supplement
|
||||
|
||||
**Always run (web search):**
|
||||
```
|
||||
1. "[Company] news" — last 30 days
|
||||
2. "[Company] funding" — recent announcements
|
||||
3. "[Company] leadership" — executive changes
|
||||
4. "[Company] + [industry] trends" — relevant context
|
||||
5. Attendee LinkedIn profiles — background research
|
||||
```
|
||||
|
||||
### Step 3: Synthesize & Generate
|
||||
|
||||
```
|
||||
1. Combine all sources into unified context
|
||||
2. Identify gaps in understanding → generate discovery questions
|
||||
3. Anticipate objections based on stage and history
|
||||
4. Create suggested agenda tailored to meeting type
|
||||
5. Output formatted prep brief
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Meeting Type Variations
|
||||
|
||||
### Discovery Call
|
||||
- Focus on: Understanding their world, pain points, priorities
|
||||
- Agenda emphasis: Questions > Talking
|
||||
- Key output: Qualification signals, next step proposal
|
||||
|
||||
### Demo / Presentation
|
||||
- Focus on: Their specific use case, tailored examples
|
||||
- Agenda emphasis: Show relevant features, get feedback
|
||||
- Key output: Technical requirements, decision timeline
|
||||
|
||||
### Negotiation / Proposal Review
|
||||
- Focus on: Addressing concerns, justifying value
|
||||
- Agenda emphasis: Handle objections, close gaps
|
||||
- Key output: Path to agreement, clear next steps
|
||||
|
||||
### Check-in / QBR
|
||||
- Focus on: Value delivered, expansion opportunities
|
||||
- Agenda emphasis: Review wins, surface new needs
|
||||
- Key output: Renewal confidence, upsell pipeline
|
||||
|
||||
---
|
||||
|
||||
## Tips for Better Prep
|
||||
|
||||
1. **More context = better prep** — Paste emails, notes, anything you have
|
||||
2. **Name the attendees** — Even just titles help me research
|
||||
3. **State your goal** — "I want to get them to agree to a pilot"
|
||||
4. **Flag concerns** — "They mentioned budget is tight"
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **account-research** — Deep dive on a company before first contact
|
||||
- **call-follow-up** — Process call notes and execute post-call workflow
|
||||
- **draft-outreach** — Write personalized outreach after research
|
||||
@@ -0,0 +1,168 @@
|
||||
---
|
||||
name: call-summary
|
||||
description: Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
|
||||
argument-hint: "<call notes or transcript>"
|
||||
---
|
||||
|
||||
# /call-summary
|
||||
|
||||
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
|
||||
|
||||
Process call notes or a transcript to extract action items, draft follow-up communications, and update records.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/call-summary <notes or transcript>
|
||||
```
|
||||
|
||||
Process these call notes: $ARGUMENTS
|
||||
|
||||
If a file is referenced: @$1
|
||||
|
||||
---
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ CALL SUMMARY │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ STANDALONE (always works) │
|
||||
│ ✓ Paste call notes or transcript │
|
||||
│ ✓ Extract key discussion points and decisions │
|
||||
│ ✓ Identify action items with owners and due dates │
|
||||
│ ✓ Surface objections, concerns, and open questions │
|
||||
│ ✓ Draft customer-facing follow-up email │
|
||||
│ ✓ Generate internal summary for your team │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │
|
||||
│ + CRM: Update opportunity, log activity, create tasks │
|
||||
│ + Email: Send follow-up directly from draft │
|
||||
│ + Calendar: Link to meeting, pull attendee context │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What I Need From You
|
||||
|
||||
**Option 1: Paste your notes**
|
||||
Just paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it.
|
||||
|
||||
**Option 2: Paste a transcript**
|
||||
If you have a full transcript from your video conferencing tool (e.g. Zoom, Teams) or conversation intelligence tool (e.g. Gong, Fireflies), paste it. I'll extract the key moments.
|
||||
|
||||
**Option 3: Describe the call**
|
||||
Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Eng and CTO. They're evaluating us vs Competitor X. Main concern is integration timeline."
|
||||
|
||||
---
|
||||
|
||||
## Output
|
||||
|
||||
### Internal Summary
|
||||
```markdown
|
||||
## Call Summary: [Company] — [Date]
|
||||
|
||||
**Attendees:** [Names and titles]
|
||||
**Call Type:** [Discovery / Demo / Negotiation / Check-in]
|
||||
**Duration:** [If known]
|
||||
|
||||
### Key Discussion Points
|
||||
1. [Topic] — [What was discussed, decisions made]
|
||||
2. [Topic] — [Summary]
|
||||
|
||||
### Customer Priorities
|
||||
- [Priority 1 they expressed]
|
||||
- [Priority 2]
|
||||
|
||||
### Objections / Concerns Raised
|
||||
- [Concern] — [How you addressed it / status]
|
||||
|
||||
### Competitive Intel
|
||||
- [Any competitor mentions, what was said]
|
||||
|
||||
### Action Items
|
||||
| Owner | Action | Due |
|
||||
|-------|--------|-----|
|
||||
| [You] | [Task] | [Date] |
|
||||
| [Customer] | [Task] | [Date] |
|
||||
|
||||
### Next Steps
|
||||
- [Agreed next step with timeline]
|
||||
|
||||
### Deal Impact
|
||||
- [How this call affects the opportunity — stage change, risk, acceleration]
|
||||
```
|
||||
|
||||
### Customer Follow-Up Email
|
||||
```
|
||||
Subject: [Meeting recap + next steps]
|
||||
|
||||
Hi [Name],
|
||||
|
||||
Thank you for taking the time to meet today...
|
||||
|
||||
[Key points discussed]
|
||||
|
||||
[Commitments you made]
|
||||
|
||||
[Clear next step with timeline]
|
||||
|
||||
Best,
|
||||
[You]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Email Style Guidelines
|
||||
|
||||
When drafting customer-facing emails:
|
||||
|
||||
1. **Be concise but informative** — Get to the point quickly. Customers are busy.
|
||||
2. **No markdown formatting** — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client.
|
||||
3. **Use simple structure** — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it.
|
||||
4. **Keep it scannable** — If listing items, use plain dashes or numbers, not fancy formatting.
|
||||
|
||||
**Good:**
|
||||
```
|
||||
Here's what we discussed:
|
||||
- Quote for 20 seats at $480/seat/year
|
||||
- W9 and supplier onboarding docs
|
||||
- Point of contact for the contract
|
||||
```
|
||||
|
||||
**Bad:**
|
||||
```
|
||||
**What You Need from Us:**
|
||||
- Quote for 20 seats at $480/seat/year
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## If Connectors Available
|
||||
|
||||
**Transcripts connected (e.g. Gong, Fireflies):**
|
||||
- I'll search for the call automatically
|
||||
- Pull the full transcript
|
||||
- Extract key moments flagged by the platform
|
||||
|
||||
**CRM connected:**
|
||||
- I'll offer to update the opportunity stage
|
||||
- Log the call as an activity
|
||||
- Create tasks for action items
|
||||
- Update next steps field
|
||||
|
||||
**Email connected:**
|
||||
- I'll offer to create a draft in ~~email
|
||||
- Or send directly if you approve
|
||||
|
||||
---
|
||||
|
||||
## Tips
|
||||
|
||||
1. **More detail = better output** — Even rough notes help. "They seemed concerned about X" is useful context.
|
||||
2. **Name the attendees** — Helps me structure the summary and assign action items.
|
||||
3. **Flag what matters** — If something was important, tell me: "The big thing was..."
|
||||
4. **Tell me the deal stage** — Helps me tailor the follow-up tone and next steps.
|
||||
@@ -0,0 +1,401 @@
|
||||
---
|
||||
name: competitive-intelligence
|
||||
description: Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
|
||||
---
|
||||
|
||||
# Competitive Intelligence
|
||||
|
||||
Research your competitors extensively and generate an **interactive HTML battlecard** you can use in deals. The output is a self-contained artifact with clickable competitor tabs and an overall comparison matrix.
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ COMPETITIVE INTELLIGENCE │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ ALWAYS (works standalone via web search) │
|
||||
│ ✓ Competitor product deep-dive: features, pricing, positioning │
|
||||
│ ✓ Recent releases: what they've shipped in last 90 days │
|
||||
│ ✓ Your company releases: what you've shipped to counter │
|
||||
│ ✓ Differentiation matrix: where you win vs. where they win │
|
||||
│ ✓ Sales talk tracks: how to position against each competitor │
|
||||
│ ✓ Landmine questions: expose their weaknesses naturally │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ OUTPUT: Interactive HTML Battlecard │
|
||||
│ ✓ Comparison matrix overview │
|
||||
│ ✓ Clickable tabs for each competitor │
|
||||
│ ✓ Dark theme, professional styling │
|
||||
│ ✓ Self-contained HTML file — share or host anywhere │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + CRM: Win/loss data, competitor mentions in closed deals │
|
||||
│ + Docs: Existing battlecards, competitive playbooks │
|
||||
│ + Chat: Internal intel, field reports from colleagues │
|
||||
│ + Transcripts: Competitor mentions in customer calls │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
|
||||
When you run this skill, I'll ask for context:
|
||||
|
||||
**Required:**
|
||||
- What company do you work for? (or I'll detect from your email)
|
||||
- Who are your main competitors? (1-5 names)
|
||||
|
||||
**Optional:**
|
||||
- Which competitor do you want to focus on first?
|
||||
- Any specific deals where you're competing against them?
|
||||
- Pain points you've heard from customers about competitors?
|
||||
|
||||
If I already have your seller context from a previous session, I'll confirm and skip the questions.
|
||||
|
||||
---
|
||||
|
||||
## Connectors (Optional)
|
||||
|
||||
| Connector | What It Adds |
|
||||
|-----------|--------------|
|
||||
| **CRM** | Win/loss history against each competitor, deal-level competitor tracking |
|
||||
| **Docs** | Existing battlecards, product comparison docs, competitive playbooks |
|
||||
| **Chat** | Internal chat intel (e.g. Slack) — what your team is hearing from the field |
|
||||
| **Transcripts** | Competitor mentions in customer calls, objections raised |
|
||||
|
||||
> **No connectors?** Web research works great. I'll pull everything from public sources — product pages, pricing, blogs, release notes, reviews, job postings.
|
||||
|
||||
---
|
||||
|
||||
## Output: Interactive HTML Battlecard
|
||||
|
||||
The skill generates a **self-contained HTML file** with:
|
||||
|
||||
### 1. Comparison Matrix (Landing View)
|
||||
Overview comparing you vs. all competitors at a glance:
|
||||
- Feature comparison grid
|
||||
- Pricing comparison
|
||||
- Market positioning
|
||||
- Win rate indicators (if CRM connected)
|
||||
|
||||
### 2. Competitor Tabs (Click to Expand)
|
||||
Each competitor gets a clickable card that expands to show:
|
||||
- Company profile (size, funding, target market)
|
||||
- What they sell and how they position
|
||||
- Recent releases (last 90 days)
|
||||
- Where they win vs. where you win
|
||||
- Pricing intelligence
|
||||
- Talk tracks for different scenarios
|
||||
- Objection handling
|
||||
- Landmine questions
|
||||
|
||||
### 3. Your Company Card
|
||||
- Your releases (last 90 days)
|
||||
- Your key differentiators
|
||||
- Proof points and customer quotes
|
||||
|
||||
---
|
||||
|
||||
## HTML Structure
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<title>Battlecard: [Your Company] vs Competitors</title>
|
||||
<style>
|
||||
/* Dark theme, professional styling */
|
||||
/* Tabbed navigation */
|
||||
/* Expandable cards */
|
||||
/* Responsive design */
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<!-- Header with your company + date -->
|
||||
<header>
|
||||
<h1>[Your Company] Competitive Battlecard</h1>
|
||||
<p>Generated: [Date] | Competitors: [List]</p>
|
||||
</header>
|
||||
|
||||
<!-- Tab Navigation -->
|
||||
<nav class="tabs">
|
||||
<button class="tab active" data-tab="matrix">Comparison Matrix</button>
|
||||
<button class="tab" data-tab="competitor-1">[Competitor 1]</button>
|
||||
<button class="tab" data-tab="competitor-2">[Competitor 2]</button>
|
||||
<button class="tab" data-tab="competitor-3">[Competitor 3]</button>
|
||||
</nav>
|
||||
|
||||
<!-- Comparison Matrix Tab -->
|
||||
<section id="matrix" class="tab-content active">
|
||||
<h2>Head-to-Head Comparison</h2>
|
||||
<table class="comparison-matrix">
|
||||
<!-- Feature rows with you vs each competitor -->
|
||||
</table>
|
||||
|
||||
<h2>Quick Win/Loss Guide</h2>
|
||||
<div class="win-loss-grid">
|
||||
<!-- Per-competitor: when you win, when you lose -->
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- Individual Competitor Tabs -->
|
||||
<section id="competitor-1" class="tab-content">
|
||||
<div class="battlecard">
|
||||
<div class="profile"><!-- Company info --></div>
|
||||
<div class="differentiation"><!-- Where they win / you win --></div>
|
||||
<div class="talk-tracks"><!-- Scenario-based positioning --></div>
|
||||
<div class="objections"><!-- Common objections + responses --></div>
|
||||
<div class="landmines"><!-- Questions to ask --></div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<script>
|
||||
// Tab switching logic
|
||||
// Expand/collapse sections
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Visual Design
|
||||
|
||||
### Color System
|
||||
```css
|
||||
:root {
|
||||
/* Dark theme base */
|
||||
--bg-primary: #0a0d14;
|
||||
--bg-elevated: #0f131c;
|
||||
--bg-surface: #161b28;
|
||||
--bg-hover: #1e2536;
|
||||
|
||||
/* Text */
|
||||
--text-primary: #ffffff;
|
||||
--text-secondary: rgba(255, 255, 255, 0.7);
|
||||
--text-muted: rgba(255, 255, 255, 0.5);
|
||||
|
||||
/* Accent (your brand or neutral) */
|
||||
--accent: #3b82f6;
|
||||
--accent-hover: #2563eb;
|
||||
|
||||
/* Status indicators */
|
||||
--you-win: #10b981;
|
||||
--they-win: #ef4444;
|
||||
--tie: #f59e0b;
|
||||
}
|
||||
```
|
||||
|
||||
### Card Design
|
||||
- Rounded corners (12px)
|
||||
- Subtle borders (1px, low opacity)
|
||||
- Hover states with slight elevation
|
||||
- Smooth transitions (200ms)
|
||||
|
||||
### Comparison Matrix
|
||||
- Sticky header row
|
||||
- Color-coded winner indicators (green = you, red = them, yellow = tie)
|
||||
- Expandable rows for detail
|
||||
|
||||
---
|
||||
|
||||
## Execution Flow
|
||||
|
||||
### Phase 1: Gather Seller Context
|
||||
|
||||
```
|
||||
If first time:
|
||||
1. Ask: "What company do you work for?"
|
||||
2. Ask: "What do you sell? (product/service in one line)"
|
||||
3. Ask: "Who are your main competitors? (up to 5)"
|
||||
4. Store context for future sessions
|
||||
|
||||
If returning user:
|
||||
1. Confirm: "Still at [Company] selling [Product]?"
|
||||
2. Ask: "Same competitors, or any new ones to add?"
|
||||
```
|
||||
|
||||
### Phase 2: Research Your Company (Always)
|
||||
|
||||
```
|
||||
Web searches:
|
||||
1. "[Your company] product" — current offerings
|
||||
2. "[Your company] pricing" — pricing model
|
||||
3. "[Your company] news" — recent announcements (90 days)
|
||||
4. "[Your company] product updates OR changelog OR releases" — what you've shipped
|
||||
5. "[Your company] vs [competitor]" — existing comparisons
|
||||
```
|
||||
|
||||
### Phase 3: Research Each Competitor (Always)
|
||||
|
||||
```
|
||||
For each competitor, run:
|
||||
1. "[Competitor] product features" — what they offer
|
||||
2. "[Competitor] pricing" — how they charge
|
||||
3. "[Competitor] news" — recent announcements
|
||||
4. "[Competitor] product updates OR changelog OR releases" — what they've shipped
|
||||
5. "[Competitor] reviews G2 OR Capterra OR TrustRadius" — customer sentiment
|
||||
6. "[Competitor] vs [alternatives]" — how they position
|
||||
7. "[Competitor] customers" — who uses them
|
||||
8. "[Competitor] careers" — hiring signals (growth areas)
|
||||
```
|
||||
|
||||
### Phase 4: Pull Connected Sources (If Available)
|
||||
|
||||
```
|
||||
If CRM connected:
|
||||
1. Query closed-won deals with competitor field = [Competitor]
|
||||
2. Query closed-lost deals with competitor field = [Competitor]
|
||||
3. Extract win/loss patterns
|
||||
|
||||
If docs connected:
|
||||
1. Search for "battlecard [competitor]"
|
||||
2. Search for "competitive [competitor]"
|
||||
3. Pull existing positioning docs
|
||||
|
||||
If chat connected:
|
||||
1. Search for "[Competitor]" mentions (last 90 days)
|
||||
2. Extract field intel and colleague insights
|
||||
|
||||
If transcripts connected:
|
||||
1. Search calls for "[Competitor]" mentions
|
||||
2. Extract objections and customer quotes
|
||||
```
|
||||
|
||||
### Phase 5: Build HTML Artifact
|
||||
|
||||
```
|
||||
1. Structure data for each competitor
|
||||
2. Build comparison matrix
|
||||
3. Generate individual battlecards
|
||||
4. Create talk tracks for each scenario
|
||||
5. Compile landmine questions
|
||||
6. Render as self-contained HTML
|
||||
7. Save as [YourCompany]-battlecard-[date].html
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Data Structure Per Competitor
|
||||
|
||||
```yaml
|
||||
competitor:
|
||||
name: "[Name]"
|
||||
website: "[URL]"
|
||||
profile:
|
||||
founded: "[Year]"
|
||||
funding: "[Stage + amount]"
|
||||
employees: "[Count]"
|
||||
target_market: "[Who they sell to]"
|
||||
pricing_model: "[Per seat / usage / etc.]"
|
||||
market_position: "[Leader / Challenger / Niche]"
|
||||
|
||||
what_they_sell: "[Product summary]"
|
||||
their_positioning: "[How they describe themselves]"
|
||||
|
||||
recent_releases:
|
||||
- date: "[Date]"
|
||||
release: "[Feature/Product]"
|
||||
impact: "[Why it matters]"
|
||||
|
||||
where_they_win:
|
||||
- area: "[Area]"
|
||||
advantage: "[Their strength]"
|
||||
how_to_handle: "[Your counter]"
|
||||
|
||||
where_you_win:
|
||||
- area: "[Area]"
|
||||
advantage: "[Your strength]"
|
||||
proof_point: "[Evidence]"
|
||||
|
||||
pricing:
|
||||
model: "[How they charge]"
|
||||
entry_price: "[Starting price]"
|
||||
enterprise: "[Enterprise pricing]"
|
||||
hidden_costs: "[Implementation, etc.]"
|
||||
talk_track: "[How to discuss pricing]"
|
||||
|
||||
talk_tracks:
|
||||
early_mention: "[Strategy if they come up early]"
|
||||
displacement: "[Strategy if customer uses them]"
|
||||
late_addition: "[Strategy if added late to eval]"
|
||||
|
||||
objections:
|
||||
- objection: "[What customer says]"
|
||||
response: "[How to handle]"
|
||||
|
||||
landmines:
|
||||
- "[Question that exposes their weakness]"
|
||||
|
||||
win_loss: # If CRM connected
|
||||
win_rate: "[X]%"
|
||||
common_win_factors: "[What predicts wins]"
|
||||
common_loss_factors: "[What predicts losses]"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Delivery
|
||||
|
||||
```markdown
|
||||
## ✓ Battlecard Created
|
||||
|
||||
[View your battlecard](file:///path/to/[YourCompany]-battlecard-[date].html)
|
||||
|
||||
---
|
||||
|
||||
**Summary**
|
||||
- **Your Company**: [Name]
|
||||
- **Competitors Analyzed**: [List]
|
||||
- **Data Sources**: Web research [+ CRM] [+ Docs] [+ Transcripts]
|
||||
|
||||
---
|
||||
|
||||
**How to Use**
|
||||
- **Before a call**: Open the relevant competitor tab, review talk tracks
|
||||
- **During a call**: Reference landmine questions
|
||||
- **After win/loss**: Update with new intel
|
||||
|
||||
---
|
||||
|
||||
**Sharing Options**
|
||||
- **Local file**: Open in any browser
|
||||
- **Host it**: Upload to Netlify, Vercel, or internal wiki
|
||||
- **Share directly**: Send the HTML file to teammates
|
||||
|
||||
---
|
||||
|
||||
**Keep it Fresh**
|
||||
Run this skill again to refresh with latest intel. Recommended: monthly or before major deals.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Refresh Cadence
|
||||
|
||||
Competitive intel gets stale. Recommended refresh:
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| **Monthly** | Quick refresh — new releases, news, pricing changes |
|
||||
| **Before major deal** | Deep refresh for specific competitor in that deal |
|
||||
| **After win/loss** | Update patterns with new data |
|
||||
| **Competitor announcement** | Immediate update on that competitor |
|
||||
|
||||
---
|
||||
|
||||
## Tips for Better Intel
|
||||
|
||||
1. **Be honest about weaknesses** — Credibility comes from acknowledging where competitors are strong
|
||||
2. **Focus on outcomes, not features** — "They have X feature" matters less than "customers achieve Y result"
|
||||
3. **Update from the field** — Best intel comes from actual customer conversations, not just websites
|
||||
4. **Plant landmines, don't badmouth** — Ask questions that expose weaknesses; never trash-talk
|
||||
5. **Track releases religiously** — What they ship tells you their strategy and your opportunity
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **account-research** — Research a specific prospect before reaching out
|
||||
- **call-prep** — Prep for a call where you know competitor is involved
|
||||
- **create-an-asset** — Build a custom comparison page for a specific deal
|
||||
@@ -0,0 +1,78 @@
|
||||
# Create an Asset — Quick Reference
|
||||
|
||||
## Invoke
|
||||
```
|
||||
/create-an-asset
|
||||
/create-an-asset [CompanyName]
|
||||
"Create an asset for [Company]"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Inputs at a Glance
|
||||
|
||||
| Input | What to Provide |
|
||||
|-------|-----------------|
|
||||
| **(a) Prospect** | Company, contacts, deal stage, pain points, transcripts |
|
||||
| **(b) Audience** | Exec / Technical / Ops / Mixed + what they care about |
|
||||
| **(c) Purpose** | Intro / Follow-up / Deep-dive / Alignment / POC / Close |
|
||||
| **(d) Format** | Landing page / Deck / One-pager / Workflow demo |
|
||||
|
||||
---
|
||||
|
||||
## Format Picker
|
||||
|
||||
| If you need... | Choose... |
|
||||
|----------------|-----------|
|
||||
| Impressive multi-tab experience | **Interactive landing page** |
|
||||
| Something to present in a meeting | **Deck-style** |
|
||||
| Quick summary to leave behind | **One-pager** |
|
||||
| Visual of how systems connect | **Workflow demo** |
|
||||
|
||||
---
|
||||
|
||||
## Sample Prompts
|
||||
|
||||
**Basic:**
|
||||
```
|
||||
Create an asset for Acme Corp
|
||||
```
|
||||
|
||||
**With context:**
|
||||
```
|
||||
Create an asset for Acme Corp. They're a manufacturing company
|
||||
struggling with supply chain visibility. Met with their COO
|
||||
last week. Need something for the exec team.
|
||||
```
|
||||
|
||||
**Workflow demo:**
|
||||
```
|
||||
Mock up a workflow for Centric Brands showing how they'd use
|
||||
our product to monitor contract compliance. Components: our AI,
|
||||
their Snowflake warehouse, and scanned PDF contracts.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## After It's Built
|
||||
|
||||
| Want to... | Say... |
|
||||
|------------|--------|
|
||||
| Change colors | "Use our brand colors instead" |
|
||||
| Add a section | "Add a section on security" |
|
||||
| Shorten it | "Make it more concise" |
|
||||
| Fix something | "The CEO's name is wrong, it's Jane Smith" |
|
||||
| Get PDF | "Give me a print-friendly version" |
|
||||
|
||||
---
|
||||
|
||||
## Output
|
||||
|
||||
- Self-contained HTML file
|
||||
- Works offline
|
||||
- Host anywhere (Netlify, Vercel, GitHub Pages, etc.)
|
||||
- Password-protect via your hosting provider
|
||||
|
||||
---
|
||||
|
||||
*That's it. Provide context → answer questions → get asset → iterate.*
|
||||
@@ -0,0 +1,169 @@
|
||||
# Create an Asset
|
||||
|
||||
**For Sales Teams Everywhere**
|
||||
|
||||
Generate professional, customer-ready sales assets in minutes. No design skills required.
|
||||
|
||||
---
|
||||
|
||||
## What It Does
|
||||
|
||||
This skill creates tailored sales assets by asking you about:
|
||||
1. **Your prospect** — who they are, what you've discussed
|
||||
2. **Your audience** — who's viewing, what they care about
|
||||
3. **Your purpose** — what you want to achieve
|
||||
4. **Your format** — how you want to present it
|
||||
|
||||
Then it researches, writes, designs, and builds a polished asset you can share with customers.
|
||||
|
||||
---
|
||||
|
||||
## Supported Formats
|
||||
|
||||
| Format | Best For | Output |
|
||||
|--------|----------|--------|
|
||||
| **Interactive Landing Page** | Exec meetings, value prop presentations | Multi-tab page with demos and calculators |
|
||||
| **Deck-Style** | Formal presentations, large audiences | Linear slides with navigation |
|
||||
| **One-Pager** | Leave-behinds, quick summaries | Single-scroll executive summary |
|
||||
| **Workflow / Architecture Demo** | Technical deep-dives, POC proposals | Interactive diagram with animated flow |
|
||||
|
||||
---
|
||||
|
||||
## Quick Start
|
||||
|
||||
### Option 1: Simple prompt
|
||||
```
|
||||
Create an asset for Acme Corp
|
||||
```
|
||||
|
||||
### Option 2: With context
|
||||
```
|
||||
Create an asset for Acme Corp. I met with their VP Engineering
|
||||
last week - they're struggling with slow release cycles and
|
||||
want to improve developer productivity. This is for a follow-up
|
||||
with their technical team.
|
||||
```
|
||||
|
||||
### Option 3: Workflow demo
|
||||
```
|
||||
I want to mock up a workflow showing how a customer would use
|
||||
our product to automate their invoice processing. The flow is:
|
||||
invoices come in via email → our AI extracts data → validates
|
||||
against their ERP → flags exceptions for human review.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What Gets Created
|
||||
|
||||
### Interactive Landing Page
|
||||
- Tabbed navigation
|
||||
- Company metrics and research
|
||||
- Use case demos
|
||||
- ROI calculator
|
||||
- Professional dark theme with prospect's brand colors
|
||||
|
||||
### Deck-Style
|
||||
- Title slide with both logos
|
||||
- Agenda
|
||||
- Content slides (one message per slide)
|
||||
- Summary and next steps
|
||||
- Speaker notes included
|
||||
|
||||
### One-Pager
|
||||
- Hero statement
|
||||
- 3 key value points
|
||||
- Proof point
|
||||
- Clear CTA
|
||||
|
||||
### Workflow Demo
|
||||
- Visual component nodes
|
||||
- Animated data flow
|
||||
- Step-by-step walkthrough
|
||||
- Play/pause/step controls
|
||||
- Sample data at each stage
|
||||
|
||||
---
|
||||
|
||||
## The Process
|
||||
|
||||
```
|
||||
1. You provide context (prospect, audience, purpose)
|
||||
↓
|
||||
2. Skill researches the prospect company
|
||||
↓
|
||||
3. Skill asks 3-4 clarifying questions
|
||||
↓
|
||||
4. You confirm direction
|
||||
↓
|
||||
5. Skill builds the asset
|
||||
↓
|
||||
6. You iterate as needed
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Sharing Your Asset
|
||||
|
||||
The output is a self-contained HTML file. Share it by:
|
||||
|
||||
- **Static hosting**: Upload to Netlify, Vercel, GitHub Pages, or any web host
|
||||
- **Password protect**: Most hosts offer simple password protection
|
||||
- **Direct share**: Email the HTML file — it works offline
|
||||
- **Embed**: iframe it into other pages or portals
|
||||
|
||||
---
|
||||
|
||||
## Tips for Best Results
|
||||
|
||||
### Provide Rich Context
|
||||
The more you share about past conversations, pain points, and stakeholder concerns, the more tailored the asset will be.
|
||||
|
||||
### Upload Transcripts
|
||||
If you have call recordings, meeting notes, or email threads, upload them. The skill will extract key quotes and priorities.
|
||||
|
||||
### Be Specific About Audience
|
||||
"Technical team" is good. "IT architects evaluating our security model" is better.
|
||||
|
||||
### Iterate Freely
|
||||
First draft not quite right? Just say what to change. Colors, sections, messaging, flow — all adjustable.
|
||||
|
||||
---
|
||||
|
||||
## Examples
|
||||
|
||||
| Scenario | Format | Key Features |
|
||||
|----------|--------|--------------|
|
||||
| Post-discovery exec meeting | Interactive page | ROI calculator, their stated priorities, case studies |
|
||||
| Technical architecture review | Workflow demo | System diagram, data flows, integration points |
|
||||
| Board presentation leave-behind | One-pager | Strategic alignment, key metrics, clear CTA |
|
||||
| Large stakeholder meeting | Deck-style | Linear narrative, one point per slide, appendix |
|
||||
|
||||
---
|
||||
|
||||
## FAQ
|
||||
|
||||
**Q: Does it work for any product/company?**
|
||||
A: Yes. The skill detects what you're selling from your email domain and researches accordingly.
|
||||
|
||||
**Q: How does it know my prospect's brand colors?**
|
||||
A: It extracts them from the prospect's website or brand guidelines. You can adjust after.
|
||||
|
||||
**Q: Can I use my company's branding instead?**
|
||||
A: Yes — after the first build, just ask to switch to your brand colors.
|
||||
|
||||
**Q: What if the research is wrong?**
|
||||
A: Flag it and provide corrections. The skill will regenerate with accurate info.
|
||||
|
||||
**Q: Can I export as PDF?**
|
||||
A: Yes — ask for a print-optimized version and use your browser's print-to-PDF.
|
||||
|
||||
---
|
||||
|
||||
## Support
|
||||
|
||||
Questions or feedback? This skill is part of the public sales skills collection.
|
||||
|
||||
---
|
||||
|
||||
*Built for salespeople who'd rather sell than design slides.*
|
||||
@@ -0,0 +1,867 @@
|
||||
---
|
||||
name: create-an-asset
|
||||
description: Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
|
||||
---
|
||||
|
||||
# Create an Asset
|
||||
|
||||
Generate custom sales assets tailored to your prospect, audience, and goals. Supports interactive landing pages, presentation decks, executive one-pagers, and workflow/architecture demos.
|
||||
|
||||
---
|
||||
|
||||
## Triggers
|
||||
|
||||
Invoke this skill when:
|
||||
- User says `/create-an-asset` or `/create-an-asset [CompanyName]`
|
||||
- User asks to "create an asset", "build a demo", "make a landing page", "mock up a workflow"
|
||||
- User needs a customer-facing deliverable for a sales conversation
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
This skill creates professional sales assets by gathering context about:
|
||||
- **(a) The Prospect** — company, contacts, conversations, pain points
|
||||
- **(b) The Audience** — who's viewing, what they care about
|
||||
- **(c) The Purpose** — goal of the asset, desired next action
|
||||
- **(d) The Format** — landing page, deck, one-pager, or workflow demo
|
||||
|
||||
The skill then researches, structures, and builds a polished, branded asset ready to share with customers.
|
||||
|
||||
---
|
||||
|
||||
## Phase 0: Context Detection & Input Collection
|
||||
|
||||
### Step 0.1: Detect Seller Context
|
||||
|
||||
From the user's email domain, identify what company they work for.
|
||||
|
||||
**Actions:**
|
||||
1. Extract domain from user's email
|
||||
2. Search: `"[domain]" company products services site:linkedin.com OR site:crunchbase.com`
|
||||
3. Determine seller context:
|
||||
|
||||
| Scenario | Action |
|
||||
|----------|--------|
|
||||
| **Single-product company** | Auto-populate seller context |
|
||||
| **Multi-product company** | Ask: "Which product or solution is this asset for?" |
|
||||
| **Consultant/agency/generic domain** | Ask: "What company or product are you representing?" |
|
||||
| **Unknown/startup** | Ask: "Briefly, what are you selling?" |
|
||||
|
||||
**Store seller context:**
|
||||
```yaml
|
||||
seller:
|
||||
company: "[Company Name]"
|
||||
product: "[Product/Service]"
|
||||
value_props:
|
||||
- "[Key value prop 1]"
|
||||
- "[Key value prop 2]"
|
||||
- "[Key value prop 3]"
|
||||
differentiators:
|
||||
- "[Differentiator 1]"
|
||||
- "[Differentiator 2]"
|
||||
pricing_model: "[If publicly known]"
|
||||
```
|
||||
|
||||
**Persist to knowledge base** for future sessions. On subsequent invocations, confirm: "I have your seller context from last time — still selling [Product] at [Company]?"
|
||||
|
||||
---
|
||||
|
||||
### Step 0.2: Collect Prospect Context (a)
|
||||
|
||||
**Ask the user:**
|
||||
|
||||
| Field | Prompt | Required |
|
||||
|-------|--------|----------|
|
||||
| **Company** | "Which company is this asset for?" | ✓ Yes |
|
||||
| **Key contacts** | "Who are the key contacts? (names, roles)" | No |
|
||||
| **Deal stage** | "What stage is this deal?" | ✓ Yes |
|
||||
| **Pain points** | "What pain points or priorities have they shared?" | No |
|
||||
| **Past materials** | "Upload any conversation materials (transcripts, emails, notes, call recordings)" | No |
|
||||
|
||||
**Deal stage options:**
|
||||
- Intro / First meeting
|
||||
- Discovery
|
||||
- Evaluation / Technical review
|
||||
- POC / Pilot
|
||||
- Negotiation
|
||||
- Close
|
||||
|
||||
---
|
||||
|
||||
### Step 0.3: Collect Audience Context (b)
|
||||
|
||||
**Ask the user:**
|
||||
|
||||
| Field | Prompt | Required |
|
||||
|-------|--------|----------|
|
||||
| **Audience type** | "Who's viewing this?" | ✓ Yes |
|
||||
| **Specific roles** | "Any specific titles to tailor for? (e.g., CTO, VP Engineering, CFO)" | No |
|
||||
| **Primary concern** | "What do they care most about?" | ✓ Yes |
|
||||
| **Objections** | "Any concerns or objections to address?" | No |
|
||||
|
||||
**Audience type options:**
|
||||
- Executive (C-suite, VPs)
|
||||
- Technical (Architects, Engineers, Developers)
|
||||
- Operations (Ops, IT, Procurement)
|
||||
- Mixed / Cross-functional
|
||||
|
||||
**Primary concern options:**
|
||||
- ROI / Business impact
|
||||
- Technical depth / Architecture
|
||||
- Strategic alignment
|
||||
- Risk mitigation / Security
|
||||
- Implementation / Timeline
|
||||
|
||||
---
|
||||
|
||||
### Step 0.4: Collect Purpose Context (c)
|
||||
|
||||
**Ask the user:**
|
||||
|
||||
| Field | Prompt | Required |
|
||||
|-------|--------|----------|
|
||||
| **Goal** | "What's the goal of this asset?" | ✓ Yes |
|
||||
| **Desired action** | "What should the viewer do after seeing this?" | ✓ Yes |
|
||||
|
||||
**Goal options:**
|
||||
- Intro / First impression
|
||||
- Discovery follow-up
|
||||
- Technical deep-dive
|
||||
- Executive alignment / Business case
|
||||
- POC proposal
|
||||
- Deal close
|
||||
|
||||
---
|
||||
|
||||
### Step 0.5: Select Format (d)
|
||||
|
||||
**Ask the user:** "What format works best for this?"
|
||||
|
||||
| Format | Description | Best For |
|
||||
|--------|-------------|----------|
|
||||
| **Interactive landing page** | Multi-tab page with demos, metrics, calculators | Exec alignment, intros, value prop |
|
||||
| **Deck-style** | Linear slides, presentation-ready | Formal meetings, large audiences |
|
||||
| **One-pager** | Single-scroll executive summary | Leave-behinds, quick summaries |
|
||||
| **Workflow / Architecture demo** | Interactive diagram with animated flow | Technical deep-dives, POC demos, integrations |
|
||||
|
||||
---
|
||||
|
||||
### Step 0.6: Format-Specific Inputs
|
||||
|
||||
#### If "Workflow / Architecture demo" selected:
|
||||
|
||||
**First, parse from user's description.** Look for:
|
||||
- Systems and components mentioned
|
||||
- Data flows described
|
||||
- Human interaction points
|
||||
- Example scenarios
|
||||
|
||||
**Then ask for any gaps:**
|
||||
|
||||
| If Missing... | Ask... |
|
||||
|---------------|--------|
|
||||
| Components unclear | "What systems or components are involved? (databases, APIs, AI, middleware, etc.)" |
|
||||
| Flow unclear | "Walk me through the step-by-step flow" |
|
||||
| Human touchpoints unclear | "Where does a human interact in this workflow?" |
|
||||
| Scenario vague | "What's a concrete example scenario to demo?" |
|
||||
| Integration specifics | "Any specific tools or platforms to highlight?" |
|
||||
|
||||
---
|
||||
|
||||
## Phase 1: Research (Adaptive)
|
||||
|
||||
### Assess Context Richness
|
||||
|
||||
| Level | Indicators | Research Depth |
|
||||
|-------|------------|----------------|
|
||||
| **Rich** | Transcripts uploaded, detailed pain points, clear requirements | Light — fill gaps only |
|
||||
| **Moderate** | Some context, no transcripts | Medium — company + industry |
|
||||
| **Sparse** | Just company name | Deep — full research pass |
|
||||
|
||||
### Always Research:
|
||||
|
||||
1. **Prospect basics**
|
||||
- Search: `"[Company]" annual report investor presentation 2025 2026`
|
||||
- Search: `"[Company]" CEO strategy priorities 2025 2026`
|
||||
- Extract: Revenue, employees, key metrics, strategic priorities
|
||||
|
||||
2. **Leadership**
|
||||
- Search: `"[Company]" CEO CTO CIO 2025`
|
||||
- Extract: Names, titles, recent quotes on strategy/technology
|
||||
|
||||
3. **Brand colors**
|
||||
- Search: `"[Company]" brand guidelines`
|
||||
- Or extract from company website
|
||||
- Store: Primary color, secondary color, accent
|
||||
|
||||
### If Moderate/Sparse Context, Also Research:
|
||||
|
||||
4. **Industry context**
|
||||
- Search: `"[Industry]" trends challenges 2025 2026`
|
||||
- Extract: Common pain points, market dynamics
|
||||
|
||||
5. **Technology landscape**
|
||||
- Search: `"[Company]" technology stack tools platforms`
|
||||
- Extract: Current solutions, potential integration points
|
||||
|
||||
6. **Competitive context**
|
||||
- Search: `"[Company]" vs [seller's competitors]`
|
||||
- Extract: Current solutions, switching signals
|
||||
|
||||
### If Transcripts/Materials Uploaded:
|
||||
|
||||
7. **Conversation analysis**
|
||||
- Extract: Stated pain points, decision criteria, objections, timeline
|
||||
- Identify: Key quotes to reference (use their exact language)
|
||||
- Note: Specific terminology, acronyms, internal project names
|
||||
|
||||
---
|
||||
|
||||
## Phase 2: Structure Decision
|
||||
|
||||
### Interactive Landing Page
|
||||
|
||||
| Purpose | Recommended Sections |
|
||||
|---------|---------------------|
|
||||
| **Intro** | Company Fit → Solution Overview → Key Use Cases → Why Us → Next Steps |
|
||||
| **Discovery follow-up** | Their Priorities → How We Help → Relevant Examples → ROI Framework → Next Steps |
|
||||
| **Technical deep-dive** | Architecture → Security & Compliance → Integration → Performance → Support |
|
||||
| **Exec alignment** | Strategic Fit → Business Impact → ROI Calculator → Risk Mitigation → Partnership |
|
||||
| **POC proposal** | Scope → Success Criteria → Timeline → Team → Investment → Next Steps |
|
||||
| **Deal close** | Value Summary → Pricing → Implementation Plan → Terms → Sign-off |
|
||||
|
||||
**Audience adjustments:**
|
||||
- **Executive**: Lead with business impact, ROI, strategic alignment
|
||||
- **Technical**: Lead with architecture, security, integration depth
|
||||
- **Operations**: Lead with workflow impact, change management, support
|
||||
- **Mixed**: Balance strategic + tactical; use tabs to separate depth levels
|
||||
|
||||
---
|
||||
|
||||
### Deck-Style
|
||||
|
||||
Same sections as landing page, formatted as linear slides:
|
||||
|
||||
```
|
||||
1. Title slide (Prospect + Seller logos, partnership framing)
|
||||
2. Agenda
|
||||
3-N. One section per slide (or 2-3 slides for dense sections)
|
||||
N+1. Summary / Key takeaways
|
||||
N+2. Next steps / CTA
|
||||
N+3. Appendix (optional — detailed specs, pricing, etc.)
|
||||
```
|
||||
|
||||
**Slide principles:**
|
||||
- One key message per slide
|
||||
- Visual > text-heavy
|
||||
- Use prospect's metrics and language
|
||||
- Include speaker notes
|
||||
|
||||
---
|
||||
|
||||
### One-Pager
|
||||
|
||||
Condense to single-scroll format:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────┐
|
||||
│ HERO: "[Prospect Goal] with [Product]" │
|
||||
├─────────────────────────────────────┤
|
||||
│ KEY POINT 1 │ KEY POINT 2 │ KEY POINT 3 │
|
||||
│ [Icon + 2-3 │ [Icon + 2-3 │ [Icon + 2-3 │
|
||||
│ sentences] │ sentences] │ sentences] │
|
||||
├─────────────────────────────────────┤
|
||||
│ PROOF POINT: [Metric, quote, or case study] │
|
||||
├─────────────────────────────────────┤
|
||||
│ CTA: [Clear next action] │ [Contact info] │
|
||||
└─────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Workflow / Architecture Demo
|
||||
|
||||
**Structure based on complexity:**
|
||||
|
||||
| Complexity | Components | Structure |
|
||||
|------------|------------|-----------|
|
||||
| **Simple** | 3-5 | Single-view diagram with step annotations |
|
||||
| **Medium** | 5-10 | Zoomable canvas with step-by-step walkthrough |
|
||||
| **Complex** | 10+ | Multi-layer view (overview → detailed) with guided tour |
|
||||
|
||||
**Standard elements:**
|
||||
|
||||
1. **Title bar**: `[Scenario Name] — Powered by [Seller Product]`
|
||||
2. **Component nodes**: Visual boxes/icons for each system
|
||||
3. **Flow arrows**: Animated connections showing data movement
|
||||
4. **Step panel**: Sidebar explaining current step in plain language
|
||||
5. **Controls**: Play / Pause / Step Forward / Step Back / Reset
|
||||
6. **Annotations**: Callouts for key decision points and value-adds
|
||||
7. **Data preview**: Sample payloads or transformations at each step
|
||||
|
||||
---
|
||||
|
||||
## Phase 3: Content Generation
|
||||
|
||||
### General Principles
|
||||
|
||||
All content should:
|
||||
- Reference **specific pain points** from user input or transcripts
|
||||
- Use **prospect's language** — their terminology, their stated priorities
|
||||
- Map **seller's product** → **prospect's needs** explicitly
|
||||
- Include **proof points** where available (case studies, metrics, quotes)
|
||||
- Feel **tailored, not templated**
|
||||
|
||||
---
|
||||
|
||||
### Section Templates
|
||||
|
||||
#### Hero / Intro
|
||||
```
|
||||
Headline: "[Prospect's Goal] with [Seller's Product]"
|
||||
Subhead: Tie to their stated priority or top industry challenge
|
||||
Metrics: 3-4 key facts about the prospect (shows we did homework)
|
||||
```
|
||||
|
||||
#### Their Priorities (if discovery follow-up)
|
||||
```
|
||||
Reference specific pain points from conversation:
|
||||
- Use their exact words where possible
|
||||
- Show we listened and understood
|
||||
- Connect each to how we help
|
||||
```
|
||||
|
||||
#### Solution Mapping
|
||||
```
|
||||
For each pain point:
|
||||
├── The challenge (in their words)
|
||||
├── How [Product] addresses it
|
||||
├── Proof point or example
|
||||
└── Outcome / benefit
|
||||
```
|
||||
|
||||
#### Use Cases / Demos
|
||||
```
|
||||
3-5 relevant use cases:
|
||||
├── Visual mockup or interactive demo
|
||||
├── Business impact (quantified if possible)
|
||||
├── "How it works" — 3-4 step summary
|
||||
└── Relevant to their industry/role
|
||||
```
|
||||
|
||||
#### ROI / Business Case
|
||||
```
|
||||
Interactive calculator with:
|
||||
├── Inputs relevant to their business (from research)
|
||||
│ ├── Number of users/developers
|
||||
│ ├── Current costs or time spent
|
||||
│ └── Expected improvement %
|
||||
├── Outputs:
|
||||
│ ├── Annual value / savings
|
||||
│ ├── Cost of solution
|
||||
│ ├── Net ROI
|
||||
│ └── Payback period
|
||||
└── Assumptions clearly stated (editable)
|
||||
```
|
||||
|
||||
#### Why Us / Differentiators
|
||||
```
|
||||
├── Differentiators vs. alternatives they might consider
|
||||
├── Trust, security, compliance positioning
|
||||
├── Support and partnership model
|
||||
└── Customer proof points (logos, quotes, case studies)
|
||||
```
|
||||
|
||||
#### Next Steps / CTA
|
||||
```
|
||||
├── Clear action aligned to Purpose (c)
|
||||
├── Specific next step (not vague "let's chat")
|
||||
├── Contact information
|
||||
├── Suggested timeline
|
||||
└── What happens after they take action
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Workflow Demo Content
|
||||
|
||||
#### Component Definitions
|
||||
|
||||
For each system, define:
|
||||
|
||||
```yaml
|
||||
component:
|
||||
id: "snowflake"
|
||||
label: "Snowflake Data Warehouse"
|
||||
type: "database" # database | api | ai | middleware | human | document | output
|
||||
icon: "database"
|
||||
description: "Financial performance data"
|
||||
brand_color: "#29B5E8"
|
||||
```
|
||||
|
||||
**Component types:**
|
||||
- `human` — Person initiating or receiving
|
||||
- `document` — PDFs, contracts, files
|
||||
- `ai` — AI/ML models, agents
|
||||
- `database` — Data stores, warehouses
|
||||
- `api` — APIs, services
|
||||
- `middleware` — Integration platforms, MCP servers
|
||||
- `output` — Dashboards, reports, notifications
|
||||
|
||||
#### Flow Steps
|
||||
|
||||
For each step, define:
|
||||
|
||||
```yaml
|
||||
step:
|
||||
number: 1
|
||||
from: "human"
|
||||
to: "claude"
|
||||
action: "Initiates performance review"
|
||||
description: "Sarah, a Brand Analyst at [Prospect], kicks off the quarterly review..."
|
||||
data_example: "Review request: Nike brand, Q4 2025"
|
||||
duration: "~1 second"
|
||||
value_note: "No manual data gathering required"
|
||||
```
|
||||
|
||||
#### Scenario Narrative
|
||||
|
||||
Write a clear, specific walkthrough:
|
||||
|
||||
```
|
||||
Step 1: Human Trigger
|
||||
"Sarah, a Brand Performance Analyst at Centric Brands, needs to review
|
||||
Q4 performance for the Nike license agreement. She opens the review
|
||||
dashboard and clicks 'Start Review'..."
|
||||
|
||||
Step 2: Contract Analysis
|
||||
"Claude retrieves the Nike contract PDF and extracts the performance
|
||||
obligations: minimum $50M revenue, 12% margin requirement, quarterly
|
||||
reporting deadline..."
|
||||
|
||||
Step 3: Data Query
|
||||
"Claude formulates a query and sends it to Workato DataGenie:
|
||||
'Get Q4 2025 revenue and gross margin for Nike brand from Snowflake'..."
|
||||
|
||||
Step 4: Results & Synthesis
|
||||
"Snowflake returns the data. Claude compares actuals vs. obligations:
|
||||
Revenue $52.3M ✓ (exceeded by $2.3M)
|
||||
Margin 11.2% ⚠️ (0.8% below threshold)..."
|
||||
|
||||
Step 5: Insight Delivery
|
||||
"Claude synthesizes findings into an executive summary with
|
||||
recommendations: 'Review promotional spend allocation to improve
|
||||
margin performance...'"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Phase 4: Visual Design
|
||||
|
||||
### Color System
|
||||
|
||||
```css
|
||||
:root {
|
||||
/* === Prospect Brand (Primary) === */
|
||||
--brand-primary: #[extracted from research];
|
||||
--brand-secondary: #[extracted];
|
||||
--brand-primary-rgb: [r, g, b]; /* For rgba() usage */
|
||||
|
||||
/* === Dark Theme Base === */
|
||||
--bg-primary: #0a0d14;
|
||||
--bg-elevated: #0f131c;
|
||||
--bg-surface: #161b28;
|
||||
--bg-hover: #1e2536;
|
||||
|
||||
/* === Text === */
|
||||
--text-primary: #ffffff;
|
||||
--text-secondary: rgba(255, 255, 255, 0.7);
|
||||
--text-muted: rgba(255, 255, 255, 0.5);
|
||||
|
||||
/* === Accent === */
|
||||
--accent: var(--brand-primary);
|
||||
--accent-hover: var(--brand-secondary);
|
||||
--accent-glow: rgba(var(--brand-primary-rgb), 0.3);
|
||||
|
||||
/* === Status === */
|
||||
--success: #10b981;
|
||||
--warning: #f59e0b;
|
||||
--error: #ef4444;
|
||||
}
|
||||
```
|
||||
|
||||
### Typography
|
||||
|
||||
```css
|
||||
/* Primary: Clean, professional sans-serif */
|
||||
font-family: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif;
|
||||
|
||||
/* Headings */
|
||||
h1: 2.5rem, font-weight: 700
|
||||
h2: 1.75rem, font-weight: 600
|
||||
h3: 1.25rem, font-weight: 600
|
||||
|
||||
/* Body */
|
||||
body: 1rem, font-weight: 400, line-height: 1.6
|
||||
|
||||
/* Captions/Labels */
|
||||
small: 0.875rem, font-weight: 500
|
||||
```
|
||||
|
||||
### Visual Elements
|
||||
|
||||
**Cards:**
|
||||
- Background: `var(--bg-surface)`
|
||||
- Border: 1px solid rgba(255,255,255,0.1)
|
||||
- Border-radius: 12px
|
||||
- Box-shadow: subtle, layered
|
||||
- Hover: slight elevation, border glow
|
||||
|
||||
**Buttons:**
|
||||
- Primary: `var(--accent)` background, white text
|
||||
- Secondary: transparent, accent border
|
||||
- Hover: brightness increase, subtle scale
|
||||
|
||||
**Animations:**
|
||||
- Transitions: 200-300ms ease
|
||||
- Tab switches: fade + slide
|
||||
- Hover states: smooth, not jarring
|
||||
- Loading: subtle pulse or skeleton
|
||||
|
||||
### Workflow Demo Specific
|
||||
|
||||
**Component Nodes:**
|
||||
```css
|
||||
.node {
|
||||
background: var(--bg-surface);
|
||||
border: 2px solid var(--brand-primary);
|
||||
border-radius: 12px;
|
||||
padding: 16px;
|
||||
min-width: 140px;
|
||||
}
|
||||
|
||||
.node.active {
|
||||
box-shadow: 0 0 20px var(--accent-glow);
|
||||
border-color: var(--accent);
|
||||
}
|
||||
|
||||
.node.human {
|
||||
border-color: #f59e0b; /* Warm color for humans */
|
||||
}
|
||||
|
||||
.node.ai {
|
||||
background: linear-gradient(135deg, var(--bg-surface), var(--bg-elevated));
|
||||
border-color: var(--accent);
|
||||
}
|
||||
```
|
||||
|
||||
**Flow Arrows:**
|
||||
```css
|
||||
.arrow {
|
||||
stroke: var(--text-muted);
|
||||
stroke-width: 2;
|
||||
fill: none;
|
||||
marker-end: url(#arrowhead);
|
||||
}
|
||||
|
||||
.arrow.active {
|
||||
stroke: var(--accent);
|
||||
stroke-dasharray: 8 4;
|
||||
animation: flowDash 1s linear infinite;
|
||||
}
|
||||
```
|
||||
|
||||
**Canvas:**
|
||||
```css
|
||||
.canvas {
|
||||
background:
|
||||
radial-gradient(circle at center, var(--bg-elevated) 0%, var(--bg-primary) 100%),
|
||||
url("data:image/svg+xml,..."); /* Subtle grid pattern */
|
||||
overflow: auto;
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Phase 5: Clarifying Questions (REQUIRED)
|
||||
|
||||
**Before building any asset, always ask clarifying questions.** This ensures alignment and prevents wasted effort.
|
||||
|
||||
### Step 5.1: Summarize Understanding
|
||||
|
||||
First, show the user what you understood:
|
||||
|
||||
```
|
||||
"Here's what I'm planning to build:
|
||||
|
||||
**Asset**: [Format] for [Prospect Company]
|
||||
**Audience**: [Audience type] — specifically [roles if known]
|
||||
**Goal**: [Purpose] → driving toward [desired action]
|
||||
**Key themes**: [2-3 main points to emphasize]
|
||||
|
||||
[For workflow demos, also show:]
|
||||
**Components**: [List of systems]
|
||||
**Flow**: [Step 1] → [Step 2] → [Step 3] → ...
|
||||
```
|
||||
|
||||
### Step 5.2: Ask Standard Questions (ALL formats)
|
||||
|
||||
| Question | Why |
|
||||
|----------|-----|
|
||||
| "Does this match your vision?" | Confirm understanding |
|
||||
| "What's the ONE thing this must nail to succeed?" | Focus on priority |
|
||||
| "Tone preference? (Bold & confident / Consultative / Technical & precise)" | Style alignment |
|
||||
| "Focused and concise, or comprehensive?" | Scope calibration |
|
||||
|
||||
### Step 5.3: Ask Format-Specific Questions
|
||||
|
||||
#### Interactive Landing Page:
|
||||
- "Which sections matter most for this audience?"
|
||||
- "Any specific demos or use cases to highlight?"
|
||||
- "Should I include an ROI calculator?"
|
||||
- "Any competitor positioning to address?"
|
||||
|
||||
#### Deck-Style:
|
||||
- "How long is the presentation? (helps with slide count)"
|
||||
- "Presenting live, or a leave-behind?"
|
||||
- "Any specific flow or narrative arc in mind?"
|
||||
|
||||
#### One-Pager:
|
||||
- "What's the single most important message?"
|
||||
- "Any specific proof point or stat to feature?"
|
||||
- "Will this be printed or digital?"
|
||||
|
||||
#### Workflow / Architecture Demo:
|
||||
- "Let me confirm the components: [list]. Anything missing?"
|
||||
- "Here's the flow I understood: [steps]. Correct?"
|
||||
- "Should the demo show realistic sample data, or keep it abstract?"
|
||||
- "Any integration details to highlight or downplay?"
|
||||
- "Should viewers be able to click through steps, or auto-play?"
|
||||
|
||||
### Step 5.4: Confirm and Proceed
|
||||
|
||||
After user responds:
|
||||
|
||||
```
|
||||
"Got it. I have what I need. Building your [format] now..."
|
||||
```
|
||||
|
||||
Or, if still unclear:
|
||||
|
||||
```
|
||||
"One more quick question: [specific follow-up]"
|
||||
```
|
||||
|
||||
**Max 2 rounds of questions.** If still ambiguous, make a reasonable choice and note: "I went with X — easy to adjust if you prefer Y."
|
||||
|
||||
---
|
||||
|
||||
## Phase 6: Build & Deliver
|
||||
|
||||
### Build the Asset
|
||||
|
||||
Following all specifications above:
|
||||
1. Generate structure based on Phase 2
|
||||
2. Create content based on Phase 3
|
||||
3. Apply visual design based on Phase 4
|
||||
4. Ensure all interactive elements work
|
||||
5. Test responsiveness (if applicable)
|
||||
|
||||
### Output Format
|
||||
|
||||
**All formats**: Self-contained HTML file
|
||||
- All CSS inline or in `<style>` tags
|
||||
- All JS inline or in `<script>` tags
|
||||
- No external dependencies (except Google Fonts)
|
||||
- Single file for easy sharing
|
||||
|
||||
**File naming**: `[ProspectName]-[format]-[date].html`
|
||||
- Example: `CentricBrands-workflow-demo-2026-01-28.html`
|
||||
|
||||
### Delivery Message
|
||||
|
||||
```markdown
|
||||
## ✓ Asset Created: [Prospect Name]
|
||||
|
||||
[View your asset](computer:///path/to/file.html)
|
||||
|
||||
---
|
||||
|
||||
**Summary**
|
||||
- **Format**: [Interactive Page / Deck / One-Pager / Workflow Demo]
|
||||
- **Audience**: [Type and roles]
|
||||
- **Purpose**: [Goal] → [Desired action]
|
||||
- **Sections/Steps**: [Count and list]
|
||||
|
||||
---
|
||||
|
||||
**Deployment Options**
|
||||
|
||||
To share this with your customer:
|
||||
- **Static hosting**: Upload to Netlify, Vercel, GitHub Pages, AWS S3, or any static host
|
||||
- **Password protection**: Most hosts offer this (e.g., Netlify site protection)
|
||||
- **Direct share**: Send the HTML file directly — it's fully self-contained
|
||||
- **Embed**: The file can be iframed into other pages if needed
|
||||
|
||||
---
|
||||
|
||||
**Customization**
|
||||
|
||||
Let me know if you'd like to:
|
||||
- Adjust colors or styling
|
||||
- Add, remove, or reorder sections
|
||||
- Refine any messaging or copy
|
||||
- Change the flow or architecture (for workflow demos)
|
||||
- Add more interactive elements
|
||||
- Export as PDF or static images
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Phase 7: Iteration Support
|
||||
|
||||
After delivery, be ready to iterate:
|
||||
|
||||
| User Request | Action |
|
||||
|--------------|--------|
|
||||
| "Change the colors" | Regenerate with new palette, keep content |
|
||||
| "Add a section on X" | Insert new section, maintain flow |
|
||||
| "Make it shorter" | Condense, prioritize key points |
|
||||
| "The flow is wrong" | Rebuild architecture based on correction |
|
||||
| "Use our brand instead" | Switch from prospect brand to seller brand |
|
||||
| "Add more detail on step 3" | Expand that section specifically |
|
||||
| "Can I get this as a PDF?" | Provide print-optimized version |
|
||||
|
||||
**Remember**: Default to prospect's brand colors, but seller can adjust to their own brand or a neutral palette after initial build.
|
||||
|
||||
---
|
||||
|
||||
## Quality Checklist
|
||||
|
||||
Before delivering, verify:
|
||||
|
||||
### Content
|
||||
- [ ] Prospect company name spelled correctly throughout
|
||||
- [ ] Leadership names are current (not outdated)
|
||||
- [ ] Pain points accurately reflect input/transcripts
|
||||
- [ ] Seller's product accurately represented
|
||||
- [ ] No placeholder text remaining
|
||||
- [ ] Proof points are accurate and sourced
|
||||
|
||||
### Visual
|
||||
- [ ] Brand colors applied correctly
|
||||
- [ ] All text readable (contrast)
|
||||
- [ ] Animations smooth, not distracting
|
||||
- [ ] Mobile responsive (if interactive page)
|
||||
- [ ] Dark theme looks polished
|
||||
|
||||
### Functional
|
||||
- [ ] All tabs/sections load correctly
|
||||
- [ ] Interactive elements work (calculators, demos)
|
||||
- [ ] Workflow steps animate properly (if applicable)
|
||||
- [ ] Navigation is intuitive
|
||||
- [ ] CTA is clear and clickable
|
||||
|
||||
### Professional
|
||||
- [ ] Tone matches audience
|
||||
- [ ] Appropriate level of detail for purpose
|
||||
- [ ] No typos or grammatical errors
|
||||
- [ ] Feels tailored, not templated
|
||||
|
||||
---
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Executive Landing Page
|
||||
|
||||
**Input:**
|
||||
- Prospect: Acme Corp (manufacturing)
|
||||
- Audience: C-suite
|
||||
- Purpose: Exec alignment after discovery
|
||||
- Format: Interactive landing page
|
||||
|
||||
**Output structure:**
|
||||
```
|
||||
[Tabs]
|
||||
Strategic Fit | Business Impact | ROI Calculator | Security & Trust | Next Steps
|
||||
|
||||
[Strategic Fit tab]
|
||||
- Acme's stated priorities (from discovery call)
|
||||
- How [Product] aligns
|
||||
- Relevant manufacturing customers
|
||||
```
|
||||
|
||||
### Example 2: Technical Workflow Demo
|
||||
|
||||
**Input:**
|
||||
- Prospect: Centric Brands
|
||||
- Audience: IT architects
|
||||
- Purpose: POC proposal
|
||||
- Format: Workflow demo
|
||||
- Components: Claude, Workato DataGenie, Snowflake, PDF contracts
|
||||
|
||||
**Output structure:**
|
||||
```
|
||||
[Interactive canvas with 5 nodes]
|
||||
Human → Claude → PDF Contracts → Workato → Snowflake
|
||||
↓
|
||||
[Results back to Human]
|
||||
|
||||
[Step-by-step walkthrough with sample data]
|
||||
[Controls: Play | Pause | Step | Reset]
|
||||
```
|
||||
|
||||
### Example 3: Sales One-Pager
|
||||
|
||||
**Input:**
|
||||
- Prospect: TechStart Inc
|
||||
- Audience: VP Engineering
|
||||
- Purpose: Leave-behind after first meeting
|
||||
- Format: One-pager
|
||||
|
||||
**Output structure:**
|
||||
```
|
||||
Hero: "Accelerate TechStart's Product Velocity"
|
||||
Point 1: [Dev productivity]
|
||||
Point 2: [Code quality]
|
||||
Point 3: [Time to market]
|
||||
Proof: "Similar companies saw 40% faster releases"
|
||||
CTA: "Schedule technical deep-dive"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Appendix: Component Icons
|
||||
|
||||
For workflow demos, use these icon mappings:
|
||||
|
||||
| Type | Icon | Example |
|
||||
|------|------|---------|
|
||||
| human | 👤 or person SVG | User, Analyst, Admin |
|
||||
| document | 📄 or file SVG | PDF, Contract, Report |
|
||||
| ai | 🤖 or brain SVG | Claude, AI Agent |
|
||||
| database | 🗄️ or cylinder SVG | Snowflake, Postgres |
|
||||
| api | 🔌 or plug SVG | REST API, GraphQL |
|
||||
| middleware | ⚡ or hub SVG | Workato, MCP Server |
|
||||
| output | 📊 or screen SVG | Dashboard, Report |
|
||||
|
||||
---
|
||||
|
||||
## Appendix: Brand Color Fallbacks
|
||||
|
||||
If brand colors cannot be extracted:
|
||||
|
||||
| Industry | Primary | Secondary |
|
||||
|----------|---------|-----------|
|
||||
| Technology | #2563eb | #7c3aed |
|
||||
| Finance | #0f172a | #3b82f6 |
|
||||
| Healthcare | #0891b2 | #06b6d4 |
|
||||
| Manufacturing | #ea580c | #f97316 |
|
||||
| Retail | #db2777 | #ec4899 |
|
||||
| Energy | #16a34a | #22c55e |
|
||||
| Default | #3b82f6 | #8b5cf6 |
|
||||
|
||||
---
|
||||
|
||||
*Skill created for generalized sales asset generation. Works for any seller, any product, any prospect.*
|
||||
@@ -0,0 +1,263 @@
|
||||
---
|
||||
name: daily-briefing
|
||||
description: Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
|
||||
---
|
||||
|
||||
# Daily Sales Briefing
|
||||
|
||||
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ DAILY BRIEFING │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ ALWAYS (works standalone) │
|
||||
│ ✓ You tell me: today's meetings, key deals, priorities │
|
||||
│ ✓ I organize: prioritized action plan for your day │
|
||||
│ ✓ Output: scannable 2-minute briefing │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + Calendar: auto-pull today's meetings with attendees │
|
||||
│ + CRM: pipeline alerts, tasks, deal health │
|
||||
│ + Email: unread from key accounts, waiting on replies │
|
||||
│ + Enrichment: overnight signals on your accounts │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
|
||||
When you run this skill, I'll ask for what I need:
|
||||
|
||||
**If no calendar connected:**
|
||||
> "What meetings do you have today? (Just paste your calendar or list them)"
|
||||
|
||||
**If no CRM connected:**
|
||||
> "What deals are you focused on this week? Any that need attention?"
|
||||
|
||||
**If you have connectors:**
|
||||
I'll pull everything automatically and just show you the briefing.
|
||||
|
||||
---
|
||||
|
||||
## Connectors (Optional)
|
||||
|
||||
Connect your tools to supercharge this skill:
|
||||
|
||||
| Connector | What It Adds |
|
||||
|-----------|--------------|
|
||||
| **Calendar** | Today's meetings with attendees, times, and context |
|
||||
| **CRM** | Open pipeline, deals closing soon, overdue tasks, stale deals |
|
||||
| **Email** | Unread from opportunity contacts, emails waiting on replies |
|
||||
| **Enrichment** | Overnight signals: funding, hiring, news on your accounts |
|
||||
|
||||
> **No connectors?** No problem. Tell me your meetings and deals, and I'll create your briefing.
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
```markdown
|
||||
# Daily Briefing | [Day, Month Date]
|
||||
|
||||
---
|
||||
|
||||
## #1 Priority
|
||||
|
||||
**[Most important thing to do today]**
|
||||
[Why it matters and what to do about it]
|
||||
|
||||
---
|
||||
|
||||
## Today's Numbers
|
||||
|
||||
| Open Pipeline | Closing This Month | Meetings Today | Action Items |
|
||||
|---------------|-------------------|----------------|--------------|
|
||||
| $[X] | $[X] | [N] | [N] |
|
||||
|
||||
---
|
||||
|
||||
## Today's Meetings
|
||||
|
||||
### [Time] — [Company] ([Meeting Type])
|
||||
**Attendees:** [Names]
|
||||
**Context:** [One-line: deal status, last touch, what's at stake]
|
||||
**Prep:** [Quick action before this meeting]
|
||||
|
||||
### [Time] — [Company] ([Meeting Type])
|
||||
**Attendees:** [Names]
|
||||
**Context:** [One-line context]
|
||||
**Prep:** [Quick action]
|
||||
|
||||
*Run `call-prep [company]` for detailed meeting prep*
|
||||
|
||||
---
|
||||
|
||||
## Pipeline Alerts
|
||||
|
||||
### Needs Attention
|
||||
| Deal | Stage | Amount | Alert | Action |
|
||||
|------|-------|--------|-------|--------|
|
||||
| [Deal] | [Stage] | $[X] | [Why flagged] | [What to do] |
|
||||
|
||||
### Closing This Week
|
||||
| Deal | Close Date | Amount | Confidence | Blocker |
|
||||
|------|------------|--------|------------|---------|
|
||||
| [Deal] | [Date] | $[X] | [H/M/L] | [If any] |
|
||||
|
||||
---
|
||||
|
||||
## Email Priorities
|
||||
|
||||
### Needs Response
|
||||
| From | Subject | Received |
|
||||
|------|---------|----------|
|
||||
| [Name @ Company] | [Subject] | [Time] |
|
||||
|
||||
### Waiting On Reply
|
||||
| To | Subject | Sent | Days Waiting |
|
||||
|----|---------|------|--------------|
|
||||
| [Name @ Company] | [Subject] | [Date] | [N] |
|
||||
|
||||
---
|
||||
|
||||
## Suggested Actions
|
||||
|
||||
1. **[Action]** — [Why now]
|
||||
2. **[Action]** — [Why now]
|
||||
3. **[Action]** — [Why now]
|
||||
|
||||
---
|
||||
|
||||
*Run `call-prep [company]` before your meetings*
|
||||
*Run `call-follow-up` after each call*
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Execution Flow
|
||||
|
||||
### Step 1: Gather Context
|
||||
|
||||
**If connectors available:**
|
||||
```
|
||||
1. Calendar → Get today's events
|
||||
- Filter to external meetings (non-company attendees)
|
||||
- Pull: time, title, attendees, description
|
||||
|
||||
2. CRM → Query your pipeline
|
||||
- Open opportunities owned by you
|
||||
- Flag: closing this week, no activity 7+ days, slipped dates
|
||||
- Get: overdue tasks, upcoming tasks
|
||||
|
||||
3. Email → Check priority messages
|
||||
- Unread from opportunity contact domains
|
||||
- Sent messages with no reply (3+ days)
|
||||
|
||||
4. Enrichment → Check signals (if available)
|
||||
- Funding, hiring, news on open accounts
|
||||
```
|
||||
|
||||
**If no connectors:**
|
||||
```
|
||||
Ask user:
|
||||
1. "What meetings do you have today?"
|
||||
2. "What deals are you focused on? Any closing soon or needing attention?"
|
||||
3. "Anything urgent I should know about?"
|
||||
|
||||
Work with whatever they provide.
|
||||
```
|
||||
|
||||
### Step 2: Prioritize
|
||||
|
||||
```
|
||||
Priority ranking:
|
||||
1. URGENT: Deal closing today/tomorrow not yet won
|
||||
2. HIGH: Meeting today with high-value opportunity
|
||||
3. HIGH: Unread email from decision-maker
|
||||
4. MEDIUM: Deal closing this week
|
||||
5. MEDIUM: Stale deal (7+ days no activity)
|
||||
6. LOW: Tasks due this week
|
||||
|
||||
Select #1 Priority:
|
||||
- If meeting with >$50K deal today → prep that
|
||||
- If deal closing today → focus on close
|
||||
- If urgent email from buyer → respond first
|
||||
- Else → highest-value stale deal
|
||||
```
|
||||
|
||||
### Step 3: Generate Briefing
|
||||
|
||||
```
|
||||
Assemble sections based on available data:
|
||||
|
||||
1. #1 Priority — Always include (even if simple)
|
||||
2. Today's Numbers — If CRM connected, otherwise skip
|
||||
3. Today's Meetings — From calendar or user input
|
||||
4. Pipeline Alerts — If CRM connected
|
||||
5. Email Priorities — If email connected
|
||||
6. Suggested Actions — Always include top 3 actions
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Quick Mode
|
||||
|
||||
Say "quick brief" or "tldr my day" for abbreviated version:
|
||||
|
||||
```markdown
|
||||
# Quick Brief | [Date]
|
||||
|
||||
**#1:** [Priority action]
|
||||
|
||||
**Meetings:** [N] — [Company 1], [Company 2], [Company 3]
|
||||
|
||||
**Alerts:**
|
||||
- [Alert 1]
|
||||
- [Alert 2]
|
||||
|
||||
**Do Now:** [Single most important action]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## End of Day Mode
|
||||
|
||||
Say "wrap up my day" or "end of day summary" after your last meeting:
|
||||
|
||||
```markdown
|
||||
# End of Day | [Date]
|
||||
|
||||
**Completed:**
|
||||
- [Meeting 1] — [Outcome]
|
||||
- [Meeting 2] — [Outcome]
|
||||
|
||||
**Pipeline Changes:**
|
||||
- [Deal] moved to [Stage]
|
||||
|
||||
**Tomorrow's Focus:**
|
||||
- [Priority 1]
|
||||
- [Priority 2]
|
||||
|
||||
**Open Loops:**
|
||||
- [ ] [Unfinished item needing follow-up]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Tips
|
||||
|
||||
1. **Connect your calendar first** — Biggest time saver
|
||||
2. **Add CRM second** — Unlocks pipeline alerts
|
||||
3. **Even without connectors** — Just tell me your meetings and I'll help prioritize
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **call-prep** — Deep prep for any specific meeting
|
||||
- **call-follow-up** — Process notes after calls
|
||||
- **account-research** — Research a company before first meeting
|
||||
@@ -0,0 +1,440 @@
|
||||
---
|
||||
name: draft-outreach
|
||||
description: Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
|
||||
---
|
||||
|
||||
# Draft Outreach
|
||||
|
||||
Research first, then draft. This skill never sends generic outreach - it always researches the prospect first to personalize the message. Works standalone with web search, supercharged when you connect your tools.
|
||||
|
||||
## Connectors (Optional)
|
||||
|
||||
| Connector | What It Adds |
|
||||
|-----------|--------------|
|
||||
| **Enrichment** | Verified email, phone, background details |
|
||||
| **CRM** | Prior relationship context, existing contacts |
|
||||
| **Email** | Create draft directly in your inbox |
|
||||
|
||||
> **No connectors?** Web research works great. I'll output the email text for you to copy.
|
||||
|
||||
---
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
+------------------------------------------------------------------+
|
||||
| DRAFT OUTREACH |
|
||||
| |
|
||||
| Step 1: RESEARCH (always happens first) |
|
||||
| - Web search (default) |
|
||||
| - + Enrichment (if enrichment tools connected) |
|
||||
| - + CRM (if CRM connected) |
|
||||
| |
|
||||
| Step 2: DRAFT (based on research) |
|
||||
| - Personalized opening (from research) |
|
||||
| - Relevant hook (their priorities) |
|
||||
| - Clear CTA |
|
||||
| |
|
||||
| Step 3: DELIVER (based on connectors) |
|
||||
| - Email draft (if email connected) |
|
||||
| - Copy for LinkedIn (always) |
|
||||
| - Output to user (always) |
|
||||
+------------------------------------------------------------------+
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
```markdown
|
||||
# Outreach Draft: [Person] @ [Company]
|
||||
**Generated:** [Date] | **Research Sources:** [Web, Enrichment, CRM]
|
||||
|
||||
---
|
||||
|
||||
## Research Summary
|
||||
|
||||
**Target:** [Name], [Title] at [Company]
|
||||
**Hook:** [Why reaching out now - the personalized angle]
|
||||
**Goal:** [What you want from this outreach]
|
||||
|
||||
---
|
||||
|
||||
## Email Draft
|
||||
|
||||
**To:** [email if known, or "find email" note]
|
||||
**Subject:** [Personalized subject line]
|
||||
|
||||
---
|
||||
|
||||
[Email body]
|
||||
|
||||
---
|
||||
|
||||
**Subject Line Alternatives:**
|
||||
1. [Option 2]
|
||||
2. [Option 3]
|
||||
|
||||
---
|
||||
|
||||
## LinkedIn Message (if no email)
|
||||
|
||||
**Connection Request (< 300 chars):**
|
||||
[Short, no-pitch connection request]
|
||||
|
||||
**Follow-up Message (after connected):**
|
||||
[Value-first message]
|
||||
|
||||
---
|
||||
|
||||
## Why This Approach
|
||||
|
||||
| Element | Based On |
|
||||
|---------|----------|
|
||||
| Opening | [Research finding that makes it personal] |
|
||||
| Hook | [Their priority/pain point] |
|
||||
| Proof | [Relevant customer story] |
|
||||
| CTA | [Low-friction ask] |
|
||||
|
||||
---
|
||||
|
||||
## Email Draft Status
|
||||
|
||||
[Draft created - check ~~email]
|
||||
[Email not connected - copy email above]
|
||||
[No email found - use LinkedIn approach]
|
||||
|
||||
---
|
||||
|
||||
## Follow-up Sequence (Optional)
|
||||
|
||||
**Day 3 - Follow-up 1:**
|
||||
[Short, new angle]
|
||||
|
||||
**Day 7 - Follow-up 2:**
|
||||
[Different value prop]
|
||||
|
||||
**Day 14 - Break-up:**
|
||||
[Final attempt]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Execution Flow
|
||||
|
||||
### Step 1: Parse Request
|
||||
|
||||
```
|
||||
Input patterns:
|
||||
- "draft outreach to John Smith at Acme" → Person + company
|
||||
- "write cold email to Acme's CTO" → Role + company
|
||||
- "reach out to sarah@acme.com" → Email provided
|
||||
- "LinkedIn message to [LinkedIn URL]" → Profile provided
|
||||
```
|
||||
|
||||
### Step 2: Research First (Always)
|
||||
|
||||
**Use research-prospect skill internally:**
|
||||
```
|
||||
1. Web search for company + person
|
||||
2. If Enrichment connected: Get verified contact info, background
|
||||
3. If CRM connected: Check for prior relationship
|
||||
```
|
||||
|
||||
**Must find before drafting:**
|
||||
- Who they are (title, background)
|
||||
- What the company does
|
||||
- Recent news or trigger
|
||||
- Personalization hook
|
||||
|
||||
### Step 3: Identify Hook
|
||||
|
||||
```
|
||||
Priority order for hooks:
|
||||
1. Trigger event (funding, hiring, news) → Most timely
|
||||
2. Mutual connection → Social proof
|
||||
3. Their content (post, article, talk) → Shows you did research
|
||||
4. Company initiative → Relevant to their priorities
|
||||
5. Role-based pain point → Least personal but still relevant
|
||||
```
|
||||
|
||||
### Step 4: Draft Message
|
||||
|
||||
**Email Structure (AIDA):**
|
||||
```
|
||||
SUBJECT: [Personalized, <50 chars, no spam words]
|
||||
|
||||
[Opening: Personal hook - shows you researched them]
|
||||
|
||||
[Interest: Their problem/opportunity in 1-2 sentences]
|
||||
|
||||
[Desire: Brief proof point - similar company result]
|
||||
|
||||
[Action: Clear, low-friction CTA]
|
||||
|
||||
[Signature]
|
||||
```
|
||||
|
||||
**LinkedIn Connection Request (<300 chars):**
|
||||
```
|
||||
Hi [Name], [Mutual connection/shared interest/genuine compliment].
|
||||
Would love to connect. [No pitch]
|
||||
```
|
||||
|
||||
**LinkedIn Follow-up Message:**
|
||||
```
|
||||
Thanks for connecting! [Value-first: insight, article, observation]
|
||||
|
||||
[Soft transition to why you reached out]
|
||||
|
||||
[Question, not pitch]
|
||||
```
|
||||
|
||||
### Step 5: Create Email Draft
|
||||
|
||||
```
|
||||
If email connector available:
|
||||
1. Create draft with to, subject, body
|
||||
2. Return draft link
|
||||
3. Note: "Draft created - review and send"
|
||||
|
||||
If not available:
|
||||
1. Output email text
|
||||
2. Note: "Copy to your email client"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Capability by Connector
|
||||
|
||||
| Capability | Web Only | + Enrichment | + CRM | + Email |
|
||||
|------------|----------|--------------|-------|---------|
|
||||
| Personalized opening | Basic | Deep | With history | Same |
|
||||
| Verified email | No | Yes | Yes | Yes |
|
||||
| Background details | Public only | Full | Full | Full |
|
||||
| Prior relationship | No | No | Yes | Yes |
|
||||
| Auto-create draft | No | No | No | Yes |
|
||||
|
||||
---
|
||||
|
||||
## Message Templates by Scenario
|
||||
|
||||
### Cold Outreach (No Prior Relationship)
|
||||
|
||||
```
|
||||
Subject: [Their initiative] + [your angle]
|
||||
|
||||
Hi [Name],
|
||||
|
||||
[Personal hook based on research - news, content, mutual connection].
|
||||
|
||||
[1 sentence on their likely challenge based on role/company].
|
||||
|
||||
[Brief proof: "We helped [Similar Company] achieve [Result]".]
|
||||
|
||||
Worth a 15-min call to see if relevant?
|
||||
|
||||
[Signature]
|
||||
```
|
||||
|
||||
### Warm Outreach (Have Met / Mutual Connection)
|
||||
|
||||
```
|
||||
Subject: Following up from [context]
|
||||
|
||||
Hi [Name],
|
||||
|
||||
[Reference to how you know them / who connected you].
|
||||
|
||||
[Why reaching out now - their trigger].
|
||||
|
||||
[Specific value you can offer].
|
||||
|
||||
[CTA]
|
||||
```
|
||||
|
||||
### Re-Engagement (Went Dark)
|
||||
|
||||
```
|
||||
Subject: [Short, curiosity-driven]
|
||||
|
||||
Hi [Name],
|
||||
|
||||
[Acknowledge time passed without being guilt-trippy].
|
||||
|
||||
[New reason to reconnect - their news or your news].
|
||||
|
||||
[Simple question to re-open dialogue].
|
||||
|
||||
[Signature]
|
||||
```
|
||||
|
||||
### Post-Event Follow-up
|
||||
|
||||
```
|
||||
Subject: Great meeting you at [Event]
|
||||
|
||||
Hi [Name],
|
||||
|
||||
[Specific memory from conversation].
|
||||
|
||||
[Value-add: article, intro, resource related to what you discussed].
|
||||
|
||||
[Soft CTA for next conversation].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Email Style Guidelines
|
||||
|
||||
1. **Be concise but informative** — Get to the point quickly. Busy people skim.
|
||||
2. **No markdown formatting** — Never use asterisks, bold (**text**), or other markdown. Write plain text that looks natural in any email client.
|
||||
3. **Short paragraphs** — 2-3 sentences max per paragraph. White space is your friend.
|
||||
4. **Simple lists** — If listing items, use plain dashes. No fancy formatting.
|
||||
|
||||
**Good:**
|
||||
```
|
||||
Here's what I can share:
|
||||
- Case study from a similar company
|
||||
- 15-min intro call this week
|
||||
- Quick demo if helpful
|
||||
```
|
||||
|
||||
**Bad:**
|
||||
```
|
||||
**What I Can Offer:**
|
||||
- **Case study** from a similar company
|
||||
- **Intro call** this week
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What NOT to Do
|
||||
|
||||
**Generic openers:**
|
||||
- "I hope this email finds you well"
|
||||
- "I'm reaching out because..."
|
||||
- "I wanted to introduce myself"
|
||||
|
||||
**Feature dumps:**
|
||||
- Long paragraphs about your product
|
||||
- Multiple value props at once
|
||||
- No clear CTA
|
||||
|
||||
**Fake personalization:**
|
||||
- "I noticed you work at [Company]" (obviously)
|
||||
- "Congrats on your role" (without context)
|
||||
|
||||
**Markdown in emails:**
|
||||
- Using **bold** or *italic* asterisks
|
||||
- Headers or formatted lists that won't render
|
||||
|
||||
**Instead:**
|
||||
- Lead with something specific you learned
|
||||
- One clear value prop
|
||||
- One clear ask
|
||||
- Plain text formatting only
|
||||
|
||||
---
|
||||
|
||||
## Channel Selection
|
||||
|
||||
```
|
||||
IF verified email available:
|
||||
→ Email preferred (higher response rate)
|
||||
→ Also provide LinkedIn backup
|
||||
|
||||
IF no email:
|
||||
→ LinkedIn connection request
|
||||
→ Follow-up message template for after connection
|
||||
|
||||
IF warm intro possible:
|
||||
→ Suggest mutual connection outreach first
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Company Configuration [CUSTOMIZE]
|
||||
|
||||
```markdown
|
||||
## Outreach Settings
|
||||
|
||||
- My name: [Your Name]
|
||||
- My title: [Your Title]
|
||||
- My company: [Company Name]
|
||||
- Value prop: [One sentence - what you help with]
|
||||
|
||||
## Signature
|
||||
[Your preferred email signature]
|
||||
|
||||
## Proof Points
|
||||
- [Customer 1]: [Result]
|
||||
- [Customer 2]: [Result]
|
||||
- [Customer 3]: [Result]
|
||||
|
||||
## CTA Options
|
||||
- Default: "Worth a 15-min call?"
|
||||
- Softer: "Open to learning more?"
|
||||
- Specific: "Can I send over a quick demo?"
|
||||
|
||||
## Tone
|
||||
- [Professional / Casual / Direct]
|
||||
- Industry-specific language: [Yes/No]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Example
|
||||
|
||||
**Input:** "draft outreach to the Head of Engineering at Notion"
|
||||
|
||||
**Research finds:**
|
||||
- Name: David Tibbitts
|
||||
- Recent news: Notion launched AI features
|
||||
- Hiring: 5 ML engineer roles open
|
||||
- Background: Ex-Facebook, Stanford CS
|
||||
|
||||
**Output:**
|
||||
|
||||
```markdown
|
||||
# Outreach Draft: David Tibbitts @ Notion
|
||||
|
||||
## Research Summary
|
||||
**Target:** David Tibbitts, Head of Engineering at Notion
|
||||
**Hook:** They're scaling AI features and hiring ML talent
|
||||
**Goal:** Intro call about AI infrastructure
|
||||
|
||||
---
|
||||
|
||||
## Email Draft
|
||||
|
||||
**To:** david@notion.so
|
||||
**Subject:** Notion's AI scaling + a thought
|
||||
|
||||
---
|
||||
|
||||
Hi David,
|
||||
|
||||
Saw Notion's AI rollout is gaining serious traction - congrats.
|
||||
With 5 ML roles open, seems like you're scaling fast.
|
||||
|
||||
Curious how you're thinking about inference infrastructure
|
||||
as usage grows. We helped [Similar Company] cut their AI
|
||||
serving costs 40% while improving latency.
|
||||
|
||||
Worth a 15-min call to see if relevant to your roadmap?
|
||||
|
||||
Best,
|
||||
[Name]
|
||||
|
||||
---
|
||||
|
||||
**Subject Alternatives:**
|
||||
1. Notion AI + scaling question
|
||||
2. Quick thought on Notion's ML hiring
|
||||
|
||||
---
|
||||
|
||||
## Email Draft Status
|
||||
Draft created - check ~~email
|
||||
```
|
||||
@@ -0,0 +1,214 @@
|
||||
---
|
||||
name: forecast
|
||||
description: Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
|
||||
argument-hint: "<period>"
|
||||
---
|
||||
|
||||
# /forecast
|
||||
|
||||
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
|
||||
|
||||
Generate a weighted sales forecast with risk analysis and commit recommendations.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/forecast [period]
|
||||
```
|
||||
|
||||
Generate a forecast for: $ARGUMENTS
|
||||
|
||||
If a file is referenced: @$1
|
||||
|
||||
---
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ FORECAST │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ STANDALONE (always works) │
|
||||
│ ✓ Upload CSV export from your CRM │
|
||||
│ ✓ Or paste/describe your pipeline deals │
|
||||
│ ✓ Set your quota and timeline │
|
||||
│ ✓ Get weighted forecast with stage probabilities │
|
||||
│ ✓ Risk-adjusted projections (best/likely/worst case) │
|
||||
│ ✓ Commit vs. upside breakdown │
|
||||
│ ✓ Gap analysis and recommendations │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + CRM: Pull pipeline automatically, real-time data │
|
||||
│ + Historical win rates by stage, segment, deal size │
|
||||
│ + Activity signals for risk scoring │
|
||||
│ + Automatic refresh and tracking over time │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What I Need From You
|
||||
|
||||
### Step 1: Your Pipeline Data
|
||||
|
||||
**Option A: Upload a CSV**
|
||||
Export your pipeline from your CRM (e.g. Salesforce, HubSpot). I need at minimum:
|
||||
- Deal/Opportunity name
|
||||
- Amount
|
||||
- Stage
|
||||
- Close date
|
||||
|
||||
Helpful if you have:
|
||||
- Owner (if team forecast)
|
||||
- Last activity date
|
||||
- Created date
|
||||
- Account name
|
||||
|
||||
**Option B: Paste your deals**
|
||||
```
|
||||
Acme Corp - $50K - Negotiation - closes Jan 31
|
||||
TechStart - $25K - Demo scheduled - closes Feb 15
|
||||
BigCo - $100K - Discovery - closes Mar 30
|
||||
```
|
||||
|
||||
**Option C: Describe your territory**
|
||||
"I have 8 deals in pipeline totaling $400K. Two are in negotiation ($120K), three in evaluation ($180K), three in discovery ($100K)."
|
||||
|
||||
### Step 2: Your Targets
|
||||
|
||||
- **Quota**: What's your number? (e.g., "$500K this quarter")
|
||||
- **Timeline**: When does the period end? (e.g., "Q1 ends March 31")
|
||||
- **Already closed**: How much have you already booked this period?
|
||||
|
||||
---
|
||||
|
||||
## Output
|
||||
|
||||
```markdown
|
||||
# Sales Forecast: [Period]
|
||||
|
||||
**Generated:** [Date]
|
||||
**Data Source:** [CSV upload / Manual input / CRM]
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
| Metric | Value |
|
||||
|--------|-------|
|
||||
| **Quota** | $[X] |
|
||||
| **Closed to Date** | $[X] ([X]% of quota) |
|
||||
| **Open Pipeline** | $[X] |
|
||||
| **Weighted Forecast** | $[X] |
|
||||
| **Gap to Quota** | $[X] |
|
||||
| **Coverage Ratio** | [X]x |
|
||||
|
||||
---
|
||||
|
||||
## Forecast Scenarios
|
||||
|
||||
| Scenario | Amount | % of Quota | Assumptions |
|
||||
|----------|--------|------------|-------------|
|
||||
| **Best Case** | $[X] | [X]% | All deals close as expected |
|
||||
| **Likely Case** | $[X] | [X]% | Stage-weighted probabilities |
|
||||
| **Worst Case** | $[X] | [X]% | Only commit deals close |
|
||||
|
||||
---
|
||||
|
||||
## Pipeline by Stage
|
||||
|
||||
| Stage | # Deals | Total Value | Probability | Weighted Value |
|
||||
|-------|---------|-------------|-------------|----------------|
|
||||
| Negotiation | [X] | $[X] | 80% | $[X] |
|
||||
| Proposal | [X] | $[X] | 60% | $[X] |
|
||||
| Evaluation | [X] | $[X] | 40% | $[X] |
|
||||
| Discovery | [X] | $[X] | 20% | $[X] |
|
||||
| **Total** | [X] | $[X] | — | $[X] |
|
||||
|
||||
---
|
||||
|
||||
## Commit vs. Upside
|
||||
|
||||
### Commit (High Confidence)
|
||||
Deals you'd stake your forecast on:
|
||||
|
||||
| Deal | Amount | Stage | Close Date | Why Commit |
|
||||
|------|--------|-------|------------|------------|
|
||||
| [Deal] | $[X] | [Stage] | [Date] | [Reason] |
|
||||
|
||||
**Total Commit:** $[X]
|
||||
|
||||
### Upside (Lower Confidence)
|
||||
Deals that could close but have risk:
|
||||
|
||||
| Deal | Amount | Stage | Close Date | Risk Factor |
|
||||
|------|--------|-------|------------|-------------|
|
||||
| [Deal] | $[X] | [Stage] | [Date] | [Risk] |
|
||||
|
||||
**Total Upside:** $[X]
|
||||
|
||||
---
|
||||
|
||||
## Risk Flags
|
||||
|
||||
| Deal | Amount | Risk | Recommendation |
|
||||
|------|--------|------|----------------|
|
||||
| [Deal] | $[X] | Close date passed | Update close date or move to lost |
|
||||
| [Deal] | $[X] | No activity in 14+ days | Re-engage or downgrade stage |
|
||||
| [Deal] | $[X] | Close date this week, still in discovery | Unlikely to close — push out |
|
||||
|
||||
---
|
||||
|
||||
## Gap Analysis
|
||||
|
||||
**To hit quota, you need:** $[X] more
|
||||
|
||||
**Options to close the gap:**
|
||||
1. **Accelerate [Deal]** — Currently [stage], worth $[X]. If you can close by [date], you're at [X]% of quota.
|
||||
2. **Revive [Stalled Deal]** — Last active [date]. Worth $[X]. Reach out to [contact].
|
||||
3. **New pipeline needed** — You need $[X] in new opportunities at [X]x coverage to be safe.
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
1. [ ] [Specific action for highest-impact deal]
|
||||
2. [ ] [Action for at-risk deal]
|
||||
3. [ ] [Pipeline generation recommendation if gap exists]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Stage Probabilities (Default)
|
||||
|
||||
If you don't provide custom probabilities, I'll use:
|
||||
|
||||
| Stage | Default Probability |
|
||||
|-------|---------------------|
|
||||
| Closed Won | 100% |
|
||||
| Negotiation / Contract | 80% |
|
||||
| Proposal / Quote | 60% |
|
||||
| Evaluation / Demo | 40% |
|
||||
| Discovery / Qualification | 20% |
|
||||
| Prospecting / Lead | 10% |
|
||||
|
||||
Tell me if your stages or probabilities are different.
|
||||
|
||||
---
|
||||
|
||||
## If CRM Connected
|
||||
|
||||
- I'll pull your pipeline automatically
|
||||
- Use your actual historical win rates
|
||||
- Factor in activity recency for risk scoring
|
||||
- Track forecast changes over time
|
||||
- Compare to previous forecasts
|
||||
|
||||
---
|
||||
|
||||
## Tips
|
||||
|
||||
1. **Be honest about commit** — Only commit deals you'd bet on. Upside is for everything else.
|
||||
2. **Update close dates** — Stale close dates kill forecast accuracy. Push out deals that won't close in time.
|
||||
3. **Coverage matters** — 3x pipeline coverage is healthy. Below 2x is risky.
|
||||
4. **Activity = signal** — Deals with no recent activity are at higher risk than stage suggests.
|
||||
@@ -0,0 +1,245 @@
|
||||
---
|
||||
name: pipeline-review
|
||||
description: Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
|
||||
argument-hint: "<segment or rep>"
|
||||
---
|
||||
|
||||
# /pipeline-review
|
||||
|
||||
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
|
||||
|
||||
Analyze your pipeline health, prioritize deals, and get actionable recommendations for where to focus.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/pipeline-review [segment or rep]
|
||||
```
|
||||
|
||||
Review pipeline for: $ARGUMENTS
|
||||
|
||||
If a file is referenced: @$1
|
||||
|
||||
---
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ PIPELINE REVIEW │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ STANDALONE (always works) │
|
||||
│ ✓ Upload CSV export from your CRM │
|
||||
│ ✓ Or paste/describe your deals │
|
||||
│ ✓ Health check: flag stale, stuck, and at-risk deals │
|
||||
│ ✓ Prioritization: rank deals by impact and closability │
|
||||
│ ✓ Hygiene audit: missing data, bad close dates, single-thread │
|
||||
│ ✓ Weekly action plan: what to focus on │
|
||||
├─────────────────────────────────────────────────────────────────┤
|
||||
│ SUPERCHARGED (when you connect your tools) │
|
||||
│ + CRM: Pull pipeline automatically, update records │
|
||||
│ + Activity data for engagement scoring │
|
||||
│ + Historical patterns for risk prediction │
|
||||
│ + Calendar: See upcoming meetings per deal │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What I Need From You
|
||||
|
||||
**Option A: Upload a CSV**
|
||||
Export your pipeline from your CRM (e.g. Salesforce, HubSpot). Helpful fields:
|
||||
- Deal/Opportunity name
|
||||
- Account name
|
||||
- Amount
|
||||
- Stage
|
||||
- Close date
|
||||
- Created date
|
||||
- Last activity date
|
||||
- Owner (if reviewing a team)
|
||||
- Primary contact
|
||||
|
||||
**Option B: Paste your deals**
|
||||
```
|
||||
Acme Corp - $50K - Negotiation - closes Jan 31 - last activity Jan 20
|
||||
TechStart - $25K - Demo scheduled - closes Feb 15 - no activity in 3 weeks
|
||||
BigCo - $100K - Discovery - closes Mar 30 - created last week
|
||||
```
|
||||
|
||||
**Option C: Describe your pipeline**
|
||||
"I have 12 deals. Two big ones in negotiation that I'm confident about. Three stuck in discovery for over a month. The rest are mid-stage but I haven't talked to some of them in a while."
|
||||
|
||||
---
|
||||
|
||||
## Output
|
||||
|
||||
```markdown
|
||||
# Pipeline Review: [Date]
|
||||
|
||||
**Data Source:** [CSV upload / Manual input / CRM]
|
||||
**Deals Analyzed:** [X]
|
||||
**Total Pipeline Value:** $[X]
|
||||
|
||||
---
|
||||
|
||||
## Pipeline Health Score: [X/100]
|
||||
|
||||
| Dimension | Score | Issue |
|
||||
|-----------|-------|-------|
|
||||
| **Stage Progression** | [X]/25 | [X] deals stuck in same stage 30+ days |
|
||||
| **Activity Recency** | [X]/25 | [X] deals with no activity in 14+ days |
|
||||
| **Close Date Accuracy** | [X]/25 | [X] deals with close date in past |
|
||||
| **Contact Coverage** | [X]/25 | [X] deals single-threaded |
|
||||
|
||||
---
|
||||
|
||||
## Priority Actions This Week
|
||||
|
||||
### 1. [Highest Priority Deal]
|
||||
**Why:** [Reason — large, closing soon, at risk, etc.]
|
||||
**Action:** [Specific next step]
|
||||
**Impact:** $[X] if you close it
|
||||
|
||||
### 2. [Second Priority]
|
||||
**Why:** [Reason]
|
||||
**Action:** [Next step]
|
||||
|
||||
### 3. [Third Priority]
|
||||
**Why:** [Reason]
|
||||
**Action:** [Next step]
|
||||
|
||||
---
|
||||
|
||||
## Deal Prioritization Matrix
|
||||
|
||||
### Close This Week (Focus Time Here)
|
||||
| Deal | Amount | Stage | Close Date | Next Action |
|
||||
|------|--------|-------|------------|-------------|
|
||||
| [Deal] | $[X] | [Stage] | [Date] | [Action] |
|
||||
|
||||
### Close This Month (Keep Warm)
|
||||
| Deal | Amount | Stage | Close Date | Status |
|
||||
|------|--------|-------|------------|--------|
|
||||
| [Deal] | $[X] | [Stage] | [Date] | [Status] |
|
||||
|
||||
### Nurture (Check-in Periodically)
|
||||
| Deal | Amount | Stage | Close Date | Status |
|
||||
|------|--------|-------|------------|--------|
|
||||
| [Deal] | $[X] | [Stage] | [Date] | [Status] |
|
||||
|
||||
---
|
||||
|
||||
## Risk Flags
|
||||
|
||||
### Stale Deals (No Activity 14+ Days)
|
||||
| Deal | Amount | Last Activity | Days Silent | Recommendation |
|
||||
|------|--------|---------------|-------------|----------------|
|
||||
| [Deal] | $[X] | [Date] | [X] | [Re-engage / Downgrade / Remove] |
|
||||
|
||||
### Stuck Deals (Same Stage 30+ Days)
|
||||
| Deal | Amount | Stage | Days in Stage | Recommendation |
|
||||
|------|--------|-------|---------------|----------------|
|
||||
| [Deal] | $[X] | [Stage] | [X] | [Push / Multi-thread / Qualify out] |
|
||||
|
||||
### Past Close Date
|
||||
| Deal | Amount | Close Date | Days Overdue | Recommendation |
|
||||
|------|--------|------------|--------------|----------------|
|
||||
| [Deal] | $[X] | [Date] | [X] | [Update date / Push to next quarter / Close lost] |
|
||||
|
||||
### Single-Threaded (Only One Contact)
|
||||
| Deal | Amount | Contact | Risk | Recommendation |
|
||||
|------|--------|---------|------|----------------|
|
||||
| [Deal] | $[X] | [Name] | Champion leaves = deal dies | [Identify additional stakeholders] |
|
||||
|
||||
---
|
||||
|
||||
## Hygiene Issues
|
||||
|
||||
| Issue | Count | Deals | Action |
|
||||
|-------|-------|-------|--------|
|
||||
| Missing close date | [X] | [List] | Add realistic close dates |
|
||||
| Missing amount | [X] | [List] | Estimate or qualify |
|
||||
| Missing next step | [X] | [List] | Define next action |
|
||||
| No primary contact | [X] | [List] | Assign contact |
|
||||
|
||||
---
|
||||
|
||||
## Pipeline Shape
|
||||
|
||||
### By Stage
|
||||
| Stage | # Deals | Value | % of Pipeline |
|
||||
|-------|---------|-------|---------------|
|
||||
| [Stage] | [X] | $[X] | [X]% |
|
||||
|
||||
### By Close Month
|
||||
| Month | # Deals | Value |
|
||||
|-------|---------|-------|
|
||||
| [Month] | [X] | $[X] |
|
||||
|
||||
### By Deal Size
|
||||
| Size | # Deals | Value |
|
||||
|------|---------|-------|
|
||||
| $100K+ | [X] | $[X] |
|
||||
| $50K-100K | [X] | $[X] |
|
||||
| $25K-50K | [X] | $[X] |
|
||||
| <$25K | [X] | $[X] |
|
||||
|
||||
---
|
||||
|
||||
## Recommendations
|
||||
|
||||
### This Week
|
||||
1. [ ] [Specific action for priority deal 1]
|
||||
2. [ ] [Action for at-risk deal]
|
||||
3. [ ] [Hygiene task]
|
||||
|
||||
### This Month
|
||||
1. [ ] [Strategic action]
|
||||
2. [ ] [Pipeline building if needed]
|
||||
|
||||
---
|
||||
|
||||
## Deals to Consider Removing
|
||||
|
||||
These deals may be dead weight:
|
||||
|
||||
| Deal | Amount | Reason | Recommendation |
|
||||
|------|--------|--------|----------------|
|
||||
| [Deal] | $[X] | [No activity 60+ days, no response] | Mark closed-lost |
|
||||
| [Deal] | $[X] | [Pushed 3+ times, no champion] | Qualify out |
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Prioritization Framework
|
||||
|
||||
I'll rank your deals using this framework:
|
||||
|
||||
| Factor | Weight | What I Look For |
|
||||
|--------|--------|-----------------|
|
||||
| **Close Date** | 30% | Deals closing soonest get priority |
|
||||
| **Deal Size** | 25% | Bigger deals = more focus |
|
||||
| **Stage** | 20% | Later stage = more focus |
|
||||
| **Activity** | 15% | Active deals get prioritized |
|
||||
| **Risk** | 10% | Lower risk = safer bet |
|
||||
|
||||
You can tell me to weight differently: "Focus on big deals over soon deals" or "I need quick wins, prioritize close dates."
|
||||
|
||||
---
|
||||
|
||||
## If CRM Connected
|
||||
|
||||
- I'll pull your pipeline automatically
|
||||
- Update records with new close dates, stages, next steps
|
||||
- Create follow-up tasks
|
||||
- Track hygiene improvements over time
|
||||
|
||||
---
|
||||
|
||||
## Tips
|
||||
|
||||
1. **Review weekly** — Pipeline health decays fast. Weekly reviews catch issues early.
|
||||
2. **Kill dead deals** — Stale opportunities inflate your pipeline and distort forecasts. Be ruthless.
|
||||
3. **Multi-thread everything** — If one person goes dark, you need a backup contact.
|
||||
4. **Close dates should mean something** — A close date is when you expect signature, not when you hope for one.
|
||||
Reference in New Issue
Block a user