Salesvue

The product operates without any artificial intelligence capability, and the vendor claims none.

Three surfaces were examined: the marketing site, the published FAQ and the marketplace listing. Across all three the described mechanism is deterministic. A cadence is a fixed sequence of activities with the timing removed as a variable. Branching is rule based, routing a prospect into a different sequence according to the outcome a seller logs on the previous step. Email and lead scoring is offered as an alternative to the customer's own marketing automation scoring, with no model claim behind it. Reporting correlates activity data against conversion using Salesforce reporting.

The context makes the absence look deliberate rather than an oversight. The marketplace listing sits on a platform that in 2026 promotes agent solutions on every page, and the listing's own highlights section, nine bullets long, mentions nothing of the kind.

That is a coherent position for a workflow layer, and it is graded here for what the axis measures rather than for whether the choice is wise. A buyer comparing this to the rest of the category is buying process discipline, not inference.

Ask whether any model capability is planned, and on what timeline.

Autonomy is low by design and the oversight story has one hole, in the place where the automation actually runs.

The seller does the work. Cadences produce a prioritised task list, a person completes each task, a person dials the phone, and branching only advances after a human logs an outcome. Nothing in the product acts on a prospect unattended except email.

Administrative control is described more concretely than most vendors in this index manage. A named permission set delegates cadence creation to sales managers, operations and enablement rather than requiring a Salesforce administrator, and the FAQ states that setting a sequence of activities is limited to users with permissions. Because the application is a managed package inside the customer's org, the customer's existing Salesforce sharing model, field level security and audit trail apply to the records.

The hole is that the vendor states its workflow engine is implemented outside Salesforce. That is the component executing automation on a schedule, and it therefore sits outside the permission and audit model the rest of the answer relies on. Two passes located no description of who administers it, what it logs, or whether an automated send can be held for approval.

Ask what the external workflow engine logs, and who can see that log.

Abstention is the disclosure here, and it is clean.

The vendor markets no artificial intelligence capability on any of the three surfaces examined, which means there is no unnamed model, no undisclosed provider, no agent of ambiguous authorship and no claim a buyer has to discount. In an index where vendor after vendor has marketed copilots, agents and generation while declining to name what produces any of it, a record with nothing to disclose is a materially different buying position, and the axis should say so plainly rather than treat silence and evasion as the same thing.

The restraint reads as deliberate. The marketplace listing was written for a 2026 audience on a platform actively promoting agent solutions, and it still sells cadences, task lists and reporting.

What holds this below the top band is that the vendor never states the position affirmatively. A buyer running an artificial intelligence governance review finds no page saying the product uses no models, no statement on whether customer content is ever processed by a third party, and no explanation of what the externally hosted workflow engine does with what passes through it. Absence of a claim is inferred from three surfaces rather than confirmed by one sentence.

Ask for a written statement that no model processes customer content, covering the external workflow engine.

The review base is the substance here, and it is larger and better sited than most in this index.

The marketplace listing carries 4.77 across 120 reviews, published on the platform the product runs inside rather than on a page the vendor controls. Secondary directories corroborate at lower volume, including a rating near 4.3 on a profile the vendor has not claimed, which is worth noting because an unclaimed profile is one the vendor has not curated.

Customer naming is unusually concrete for a company this size. John Hancock, Bloomberg Industry Group and Global Atlantic Financial Group appear on the vendor's own channels, and an independent company profile adds Nationwide. The listing claims use by five of the top ten annuity providers, which is a checkable class of claim even though the members are not named.

Homepage testimonials carry a full name and a job title in three of four cases, including an assistant vice president of internal sales and a director of inside sales.

Quantification is where this stops short of the top band. One testimonial claims a ninefold productivity gain in prospecting with nothing behind it, and two passes located no case study, no customer count and no methodology anywhere.

Ask for one named customer's follow up timeliness and conversion figures before and after deployment.

Two sending channels operate at scale with no compliance surface published behind either.

The product sends automated and bulk email, and the FAQ answers a question about sending volume by stating there are no daily limits. A dialer places calls from inside the same interface. Together that is outbound email and outbound telephony aimed at prospects.

Two passes located no privacy policy, no terms of service, no acceptable use policy and no compliance page on the vendor's own domain. That absence carries through to every specific a buyer would check: no unsubscribe handling or propagation across cadences, no suppression list, no screening against do not call registers, no calling hour restriction, no consent basis described for contacting a prospect placed into a cadence, and no jurisdictional guidance for any market despite telephony being one of the two channels.

One structural mitigation is real and should be stated. Because records live in the customer's Salesforce org, whatever consent flags, opt out fields and suppression logic the customer already maintains in Salesforce remain available to gate a cadence. That is the customer's control rather than the vendor's, and the vendor does not describe how a cadence honours it.

Ask how a cadence honours a Salesforce opt out flag, and what stops a dialer task on a registered number.

The architecture is genuinely privacy relevant and the documentation behind it is absent.

The strongest fact is structural: as a native managed package the product stores customer records in the customer's own Salesforce org, so the vendor does not maintain a second copy of the prospect data. A vendor that holds less is exposed to less, and that is a better answer than most policies.

Against that, two passes located no privacy policy, no data processing agreement, no list of the suppliers it relies on, no retention or deletion statement, no rights request process and no reference to any privacy regime on the vendor's own domain. The marketing assurances that stand in their place are absolute and unsupported: that data is always protected, and that the product will never cause data to be corrupted.

The hedge in the FAQ is the sharp detail. The vendor states that its workflow engine is implemented outside Salesforce, and that at no time does protected information need to be sent outside the customer's Salesforce account. A statement that data need not leave is not a statement that it does not leave, and the sentence stops exactly where a buyer's question begins.

Ask what data the external workflow engine receives, where it is held and for how long.

The vendor supplies no data, and that is the finding rather than a gap in one.

The product is a workflow and reporting layer over records the customer already owns in Salesforce. Two passes located no contact database, no enrichment offering, no email or mobile lookup, no credit model, no profile count and no waterfall of upstream suppliers. There is nothing here sourced from anywhere, so there is no provenance question to answer and no unlicensed pool for a buyer to inherit.

In a category where the standard package pairs outbound automation with a database of tens or hundreds of millions of records whose origin is never disclosed, a buyer should register that this vendor exposes them to none of that. The records a cadence works are the ones the customer put in Salesforce, under whatever basis the customer holds them.

What keeps this below the top band is that the vendor never says so. The position has to be inferred from the absence of any data claim across three surfaces rather than read from a statement, and the partnership with a contact data provider that routes records into Salesforce for cadencing is described on the partner's site rather than governed by anything the vendor publishes.

Ask whether any data reaches the product from a source other than the customer's own Salesforce org.

Every surface this product touches is one it is licensed to touch, and the licensing is verifiable by a third party rather than asserted.

Distribution runs through the Salesforce marketplace under the published partner programme agreement, and the vendor states the application passed the platform's 60 day security review. That review is a real gate with a published standard, applied by the platform owner, not a badge the vendor issued itself. The application is a managed package installed by the customer into their own org, so it operates inside the platform's supported extension model rather than around it.

Email sending goes through the seller's own Outlook or Google mailbox using the sanctioned integrations for each.

Two passes located no scraping, no browser extension driving a site the vendor does not own, no automation of a social network, no unofficial interface use and no capability whose operation would depend on a platform not noticing. In a category where a large share of records carry exactly those exposures, this one carries none.

The trade is concentration rather than violation. Total dependence on one platform means the platform's roadmap is the vendor's risk, and the platform now ships competing engagement and agent functionality of its own.

Ask what the vendor's position is if the platform's native engagement product absorbs the cadence layer.

Half of this axis is inapplicable and the half that applies rests on architecture rather than commitment.

There is no model in the product, so there is no generated output to govern, no hallucination surface, no training use of customer content, no evaluation to publish and no human review step to design. That side of the axis carries no risk because it carries no capability, and a buyer should read the grade accordingly rather than as a judgement on model handling.

Stewardship is where the record is thin. The one substantive commitment is architectural: records stay in the customer's Salesforce org, so the customer retains custody of the material that matters and the vendor is not a second holder of it. That is worth real credit, and it does more for a buyer than most published policies in this index.

Everything around it is undescribed. Two passes located no retention schedule, no deletion commitment, no incident response or breach notification process, no security contact, no vulnerability disclosure route and no statement covering whatever transits the externally hosted workflow engine. A vendor holding less still owes an account of what it does hold.

Ask for the breach notification commitment and the retention schedule for anything held outside the customer's org.

A prospect contacted through this product is contacted by a person, and the product does not pretend otherwise.

Individual email is sent through the seller's own Outlook or Google mailbox, so the address on the message belongs to the human whose name is on it. Calls are placed by a seller working a task list, not by a synthetic voice. Nothing in the product generates a message, adopts a persona, replies on a seller's behalf or continues a conversation after the prospect answers.

The contrast with the current cohort is the point. Several records in this sweep market undetectability as a purchasable property, one of them in the vendor's own words. This vendor sells the opposite arrangement: a seller who knows what they are sending because they are the one sending it, and a recipient whose reply reaches a person.

Bulk send is where the framing loosens. A bulk send is not an individual message however it is addressed, and two passes located no requirement or guidance on sender identification, physical address in the footer, or how a bulk message is distinguished from a personal one to the person receiving it.

Ask what a bulk send includes by default in the footer, and whether that is enforced or left to the sender.

The reachable surface is very large and almost none of it belongs to the vendor.

What the vendor owns is one integration: Salesforce, at maximum depth. The application supports Sales Cloud, Service Cloud and Financial Services Cloud, Classic and Lightning, the mobile app, and the Professional, Enterprise and Unlimited editions. Sending connects to Outlook and Google. Marketing automation interoperability is named specifically for Marketo, HubSpot and Pardot, including handing scoring to whichever the customer already runs. Third party directories add a document and forms platform and a sales content platform, and a contact data provider publishes its own integration.

Everything beyond that is inherited. The vendor's claim of thousands of available integrations is accurate in substance, since anything already connected to a customer's Salesforce org is reachable by data that never leaves it, and for a Salesforce shop that is a genuine architectural advantage rather than a marketing dodge.

What the vendor does not have is any developer surface of its own. Two passes located no documented interface, no authentication scheme, no rate limits, no webhooks, no command line tooling, no model context protocol server and no developer documentation. For a buyer not standardised on Salesforce, the integration story is empty.

Ask whether cadence and outcome data is reachable programmatically outside Salesforce reporting.

The deployment model is stated more precisely than most records in this index manage, and the residency answer follows from it.

The application is a native managed package installed into the customer's own Salesforce org. The vendor is specific about the consequences: no synchronisation to configure, no import or export, no data mapping, and installation stated at 45 minutes with a Salesforce administrator helpful but not required. Supported editions are enumerated rather than implied, covering Professional, Enterprise and Unlimited, with Lightning and console applications.

Residency inherits cleanly. Customer records sit wherever that org sits, which is a location the customer already selected, already knows and already governs under their own agreement with the platform. For a buyer with a residency requirement, that is a stronger answer than a vendor listing its own regions, because it removes a party from the chain rather than describing one.

The ceiling is the component the vendor mentions once and never returns to. Its workflow engine is implemented outside Salesforce, and two passes located no hosting provider, no region, no architecture description and no statement of what transits it. Residency is therefore precisely known for the data at rest and entirely unknown for the layer that automates it.

Ask where the workflow engine runs and whether its region can be pinned to match the org.

The vendor describes its attestation more accurately than the directories describing it, and then publishes nothing else.

The homepage states passage of a SOC 2 Type 1 audit and enumerates all five trust services categories examined: security, availability, processing integrity, confidentiality and privacy. Naming the type rather than claiming SOC 2 in the abstract is honest, and it matters, because a Type 1 is an opinion on control design at a point in time rather than on operating effectiveness across a period. Several directory profiles flatten this to certified, and the marketplace listing softens it to compliance, both of which overstate what was actually issued. The vendor's own copy is the most precise version in circulation.

A second credential is the platform's 60 day security review, which the application passed as a condition of marketplace listing.

What is absent is everything that would let a buyer act on either. Two passes located no audit date, no auditor named, no renewal or annual cadence, no report request process, no trust portal, no penetration test, no ISO certification, no encryption or access control detail and no list of the suppliers involved.

Ask for the audit date, the auditor, and whether a Type 2 is scheduled.

A published list rate exists, and it is not on the vendor's website.

The marketplace listing publishes 149 dollars per user per month for one to nine users, and states that volume discounts begin at ten users and tier upward to 2500 and beyond. That is a real anchor: a buyer knows the starting rate, the unit, and the seat count at which the curve begins to bend.

The FAQ supplies the commercial shape around it, which is the part most vendors in this index withhold. Agreements are annual. The annual fee includes the software licence, training, implementation assistance and support, so onboarding is not a separate line. Licences can be added mid term. Two priced user classes are named, power users and administrative users, so the buyer knows the pricing dimension before the call. And the vendor discloses the exception rather than burying it, stating that customisation and some configurations may incur additional fees.

Three things keep this out of the top band. The discount curve itself is unpublished, the administrative user rate is never given, and the vendor's own site carries no pricing page at all, so a buyer who does not think to check the marketplace listing sees a demo request and nothing else. A procurement marketplace showing a proposed figure near 10,960 dollars suggests negotiated contracts land well away from list.

Ask for the administrative user rate and the discount schedule at the buyer's seat count.

Portability is largely solved before it is asked, because the vendor never takes custody in the first place.

Customer records live in the customer's own Salesforce org throughout. The vendor states the consequence directly and repeatedly: no importing or exporting, no synchronisation, and information that never leaves the Salesforce ecosystem. A customer that stops paying does not have to retrieve anything, wait on an export queue, accept a delivery format or trust a deletion promise, because the accounts, contacts, leads, opportunities and activity history were never anywhere else. That is a materially better position than an export button, and it is the strongest thing about this record.

The edge that is never described is what happens to the vendor's own objects. A managed package brings custom objects and fields, and cadence membership, step outcomes and the engagement history that feeds the reporting live in them. Uninstalling a managed package typically removes or orphans exactly that layer, which means the analytics the product is sold on may be the one thing a departing customer cannot keep. Two passes located no uninstall procedure, no statement on custom object retention and no deletion commitment covering the externally hosted workflow engine.

Ask what happens to cadence history and step outcomes when the package is uninstalled.

The absence of sending limits is marketed as a benefit, on two separate surfaces, in the vendor's own words.

The FAQ answers a question about email volume by confirming there are no daily limits either. The marketplace listing describes the email tooling as built in bulk send with no limit. Neither is a footnote a buyer has to dig for; both are selling points positioned where a buyer will see them.

Around that claim there is no discipline described at all. Two passes located no warmup, no throttling or send rate control, no domain reputation guidance, no authentication guidance covering sender policy, key signing or reporting records, no bounce handling policy, no list hygiene or verification step, no seed testing and no deliverability reporting beyond raw delivery, open and click tracking. Tracking whether a message arrived is not managing whether the next thousand will.

The practical reading is that the claim will not survive contact with the infrastructure. Sending routes through the seller's own Outlook or Google mailbox, and those providers enforce their own limits and reputation rules regardless of what the application permits. So the ceiling exists, the vendor simply is not the one setting it, and the reputation consequences accrue to the customer's sending domain.

Ask what the actual per mailbox send ceiling is once the mail provider's limits apply.

The target is named at three levels, and one of them is a genuine concentration rather than a list.

Industry is stated on the marketplace listing as financial services, professional services and public sector. Financial services is clearly the centre of gravity, and the evidence goes past a landing page: a dedicated practice covering internal and external sellers, an annual customer summit run for that industry, a claim of use by five of the top ten annuity providers, and named customers in insurance, annuities and asset management.

The prerequisite is stated plainly, which matters more here than category labels. The buyer must already run Salesforce, on Professional, Enterprise or Unlimited edition. That single sentence disqualifies a large share of the market honestly and early, rather than letting a prospect reach a demo before discovering it.

Company size is bounded by the pricing structure, which runs from a single user to tiers above 2500, so the product does not claim to be only enterprise or only small team.

Geography is the omission. Two passes located no region statement, no international presence, no localisation, no currency other than dollars and no non United States customer. Everything about the record reads as domestic without ever saying so.

Ask whether the product is sold and supported outside the United States.