ProspectB2B

This is a conventional workflow product and it makes no artificial intelligence claim anywhere on any page read, which in the middle of 2026 is itself worth recording in an outbound category where almost every competitor leads with one. What is sold is structure: a daily queue, explicit ownership per record, staged pipeline movement, and cadences that fire on schedule.

The convention reserves the bottom band for a marketed claim that fails the removal test, not for a competent product that declines to make one, so a vendor with nothing to remove lands here rather than lower.

Oversight here is administrative rather than agentic and several of the right elements are named: audit trails held inside the lead record so status changes and next actions stay attached, role driven access, explicit ownership per lead and per stage, and change awareness described as keeping handoffs transparent. Against that, each is a phrase rather than a described mechanism.

No role is enumerated, no permission set is listed, no approval step is documented, and the cadence engine that sends email and text messages unattended carries no stated ceiling, throttle or review gate. The published operating discipline covering weekly reviews and monthly stale stage audits is a habit recommended to the buyer, not a control the platform enforces.

With no model capability marketed anywhere, there is nothing claimed to disclose and nothing is disclosed. That is a neutral position rather than a concealment, and it is graded in the middle on the same reasoning that governs the centrality row: a vendor making no claim is not hiding a model, it simply has not said it has one.

Worth flagging for re verification, because the product does run email and text message cadences and content assistance is the commonest place a claim of this kind appears later without a provider ever being named.

Three testimonials carry a role and a sector and nothing else, no name, no employer, no result, and the same three are printed twice on the homepage under two different headings. Beyond them there is not one named customer, logo, case study, customer count or quantified figure anywhere on the site. Six product screenshots are offered as the strongest evidence and each is captioned with the words real product screenshot, an insistence that is itself notable.

One thing belongs on the credit side: the vendor states plainly that it makes no guaranteed performance or outcome claim, so this is an absence of evidence rather than an invention of it, which is the distinction between this band and the one below. In its place the site offers an evaluation protocol, importing fifty to one hundred and fifty leads, assigning an owner and cadence, working the queue for a week and reviewing movement. That is a falsifiable test the buyer runs on themselves, which substitutes for evidence rather than supplying it.

For a vendor this size the position is unusually complete and it appears in two places. The terms of service require the customer to confirm a lawful basis to contact prospects and to store their data, to honour opt out and suppression requests promptly, and to follow applicable anti spam and privacy rules in their regions of operation, while the acceptable use section separately prohibits using the service to violate privacy rights or applicable consent requirements.

Alongside the contract, the about page publishes a working discipline that says the same thing operationally: remove or update any record with repeated bounces or opt out requests, and verify a record has an owner, a segment and a next step before it enters a cadence. A compliance position expressed as a workflow habit is rarer than one expressed as a clause.

Holding it off the top band, not one statute or regime is named anywhere, no suppression list or unsubscribe mechanic is documented inside the product for either sending channel, and the obligation is transferred to the buyer without the platform describing anything it enforces itself.

The privacy policy is a real policy rather than a generated gesture. It enumerates four lawful bases individually and says what each covers, being contract for processing needed to deliver the service, legitimate interests for operating and securing it, consent for marketing and optional cookies where required, and compliance for legal and regulatory obligations.

It states plainly that personal data is not sold, names the categories of service provider used for hosting, analytics, email delivery and customer support and limits them to processing for those services, scopes the product to business use, and publishes a request route with the subject line to use. A separate cookie policy sits beside it.

Holding it off the top band: no processing addendum is offered or referenced anywhere for a platform that processes the buyer's prospect records, no retention period is stated, no sub processor is named to go with the four categories, and no transfer mechanism is identified despite the site running a British locale alongside an American one.

The denial is emphatic and repeated, and the rest of the site does not support it. The frequently asked questions state that the vendor is not a lead list seller and is not a data provider, and the about page repeats it as a boundary offered to make evaluation easier.

Yet the single plan is priced by leads extracted per month, and the footer carries a companies directory, an industries hub and a United States research hub, sitting in a legal column alongside a data methodology page, a sources page, an update request route and a report an issue route. An update request route exists so that a person or company can ask for a record about them to be corrected, which presupposes records about them being held.

Whatever the denial is intended to mean, a buyer cannot reconcile it with the unit the product is billed in. Neither the methodology nor the sources page was opened and both are flagged, since either could resolve this in the vendor's favour.

The architecture is conservative and deserves crediting: nothing rents or rotates an identity, no browser extension is shipped, no professional network is touched, no evasion is advertised, and the acceptable use section prohibits probing systems, bypassing access controls and interfering with other users. Two exposures sit unaddressed.

The pricing unit is leads extracted per month and no page read states where extraction happens or from what source, so whatever obligations attach to that collection are undescribed. And the base plan includes one thousand text messages with further packages sold on top, at a vendor whose principal market operates a carrier registration regime for application to person messaging, with no position on it anywhere.

With no model in the product the sharpest version of this axis, the training question, does not arise. What remains is stewardship of the buyer's prospect records, and the security page answers part of it in terms many larger vendors avoid: data stays attached to the owning account and workspace, and sharing across teams is avoided unless it is explicitly part of the workflow. That is a cross tenant boundary stated rather than implied.

Against it, no retention period, deletion commitment, backup arrangement or encryption statement appears anywhere, and the privacy policy names analytics and email delivery among its service provider categories without identifying who performs either.

The platform sends email and text messages on the buyer's behalf to business contacts who did not ask to be approached, and nothing published describes an unsubscribe mechanic inside the sending product, a sender identification requirement, a physical address requirement, or any route by which a recipient rather than a customer can act.

The counterweight is real and it is contractual: the terms require the customer to honour opt out and suppression requests promptly, and the published operating discipline instructs removal of any record showing repeated bounces or opt out requests. So the obligation is stated even though the mechanism is never shown. There is no synthetic content to mark, since the product claims none, which removes the artificial authorship question entirely.

Open interfaces are claimed, three named automation platforms are supported, comma separated import and export work in both directions, and an integrations and partnerships page exists. Everything that would make the claim checkable is missing: no developer documentation, no reference, no authentication description, no webhook list, no marketplace, and no listing in any partner directory. The sharpest gap is structural rather than technical.

The entire positioning rests on sitting in front of the buyer's existing system of record so that the system of record stays clean, and not one such system is named anywhere as an integration. A product sold as the execution layer for your system of record does not say which ones it connects to.

Hosting provider, country, region and residency option are absent from every page read, including the security page where such a statement would normally sit, and the privacy policy names hosting as a service provider category without identifying the provider or its location. Two published facts frame the gap rather than filling it. A street address is given in Orlando, Florida, though the suite line reads Office 12345, which has the shape of a placeholder that was never replaced. And the site serves two locales, one American and one British, so a vendor addressing buyers on both sides of a transfer boundary answers the transfer question nowhere.

A dedicated security page exists and contains one sentence rarer than any badge: the vendor says it keeps security guidance clear and practical without overstating compliance claims, which acknowledges holding none rather than implying it might. Around it sits a genuine narrative.

Sessions are scoped to the minimum required, unusual access patterns are monitored, data stays attached to the owning account and workspace, access is role driven, a responsible disclosure route is published with an address and a request for reproduction steps and supporting evidence, and the vendor commits to communicating directly with affected users and summarising remediation if a material issue occurs.

Holding it here rather than higher, every item is a posture rather than a verifiable control, and there is no certification, audit, attestation, penetration test, encryption statement, authentication requirement, backup arrangement or status page, with a security review available only on request.

One plan scaling by lead volume, with a worked public example: one thousand leads extracted per month at seventy seven dollars and sixty cents a month on annual billing, or nine hundred and thirty one dollars and twenty cents for the year, and the arithmetic reconciles exactly. The annual discount is stated at twenty percent, which makes the monthly equivalent derivable rather than hidden.

What is included is enumerated, being email workflows and one thousand text messages, with further text message packages sold as one off additions and tax noted as possibly applying. A seven day trial is offered. Holding it off the top band, and the gap matters more here than it would elsewhere because the plan is priced by volume: exactly one point on that volume curve is published, so a buyer running five thousand leads a month cannot compute their own bill. The additional message packages carry no price, and trial access is by request with the guidance appearing only once signup has begun.

Export is treated as a property of the product rather than a concession extracted from a contract, and it is stated in four separate places. Structured, exportable data appears as one of three headline attributes on the homepage, comma separated import and export are both confirmed in the frequently asked questions, keeping pipeline data structured and exportable for downstream reporting is named as one of the three outcomes the product is sold on, and the terms confirm the customer controls how their data is collected, used and shared.

Holding it off the top band: no post termination retention period, deletion timeline or data return commitment appears in the terms as read, and no export format beyond comma separated values is named. One structural point belongs on this row and it is not small. The terms of service does not identify the contracting entity at all, saying instead that company details are available on request, so a buyer signing this agreement cannot know from the document who is on the other side of it.

The product runs email workflows and includes one thousand text messages in the base plan, and publishes no warmup, ramp schedule, daily ceiling, throttle, authentication requirement, complaint threshold, bounce threshold or reputation monitoring anywhere. Two items sit on the credit side and both are workflow habits rather than infrastructure.

The published operating discipline instructs removing or updating any record with repeated bounces or opt out requests, and the review loop tells a team to validate the list before blaming the copy when a segment stops responding, which is list hygiene stated as a practice. One unanswered question decides the whole axis and is asked nowhere on the site: whether sending runs through the customer's own mailbox or the vendor's infrastructure, which determines who carries the reputation risk.

The vendor publishes a boundary statement of the kind this index rewards and it is unusually direct, running to four negatives: it does not sell lead lists, it does not position itself as a data provider, it is not a replacement for every use of a system of record, and it claims no guaranteed performance or outcome. A fit statement sits beside it, saying the product suits teams needing outbound workflow clarity more than heavy customisation.

Six buyer types are named on the homepage and a longer list of eight in the questions, spanning sales development, founders selling directly, sales leads, agencies, consultants, outbound operations, revenue operations and lean prospecting teams, with recruiting and partnerships added separately. A segments page and two locales support it.

Holding it off the top band: no customer count, seat band, headcount range, language coverage or industry data appears anywhere, the region claim extends no further than the two locales, and not one customer is named in any sector.