Skip to main content
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

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 for how each source feeds the answer.

​
Choose your path

​
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.
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 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:
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:

​
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 so managers get the same read on their reps’ deals before each conversation
  • 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 →

​
Next steps

  1. Sign in to Clearskies
  2. Connect your data sources
  3. Get your Clearskies MCP server and try with Claude or ChatGPT