Consensus

Most of the product works without its models. On demand video demos, interactive tours, live demos with injected data, Discovery Builder journeys and Demolytics stakeholder analytics are the platform Consensus has sold since 2013, and each stands on its own.

The AI layer sits across it: an AI Demo Agent that delivers autonomous demos on the same demo data as live sessions and answers buyer questions, agents for lead generation, pitch, demo automation, enablement and data preparation, and AI features the agreement defines as machine learning and large language model functions that generate, analyze or transform data.

Agents hold conversations with prospects without a person present, and what bounds them is unstated. The vendor sells agents that qualify buyers, answer their questions, guide discovery and capture intent, which means a machine is speaking to a customer's prospects about that customer's product with no human in the exchange. That is meaningful autonomy directed at external parties rather than internal automation.

What is published on the control side is administrative rather than behavioural: single sign on, opt in and out functionality, two factor authentication on the content board, role based access control customisable by administrators, and global admin control on the top tier. None of that addresses the agent.

Nothing states what an agent may assert about the product, what it does when it does not know, whether answers are reviewed or logged for correction, or who is accountable for a wrong claim made to a buyer. Ask what happens when the agent answers a product question incorrectly, and whether transcripts are reviewable.

The agents and their jobs are described; the models behind them are not. Consensus names an AI Demo Agent and agents for lead generation, pitch, demo automation, enablement and data preparation, and its agreement defines AI models as those used to deliver AI features, third party models included, and warns that output may be inaccurate, incomplete or inappropriate. No provider, model family or version is named for any of them, and nothing published says whether a buyer talking to an agent is told it is software.

The deepest attributed customer surface graded in this batch, sitting above three headline figures with nothing behind them. Eight testimonials carry a full name, a job title and a named employer, and the employers are large and checkable, spanning enterprise software, procurement, engineering and industrial technology, with a ninth from a named chief procurement officer citing a deployment of close to a thousand users.

One of them is quantified and attributed together, a named business unit leader stating presales scaled by over twenty percent without added headcount, which is the form this axis actually rewards. Behind them sit dedicated customer story, testimonial, review and research sections and a public return calculator.

What holds it below the top band is the banner: fifty percent larger deals, twice the deal count and thirty percent shorter cycles are published with no sample, no period, no control and no method, floating free of any customer they belong to. Ask which customers those three figures were measured across, over what period, and against what baseline.

The product conducts no outreach and its output travels inside somebody else's. Demos are shared as links, embedded on websites, dropped into marketing systems or attached to sequences run in a separate sending tool, so the sending obligations sit with whichever platform the customer sends from and the vendor does not claim otherwise.

Graded in the middle of the band with that scope stated rather than at the floor, since the floor asserts an undisciplined sending product and this does not send. Two adjacent controls are published and are real: customisable lead forms govern what a viewer is asked to supply before access, and opt in and out functionality is listed as an administrative capability.

What is not addressed anywhere reached is what the opt out actually governs, whether it covers a viewer who never filled in a form, or how it reaches someone who received the demo by internal forward. Ask what the opt out covers, who can exercise it, and how a forwarded viewer would know it exists.

A substantive summary and an unread instrument underneath it. The security page is more forthcoming than most on this subject and states several things plainly: the privacy programme is aligned to three named regimes covering the United States framework, the European regulation and the California statute, personal data commitments are incorporated into the subscriber agreement with processing on the controller's instructions, a subprocessor list is published and described as kept current, and a named security address is given for privacy questions.

It also publishes a data inventory, confirming that customer and employee personal information are collected while payment card and health information are not, which is a clearer statement of scope than most vendors offer. The operative privacy policy itself was not retrieved on this pass, so retention periods, the rights exercise route and the lawful bases relied on are unestablished and nothing here asserts they are absent. Ask for retention periods on viewer engagement records and the route for a viewer to exercise rights.

No third party corpus, and one question about what appears inside the demos. There is no contact database, no enrichment and nothing brokered here, so the usual chain of sources, licences and lawful bases does not apply and much of the axis is out of scope. The content is the customer's own product, recorded or captured by them.

What does sit in scope arrived with an acquisition: the platform now injects data into demos so that a prospect sees a populated product rather than an empty one, described by the vendor as helping buyers validate. Nothing published states where that data comes from, whether it is synthetic, whether it derives from a real customer environment, or what governs its use if it does.

A demo populated with data traceable to a real account would be a different thing from one populated with generated records. Ask what the injected demo data consists of, whether it can derive from production systems, and what controls apply if it does.

Nothing here operates on a platform belonging to somebody else. The demos run on the vendor's own player, embedded by the customer on their own properties or shared as links the vendor hosts, so there is no data taken from a third party network, no account automation and no access that another company could withdraw.

The connected products are reached through each destination's own documented route, and the named list is long and specific, covering customer record systems, marketing automation platforms, sales engagement tools, conversation intelligence, two competing enablement platforms, mail clients and a general automation connector, with availability stated per tier. A browser extension and an interface for external assistant clients extend the surface without changing who holds the permissions.

It stops below the top band for the reason most vendors in this position do: no conformance position of the vendor's own is stated against any connected platform, so the grade rests on architecture rather than on a documented commitment.

The master subscription agreement answers the training question with the default set to in. Consensus may collect, anonymize and aggregate data derived from operating the service, including usage data, and use it to improve the service and its AI features and for "training and improving AI Models"; usage data excludes customer input and output except in deidentified or aggregated form. No opt out is offered.

Customers may not submit personal or sensitive data to AI features beyond what the agreement permits, and admins get SSO, role based access, opt in and out settings and two factor authentication on DemoBoards.

The people this product observes most closely are the ones it tells least. Two mechanisms sit squarely here. Synthetic presenters and generated voiceover in more than a hundred accents mean a prospect may watch a person who does not exist explain a product, and nothing published states whether the viewer is told the presenter is generated.

And the analytics are explicitly designed to reach beyond the person contacted: the vendor sells discovery of stakeholders and automated multi threading, meaning it identifies and reports on colleagues to whom a demo was forwarded internally, people who never received an approach, never filled in a form and have no relationship with either company's sales process. Customisable lead forms and opt in and out functionality exist, and nothing establishes that either reaches a forwarded viewer.

Graded in the middle of the band rather than lower because the vendor describes both capabilities openly rather than concealing them. Ask what a forwarded viewer is told about being tracked, and whether generated presenters are disclosed as generated.

Consensus lists named integrations with what each one does: Salesforce and HubSpot for opportunity and funnel reporting, Pardot, Marketo webhooks and Eloqua for demo qualified leads, Outreach sequences and templates, Gmail and Outlook for sharing from the demo library, Gong for tracking demo engagement and sending demos inside Gong Engage, Slack, an enablement platform, G2 and SourceForge profiles, and the SNAP Chrome extension.

A RESTful API carries Demolytics into other systems or custom dashboards, a connector reaches hundreds of third party apps, and the home page lists MCP access beside the API. Sync direction and failure behavior are not described.

Who hosts it is named and where it sits is not. The vendor states that the platform runs on two named cloud providers and links to each provider's own security documentation, which is more than most vendors in this category disclose and lets a buyer establish the infrastructure chain. A subprocessor list is published and described as kept up to date. From there the question stops being answered.

No hosting region appears anywhere, no processing location, no residency election, and no transfer mechanism for moving European personal data, despite the privacy programme being described as aligned to the European regulation and to the United States framework, which is the mechanism itself and is named without being explained. That matters because the records at stake identify individuals inside prospect organisations across whatever markets a customer sells into. Naming a cloud provider is infrastructure rather than residency. Ask in which regions data is processed and stored, whether a region can be elected, and what governs transfers out of Europe.

A real certification of the stronger type, on a dedicated page with an enumerated control set behind it. The attestation is the period type rather than the point in time type, which is the distinction that matters and which several vendors graded this batch do not clear.

Around it the controls are named individually rather than gestured at: encryption in transit and at rest, routine internal and third party assessments, annual third party penetration testing, least privilege access, security focused development against a named secure coding standard and its published vulnerability list, a dedicated team described as monitoring continuously, and security training at hire and annually.

Product side controls are enumerated too, covering single sign on, two factor authentication and customisable role based access. Hosting providers are named and a current subprocessor list is published, with a security address given for questions. Held below the top band because no auditor is named, no report or audit period is published, and access runs through an account contact rather than a documented request process. Ask for the report, its period and the auditor.

The pricing page explains how Consensus charges and prints no number. Price rests on per user licenses and optional usage based capabilities and tools, integration with the customer's existing stack carries no fee, and a form leads to a package conversation. No plan name, seat count, rate or contract term appears, so a buyer learns the units of the bill but not its size.

The asset this platform accumulates is the one thing nothing addresses. Demo content largely originates with the customer, who recorded or captured their own product, so the source material exists outside the platform in most cases. Programmatic access is available from the second tier and would in principle provide a retrieval route, though it is listed as an entitlement rather than documented, so what could actually be extracted is unestablished.

What is absent entirely is any statement about the engagement record. Viewer analytics, stakeholder maps, replay behaviour and intent captured by the agents build up over years and are the reason the reporting has value, and nothing published describes exporting any of it, in any format, or states what happens to it after termination or how long a departing customer has to retrieve it. Ask for a documented export of demos, viewer analytics and agent transcripts, and the retention window after an account closes.

There is no sending apparatus here to examine. The platform operates no mailbox, no sending domain, no warmup, no rotation and no throttling, because a demo reaches a prospect as a link the customer places in an email sent from their own system, embeds on their own website, or attaches to a sequence in a separate tool. Graded in the middle of the band with that scope stated rather than at the floor, since the floor asserts a sending product without discipline and this does not send.

The one adjacent property is that the hosted player and its links sit on the vendor's own domain, so a link's reputation attaches to the vendor rather than the customer, and nothing published addresses what happens if that hosting domain is filtered or blocked by a recipient's mail security, which would affect every customer at once. Ask what happens to demo links if the hosting domain is blocked at a prospect's mail gateway.

Solutions pages address presales, sales reps, channel partners, marketing and customer success, each with its own use: presales taking repeat first demos off the calendar, partners showing the product the way the vendor would, customer success running onboarding and adoption demos. Named customers include Coupa, Lucid, Hexagon, Sage, SAP and Aavenir, and Consensus says more than half of the world's top 30 software companies use it. SSO, role based access and opt in and out settings serve large deployments. No regions or markets are listed.