What you can ask

Before you start. Connect a client first (see the MCP Server overview). Name the deal by company or deal name; that is how the assistant finds it.

Read a deal

• "Pull up the Acme deal and walk me through the value breakdown." Returns the deal summary, each applicable driver with its calculated impact, and the readiness assessment from the latest story.
• "What are the risk factors in this deal based on what we know?" Returns the risks vIQ sees in the deal context, customer model and conversation history, with what to do about each.

Generate a business case

• "Build a business case for [company] using [product]." Creates a deal on that product and generates the customer model. This draws credits.
• "Build an executive briefing for the economic buyer at [company]." Generates a value story from the Executive Briefing template, written for that audience and grounded in the deal's drivers. It can take a few minutes.
• "Build the deck for tomorrow's meeting." Creates a Sales Deck on the deal and starts full generation. Exporting it as PPTX or PDF draws credits.

Coach an objection

• "They pushed back on price. Give me a response backed by the drivers." Returns an evidence-backed response anchored to the deal's quantified value drivers.
• "The buyer says the other vendor is cheaper. How should I respond?" Returns a response that uses the competitor comparison and pricing analysis on the deal, if you have attached them.
• "The prospect says their team handles this manually and it's 'good enough.' Based on our value model, help me quantify what 'good enough' is actually costing them." Returns the cost of the status quo, driver by driver.

Draft a follow-up

• "Draft a follow-up to their economic buyer, led with the payback number." Returns a draft that opens with the headline value, leads with the two drivers most relevant to that audience, and closes with a next step. It comes back for you to review and send; nothing is sent for you. Add tone, length and audience constraints to the prompt and the draft follows them.

Update a variable

• "Update their headcount to 1,200 and recalculate." Updates the customer variable, triggers a recalculation, and returns the new expected value and payback.
• "Update the deal notes: the champion confirmed budget is approved." Writes the note to the deal. Discovery details you mention (goals, pain points, stakeholders, timeline, budget) go into the deal's structured context.
• "Set the Acme deal's website to acme.com." Saves the customer's website on the deal and starts the customer analysis if none has run yet.

Estimate from comparables

• "Which variables on the Acme deal should we estimate from comparable companies?" Ranks the customer variables whose value rests on thin evidence or carries a large share of the deal's value, and says which ones the account executive set and which the customer confirmed. Estimating from comparables is in beta.
• "Estimate hosting cost and headcount from comparables." Starts a background search for comparable companies, for up to five variables at once, and proposes a value for each with a rationale, how well the comparables fit and the sources. Nothing on the deal changes yet. A value the customer confirmed is never estimated, and a value the account executive set is replaced only if you agree. See Estimate from comparables.
• "Show me the proposals and accept the hosting cost one." Lists the proposals next to today's values. Accepting writes the value to the deal as a seller update, so the assistant shows you the proposal and asks first. A proposal goes stale if the deal's value changed after it was made; ask for a new estimate.

Run a DIY Reality Check

• "Run a DIY Reality Check on the Acme deal." Starts a background assessment of whether this buyer could realistically build the solution themselves, based on the deal's selected value drivers. It needs at least one driver with a value, and it draws credits when it finishes. The DIY Reality Check is in beta.
• "Show me the DIY Reality Check for the Acme deal." Returns the assessment and the effort comparison. If the deal has changed since, it is marked stale and the assistant offers to run it again. Reading it is free.

Add a competitor

• "Add [competitor product] as an opposition model to the Acme deal." Attaches the competitor's value model to the deal and returns a side-by-side, driver-by-driver comparison. The competitor model must already exist in your workspace.

Browse products and benchmarks

• "Which products in my workspace are ready for deals?" Returns the products whose value model and market values are complete.
• "Show me the value drivers and equations for [product]." Returns each driver with its equation and the variables it uses.
• "What are the market values for [variable] on [product]?" Returns the low, typical and high figures from the market estimates.
• "List the deals in this workspace at the proposal stage." Returns the matching deals with stage and expected value.

Build and edit products

• "Create a product for [company] selling [product], using [website]." Creates the product and starts building its value model and market values. This draws credits.
• "Create a variant of [product] for the mid-market." Creates a variant that shares the parent's company and competitors, tuned to the new market. This draws credits at the parent's rate. Variants are in beta.
• "Rename the driver 'Faster onboarding' to 'Shorter time to productivity', then undo it if the numbers change." Applies the edit, and can reverse the last edit on request. Editing value models is in beta.
• "Mark the travel savings driver as not applicable for this deal, and add a note to the labour driver that it assumes two shifts." Updates the driver and records the note.
• "Rename [product] to [new name]." Renames the product. Owners and Admins only.
• "Show me the edit history of [product]." Lists every edit, newest first: who made it (a person, the assistant or the system), when, why and what it changed, and where the product sits in its history now. Editing value models is in beta.
• "Put [product] back to how it was before the labour driver edit, then redo it." Moves the product to any earlier or later point in its history, including redoing an edit you undid. It is refused when the product has changed outside its history since, or when active deals, variants or siblings now depend on a part the move would change. Review acceptances and market estimates are not restored. This needs the value model edit permission.
• "Refresh the market data for [product]." Reruns the market estimates for the product's variables. Market values an admin set by hand are kept, the earlier estimates stay visible until the new ones arrive, and the product's Market Estimates sign-off is reset, so the estimates need accepting again. This is in beta.
• "Archive the [product] product." Owners and Admins only. Archiving a product also archives its variants and every deal on them, so the assistant first lists the product, its variants and each deal that would go, and archives only after you confirm that list. If a deal was added or removed in the meantime it lists them again. Nothing is deleted.
• "Restore the [product] product and bring back the Acme deal." Restoring draws the product's monthly credits again, and each deal you bring back with it is charged as a new deal. The assistant shows the cost and the archived deals first. Deals do not come back unless you name them.

Manage deals

• "Add [second product] to the Acme deal." Adds the product to the deal and builds its customer model. "Remove it again" takes it off. Deals with more than one product are in beta.
• "Move the Acme deal onto [other product]." Copies the deal and its variable values onto the other product in the same workspace and reruns the customer analysis. The original deal is archived, and its value stories are not copied.
• "Archive the deals we lost last quarter." Archives them; "restore the Acme deal" brings one back.
• "Add priya@yourcompany.com to the Acme deal team." Adds a colleague who already has a valueIQ account in the workspace. New people are invited from Settings → Team first.
• "Sign off the Acme numbers for the AE." Records sign-off, and can revoke it.

Link to your CRM

• "Link the Acme deal to opportunity [CRM id]." Stores the CRM reference on the deal. Products can be linked the same way.
• "What is the CRM scorecard for the Acme deal?" Returns Value Capture, zone, estimated value and the value summary link that the CRM displays. valueIQ integrates with leading CRMs.

Attach documents

• "Attach this discovery call transcript to the Acme deal." Uploads the file to the deal so coaching and the customer model can use it.
• "List the documents on the Acme deal and remove the old pricing sheet from the chat." Lists them and stops that file being used in coaching. Only the person who uploaded a document can remove it from the chat. Deleting a document removes it from the deal.

Work with value stories

• "List the value stories on the Acme deal and open the latest one." Returns the stories and the content of the one you pick.
• "Use labour savings and churn as the top drivers, then lock the story for tomorrow's presentation." Sets the drivers and freezes seller-side edits for four hours.
• "Archive the old Acme story." / "Bring back the archived one." Archiving takes a story off the deal's list and keeps everything in it. Anyone who can edit the deal can do it.
• "Show me the version history of the Acme story, bookmark the version we sent on Friday and restore the one before my edits." Every change is saved as a new version, and a restore saves the old content as a new version, so nothing is lost. Only the story's owner can bookmark a version.
• "Change the cover headline to '...', show the story in euros and hide the competitor box." Edits the seller's wording of a headline, paragraph or lede (not stats, tables or lists), switches the displayed currency between dollars, euros and pounds (no amounts are converted), and shows or hides a box. Your edits within two minutes of each other are folded into one version unless it is bookmarked. The assistant cannot edit while someone else has the story locked for presentation or while it is still generating.
• "What comments has the customer left on the story?" Returns the comment thread; you can also post a reply. A comment you post is visible to everyone with access to the story, including customer partners.
• "Who has been invited to this story, and has anyone claimed their invite?" Lists the customer partner invites, and can remove one.

Check the workspace

• "Give me the pipeline rollup for this workspace." Returns active deal count, total expected value and a per-stage breakdown.
• "Rename this workspace, change its value capture limits, or rename or hide a deal stage." Owners and Admins only.
• "Invite sam@yourcompany.com to this workspace." Invites a new teammate who has no valueIQ account yet, with the role their job implies. Only Owners and Admins can do this. It sends them an invitation email, so the assistant confirms with you first.
• "How many credits do we have left?" Returns the workspace credit balance.
• "Show my previous coaching threads on the Acme deal." Lists earlier threads so you can pick one up.

Pull competitor pricing

• "Pull the competitive pricing analysis for the Acme deal." Returns structured data from the competitor's published pricing page: tiers, features, billing model and usage metrics, with competitive positioning. Analyses are cached for 90 days, so the data is current rather than real-time.

Get more from every prompt

• Give context, say what you need, and set constraints: who you are meeting, what stage the deal is in, what output you want, and the tone, length and audience.
• Name the persona. "The economic buyer" gets a better answer than "the buyer".
• Tell it what happened. The assistant builds on what you say, and what you say is written back to the deal.
• Save where you got to: "Save a checkpoint of this session." See Session checkpointing.

Related

• MCP Server overview
• Coach a stalled deal from Claude