ReachRobin

The model's role is drafting: every outreach message is described as personalized by a model using prospect profile data, company signals and the customer's playbook, and reply scoring is claimed for qualification. Apply the removal test and the platform remains substantially intact, since multichannel sequencing across the professional network, mail and the messaging service, rate aware sending caps, lead search and enrichment, and synchronisation to a system of record are all conventional machinery. What is lost is the first draft and the reply score. The claim is central to the marketing and not to the architecture.

Automation runs connection requests, messages and follow ups across three channels, and the only governors described are volume caps: roughly one hundred network connections per week, eighty enrichment actions per day and eighty mail sends per address per day, enforced per account automatically. Those are throughput controls rather than oversight.

No approval step, review queue, role model, permission set, escalation rule or audit record is described anywhere, and nothing states whether a person reads a drafted message before it goes out or whether sequences run start to finish untouched.

The drafting inputs are named plainly, prospect profile data, company signals and the customer's own playbook, which is more than some vendors state. No provider, model, family, version or hosting arrangement appears anywhere, no accuracy or evaluation is published for the reply scoring claimed to qualify opportunities, and the roadmap language of nine features live and three coming does not identify which capabilities are model dependent.

No customer is named anywhere, and no testimonial, case study, logo or quantified result appears on any page read. The evidence surface that does exist is six reciprocal launch directory badges repeated in the footer of every page, a link to a reviews listing on a software hosting directory, and a review platform verification tag in the page metadata with no reviews displayed. A team page naming four people with roles is the most concrete fact published. Nothing here is fabricated, which keeps it off the floor, but nothing is evidenced either.

The product sends cold outreach at volume across mail, the professional network and the messaging service, and no statute, regime, consent position, suppression mechanism, unsubscribe handling or sender identification requirement is stated anywhere on the pages read. The published sending caps are deliverability discipline rather than a compliance posture. The messaging channel raises the sharpest version of the question, since business initiated messaging there is consent gated under that platform's own rules, and nothing addresses it.

The privacy policy route exists, is linked from the signup flow, and serves no policy text at all to a fetcher: the page body contains only the site's badge strip, and the route is marked not to be indexed. Every marketing page on the same site serves its full content to the same fetcher, so the emptiness is specific to the legal documents.

Beyond that, no operating entity, address or jurisdiction is published, no retention period or processing addendum appears, and the platform necessarily processes prospect personal data across three channels plus whatever the enrichment lookups return.

The vendor sells contact discovery and enrichment, with verified mail addresses, phone numbers and firmographic data delivered against per unit credits, and no source, database, partner, collection method, coverage figure, refresh cadence or accuracy claim is published for any of it.

The pricing page prices the lookups precisely, twenty five cents for a network enrichment, ten cents for a mail address and twenty cents for a phone number, and says nothing about where any of the answers come from.

Automation of connection requests, messages and inbox mail on the professional network is the core product, the network prohibits automation of exactly those actions, and no conformance position, execution method or account model is stated. Two things keep this in the middle band rather than the bottom.

The caps are published and conservative, roughly one hundred connections per week per account with a four hundred invitation monthly ceiling on enrichment credits, and the framing throughout is keeping accounts safe rather than evading detection, with no rotation or multi account scaling sold anywhere. The messaging channel adds a second exposure, since nothing states whether sends run through that platform's sanctioned business interface or an unofficial route.

The model reads prospect profile data, company signals and the customer's uploaded playbook to draft every message, and reads reply content to score it. Nothing published addresses retention, training use, isolation between customers or where inference runs. The two legal routes where an answer would live serve no document body to a fetcher.

Messages are drafted by a model and sent under the customer's name across three channels, with the stated design goal that messages feel hand written at any volume. That sentence is the axis inverted, since the recipient's inability to tell is the marketed quality bar. No position on the European marking obligation appears, no unsubscribe or opt out mechanic is described for any channel, and nothing marks any message as automated. Held in the middle band because the phrase markets personalization quality rather than celebrating detection evasion.

System of record synchronisation is claimed as a headline capability and not one system of record is named on any page read. No integrations page, marketplace, developer documentation, programmatic interface or webhook surface was located. The application signup offers identity through the two major business providers, which is a sign in mechanic rather than an integration. For a product selling itself as one workspace from first lead to closed deal, the connective surface is asserted in a single sentence.

Hosting provider, country, region and residency options are absent from every page read, and no security page or trust centre exists where a statement would sit. The corporate identity is absent too, with no entity name, registered address or jurisdiction anywhere, so a buyer cannot establish which law governs the platform holding their prospect data and channel credentials.

The product operates customers' accounts on three channels, placing connection requests and messages on the professional network, sending mail at a published eighty sends per address per day, and running follow ups on the messaging service, all by unstated methods. That is the most sensitive access class this index grades.

Against it, no certification, audit, attestation, control set, encryption statement, trust centre, status page or vulnerability disclosure route was located anywhere on the site, and the two legal routes serve no document body to a fetcher. The precedent from the first session holds: operating a customer's channel accounts with no documented security surface at all is the bottom band.

The most complete pricing disclosure a vendor this size has produced in this index. One plan with three per seat workloads, each priced: eighty nine dollars per seat monthly for all channel, one hundred fifty nine for the high volume workload, one hundred twenty nine for the network only workload, with every allowance published as a number flowing into a shared monthly pool. The annual benefit is stated concretely as two months free.

The team discount schedule is published as exact percentages at exact seat bands, five percent from three seats, seven from six, ten from ten and fifteen at twenty and above, which almost no vendor at any size prints. Overage is priced per unit for every credit type, and the per account sending caps that govern real throughput are printed on the same page. There is no quote only tier and no unpriced add on anywhere. A buyer can compute their exact bill including growth and overage before any conversation.

No export function, format, path, post termination right, deletion commitment or retention period appears on any page read. System of record synchronisation, the one mechanism that would move records outward by default, names no system and describes no direction of flow. The terms of service route bound at signup serves no document body to a fetcher, so the contractual half cannot be read either.

Sending discipline is the product's central claim and it is published in numbers where a buyer sees them: rate aware sending is the headline, and the pricing page prints the per account caps, roughly one hundred network connections per week, eighty enrichment actions per day and eighty mail sends per address per day, with the explicit framing that caps protect accounts while the pooled allowance covers monthly volume.

Eighty sends per address per day is genuinely conservative for the category, and separating the safety cap from the commercial allowance is a design decision most competitors avoid stating. Holding it off the top band, nothing addresses warmup, authentication records, bounce handling, complaint monitoring or degradation response, and the sending infrastructure for mail is never described.

The buyer is named as founders, sellers and agencies, and the three workload structure sketches a light segmentation between full stack representatives, heavy senders and network only teams. Beyond that, no customer count, region, country, industry, language coverage or seat band appears, and nothing says who the product is wrong for. The messaging channel implies markets where that channel dominates business communication, and no page says so.