> ## 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. # Deal Status > Ask what changed in this deal since the last review and get an answer from evidence, not memory. Every call, email, and CRM change on one deal, read back to you. Deal reviews start with a rep narrating. The narration is confident, incomplete, and shaped by what the rep remembers from the last two weeks. Nobody in the room can check it, so the review becomes a conversation about a story rather than about a deal. Deal status answers the question directly: what changed since the last review, what moved it, and what has not moved at all. Read from the calls, the emails, and the CRM record rather than from anyone's recollection. ## Data Sources | Category | Required | Recommended | | :--------------- | :------- | :---------- | | CRM | ✓ | | | Calls | ✓ | | | Email + Calendar | | ✓ | | Messaging | | ✓ | **Starter** (required only): stage, amount, and close-date history, plus what the last calls covered and what was left open. **Full** (required + recommended): the same, plus what happened between calls. Who replied and who went quiet, what threads are still unanswered, and what your own team said internally about the deal. See the [Context Graph](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the answer. ### Choose your path | Path | Best for | Output is delivered | | :------------------------- | :------------------------------------------------------------------------- | :------------------------------------ | | Build in Claude or ChatGPT | Anyone who wants to ask, on demand, mid-review or before one | In the Claude or ChatGPT conversation | | Build in Clearskies | Teams who want the answer waiting before the review, without anyone asking | To Slack DMs or channels | ## Build in Claude or ChatGPT Deal status is the most natural question to just ask, so this is the path most teams start with. A manager mid-review, a rep before one, a CRO reading into a deal they have not seen. ### The Prompt Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). Replace the account name and the window with your own. ```text theme={null} Using the Clearskies Context Graph, tell me what changed on the Acme deal in the last two weeks. Cover: - What moved: stage, amount, close date, and what caused each change - What was said on calls, and by whom - What happened over email and Slack between calls - What has not moved: open items with no reply, next steps with no date - Where the deal stands now versus where it stood two weeks ago Answer from evidence. Cite the call or thread behind each point. If something is unclear from the record, say so rather than filling it in. ``` The last instruction earns its place. The value of this answer is that it is checkable, so an honest "no evidence either way" is worth more than a confident guess. ### Make it yours * Swap the window: `since the last review`, `since Monday`, `since the deal entered this stage`. * Add `Compare what the rep said in our last 1:1 against what the record shows` when you are preparing a coaching conversation rather than a deal review. * Add `List the three questions I should ask in the review that the record cannot answer` to turn the output into an agenda. * Add `Do this for every deal in commit` to run the same read across a forecast category. ### The Skill (Claude) Two skills in the Clearskies plugin for Claude cover the two ways this question gets asked. `clearskies:deal-review` audits a deal against its risk signals: champion engagement, economic buyer status, unanswered communications, close-date health, deal velocity. Use it when the question behind "what changed" is really "what is going wrong." `clearskies:deal-strategy` works a stuck or complex deal from first principles: the real buyer, the real blocker, what has to be true to close, and whether to push the date or qualify out. Use it when the status read is finished and the question is what to do about it. #### Trigger phrases * "What changed on \[account] since the last review" * "Review the \[account] deal" * "Walk me through where \[account] stands" #### Customize it for your team * Match the output to the structure your deal reviews already use * Set the default window to your review cadence, weekly or biweekly * Name the signals your team treats as red flags so they always surface Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow. ## Build in Clearskies For teams who would rather the answer be waiting than have to ask for it. Build the workflow once and a status read on every deal in a chosen set lands before the review. ### The Workflow In the Clearskies app, open the workflow builder and describe what you want in plain language: ```text theme={null} Every Monday at 8am, find the open deals over $50,000 with a close date this quarter. For each one, write what changed in the last week: stage, amount, close date, what was said on calls, what happened over email, and what has not moved. Post each deal to the #deal-reviews channel. ``` The app configures the schedule, the deals in scope, and the destination. Scheduled workflows have no meeting context, so the deals in scope come from a record lookup rather than from a calendar. You can select them with a plain-English description or with explicit filters on stage, amount, close date, and owner. Explicit filters are worth a test run before you publish. ### Deploy to Slack Once published, each deal in scope arrives as its own message: ```text theme={null} Deal Status — Acme Corp Renewal + Analytics Owner: Daniel · $84,000 · Close Jul 31 · Negotiation Window: last 7 days What moved Close date pushed Jun 30 → Jul 31 on Tuesday. Cause is on the record: David Park raised onboarding capacity before Q4 on the renewal call, and Sarah Kim asked for the analytics module in the same paper. Stage unchanged for 19 days. What was said Renewal review call Tuesday. Renewal terms settled. Expansion into the analytics module is the open item. We committed to a 30-day pilot at no charge if onboarding capacity is the blocker. Between calls Sarah forwarded the pricing one-pager internally Thursday with "let's discuss." No reply since. Daniel flagged in Slack that legal raised data residency questions. What has not moved • Thursday follow-up call is agreed but not on the calendar • Security review question raised on the call is still unanswered • Mark Chen (economic buyer) last touchpoint was 9 days ago, and the expansion increases deal size above what he previously approved Not in the record Whether Mark Chen is still the economic buyer, or whether David Park's arrival changed the decision path. Nothing on file either way. ``` ### Customize the rollout * Choose the deals in scope: a forecast category, a stage, a threshold, one rep's book * Set the cadence to match your review rhythm and the channel to match where reviews happen * Send one message per deal, or a single digest, depending on volume * Add the signals your team treats as red flags so they always appear * Chain it with [1:1 prep](/docs/use-cases/one-on-one-prep) so managers get the same read on their reps' deals before each conversation ## Related * [Pipeline Risk Detection](/docs/pipeline-risk-detection) — deal risk alerts that fire without being asked, complementary to the on-demand read here ## The Plugin **Ready to make this part of your team's workflow?** We'll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works. [**Book 15 minutes →**](https://calendly.com/pouyan/new-meeting) ## Next steps 1. [Sign in to Clearskies](https://app.clearskies.cc/) 2. Connect your data sources 3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)