Six questions to ask any value intelligence vendor
Ask every value intelligence vendor the same six questions. Below each question is every vendor's answer, as a fact from its own public pages with the source linked.
Facts read 23 to 29 October 2026 from each vendor’s public pages · valueIQ is one of the eight · How we checked
1
What has to exist before the first business case?
The answer decides how long it takes to get value, and who keeps the framework current.
| Platform | What has to exist before the first case | Stated time to first model and first case |
|---|---|---|
| valueIQ | Company website and product name; for a deal, the prospect's website (source) | About 20 minutes from account to first case; model under 30 minutes (source) |
| Minoa | Published value framework of use cases, plus CRM opportunity and call context (source) | Minutes to first case, about twenty in docs; enterprise rollout 30-60-90 days (source) |
| Cuvama | Value framework configured first: drivers, personas, formulas, proof points; Salesforce connected (source) | Live within weeks of signature; value proposition workshops take three to four weeks (source) |
| Symbe | CRM deal data, call insights, company research and an approved value framework (source) | Cases built in seconds; no time to first model or setup published (source) |
| Ecosystems | Spreadsheet value model and branding guidelines, loaded by Ecosystems before launch (source) | Up and running in as little as three weeks; Spark pilot two weeks (source) |
| ValueCore | ROI spreadsheet, sales deck and discovery questions; vendor builds a model if none (source) | Model live in a day; reps using it within days (source) |
| Mediafly Value | A template built and published by an Author; sellers then create analyses (source) | Suite implementation 8 to 10 weeks, 90 days maximum; no time to first case (source) |
| Built yourself | An AI subscription, plus the team's own prompts, templates and source files (source) | No vendor-stated time; one vendor case built an ROI calculator in 60 minutes (source) |
Swipe sideways for more →
2
Where does each number come from, and who confirmed it?
Some platforms show where each input came from; others show the assumptions without a source. The sharper question is where the improvement assumptions come from, and whether you can tell a market benchmark from a figure the seller set or one the customer confirmed.
| Platform | Every number shows where it came from | The buyer's own numbers replace estimates |
|---|---|---|
| valueIQ | Yes Each estimate lists sources with links; provenance state per variable (source) | Yes Invited buyer edits inputs and confirms them; confirmations kept with history (source) |
| Minoa | Yes Owner avatar and source note per input; survey attribution; calculation popovers (source) | Yes Buyer fills a survey or edits inputs; accepted values kept with attribution (source) |
| Cuvama | Partial Audit trail of assumption changes and validation; per-number source not shown (source) | Yes Champion views, comments or edits; validation recorded with change history (source) |
| Symbe | Partial Assumptions and calculations shown; audit log; sources per number not shown (source) | Yes Buyers edit assumptions and inputs live; cases versioned and audited (source) |
| Ecosystems | Partial IDC defaults and benchmarks named; per-number source or confirmer not shown (source) | Partial Customers enter their own data; marking numbers as buyer-confirmed not shown (source) |
| ValueCore | Partial Tooltips can carry a source per number, added per model (source) | Yes Buyer edits inputs via share link; owner reviews and merges each change (source) |
| Mediafly Value | Partial Row tooltips and descriptions; audit log records user and timestamp per item change (source) | Partial Buyer edits through an edit-and-save share link persist in the analysis (source) |
| Built yourself | Partial Published skill cites the source of each value; no record of who set it (source) | Partial Buyer numbers enter from transcripts, email and CRM; unevidenced claims flagged (source) |
Swipe sideways for more →
3
What happens when the buyer says the alternative is cheaper?
A price-only comparison invites a discount. A value comparison shows what each option is worth to this customer, next to what each one costs.
| Platform | Value against a named competitor on this deal | The competitor's published pricing, analysed beside the case |
|---|---|---|
| valueIQ | Yes Competitor model attached to the deal, valued on the same customer variables (source) | Yes Competitor pricing page analysed into a report attached to the deal (source) |
| Minoa | Partial Competitor modelled by hand as a scenario with seller-set improvement rates (source) | Partial Competitor fees entered by hand in a scenario; no pricing page analysis (source) |
| Cuvama | Not found No competitor valued on the customer's numbers, checked twice (checked 28 Oct) | Not found No competitor pricing analysis or pricing page analysis found, checked twice (checked 23 Oct) |
| Symbe | Not found No competitor valued on the customer's numbers, checked twice (checked 24 Oct) | Not found No competitor pricing or pricing page analysis found, checked twice (checked 24 Oct) |
| Ecosystems | Not found No competitor valued on the customer's numbers found (checked 24 Oct) | Not found No competitor pricing analysis or pricing page analysis found (checked 24 Oct) |
| ValueCore | Not found ValueHub makes competitor battle cards; no competitor valued on deal numbers (checked 24 Oct) | Partial Competitor prices logged on the deal; no pricing page analysis found (source) |
| Mediafly Value | Partial One undated custom TCO tool compared ShoreTel's costs with competitors (source) | Not found Not found; no competitor pricing or pricing page analysis (checked 2026-10-24) (checked 24 Oct) |
| Built yourself | Not found Not found; competitor research and battlecards on request, no competitor valuation (checked 24 Oct) | Partial Battlecards cite competitors' public pricing moves; competitive brief can cover pricing (source) |
Swipe sideways for more →
4
How is value connected to pricing?
Most platforms set one price against value on one deal. A pricing team needs the view across deals: which pricing approach leaves customers the most value, what share of the value your price captures, where discounts went with no value reason behind them, and which competitors are pulling price down.
| Platform | Test pricing approaches against value, by segment | Price as a share of value, across all deals | Discounting measured against value, across deals | Competitor pricing pressure, across deals |
|---|---|---|---|---|
| valueIQ | Yes Pricing approaches set against value per product, segment or competitor; surplus compared (source) | Yes Value Capture on every deal and across the pipeline, with trend and segment (source) | Yes Discount against each deal's expected value, by segment, with win-loss at price (source) | Yes Pricing team sees which competitors appear across deals and at what prices (source) |
| Minoa | Partial Scenarios carry different investment amounts, compared side by side on one deal (source) | Partial Pipeline Review lists ROI and investment per open deal; no trend view (source) | Not found No discount tracking against value found in docs or site, checked twice (checked 29 Oct) | Partial Competitor modelled per deal as a scenario; no cross-deal competitor view (source) |
| Cuvama | Partial ROI and TCO built per value plan; no pricing options compared (source) | Partial ROI per deal only; dashboards cover adoption, velocity and win rate (source) | Not found No discount tracking against value found; discount figure is marketing only (checked 29 Oct) | Not found No competitor pricing across deals found; no battlecards or competitor tracking (checked 29 Oct) |
| Symbe | Partial Case defends one price with ROI; no pricing approaches compared (source) | Partial Tailored ROI per deal; no price-to-value view across deals shown (source) | Not found Claims less discount pressure; no discount tracking or measurement found (checked 29 Oct) | Not found No competitor pricing across deals found; comparison tables cover tools only (checked 29 Oct) |
| Ecosystems | Partial ROI and TCO per case; no comparison of pricing approaches found (source) | Partial ROI and TCO per deal; no price-to-value view across deals (source) | Partial Discount rates tracked as program impact in Salesforce; not set against value (source) | Not found No competitor pricing across deals or battlecards found, checked twice (checked 29 Oct) |
| ValueCore | Partial Example case shows total cost against benefit and 3-year ROI; no pricing scenarios (source) | Partial ROI and total cost per case only; no cross-deal value-to-price view (source) | Partial Discount percentage recorded when a case closes Won; no cross-deal report (source) | Partial Competitor prices logged per deal; battle cards in ValueHub; no cross-deal view (source) |
| Mediafly Value | Partial One investment set against benefits per analysis; TCO and pricing calculators compare cost (source) | Partial Average ROI across analyses, over time and by industry; not price share (source) | Not found No price discount tracking in Value; only the NPV discount rate (checked 29 Oct) | Not found No competitor or competitor pricing data in Value, checked twice (checked 29 Oct) |
| Built yourself | Partial Published prompt compares three pricing strategies from past pricing data, not value (source) | Partial Business case sets price against value per deal; no cross-deal ratio view (source) | Partial Comparable-deal analysis reports average discount on wins; no value behind discounts (source) | Partial Win-loss by competitor across deals and battlecards; competitor prices not tracked per deal (source) |
Swipe sideways for more →
5
Can the buyer's AI read and check your numbers?
Buyers increasingly research with AI assistants, and teams build value into their own agents. The numbers, and how they were worked out, have to be readable by both.
| Platform | Works with AI assistants and agents (MCP) | Value and pricing models in an open format the buyer's AI can read |
|---|---|---|
| valueIQ | Yes Remote MCP server live, included on every plan including Free (source) | Yes Own value and pricing models published as Value Project files (source) |
| Minoa | Yes Remote MCP server at mcp.minoa.io on all plans; bring-your-own MCP beta (source) | Partial List prices served as JSON by a public API, own format; no value model (source) |
| Cuvama | Yes Cuvama MCP generally available to customers since 9 September 2026 (source) | Not found No value or pricing model file published in an open format (checked 23 Oct) |
| Symbe | Partial Symbe MCP listed on Enterprise only; no MCP documentation found (source) | Not found No value or pricing model file published in an open format (checked 24 Oct) |
| Ecosystems | Partial MCP connection to Claude announced on LinkedIn by Ecosystems staff; no documentation (source) | Not found No value or pricing model published in an open format (checked 24 Oct) |
| ValueCore | Yes Remote MCP server with 18 tools for five named AI assistants (source) | Not found No value or pricing model published in an open format (checked 24 Oct) |
| Mediafly Value | Partial Command MCP in early beta for Value Toolbuilder customers, joined on request (source) | Not found Not found; no published value or pricing model file (checked 2026-10-24) (checked 24 Oct) |
| Built yourself | Not found Not found; assistants connect to MCP servers but publish none for cases (checked 28 Oct) | Not found Not found; no published value or pricing model format (checked 24 Oct) |
Swipe sideways for more →
6
What carries into renewal and expansion?
"Post-sale tracking" covers very different things: a manual monthly entry, an automated product metric, and an economic result the customer has agreed to.
| Platform | Renewal starts from what was promised at signature | Delivered value measured from the customer's own systems | QBR, renewal and expansion cases from the same model |
|---|---|---|---|
| valueIQ | Yes Business case built at close kept on the deal for renewal (source) | Partial CSMs record measured results; connecting own data listed as coming soon (source) | Yes QBR Deck, renewal and expansion cases reuse the sold model's equations (source) |
| Minoa | Yes Value Realization Scenario copied from the sold scenario inside the same case (source) | Yes Monthly manual measurements; Salesforce metrics, warehouse sync or tracker API (source) | Yes Renewal and upsell cases copy scenarios from the sold business case (source) |
| Cuvama | Partial CSM opens the plan the AE built; vendor labels post-sale Emerging (source) | Partial Actuals recorded in the plan through the User MCP; no data feed named (source) | Yes Renewal and expansion cases built from the original plan; QBR not mentioned (source) |
| Symbe | Yes Create value tracker carries the case's outcomes, assumptions and drivers forward (source) | Yes Product telemetry or data warehouse sync, plus manual inputs by CSMs (source) | Yes QBRs, renewal and expansion cases built from the tracked sold case (source) |
| Ecosystems | Yes Presales business case retrieved by Customer Success in Gainsight (source) | Yes Product usage telemetry through Eco Web Services APIs; KPI actuals to Gainsight (source) | Partial Quarterly value reviews in the success plan; QBR or renewal case not named (source) |
| ValueCore | Partial Cases close as Won or Lost; renewal carry-over claimed, not documented (source) | Partial QBRs use adoption data and value estimates; data sources not named (source) | Yes Renewal Expert builds QBR presentations; one model stated from first touch to renewal (source) |
| Mediafly Value | Partial Analyses can inherit data from other analyses; prior analyses listed on Salesforce accounts (source) | Partial No documented method; one case connected Snowflake and Power BI for KPIs (source) | Partial Realized Value calculators, a separate tool type, for renewals and upsells (source) |
| Built yourself | Partial Microsoft scenario retests an implemented business case after six months; internal, not sold (source) | Partial Results pasted or uploaded by the user; connectors read systems on request (source) | Partial Customer-health skill preps QBRs separately from the sale-time case (source) |
Swipe sideways for more →
Last updated 29 October 2026
