valueIQDOCS
Open valueIQ

Plays · Plays · Coach a stalled deal from Claude

Coach a stalled deal from Claude

Use this play when a deal has gone quiet and you are already working in Claude, Cursor, VS Code Copilot, Windsurf or ChatGPT. The assistant coaches from the deal's own value model, drafts the follow-up, and saves where you got to.

Before you start. Connect the valueIQ MCP Server to your client first. See Connect Claude Desktop or Connect claude.ai. The prompts below work the same in every supported client.

The situation

The last email went unanswered, or the buyer said "let's revisit next quarter". You want a plan grounded in this deal, and you do not want to open another tab to get it.

Why it matters

Once the MCP Server is connected, the assistant works with your live deal data, your workspace's value models and valueIQ's competitive pricing intelligence. The same coaching engine backs the in-app Deal Copilot and the MCP connection, and every turn is saved to the deal's conversation history. What you do in Claude is waiting for you in the app.

Steps

  1. Pull up the deal. Type: "Pull up the Acme deal and walk me through the value breakdown." The assistant returns the deal summary, the drivers with their calculated impact, and the readiness assessment from the latest story.
  2. Ask for the play. "What's the highest-leverage play for this deal right now?" Follow with "What are the risk factors in this deal based on what we know?" You get a next action tied to the drivers and the context on the deal.
  3. Handle the objection that stalled it. If it was price: "They pushed back on price. Give me a response backed by the drivers." If it was timing: "The prospect wants to revisit in Q3. Help me write a follow-up that acknowledges their timeline but quantifies the cost of waiting and suggests a low-friction way to stay engaged."
  4. Draft the follow-up. "Draft a follow-up to their economic buyer, led with the payback number." The draft opens with the headline value, leads with the two drivers most relevant to that audience, and closes with a next step. It comes back to you. Nothing is sent on your behalf.
  5. Tell it what happened. "Update the deal notes: the champion confirmed budget is approved, but the economic buyer wants to see the case in Q3." Discovery information mentioned in conversation (goals, pain points, stakeholders, timeline, budget) is written into the deal's structured context, and the customer model recalculates.
  6. Save a checkpoint. "Save a checkpoint of this coaching session." When you come back, in the same client or another one: "Resume from my last checkpoint on the Acme deal." See Session checkpointing.

What to say

To the buyer, from the draft: lead with the payback number, name the two drivers they cared about, and give a specific low-commitment next step, such as a fifteen-minute call to confirm two variables. Edit the draft before you send it. The assistant writes the first version; you write the one that goes out.

What good looks like

  • One specific next action, with a reason tied to a driver.
  • An objection response you could say out loud without sounding defensive.
  • A follow-up you edited and sent yourself.
  • The deal's Copilot panel in the app shows the same thread when you open it.
  • A checkpoint you can resume from tomorrow.