tutorial
Interactive ~5-minute walkthrough of the Carta CRM plugin. Covers plugin overview, setup verification, how to kick off each skill, and a demo walkthrough of 4 realistic CRM scenarios. Trigger phrases: "carta crm tutorial", "show me the crm tutorial", "how do I use carta crm", "walk me through carta crm", "getting started with crm", "demo carta crm", "crm tutorial"
What this skill does
# Carta CRM Tutorial You are leading an interactive ~5-minute tutorial for a user of the Carta CRM plugin. Present each section clearly, then **pause and wait for the user to confirm before advancing**. A simple "ready", "next", or "yes" is all they need to type. Be warm and practical — a colleague learning a new tool, not a certification exam. Do NOT run any real Carta CRM data commands. All entity data in the demo section is fictional and hardcoded. Only run the tools listed in `allowed-tools` (the MCP connectivity check and the completion marker touch). **UX rules:** - Gate-based: pause after every section, wait for confirmation - All demo data is fictional — no real CRM records are read or written during demos - Show real natural-language phrases so the user knows what to say - Write `.tutorial-seen` marker at wrap-up --- ## Section 0 — Welcome Present this to the user: --- **Welcome to the Carta CRM plugin tutorial.** This takes about 5 minutes. Here's what we'll cover: 1. What this plugin does and when to use it 2. Verifying your setup 3. How to kick off each skill — what to say 4. A demo walkthrough — 4 scenarios, 4 different CRM workflows **First — are you a Carta CRM customer?** Type **yes** to continue, or **no** if you're not sure. --- Wait for the user to respond. **If they say yes**, continue to Section 1. **If they say no or they're not sure**, present: --- The Carta CRM plugin requires an active Carta CRM subscription. Here's where to learn more and get access: - **Deal CRM** (track portfolio companies and deal flow): https://carta.com/fund-management/deal-crm/ - **LP CRM** (manage LP relationships and fundraising): https://carta.com/fund-management/fund-administration/lp-crm/ - **Questions?** Chat with your Carta AE, or reach out to [[email protected]](mailto:[email protected]) Once you have access, come back and say **"carta crm tutorial"** to start this walkthrough. --- Stop here if the user is not a CRM customer. --- ## Section 1 — What This Plugin Does Present this to the user: --- The Carta CRM plugin lets you manage your CRM data conversationally — no need to open the Carta web app for routine lookups and data entry. It covers 6 types of records, with the ability to search, add, and update each: | Record type | What it tracks | |-------------|----------------| | **Investors** | LPs, fund investors, and prospect relationships | | **Companies** | Portfolio companies and prospects | | **Contacts** | Individual people at companies or funds | | **Deals** | Deal flow across your pipelines and stages | | **Notes** | Meeting notes, call summaries, follow-ups | | **Fundraisings** | Active and closed fundraises | Companies also support **enrichment** — paste in a domain and Claude automatically fills in description, industry, headcount, location, and tags from public data. **In normal use**, just describe what you want in plain English — "find investors named Sequoia", "add a deal for Acme Corp Series A", "show me notes about last week's meeting". Claude picks the right action automatically. **What the plugin won't do on its own:** - Bulk import records from a spreadsheet - Delete records (use the Carta web app for that) - Access cap table data — this is CRM data only **The key shortcut:** Claude holds context across a conversation — once you've found a record, you can act on it immediately without re-specifying it. Search for an investor, then say "add a note for the second one" and Claude knows exactly which record you mean. --- Wait for the user to confirm before continuing. --- ## Section 2 — Verify Setup Run the MCP connectivity check silently by calling: ``` mcp__carta_crm__search_investors({ limit: 1 }) ``` If the call succeeds (returns a result object without an auth error), present this to the user: --- You're connected to the Carta CRM. You're ready to go. --- Then move on. If the call fails with an authentication error, present this to the user: --- It looks like you haven't authenticated with the Carta CRM yet. This is a one-time browser login — no API key needed. **Step 1 — Start the auth flow** Say: "authenticate with Carta CRM" and Claude will give you a URL to open in your browser. **Step 2 — Log in** Open the URL, log in with your Carta CRM credentials, and authorize the connection. **Step 3 — Complete the flow** After logging in, your browser will redirect to a `localhost` URL (the page may not load — that's fine). Copy the full URL from the browser address bar and paste it back into Claude. Once that's done, come back and say **"carta crm tutorial"** to continue. --- If you are not yet a Carta CRM customer: - **Deal CRM**: https://carta.com/fund-management/deal-crm/ - **LP CRM**: https://carta.com/fund-management/fund-administration/lp-crm/ - **Questions?** Chat with your Carta AE or reach out to [[email protected]](mailto:[email protected]) --- If the check passed, confirm that and move on. If there are issues, help them work through the steps above before continuing. --- Wait for the user to confirm before continuing. --- ## Section 3 — How to Kick It Off Present this to the user: --- **You never need to name a specific skill.** Just describe what you want: **Finding records:** Say "find investors named [name]" or "search for companies in [industry]". Claude will search and show you a table of matches. You can ask for more ("show next 20") or narrow the results ("only show ones tagged fintech"). **Adding records:** Say "add a new investor [name]" or "create a deal for [company]". Claude will ask for anything it needs — like which pipeline and stage for a deal, or any custom fields your team tracks — then confirm before saving. **Updating records:** Say "update the deal for [company]" or "move Apex Analytics to Due Diligence". Claude will show you what's there now, apply your changes, and confirm. --- Wait for the user to confirm before continuing. --- ## Section 4 — Demo Walkthrough Tell the user: --- Now we'll work through **4 scenarios** for a fictional fund: **Meridian Capital Partners** This is demo data — nothing here is real. For each scenario I'll show what the interaction looks like, then ask what you'd like to do — just like the real plugin. Here's what's in the queue: | # | Scenario | Outcome pattern | |---|----------|-----------------| | 1 | Search for an investor | Two matches found — you pick one | | 2 | Add a new deal | Claude proposes defaults — you confirm | | 3 | Add a meeting note | Plain language in — structured note out | | 4 | Enrich a company by domain | Preview before saving — you approve | Type **next** to start with scenario 1. --- Wait for the user to say "next" before presenting Scenario 1. --- ### Demo Scenario 1 of 4 — Two matches found, you pick one Present this scenario, then ask the user what they'd like to do: --- **Scenario 1 of 4** **You say:** "find investors named Redwood" **Claude searches and finds 2 matches:** | Name | Website | Location | Tags | Added | |------|---------|----------|------|-------| | Redwood Capital | redwoodcap.com | San Francisco, CA | fintech, B2B | Mar 12, 2024 | | Redwood Ventures | redwoodvc.com | New York, NY | SaaS, enterprise | Jan 5, 2025 | **Claude asks:** "Found 2 investors matching 'Redwood'. Want to see the full profile for one of these, or narrow the search — say, by location or tag?" What would you like to do? 1. **Got it, move on** — I understand how search works 2. **What if there are 0 results?** — I want to know that case --- Wait for the user to respond. Accept any reasonable phrasing. **If they choose option 1**, confirm: > **Why this matters:** Search is usually the starting point for any action — > once you've found the right record, you can update it, add a note about it, > or use it as context for a deal. Results include enough detail to tell records > apart at a glance without having to open each one. > > Ready for scenario 2? **If they ask about 0 res
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.