Opine AI Presales Platform
Workspace and system of record for the technical half of a complex sale, built for sales engineers and solutions consultants and the leaders who manage them. The premise is that the work presales actually does, running proofs of value, assessing technical fit, routing specialist requests and clearing product blockers, never lands in the sales system of record and therefore never appears in a pipeline review.
Opine gives that work its own workflow rather than bending the sales database to fit, turning playbooks into executable plans with owners and dates, opening a shared portal so the buyer can follow the same thread, and capturing activity automatically instead of asking a sales engineer to log it. A model layer sits on top, summarizing recorded calls, scoring deal risk and technical fit, generating stakeholder updates and handing context to post sales at contract signature. A query language surface exposes pipeline, evaluations, accounts, tickets and activity through an in product editor, a public interface or a protocol server, with scheduled exports into a warehouse. Named customers cluster heavily in security and developer infrastructure.
Capability Axes
Capability grades
17 of 17 axes rated · 12 graded A or B
The model layer is load bearing for everything that differentiates this product, and a real workspace survives its removal. Strip it and the buyer loses automatic activity capture and returns to manual logging, loses call summarisation and risk scoring, loses the document parsing behind technical fit assessment, loses automatically built proof of value plans and generated stakeholder updates, and loses the plain English to query translation.
What remains is a structured presales workspace with templates, task assignment, specialist routing, a buyer portal and a sync to the sales database, which is a functioning product and is exactly the previous generation of presales tooling this vendor positions against. Held at the middle band rather than the top for that reason, and above the established platform band because the vendor is model native by vintage and the intelligence is not an addition to a mature stack.
One genuinely unusual oversight disclosure carries this. The privacy policy contains a dedicated automated decision making section addressing article 22 directly, stating that deal scores, risk indicators and win predictions are presented as inputs to human decisions rather than final determinations, that no decision with legal or similarly significant effect is made on a solely automated basis without human review, and publishing a contact route for anyone who wants human review of an output that affects them.
Almost nothing else in this index engages article 22 at all. Alongside it sits role based access control, federated sign on and provisioning, and granular controls governing both internal and external viewers, which matters because the buyer portal exposes deal content outside the customer's own organisation.
Off the top band because the autonomy on offer is described in strong terms, with autonomous agents deployed, an assistant acting as project manager and agents that nudge prospects to complete their tasks, and no approval queue, escalation threshold, guardrail description or agent action audit trail is published anywhere. An agent that contacts a buyer directly is the point at which a review step most needs describing.
The architecture is described in real detail and the model estate is absent entirely. The vendor explains its integration and search layer as real time data warehousing with semantic search and retrieval over presales specific context, publishes a query language surface reachable three ways, ships a protocol server and documents an interface.
Against that, no base model, provider, family, version or hosting arrangement appears anywhere on the site, in the documentation or in the privacy policy. The sub processor table for the platform lists a category reading artificial intelligence and machine learning providers, covering speech to text, language processing and conversation analytics, and names not one of them.
The single strongest word available is a customer testimonial describing the product as built on generative technologies. A buyer whose recorded sales calls are being transcribed and analysed cannot learn from any published source which company processes them.
Among the better evidenced young vendors in this index. Four case studies are published on named and recognisable customers, each carrying a quantified claim in its own title, covering three times more closed won revenue per sales engineer hour at one, over a hundred hours saved at another, and proof of concept volume up eighty five percent at a third. Named customers extend further into security and developer infrastructure.
A review platform rating of four point eight is published with a link to the underlying reviews, and eight testimonials carry a job title. Off the top band because the four headline aggregate figures, covering sales cycle reduction, hours saved per opportunity per week, win rate increase and trial conversion, carry no sample size, period, denominator or method.
The trial conversion figure also appears in two different framings, once as trials and twice as proofs of concept, at slightly different values. Note for retrieval that the animated counters render as zero to a machine, and while three recover their figure from adjacent text, the trial conversion counter loses its number entirely on the homepage.
Structurally a weak fit for this axis, graded on what is knowable, with the context carried here. This is a workspace rather than a sending platform, so there is no sequencer, no dialer and no list. Two surfaces still reach people outside the customer's organisation: the buyer portal shares deal content externally, and agents are described as nudging prospects to execute their tasks. Neither carries a statute, consent position, opt out or suppression route anywhere.
One point in the vendor's favour that sits adjacent to this axis rather than on it: the vendor handles its own marketing correctly, identifying consent as the lawful basis for approaching new contacts in Europe and the United Kingdom, relying on legitimate interests only for contacts with an existing relationship, and committing to a clear opt out in every case.
The most complete privacy disclosure encountered in this index to date, and the vendor is two years old. An article 6 table assigns a lawful basis to each processing activity with worked examples, states that legitimate interests assessments have been conducted and offers a summary of them on request.
An external data protection officer is appointed and named with organisation, postal address, telephone and email, alongside separately named European and United Kingdom article 27 representatives with full contact details. Transfers are covered by a certified data privacy framework registration, the 2021 standard contractual clauses cited by module, and the United Kingdom addendum. A retention schedule is published as a table with real day counts rather than adjectives.
Breach notification is committed at seventy two hours by article, with the high risk individual notification duty named separately. All eight data subject rights are tabled by article with a thirty day response commitment, and the California statute is covered in its own section with the collected categories enumerated.
The finding that lifts this to the top band is the website vendor table: sixteen third parties named individually, each with what it does, exactly what data it can receive, and which consent category gates it, followed by an explicit statement of which are not profiling tools and why, and which single measurement tool runs without asking and what it therefore cannot do. Visitor identification, company lookup and geolocation vendors are all named outright rather than described as partners.
Well above category norm on the website side and thin on the platform side. Three data vendors are named individually with what each receives: the visitor identification service that attempts to resolve an anonymous visit to a company and, where its data allows, to an individual; the enrichment platform that resolves a submitted email domain to a company record for routing; and the geolocation service deriving country and region from an address.
Naming a visitor identification vendor outright rather than referring vaguely to data partners is rare and is the reason this sits above the middle. Off the top band because the platform side is unsourced by comparison: lead and contact enrichment data is attributed only to permitted third party partners where lawfully obtained, with no partner named, no licence described and no coverage or accuracy stated, and publicly available professional profile data is described as used for business outreach where applicable law permits, which names a practice and no source.
Conservative and built on official routes. The recorder joins calls as a participant through integrations with four named conferencing platforms rather than through capture at the device, identity flows through three named federated providers, and the sales database connections are the standard ones. Nothing rotates an identity, rents an account, ships a scraping extension or advertises evasion, and the vendor names its conferencing dependencies openly. Off the top band on two counts.
No conformance position is stated for any conferencing platform's recording or bot participation rules, which is the term that actually governs this product's core mechanic. And a competing conversation intelligence platform is named repeatedly as an ingestion source, so recordings and transcripts held under another vendor's subscription are pulled into this one, with no position stated on the terms governing that extraction. Held at the middle band rather than lower because the posture toward every connected platform is cooperative and the integrations are official.
The training question is answered directly, in writing, with the exception disclosed rather than hidden. The policy states that the content of customer call recordings and conversation data is not used to train the vendor's models without explicit written consent from the customer. That is a real commitment with a real gate on it, and disclosing that a consent path exists is more honest than an absolute claim that quietly carves itself out elsewhere.
Product improvement is separately scoped to aggregated and de identified usage patterns. Off the top band for three reasons. The commitment lives in a privacy policy rather than in the subscription terms or a data processing agreement, and that agreement is available only on request. The processing addendum being request gated means a buyer cannot read the contractual version before signing.
And most sharply, the platform sub processor list, the one covering recorded calls and customer records, is published as nine unnamed categories with the actual vendor list obtainable only by requesting access through the trust portal, so the parties handling recorded conversations are undisclosed at the point a buyer is evaluating.
Better than most conversation capture vendors and still short of the middle band, on a distinction worth stating precisely: the platform supports automatic in call disclosure announcements and the customer is made responsible for configuring them appropriately for their jurisdiction. A supported setting the customer must switch on is not the same as a default behaviour the vendor guarantees.
The recorder does join as a bot participant, which is visible, and the policy names two party consent jurisdictions and European electronic privacy rules explicitly while placing the consent obligation on the customer, which is clearer than most vendors manage.
Against that, no position on article 50 of the European artificial intelligence regulation appears anywhere, no participant opt out mechanic is described, and the agent layer generates external stakeholder updates and nudges prospects with nothing stated about whether the recipient learns a machine composed the message. The vendor engages article 22 thoroughly and article 50 not at all, which is an unusual asymmetry and worth recording.
Open at the developer layer in a way that goes beyond a connector list. A query language surface sits on top of the customer's own data, exposing pipeline, evaluations, accounts, tickets and activity, and it is reachable three ways: an in product editor, a public interface, and a protocol server connecting external assistants. Scheduled exports push the results of those queries into a warehouse or another tool, which turns the integration story into a data ownership story.
A documentation subdomain, a status page and a machine readable site summary file round it out, the last of which indicates a vendor thinking about how models read its site. Named connections cover two sales databases, four conferencing platforms, a messaging platform, a competing conversation intelligence tool, three federated identity providers and a ticketing surface.
Off the top band because no webhook documentation, marketplace, public roadmap or extension was located, and because the entirely custom commercial model makes it impossible to establish whether any of this is gated, which is precisely the question the top band turns on elsewhere in this index.
A single region posture with no options in it, disclosed clearly and supported by a fully specified transfer mechanism, which is the treatment given to comparable vendors in this index. Personal data the vendor controls is stated to sit on servers located in the United States, the company is stated to be headquartered there, and European, United Kingdom and Swiss transfers are covered by a certified framework registration, the standard contractual clauses cited by module, and the United Kingdom addendum, with the transfer documentation available on request.
Sub processors making international transfers are stated to be bound by equivalent mechanisms. Off the top band because there is no region choice, no country option and no residency alternative offered to a European customer, the cloud infrastructure providers are given as examples rather than as a definitive list, and the residency statement is written about data the vendor controls without a separate explicit statement covering where customer platform data, including recorded calls, physically resides.
A control set well beyond what a company at this stage usually carries, and the vendor explains why on its own page: its customers are security companies. A service organisation control type two audit is held, annual third party penetration testing is stated as a cadence rather than a one off, monitoring runs continuously, federated sign on and provisioning are shipped, access is role based, multi factor authentication is required for all administrative access, and the cryptography is named with the actual cipher and protocol rather than described as bank grade.
Vendor security assessments, mandatory staff training, documented incident response and a public status page complete it. Off the top band because the assurance is asserted and the evidence is gated: the trust portal renders nothing to a machine, no audit period, audit date or auditor is published anywhere, the sub processor list itself requires requesting access through that portal, and no vulnerability disclosure route or security contact address appears on any public page. Note a small inconsistency worth checking at renewal, in that the commercial page states one transport encryption version while the privacy policy states a lower minimum.
No price, no unit of pricing and no tier structure appears anywhere. The pricing page is a four step quote form that asks the buyer how large their revenue team is and promises a tailored figure within one business day. The only commercial content published is what is included rather than what anything costs, covering onboarding, data migration and integration to the sales database.
The vendor makes a virtue of the opacity, stating that it will never force a buyer into the same bucket as anyone else and presenting this as a differentiator, which is opacity marketed as personalisation. The four team size bands offered in the form indicate that team size is a pricing input but publish no rate against any of them, and the page separately disclaims per seat pricing without saying what replaces it.
This is the same shape recorded at the largest vendors in this index, where the most disclosed vendor on every other axis publishes nothing at all on price, and it is notable that a company two years old has arrived at the identical posture.
Portability is treated as a product capability rather than a contractual concession, which is the pattern that separates vendors who actually have it. A query language surface reads the customer's own pipeline, evaluations, accounts, tickets and activity, reachable through a public interface and a protocol server as well as in product, and those queries can be scheduled to export into a warehouse or another tool on a recurring basis. That is bulk retrieval as a designed feature.
Deletion is published as a schedule with real numbers rather than adjectives: customer account data deleted within sixty days of contract termination, integration data within ninety days of an explicit deletion request or sixty days of termination, usage logs at thirty days. The machine readable portability right is stated by article.
Off the top band because the sixty day window functions as a de facto retrieval period but is never framed as one, so no post termination export window is actually promised, no export format is guaranteed, the subscription terms were not read, and the entirely custom commercial model leaves it unknowable whether the query surface is available to every customer or only to some.
Structurally a weak fit for this axis, graded on what is knowable, with the context carried here. This product runs no marketing send, no sequencer and no dialer, so the reputation exposure that this axis usually measures does not arise in its normal form. Transactional mail leaves through a named third party service, disclosed in the website vendor table.
What does generate outbound volume is the agent layer, which produces internal and external stakeholder updates automatically and nudges prospects to complete assigned tasks, and none of that arrives with any published warmup, pacing, volume ceiling, bounce handling, authentication position or complaint threshold.
Nothing here suggests poor practice; there is simply no sending discipline published because sending is not what the vendor considers itself to do, and the agent layer quietly makes that less true than it was.
The ideal customer is drawn more sharply than most vendors attempt. Five audience pages cover sales engineering leaders, revenue operations, sales managers, post sales and, unusually, buyers themselves, which almost nothing else in this index publishes. The written statement of who this is for is specific rather than generic, naming business technology companies selling from the top down where every deal matters and every proof of concept is precious.
Four team size bands appear in the quote flow, running from one to ten people up to two hundred and above. The named customer list corroborates the claim and clusters tightly in security and developer infrastructure, and the vendor says outright that it is tested by the largest security companies.
Off the top band because no customer count, region, country coverage, language coverage or industry breakdown is published, and there is no statement of who this is wrong for, which would be easy to write given how narrow and well understood the target appears to be.
Pricing
What this vendor charges, what it commits to in writing, and where the bill can move. Figures the vendor publishes itself are labeled Vendor Published. Figures labeled Estimated come from other sources and the vendor has not confirmed them.
- ›No price is published. What is published instead is a promise about the shape of it: custom pricing scaled to your team, no rigid tiers, and no per seat surprises. Plus a commitment to respond to a pricing request within one business day.
- ›That tells you one thing the price is not, and nothing about what it is. Useful, because for this kind of tool the people who need access include your solutions engineers, your sellers and sometimes the prospect's own people, and a per seat model charges for all of them.
- ›What occupies the space where the price would be is the security disclosure, and it is strong. Certification with its type level, European regulation compliance, annual outside penetration testing and continuous monitoring.
- ›That ordering makes sense for a product that gets reviewed by security before it gets reviewed by procurement.
- ›Ask what the meter actually is, and whether your prospect's people consume anything.
How the price works
What you are charged for, and what makes the bill go up.
Not published. The pricing page carries no currency figure in any currency, no tier name with a rate, no band, no starting point, no seat minimum and no contract length.
Two commitments about the pricing arrangement are published in place of figures. The vendor states that pricing is custom and scaled to the team, with no rigid tiers and no per seat surprises. Separately, the page description tag commits to responding to a pricing request within one business day.
The metering basis is otherwise unpublished. The absence of per seat charging is stated, which leaves per opportunity, per proof of value engagement, per solutions engineer, or an annual platform license as the plausible alternatives, none of which is confirmed.
Security and compliance are published on the pricing page: certification to the second type of the service organization control standard, compliance with the European regulation, annual third party penetration testing and continuous monitoring, all described as built in rather than gated.
Published capabilities cover proof of value planning, running and sharing across stakeholders.
No trial term, free tier or self serve route exists. No credible third party estimate was located, so none is recorded.
What the contract says about your data
What the vendor commits to in writing once your data is in the product.
The second strongest security disclosure on a pricing page in this index, after Map My Customers, and it is published where the price would be.
The vendor states certification to the second type of the service organization control standard and compliance with the European regulation, both described as built in rather than as tier entitlements, together with annual third party penetration testing and continuous monitoring.
Three of those are worth separating because they are different kinds of claim. The certification with its type level attests that controls operated over a period rather than existing at a point, which is the distinction a security function actually asks about. Annual third party penetration testing is a recurring external assessment rather than a one time certificate. And continuous monitoring is an operational claim about detection.
Publishing all three on a pricing page, from a vendor that publishes no price at all, is a deliberate ordering: this vendor has decided its security posture is the thing worth showing a buyer at the point of evaluation.
What was not established: a signable processing agreement, an enumerated sub processor list, a retention period expressed as a duration, and a residency statement. The claims are strong and a buyer should still request the report and the agreement.
The custody question follows from proof of value work, which means the platform holds material about live opportunities and the technical evaluation criteria of named prospects.
Getting started
What it costs and what is included before the product is running.
Not published. No setup fee, onboarding charge, migration rate, professional services rate, seat minimum, contract length, trial term or free tier was located.
The vendor publishes two commitments about the process rather than the price. Pricing is stated as custom and scaled to the team, with no rigid tiers and no per seat surprises. And a response to a pricing request is committed within one business day.
A buyer should treat the first as a constraint on the eventual quote rather than as information about it. Knowing the meter is not seats narrows the possibilities to per opportunity, per proof of value engagement, per solutions engineer, or an annual platform license banded by team size, and those produce materially different bills.
For a presales platform the metering question matters more than usual because of who needs access. Proof of value work involves the buyer's solutions engineers, their account executives, and frequently stakeholders at the prospect organization. A per seat model would charge for all of them; the vendor's statement suggests it does not, which if true removes the cost that most inflates presales tooling.
The implementation effort to model is process rather than configuration. A platform for planning and sharing proof of value work is only useful once a team adopts a consistent practice around it, which is a change management exercise inside the buyer's organization.
A buyer should ask what the meter is, whether prospect stakeholders consume anything, and what the minimum commitment is, in that order.
What to watch for
Where this pricing can surprise a buyer who has not read it closely.
No price, and an explicit commitment about the shape of pricing in its place, which is a different thing from silence.
The page publishes no currency figure anywhere. What it publishes instead is a statement that pricing is custom and scaled to the team, with no rigid tiers and no per seat surprises, and a commitment in the metadata to respond to a pricing request within one business day.
Those two elements distinguish this from the quote only vendors elsewhere in this index. Most publish a contact form and nothing else. This one makes two claims about the arrangement a buyer will be offered, and one about how quickly they will hear back.
The no per seat surprises phrasing is worth reading carefully rather than crediting outright. It signals that seats are not the meter, which for a presales platform matters because the people who need access, being solutions engineers, account executives and sometimes the prospect's own stakeholders, are a wider group than the sellers. But no per seat surprises is a promise about the absence of a charge rather than a statement of what the charge is, so a buyer learns one thing the price is not and nothing about what it is.
The one business day commitment is the more testable claim, and it is the second such undertaking recorded in this index after Alta's quote in hours rather than days. Both are competing on the interval between asking and receiving a number, which is itself a cost when a buyer is comparing several vendors.
The security disclosure occupying the pricing page is the notable structural choice. Certification with its type level, regulation compliance, annual third party testing and continuous monitoring are all published where the rate would be. For a product sold into technical evaluation processes that is a rational ordering, since the security review frequently precedes the commercial one.
The metering basis is unpublished alongside the rate, and for this category the plausible models are per opportunity, per proof of value, per solutions engineer, or an annual platform license.
No dollar figure is recorded in the numeric field and no estimate is recorded in the display field.