Reachmigo

Two model capabilities are marketed and both sit on top of the platform rather than under it: classification of every inbound reply into five named categories, and generation of a draft response for the operator to approve. Apply the removal test and the product remains substantially intact, since delegated mailbox authorisation, sequence building, automatic warmup, address validation, daily caps, timezone aware sending, authentication checking, tracking, analytics and two way system of record synchronisation are all conventional.

What is lost is the sorting of the inbox and the first draft of the answer. The vendor's own comparison table makes the same point unintentionally, listing classification and drafting as the two rows where it differs from three named competitors while matching them on everything structural.

The control surface is described more concretely than most vendors of any size manage. Sending rules cover a daily cap, a timezone aware sending window, and batch size, and the vendor states all three are enforced automatically rather than offered as guidance. A campaign pauses itself when open rate falls. Opt outs are actioned immediately on classification. And drafted replies are explicitly presented for approval rather than sent, so a person reads the words that go out under their name.

Holding it off the top band, no role model, permission set or audit record appears anywhere, and one failure mode goes entirely unaddressed: the classifier decides which inbound messages are unsubscribes, that decision has legal consequences, and nothing describes review, correction or what happens when it labels one wrongly. Every control listed is also visible only inside interface illustrations rather than in documentation.

Classification into five named categories and generation of draft replies are the two marketed capabilities, and no provider, model, family, version or hosting arrangement is named for either. No accuracy figure, confidence measure or evaluation is published for the classifier, which matters more here than in most builds because one of its five output labels is unsubscribe, and a wrong label on that category is a compliance failure rather than an inconvenience.

The evidence and the commercial stage contradict each other on the same page, repeatedly. The pricing section's entry tier is literally named waitlist, with the action reading request access, and the tier above it is a founding member rate whose pitch is to lock in pricing before the product goes public. A banner offers founding member places limited to fifty teams. The hero of the same page states that more than fifty business sales teams already trust the product.

Fifty places cannot be open while fifty teams are already aboard. Three testimonials then describe completed usage, including replacing three separate tools and a reply rate rising from eleven to eighteen percent over a first month, attributed to initials and a company description rather than a name. Two external ratings appear as unlinked badges, one claiming a four point nine score from forty eight reviews on a named review platform and one claiming a first place ranking on another.

And every figure inside the interface illustrations is invented, with fictional contacts attached to five real and well known technology companies shown as leads and as replies. The eighteen point four percent reply rate shown inside that mock dashboard is then reproduced in the numbers band as the product's average against an eight percent industry figure. The banner's own deadline had passed a week before this reading and was still displayed.

The compliance behaviour here is mechanised rather than declared, which is the harder and more useful version. Unsubscribe is one of five reply categories, opt outs are stated to be actioned immediately on classification, and they synchronise onward into the customer's system of record automatically, so a suppression does not stay trapped in one tool.

Every lead address is validated through a named third party service before any send, with a default bounce ceiling published at under two percent, which is list hygiene enforced by default rather than left to the operator. The sequence preview includes a footer toggle, implying a compliance footer exists on the message.

Holding it off the top band, no statute, regime or regulator is named anywhere, no consent standard is stated for the cold lists the product is built to work, no persistent suppression list across campaigns is described, and no sender identification or physical address requirement is mentioned.

A privacy policy and terms of service exist at their own routes and neither was opened, so this row rests on the surrounding surface and is flagged. One disclosure on the page is genuinely customer favouring and worth crediting: authorisation to the mailbox runs through delegated tokens and the vendor states plainly that those tokens can be revoked at any time from the customer's own provider settings, which puts the off switch outside the vendor's control.

Against that, no operating entity, corporate address or jurisdiction is published anywhere on the site, no retention period, processing addendum or residency statement appears, and a named third party validation service receives every lead address the customer uploads, which makes it a sub processor disclosed by marketing copy rather than by any policy.

The vendor sells no contact data and compiles no database. Leads arrive by comma separated upload or by import from a named data platform the customer already subscribes to, and duplicates are removed and timezones inferred on the way in. The only outward data operation is address validation through a named partner, which reads what the customer supplied rather than sourcing anything new.

Graded in the middle because the clean position follows from the business model rather than from any stated provenance policy, and because the imported records carry whatever licence terms the upstream data platform imposed, which nothing here addresses.

The two channels are handled to completely different standards and the asymmetry is the note. Email is exemplary: delegated authorisation with both major business mail providers, no stored passwords and no mail protocol credentials, sending from the customer's own mailbox, and revocation available from the customer's own provider settings. That is the sanctioned route used properly. The professional network side is the exposure and it is not described at all.

Sequences include connection requests and messages on that network, the network prohibits automation of exactly those actions, and no page read says how they execute, whether through an extension, a server side session or anything else, and takes no conformance position of any kind. One channel is done right and the other is unaddressed.

Nothing published addresses retention, training, isolation between customers or where inference runs, at a platform whose core capability is reading the full text of every inbound reply and generating a response from it. The material at stake is other people's messages, written by prospects who have no relationship with this vendor. The privacy policy was not opened and is flagged as the only plausible home of an answer.

Cold email and network connection requests go out under a named human sender with nothing marking them as automated, and replies to inbound messages are drafted by a model, with no position taken on the European marking obligation anywhere. Two mitigations are real and structural rather than promised. Drafted replies are presented for approval, so a person reads and sends the words attributed to them.

And unsubscribe is a first class classification actioned immediately and pushed into the customer's system of record, so a recipient who writes remove me in ordinary prose is suppressed everywhere rather than only in one tool, which is the single most useful thing an outbound product can do for the person receiving it.

Six integrations are named individually and each does identifiable work: two major mail providers by delegated authorisation, a professional network, a system of record with two way synchronisation that carries interested replies, new leads and opt outs in both directions, a data platform for lead import, and a transactional mail service. A webhook interface and comma separated export are both listed as capabilities alongside that synchronisation.

Two way movement of suppression state in particular is a connection most vendors do not build. Holding it off the top band, none of it is documented: no reference, developer hub, marketplace, authentication description or protocol server exists, and the programmatic surface appears as a tick on a feature list rather than as anything a developer could build against.

Hosting provider, country, region, data centre and residency option are absent from every page read, and no security page or trust centre exists where such a statement would sit. The gap is wider than usual because the corporate identity is absent too: no operating entity, registered address, jurisdiction or country appears anywhere on the site, so a buyer cannot even establish which regulator would have anything to say about where the data rests.

One real control is published and it is the right one for this product: mailbox access runs through delegated authorisation with both major providers, explicitly without stored passwords or mail protocol credentials, and the vendor states the grant can be withdrawn by the customer at any time from their own provider account. Authentication record checking is offered as a product feature.

Past those, no certification, audit report, attestation, penetration test, control set, encryption statement, trust centre, status page or vulnerability disclosure route was located on any page read, and neither legal document was opened. For a platform holding live mailbox grants and the complete reply history of every campaign, one good authentication decision is not a security posture.

Two tiers are published and neither carries a price. The lower one is a waitlist offering a basic builder, one hundred leads and community support in exchange for requesting access. The upper one is named the founder rate, lists seven inclusions clearly, and its action is to book a demonstration to discuss pricing, sold on the argument that the buyer should lock in a rate before the product goes public.

A buyer is therefore asked to commit early to protect against a future increase, with no figure published on either side of that comparison. Trial terms are stated well, at forty five days with no card and cancellation at any time, and the feature split between the two tiers is unambiguous.

What makes this the bottom band rather than the one above is the vendor's own argument: its published comparison against a named competitor turns explicitly on price, criticising that competitor's per active lead charge as expensive at scale and contrasting it with a per seat model carrying no per lead fee, while never publishing the seat rate. A price argument made without a price is worse than silence.

Portability is treated as a capability rather than a concession, and three separate routes are named. Comma separated export appears as a listed feature. A webhook interface sits beside it. And two way synchronisation with a system of record continuously pushes new leads, interested replies and opt outs into a database the customer already owns, so the commercially valuable part of the record accumulates outside this platform by default rather than only inside it.

Holding it off the top band, no post termination right, deletion timeline, retention period or export format is stated anywhere, the terms were not opened, tier availability of the export is not specified given the free tier is a waitlist, and every one of the three routes is a tick on a feature list rather than a documented behaviour.

The mechanics are specific and unusually complete for a product at this stage. Mail leaves from the customer's own mailbox through delegated authorisation, so reputation stays with whoever owns the domain. Warmup begins automatically on the first day through a network exchanging real messages, with reputation tracking alongside it. Authentication records are checked.

Every address is validated through a named third party service before sending, with a default bounce ceiling published at under two percent, which is the only stated numeric guardrail on the site. A daily cap, a timezone aware sending window and a batch size are all configurable and stated to be enforced automatically, and a campaign pauses itself when open rate degrades, with bounce alerts surfacing in analytics.

Holding it off the top band: not one of those governors carries a published figure, so a buyer cannot know what the default cap or pause threshold actually is, the eighteen point four percent reply rate presented against an eight percent industry average has no sample, period or method behind it, and campaign level rotation across several assigned inboxes is described with nothing said about what governs the distribution.

The buyer is described consistently as a business to business sales team, and three testimonial personas sketch the range across a forty person software company, a lead generation agency and an early stage company's revenue operations function.

One passage does real disqualification work and deserves credit: the published comparison states that an agency sending five hundred thousand messages a month across a hundred or more client inboxes should choose the named competitor instead, which is a vendor naming the buyer it is wrong for.

Against that, no customer is named, no region, country, language or industry coverage appears, no seat band is given, and the only scale figure on the site is the claim of more than fifty teams, which the same page contradicts by offering fifty founding places as still open.