Deal Copilot
The Deal Copilot is the chat inside every deal. It answers with the deal's own numbers, so you use it to prepare for meetings, work through objections and draft what you send next.
Before you start. You need a deal with a value model attached. The copilot builds every answer on that model, so review your value drivers and their display names before you start asking questions.
What the copilot draws on
The copilot is grounded in the deal, not in a generic picture of selling. Every answer is built from:
- the product's value model and the deal's customer model, including the value drivers that apply and the variables behind them
- any competitor (opposition) models attached to the deal
- documents you have uploaded into the deal
- the deal's notes, stage and structured context
- the readiness assessment from the latest business case
It also listens. When discovery information comes up in conversation (goals, pain points, stakeholders, competing alternatives, buying process, timeline, budget), the copilot writes it into the deal's structured context and triggers a customer model recalculation. A coaching conversation keeps the deal's intelligence current as a side effect.
Long threads are condensed automatically. After roughly 20 turns, older messages are summarised so the copilot keeps its context on deals that run for months.
Threads per deal
- Open the deal. The Copilot composer sits at the bottom of the deal page. Type a question or send a Smart Question.
- Start fresh when the topic changes. Use New thread to begin a new conversation. Threads are saved per deal.
- Review earlier coaching. Scroll the Deal Copilot panel, or use the thread switcher at the top of the panel to move between saved threads.
Beta. With beta access, + New chat in the Deal Copilot panel opens a second thread that runs alongside the first. Switch between them with the thread tabs at the top of the panel without losing state. Use it to keep a discovery thread separate from an objection-handling thread.
Upload documents
- Click the attach icon in the Copilot composer.
- Add the file. PDF, Excel, PowerPoint, Word and images are supported. Excel formulas are preserved, and images and scanned PDFs are read with OCR.
- Ask a question that uses it. The copilot reads the document and references it in its answers. Uploaded documents also appear in the Deal Context panel on the left of the deal page.
Upload background on a new stakeholder, a procurement checklist or the prospect's annual report before you prompt. The copilot factors the content into every response on that deal.
The three coaching surfaces
valueIQ gives you three places to ask for coaching. They differ in what context travels with your question.
| Surface | Where it is | What it knows |
|---|---|---|
| Deal Copilot | Open a deal, composer at the bottom | The whole deal: value model, customer model, opposition models, documents, notes |
| Product coach | Open a product, Coach tab | The product's value model and market analysis, no specific deal |
| Value Advisor | Top-right help icon, Value Advisor | Nothing from your workspace. General value selling methodology only |
Use the Deal Copilot for anything about a live opportunity. Use the product coach for methodology questions about how to sell a product in general. Use the Value Advisor when you want a plain answer about value selling and do not want any deal or product context sent.
Beta. With beta access, the workspace switcher also offers Workspace Chat: a coach scoped to the whole workspace. Ask it about pipeline patterns, cross-deal trends and portfolio-level questions without tying the thread to one deal or product.
The prompting formula
Smart Questions get you started. Free-form prompts get the most out of the copilot. The strongest prompts have three parts.
| Part | What it means | Example |
|---|---|---|
| Context | Who you are meeting, what stage you are in, what has happened so far | "I'm heading into a second call with the economic buyer at a healthcare SaaS company..." |
| What I need | The specific output you want | "...draft a three-paragraph executive summary of our business case..." |
| Constraints | Tone, length, persona, format | "...written for a financial audience, under 200 words, no jargon." |
Four habits sharpen the output further:
- Name the persona precisely. "A sceptical CTO who has been burned by failed implementations" gets a better answer than "the buyer".
- Include what you already know. Tell the copilot what you learned on the last call, what the prospect pushed back on, and the internal dynamics you have uncovered.
- Ask for a format. A bulleted brief, an email, a table or a one-page summary. Say which.
- Iterate. Treat the first answer as a draft. Ask the copilot to sharpen it, shorten it, change the tone or reframe it for a different audience.
Five reusable prompt templates
Copy these into the composer and fill in the brackets.
Meeting prep "I have a [role] meeting tomorrow at [company]. Based on our value model and deal context, give me: (1) the top 3 things I should establish in this call, (2) two questions to uncover urgency, and (3) one value statement to leave them with."
Objection response "The prospect said [exact objection]. Using our value drivers and market data, give me a concise, confident response that doesn't get defensive and re-anchors on outcome."
Stakeholder email "Draft an email to [title] at [company] following up on [topic]. Reference our quantified business case. Tone: [direct / warm / executive]. Length: 2 to 3 short paragraphs."
Competitive positioning "[Competitor] came up in the last call. Based on our value model and their typical positioning, how should I frame our differentiation for a [title] audience?"
Post-call debrief "Here's a summary of today's call: [notes]. Based on this, what should my next 3 actions be, and what's the biggest risk to this deal right now?"
Tip. The same coaching runs when you ask through an MCP-connected assistant. Every turn is saved to the deal's conversation history, so a thread you start in your assistant continues in the app.