Hand off a deal to a colleague

Use this play when a deal changes hands: a territory change, leave, or a value engineer passing the deal back to the account executive. Everything lives on the deal, so the hand-off happens there rather than in a document. The workspace members and roles step is a beta feature.

Before you start. Your colleague needs a valueIQ account in the same workspace, or a workspace the product can be moved to (step 6).

The situation

Someone else is taking the deal. They need everything you know about it, and the value model must not be rebuilt.

Why it matters

The value model, the customer model, the coaching threads and the customer's confirmations all sit on the deal. A hand-off written up in a document loses the provenance: who confirmed which variable, what the customer explored, what the copilot already knows. Hand off the deal itself and all of that comes with it.

Steps in valueIQ

Bring the structured context up to date. Deal page → Deal Context panel. Each subsection has an edit pencil: Goals, Pain Points, Stakeholders, Technical Context, Value Story Readiness. Write down what currently lives only in your head. Most saves trigger a recalculation.
Write the hand-off note where the copilot can read it. Deal header → Notes field. Notes replace the existing text, so include the whole picture: where the deal stands, what was promised, what is unresolved.
Annotate the variables. Customer Model → Variables tab → expand a row → Sources and Notes fields. Your colleague should be able to see why each confirmed value is what it is. The customer-confirmed chips and provenance badges carry over untouched.
Leave the threads in place. Deal Copilot threads are saved per deal. Your colleague can scroll back or use the thread switcher at the top of the panel. Documents you uploaded into the chat stay attached. Do not start a fresh thread to tidy up; the history is the hand-off.
Give them access. Workspace Settings (near the workspace switcher) → Members tab → invite by email and assign a role: Owner, Admin, Member or Viewer. Admins see a Team view toggle in Pipeline that includes other members' deals.
Move or copy the product if they work in another workspace. Products page → product card → ⋯ More → Move / Copy. Read the dialog: it lists what carries over and what does not. Multi-product deals, opposition slots, chat history and existing stories do not copy. If any of those matter for this deal, keep it in the current workspace and add your colleague there instead.
Hand over the customer relationship in the story. Value Story → Share. The invite list shows which customer partners have accepted. Your colleague can Resend an unclaimed invite from the same dialog.

Beta. Workspace members and roles are in beta. Turn on beta mode from the workspace switcher; the Members tab appears for users with beta access.

What to type to the copilot

Your colleague, on their first day with the deal: "Brief me on this deal. Where does it stand, what has the customer confirmed, what was the last objection, and what are the top three risks to closing?" The copilot answers from the deal context, the customer model, the threads and the uploaded documents.

What good looks like

Your colleague can answer "who confirmed this number" without asking you.
Nothing in the customer model was re-entered.
The customer partner's story link still works, and their confirmations are intact.
The first copilot answer your colleague gets is specific to this deal.