Skip to main content

Documentation Index

Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt

Use this file to discover all available pages before exploring further.

You’ve connected Clearskies MCP to Claude, and your selected data sources — CRM, calls, email, calendar, and Slack — are now unified in your Clearskies Context Graph. Claude now has access to your unified data. This guide covers best practices for Sales Leaders, Sellers, and Account Managers that want to get the most out of Claude and their Clearskies Context Graph.

Claude powered by your Clearskies Context Graph

Most teams that connect Claude to their sales stack using individual connectors hit the same wall: Claude can pull a Salesforce record, surface a Gong transcript, or find a thread in Slack — but it can’t reason across all of them together. The data still lives in separate silos. Claude answers from whichever source it touches, not from the full picture. Connecting your tools and unifying your data are two different things. The Clearskies Context Graph is what makes the difference. It takes everything from your CRM, call recordings, email, calendar, and Slack and builds a single, always-current view of every account and deal. When Claude has access to it through the Clearskies MCP, it’s not pulling from individual systems in isolation — it’s reasoning across all of them at once. That fundamentally changes what Claude can do.

The most important mindset shift

Clearskies + Claude are more than just a search box. Don’t ask Claude to retrieve a specific thing (“what did the last call transcript say?”). Ask it to reason across everything it knows (“what’s the current state of this deal, and what should I do next?”). The best questions ask Claude to connect dots using your Context Graph — not look things up.

How to ask good questions

A few principles that will consistently get you better outputs: Name the account, deal, or person. “What are the risks in the NovaTech deal?” gives Claude something to work with. “What are common deal risks?” doesn’t. Say what you need it for. “I have a call with their VP of Sales tomorrow and I want to walk in prepared” is more useful context than just “tell me about this account.” Claude will shape the output to fit your actual situation. Ask for synthesis, not retrieval. “What’s the full picture on where this deal stands?” beats “what’s the CRM stage?” Ask it to surface the unified context. Tell it what you already know. “I know the champion is on board but I haven’t been able to get economic buyer access” — that context changes the answer. Don’t make Claude guess what you know and don’t know. Ask follow-up questions. The first answer is a starting point. Push deeper: “What’s the biggest risk here?” or “What would you do next?” or “What data would change that assessment?” Ask it to flag what’s missing. “What would change your answer?” or “What are we not seeing here?” will surface gaps in your knowledge — and sometimes gaps in what’s been logged.

Part 1: The Seller

These use cases follow the natural arc of an seller’s day — from getting ready for a conversation to processing what came out of it to figuring out what to do with a deal that’s stalled. Work through them in order and you’ll have a repeatable workflow that covers the full cycle.

Before a call

Getting prepared used to mean digging through Salesforce, re-reading a Gong transcript, and hoping you remembered the right email thread. Now you can ask Claude to do that synthesis for you. Try things like:
  • “I have a call with Acme on Thursday. What do I need to know going in?”
  • “What’s happened with this account since the last time we had a call?”
  • “Who am I talking to at this company and what do I know about each of them?”
  • “What open items or commitments haven’t been followed up on?”
  • “What questions should I prioritize in this call to move the deal forward?”
  • “What’s the one thing I most need to learn in this conversation?”
What makes this work well: Give Claude the company name, the meeting date, and who you’re meeting with. If you have a specific goal for the call, say it. The more context you give, the more targeted the prep will be.

After a call

The best follow-up happens fast. But writing up notes, drafting an email, and figuring out what to update in CRM takes time you often don’t have back-to-back. Paste in rough notes and let Claude do the processing. Try things like:
  • “Here are my notes from the call. What are the action items and who owns each one?”
  • “Draft a follow-up email based on what we discussed. Keep it short and direct.”
  • “What should I update in Salesforce based on this conversation?”
  • “Based on what came up in the call, what’s the biggest risk in this deal right now?”
  • “Did anything in this call change how we should think about where the deal stands?”
What makes this work well: Paste in your actual notes — even rough ones. When paired with the Clearskies Context Graph, Claude can work with bullet points, stream-of-consciousness notes, or fragments. The goal is speed, not polish on the input. Making it repeatable: Once you’ve run the post-call workflow a few times, you’ll land on a version that fits how you work — your preferred follow-up format, the CRM fields you always update, the risk flags you care most about. That’s the foundation for a skill. The Clearskies plugin lets you save that workflow so it runs the same way every time, with a single prompt. See What’s next for how to set that up.

Understanding where a deal stands

CRM records tell you what fields have been filled in. Claude can tell you what’s actually happening. Try things like:
  • “Give me an honest read on where the NovaTech deal stands.”
  • “What does the full history of this deal look like? How did we get here?”
  • “What signals suggest this deal is healthy? What signals suggest it’s at risk?”
  • “The deal is supposed to close next month. Does the evidence support that?”
  • “When did we last have a real conversation with the decision-maker, and what was said?”
  • “What’s been left unresolved in this deal that we should address?”
What makes this work well: Ask Claude to be direct. “What would need to be true for this deal to close on time?” forces an honest assessment. “What’s the status of the deal?” tends to produce a summary of what’s in CRM.

Researching an account

When you’re picking up a new account, preparing for a renewal, or handing off a deal, you need the full picture fast. Try things like:
  • “Give me a full rundown on Acme — deal history, key contacts, what we’ve discussed, where things stand.”
  • “Who are the key people at this account and what do I know about each of them?”
  • “What’s been the main theme of our conversations with this company over the last six months?”
  • “What’s the relationship history here — how did we land them, what’s happened since?”
  • “Is there anything about this account I should know before I take it over?”
What makes this work well: Account research questions work best when you’re clear about why you need the information. “I’m taking over this account” or “we have a renewal in 60 days” gives Claude context to decide what’s most relevant across your Clearskies Context Graph.

Drafting outreach

Generic outreach gets ignored. Claude can write something grounded in what’s actually been happening with an account — what was said on the last call, what’s changed recently, what the contact cares about. Try things like:
  • “Draft an email to Sarah at NovaTech. We haven’t talked in six weeks. Find a relevant angle.”
  • “I need to re-engage a deal that went quiet after procurement got involved. What should I say?”
  • “Write a short note to the new CRO who just joined the account — they weren’t part of our earlier conversations.”
  • “Our champion told us they’d have a decision this week and we’ve heard nothing. Help me follow up without being pushy.”
What makes this work well: Tell Claude who you’re writing to, your relationship history, and what you want the email to accomplish. Also tell it what tone to strike — direct, warm, brief, whatever fits.

Thinking through a stuck deal

Sometimes a deal stalls and you need help figuring out the right move. Claude can reason through it with you — not just summarize what happened, but help you think about what to do next. Try things like:
  • “The Databridge deal has been stuck in legal for five weeks. What are my options?”
  • “Our champion just left the company. How do I recover this deal?”
  • “I’ve followed up three times and haven’t heard back. Should I push, wait, or walk away?”
  • “What’s the one thing I should do this week to move this deal forward?”
  • “We’re getting compared to [Competitor]. What should I know about how to position against them based on what this customer has told us?”
What makes this work well: Tell Claude what you’re considering. “I’m considering sending another follow up email and looping in my manager” changes the guidance significantly versus just “the deal is stuck.” The more context you give, the more useful the thinking.

Part 2: The Sales Leader

The questions that matter for a sales leader are different from what a rep needs day-to-day. Less about individual call prep, more about seeing across the pipeline, reading rep performance patterns, and spotting customer risk before it turns into a conversation you weren’t ready for. Your Clearskies Customer Graph provides Claude a holistic understanding of your accounts and deals.

Pipeline health and forecast

Claude can give you a clearer picture of pipeline health than any CRM view — because your Clearskies Context Graph surfaces engagement signals, not just field values. Try things like:
  • “Which deals in my pipeline are actually at risk this quarter?”
  • “Rank my open opportunities by urgency — not by close date.”
  • “Which accounts have had no meaningful activity in the last three weeks?”
  • “Where do I have deals with no confirmed economic buyer?”
  • “The pipeline says we’ll hit number — does the evidence support that?”
  • “What’s the one deal I should focus on this week and why?”
What makes this work well: Ask Claude to surface what CRM alone can’t show you — engagement patterns, communication gaps, momentum signals. “What does the activity data suggest about deal health?” gets to things a spreadsheet won’t tell you.

Coaching reps

Getting a real read on rep performance used to mean listening to hours of calls. Claude can process recent transcripts for a rep and tell you what to pay attention to. Try things like:
  • “What patterns do you see in how [rep] handles discovery calls?”
  • “Is [rep] asking discovery questions before pitching, or leading with the product?”
  • “What’s a coaching moment from [rep]‘s recent calls I should address?”
  • “What’s [rep] doing well that I should call out?”
  • “Draft feedback I can give [rep] based on their last few calls.”
What makes this work well: Be specific about the rep and the time range. Also ask for both strengths and gaps — coaching that only flags problems doesn’t build trust.

Customer health and churn risk

Churn signals often appear in your unified data before they show up in a conversation. Engagement drops, unresolved issues, no champion contact in weeks. Try things like:
  • “Which customers are showing signs that something might be wrong?”
  • “When did we last have a real conversation with the decision-maker at [account]?”
  • “We have a renewal coming up with [customer]. What’s the honest state of that relationship?”
  • “What issues or concerns have come up in recent calls with [account] that haven’t been resolved?”
  • “Which renewals in the next 90 days should I be worried about?”
What makes this work well: Don’t wait for a red flag to ask these questions. Run them monthly across your book of business. It’s almost always easier to address a churn signal early than to recover a customer who’s already checked out.

Part 3: The Customer Success Manager

The CSM’s relationship with an account starts where the deal ends — and the context that lives in your Clearskies Context Graph from the sales cycle is one of the most underutilized assets in most orgs. Everything said in discovery calls, every commitment made, every concern raised: your Context Graph has access to it.

Onboarding and account handoff

When you take over an account, you need to understand not just what was sold, but how you got here — the relationships, the expectations set, the concerns that came up before they became your problem. Try things like:
  • “I’m taking over the Acme account from [rep]. What do I need to know about this relationship?”
  • “What did we promise in the sales process that I should make sure we’re delivering on?”
  • “Who are the key contacts at this account and what should we know about each of them?”
  • “What concerns or objections came up in the sales process that might resurface during implementation?”
  • “What does success look like for this account based on what they told us they needed?”
What makes this work well: The sales cycle often surfaces information that never makes it into the handoff doc. Ask Claude to pull from all recent customer engagement, not just CRM notes.

Ongoing health monitoring

The accounts that churn quietly are rarely the ones where something dramatic happened. They drift. Usage drops, champions go quiet, issues accumulate. Try things like:
  • “What’s the current state of my relationship with [account]?”
  • “Has engagement at [account] changed in the last 60 days? What do you see?”
  • “What issues have come up in recent conversations with [account] that haven’t been resolved?”
  • “Is our champion still engaged? When did we last hear from them directly?”
  • “What’s changed at this account in the last quarter that I should know about?”
What makes this work well: Set a cadence for these questions — once a month across your full book of business. Don’t wait until something feels off to ask.

Renewal preparation

A renewal conversation should never be the first time you’re getting honest about the health of the relationship. Try things like:
  • “We have a renewal coming up with [customer] in 60 days. What’s the honest state of this account?”
  • “What value have we delivered for [customer] that I should be able to point to in the renewal conversation?”
  • “What unresolved issues or concerns should I address before we get into renewal discussions?”
  • “Who are the right stakeholders to have in the renewal conversation and what do I know about each of them?”
  • “What would make [customer] say no to renewing, and how do I get ahead of it?”
What makes this work well: Ask Claude to be direct about risks. “What’s most likely to make this renewal hard?” is a better question than “how is this account doing?” The first forces an honest answer.

Getting better answers over time

A few things that will improve your experience as you keep using Claude + Clearskies: Keep your CRM clean. Claude is only as good as the data in your Context Graph. If call notes aren’t logged and contacts aren’t updated, Claude is working with an incomplete picture. The reps and CSMs who get the most out of this are usually the ones with clean hygiene habits. Push back when the answer feels too generic. If Claude gives you something vague, ask for specifics. “Be more direct” or “what’s the actual risk here?” will usually get you a more useful answer. Use it to think, not just to produce. Some of the best use cases aren’t about generating an output — they’re about working through a problem. “Help me think through whether this deal is worth pursuing” or “what am I missing here?” are legitimate prompts. Build repeatable workflows for the things you do every day. The post-call sequence, the monthly health check, the weekly pipeline review — once you know what questions work, you can save them. See below.

What’s next

Once you’re comfortable using Claude with natural prompts, there’s a next level available: the Clearskies plugin for Claude. It adds pre-built skills and commands — call prep, post-call processing, pipeline review, rep coaching, and more — that run structured workflows against your Context Graph automatically. Skills load context and guidance for Claude behind the scenes; commands kick off a full workflow with a single instruction. You can also build your own skills from the workflows you’ve already developed. If you’ve landed on a post-call prompt sequence that works for your team, or a monthly account health check you run every time, those are exactly what skills are built for — one saved workflow that anyone on your team can run consistently. Explore use cases and see what’s possible at clearskies.cc/claude/use-cases, or ask your Clearskies contact about installing the plugin and setting up your first custom skill.