BoostUp

The forecasting engine is modelled and it is the reason the product exists. The vendor was founded in 2018 as a predictive platform extracting insight from unstructured data, and the components it names are machine forecasting, projections, deal and engagement risk scoring and activity matching, all of which are inference rather than aggregation.

Activity matching in particular is a probabilistic problem: deciding which email thread and which meeting belong to which opportunity across systems with no shared key cannot be done with rules at useful accuracy. Strip the models and what remains is the business intelligence module, meaning dashboards over revenue data the customer already had, which is a materially smaller product rather than the same one with a feature disabled.

Held below the top band because that business intelligence module is a substantial named part of what is sold and is conventional analytics, and because conversation intelligence was added natively only in 2025, so part of the current surface postdates the modelling core. Ask which capabilities stop working without the forecasting engine, and whether the business intelligence module is separately licensed.

An automation component is named and nothing describes what it may do. The platform includes an assistant marketed for automating tasks and improving productivity, and independent coverage describes a focus on agents that both analyse and act across the revenue lifecycle, which is the language of systems taking action rather than surfacing recommendations.

Nothing published states what those agents may change, whether they write into the customer record system, whether any approval precedes an action, what an administrator can constrain by role, or what halts activity in progress.

The exposure is bounded in one respect worth recording: the platform's outputs are forecasts, dashboards and risk scores consumed by revenue leaders rather than messages sent to buyers, so a wrong output misleads an internal decision rather than reaching a customer. That limits blast radius without describing controls. Ask what the automation component can change without approval, whether it writes to the customer record system, and what an administrator can disable.

The architecture is named at the component level and nothing beneath it is disclosed. The vendor identifies machine forecasting, projections, deal and engagement risk scoring and activity matching as distinct engine components, which is more granular than a generic assistant claim and tells a buyer where inference happens. Below that nothing appears: no model provider, family or version, no model card, and no evaluation of any component.

The accuracy gap is the material one and it compounds across the product, because activity matching feeds deal scoring which feeds the forecast, so an unmeasured error at the first stage propagates through every number a revenue leader acts on, and none of the three stages carries a published figure. Describing activity matching as best in class without publishing what class means is the specific instance. Ask which models power forecasting and risk scoring, and for measured accuracy at each stage from activity matching through to the forecast.

A forecasting vendor that publishes no forecast accuracy, which is the finding here. The product's central promise is calling the right number early in the quarter, and the supporting claims are superlatives rather than measurements: superior accuracy, best in class activity matching, the widest range of forecast use cases and the fastest time to value in the industry, none of them accompanied by a figure, a comparison basis or a study.

For a category where accuracy is measurable against realised outcomes every quarter, and where the customer's own historical data would supply the ground truth, the absence of any published measurement is conspicuous rather than ordinary. What is genuinely evidenced is the customer base, which is substantial and named across networking, database, data warehousing, education technology and automation software, and which corroborates that the platform operates at enterprise scale.

Independent coverage adds one operational caveat the vendor does not, that setup requires adjustment for complex revenue models. Ask for forecast accuracy measured against realised outcomes across a stated customer population and number of quarters, and for the activity matching accuracy rate.

The platform contacts nobody and ingests the correspondence of people who never agreed to it, which relocates this axis rather than removing it. There is no sequencer, dialer or campaign delivery, so consent capture, suppression and unsubscribe obligations sit entirely with the customer's own execution tools.

What the product does instead is capture email and meeting activity across the revenue team and match it to opportunities, which means the correspondence of external counterparties at customer and prospect organisations is ingested, analysed and surfaced to sales leadership.

Those individuals have a relationship with the seller, not with this vendor, and nothing published describes what notice reaches them, what content as opposed to metadata is retained, or how a counterparty would exercise any right over activity data held about them. That is the compliance surface this product actually has. Ask what activity capture retains about external counterparties, what notice reaches them, and how a counterparty could request deletion.

No privacy documentation was reached on the routes taken this pass. No privacy policy contents, processing agreement, subprocessor list, transfer mechanism, retention period or data protection officer was located, and no privacy certification is claimed in anything found. This records what a buyer could establish before contacting sales rather than asserting the documentation is absent, and a vendor with this customer base almost certainly maintains it behind a sales conversation.

The stakes are set by the corpus rather than by company size. The platform ingests the revenue team's email and calendar activity, matches it to named accounts and opportunities, and now records calls natively, which means it holds correspondence and conversations involving external individuals at customer and prospect organisations alongside performance data about the customer's own employees. Both categories carry obligations the public record does not address. Ask for the processing agreement, the subprocessor list, the retention period for captured activity and recordings, and the transfer mechanism for European data.

No external corpus is licensed and the provenance question is internal and unanswered. Everything the platform reasons over originates in the customer's own systems, whether the customer record platform, mail and calendar, connected conversation intelligence tools, product analytics or the customer's warehouse, so there is no purchased database, cooperative or third party feed to trace. The question that does apply concerns aggregation.

A forecasting engine improves with historical outcome data, and nothing published states whether patterns learned from one customer's closed deals inform the models or benchmarks serving another, whether any cross customer benchmarking exists, or what form it would take if it did. For a vendor whose accuracy claim is its principal differentiator, whether that accuracy is built partly on other customers' revenue histories is a question a buyer is entitled to ask. Ask whether outcome data from one customer contributes to models or benchmarks used for others, and in what form.

Integration runs through official routes across an unusually wide set of systems, and the vendor's posture toward its own competitors is the notable part. Named connections cover the major customer record platform, two conversation intelligence vendors it competes with directly, two sales engagement platforms, product analytics tools and the customer's own data warehouse.

Connecting to rival conversation intelligence products rather than requiring customers to abandon them is a low exposure architectural choice as well as a commercial one, because it means the platform consumes data through those vendors sanctioned interfaces instead of building its own capture against the same meeting platforms. Nothing resembling credential storage, scraping or unsanctioned automation appears in anything located.

Held below the top band because no stated conformance position against any specific platform's terms was found, and because the activity capture layer necessarily reads mail and calendar through grants those platforms control, with nothing published about the permission scopes requested or what happens if access narrows. Ask what permission scopes the mail and calendar capture requests, and whether any named platform conformance commitments exist.

A sensitive combined corpus and no stewardship position located. What accumulates here is the revenue team's correspondence and meetings with external parties, native call recordings since the conversation intelligence addition, complete opportunity and pipeline history, and derived risk and performance scoring about named individual representatives.

Nothing published states whether that material trains or tunes any model, which providers process it when the assistant or the scoring engine runs, what retention applies to recordings and captured activity, or whether anything crosses a tenant boundary. No artificial intelligence governance document, evaluation record or independently audited management standard was located.

The employee dimension deserves its own answer, since engagement and performance scoring about individuals feeds leadership dashboards and nothing describes what recourse a representative has to a score they consider wrong. Ask whether captured activity or recordings train any model, what retention applies, and what recourse exists against automated performance scoring.

Nothing generated by this platform reaches a buyer, and the people whose data it holds are not addressed. No message is composed for external delivery, no agent speaks to a customer and no content is authored for anyone outside the customer's organisation, so the authorship and impersonation questions this axis normally asks do not arise. What does arise concerns the external counterparty.

A person corresponding with a seller has their emails and meetings ingested and matched, their engagement scored, and their responsiveness reported to that seller's leadership, and since the native conversation intelligence addition their calls are recorded and analysed as well. Nothing published indicates they are told any of it happens or that a route exists for them to find out.

That is a disclosure gap about people rather than about generated content, and it is inherent to activity capture rather than incidental to it. Ask what notice reaches external participants whose correspondence and calls are captured, and how one would exercise rights over that data.

Genuine openness, including toward competitors, plus a warehouse connection that changes the shape of the integration. The platform ingests from the customer record system, two named conversation intelligence vendors, two sales engagement platforms and product analytics tools, and connects to the customer's own data warehouse so that revenue operations teams retain direct control over the underlying data rather than only seeing it through the vendor's interface.

That warehouse link is the substantive point: it means the analytical layer sits over data the customer can also reach independently, which is a materially different arrangement from a closed platform that holds the only copy. A flexible data model is described as accommodating revenue structures that opportunity centric tools cannot represent.

Held below the top band on verification rather than architecture: no developer documentation, interface reference, authentication model or rate limits were reached on this pass, and no integration inventory was counted. Ask for the interface documentation, the current connector list, and how the warehouse connection handles write back.

Cloud delivered with no residency answer published. No hosting provider or region is named, no European or United Kingdom residency election is described, no tenancy model is stated, and no recovery time or recovery point objective appears in anything located on this pass.

The one architectural detail that is described cuts in the buyer's favour and is worth recording: the platform connects to the customer's own data warehouse, so a portion of the analytical estate sits in infrastructure the customer controls and has already made residency decisions about. That does not answer where the vendor processes captured activity, recordings and derived scoring, which is the question.

The gap matters for a platform holding correspondence and call recordings involving identifiable individuals across whatever territories the customer sells into. Ask which regions captured activity and recordings are stored in, whether regional residency is available, what the tenancy model is, and what the recovery objectives are.

No certification, attestation or trust surface was reached on the routes taken this pass. No trust centre, service organisation control report, international information security certification, penetration testing statement, vulnerability disclosure route or enumerated control page was located.

This records what a buyer could establish before a sales conversation rather than asserting nothing is held, and a vendor selling to networking, database and data warehousing companies of this size would not clear their procurement without documentation, so it very likely exists behind a request.

One caution recorded rather than graded: at least two unrelated companies trade under closely similar names, including a Norwegian conversational artificial intelligence business and a coaching platform, and both publish detailed certification claims that surface readily against this vendor's name in search. Neither was used and neither belongs to this record. Ask which certifications and attestations are held, with audit periods and auditors, and whether a completed security questionnaire is available.

Sources disagree on whether a rate is published at all, and that conflict is itself the finding. Two software directories state a publicly listed starting price of roughly seventy nine dollars per user per month with a trial available, while a third states that cost is available only on request and varies by organisation type and need. Those cannot both describe the same surface.

The vendor's own pricing page was not reached on this pass, so this grade records an unresolved conflict rather than a verified position, and it sits mid band for that reason rather than lower. Directory listings in this category have proven unreliable elsewhere in this index, frequently propagating a single inferred figure across several sites, and two of the three sources here carry an unclaimed profile notice inviting the vendor to correct the listing, which is a signal that the vendor is not maintaining them.

Independent coverage separately notes that actual pricing depends on user count and which modules are deployed, meaning forecasting, business intelligence and conversation intelligence are licensed separately, so any single figure understates a full deployment regardless. Ask whether a published rate exists, what each module costs separately, and what the seat minimum is.

One architectural feature helps and the contractual terms are absent. The platform connects to the customer's own data warehouse and independent coverage describes that connection as giving revenue operations teams direct control over their revenue data, which means a meaningful part of the underlying material sits in infrastructure the customer already owns and would retain regardless. That is a genuine mitigation and unusual in this category.

What it does not cover is everything the platform adds: matched activity records, derived forecasts and projections, deal and engagement risk scores, conversation recordings and transcripts, and the configured multi dimensional forecast model itself, which independent coverage says takes setup effort to build for complex revenue structures.

Nothing published states whether any of that exports, in what format, what retention applies after termination, or what the deletion timeline and notice terms are. Ask what exports beyond the warehouse connection, specifically whether recordings, matched activity and forecast configuration are portable, and what the deletion timeline is.

The exposure this axis measures is architecturally absent rather than merely undocumented, and that distinction is the grade. The platform operates no sending infrastructure of any kind: no sequencer, no dialer, no campaign delivery, no mail relay and no advertising activation. It reads from the customer's systems and writes analysis back, and every outbound message a customer sends leaves through tools this vendor does not operate.

There is therefore no pooled sending estate where one customer's behaviour degrades another's delivery, no shared domain reputation to burn, and no warmup, rotation, bounce or complaint machinery that could be mishandled. A buyer asking whether this vendor's sending practices could damage their domain reputation gets a definitive answer rather than a documented process, and a definitive absence of risk is a better answer than a well described management of it.

Held below the top band because the platform does ingest and analyse email activity, so it sits adjacent to the sending estate even without operating one, and nothing published describes what it does with message content as distinct from metadata. Ask whether any notification or digest is delivered from vendor operated mail, and what message content the activity capture retains.

Coverage is stated on the dimension that actually matters for this product, which is revenue model rather than company size. The platform natively supports subscription, consumption and usage based, product led, renewal, expansion and advertising revenue streams in a single forecast, and independent reviewers consistently identify that as the reason to choose it over larger competitors whose opportunity centric models struggle with usage based or product led motions.

A buyer whose revenue arrives in more than one of those shapes can tell immediately whether this fits. The conventional dimensions are also stated: mid market through large enterprise, roughly one hundred to more than five thousand employees, named industries spanning technology, financial services, education, healthcare and telecommunications, and named buyer roles across revenue operations, sales leadership and analysis. The named customer base corroborates the enterprise end.

Held below the top band because the floor is not stated, no localisation was located, and independent coverage reports that complex revenue models require setup adjustment, which is a caveat attached to the very capability the vendor leads with. Ask what the smallest viable deployment is and what configuration effort a multi stream revenue model requires.