Reachdesk

A fulfilment business with an assistant on the front of it. The substance of this company is a marketplace of vetted suppliers, warehouses in several regions, kitting and packing operations, carrier and customs handling across more than a hundred and eighty countries, and the software that triggers a send and tracks it. None of that requires a model and none of it stops working without one.

The generative layer arrived later as a named assistant that researches a recipient, recommends up to six gifts and drafts the accompanying note in the recipient's language, plus a semantic search that filters the catalogue by persona, occasion, budget and preference. Those genuinely are model capabilities and they change how quickly a sender chooses something, not whether the thing arrives.

The vendor's own account of what it sells supports the reading, since its differentiation is stated as global coverage, warehousing and measurable attribution rather than as anything the assistant does. Strip the assistant and a buyer still has the platform the reference customers describe using. Ask which capabilities depend on a model, and what proportion of sends are chosen through the assistant rather than by search.

The most complete spend governance published by any vendor in this category, and it is the right control set for the problem. Published are team level budgets, user level sending limits that cap what an individual may send, wallets that hold funds against a team or region, and spend monitoring across departments and regions, alongside role based permissions, single sign on, and multi team multi region workspaces that keep governance and branding consistent as the programme spreads.

A per user send ceiling is the specific mechanism that stops a well meaning representative sending something expensive to the wrong person, and it is configured rather than assumed. One further control sits on the claiming side rather than the sending side: for link based campaigns the recipient must confirm an email address that matches a lead or contact already in the connected record system, and a gift cannot be claimed by anyone who does not.

That prevents a forwarded link being redeemed by a stranger. Held below the top band because the governance question specific to gifting is unaddressed. Nothing describes a value ceiling per recipient, approval routing above a threshold, or the ability to exclude recipients in sectors where gifts above a statutory limit create a problem for the person receiving them. Ask what per recipient value limits and approval thresholds can be enforced, and whether restricted recipients or sectors can be excluded.

Recommendation reasoning is surfaced to the user, which is genuinely uncommon, and nothing underneath it is described. The assistant returns up to six gift options and explains why each one fits the recipient, so the person sending sees the reasoning rather than an unexplained ranking, and can reject it. Explainability offered as a product feature rather than a compliance artifact is worth recording.

The inputs are named too: job history, education, location and interests, described as drawn from public information about the recipient. Everything below that is absent. No model provider, family or version is stated for the assistant, the note generation or the translation, no model card exists, and no accuracy or acceptance measurement is published, which is a gap the vendor could close with data it already holds since the platform observes whether a recommended gift was sent and whether it was redeemed.

The note generation also translates into the recipient's language, and nothing states what checks translated commercial copy before it is printed and dispatched, which is a one way operation. Ask which models power recommendation, note generation and translation, what proportion of recommendations are accepted, and what reviews translated copy before printing.

Reachdesk's pricing page guarantees 5x ROI on pipeline generated in the first year with Reachdesk or the customer's money back, which now gives the guarantee a period and a remedy; how pipeline is counted, how it is attributed to gifting and who confirms the result are not published.

The rest of the evidence is customer testimony, such as a customer marketing manager reporting almost 10x return on spend within a year, and percentage claims on response and conversion published without a population, period or method.

One real control on who may receive a gift, and no statement of the legal frame around any of it. The control that exists is on the claiming side: for link based campaigns the recipient must confirm an email address that already matches a lead or contact in the connected record system, and the platform will not release a gift to anyone who does not, which limits redemption to people already in a relationship with the sender and prevents a forwarded link being claimed by a stranger.

Recipients of an electronic gift may also decline what was chosen and take a different one or donate its value to charity, which gives the person some agency over an unsolicited approach. Beyond those, the obligations attaching to sending physical goods to people who did not ask for them are unaddressed. Nothing published states a consent basis, describes a suppression list that persists across campaigns and teams, or explains how a recipient stops receiving future sends.

Two category specific regimes go unmentioned: unsolicited goods rules that give recipients rights over items they did not request, and anti bribery constraints on gifts to public officials and to staff at regulated organisations, both of which fall on the sender rather than the platform and both of which apply across the many jurisdictions this vendor ships into. Ask what consent basis supports a first send, how a recipient opts out permanently, and what guidance exists for regulated recipients.

Named privacy tooling in the integration list and no instruments reached. The signal worth crediting is specific: the vendor lists an integration with a privacy management platform whose purpose is servicing data subject requests, alongside single sign on and role based permissions with an identity provider integration.

A vendor that has built a connection to request handling infrastructure has at least anticipated that people will ask what it holds about them, which is more than a policy page demonstrates. Against that, no processing agreement, subprocessor list, retention period, transfer mechanism or data protection contact was reached on this pass, and no vendor trust surface was retrieved. The corpus needs stating because one part of it is built rather than collected.

The assistant researches recipients from public information about their careers, education, location and interests in order to recommend a gift, which produces an inferred profile of a named individual who has no relationship with the vendor, and nothing published states whether that research is retained after the send, whether it is reused for future campaigns, or whether the person can see it. Ask for the processing agreement and subprocessor list, the retention period for recipient records and assistant research, and how a recipient exercises rights over data held about them.

Two supply chains run through this product and neither is documented at the level a buyer needs. On the data side, the assistant is described as researching recipients using public information covering job history, university background, location and interests.

Public information is a characterisation rather than a source: nothing states whether it comes from a licensed data provider, a professional network, general web retrieval or a purchased dataset, and those carry materially different provenance and terms. No indemnification position was located.

On the goods side, the marketplace is described as carrying gifts from vetted vendors, and the vetting criteria are not published, which matters more here than for software because a customer's logo goes on the branded items and the recipient associates the quality and origin of a physical object with the sender rather than with the platform. A separate integration routes fulfilment through a large online retailer, which is a named supplier and the clearest provenance in the record. Ask what supplies the public information the assistant researches from, what vetting applies to marketplace suppliers, and whether provenance is indemnified.

A long list of official connections and the vendor operates its own fulfilment rather than borrowing anyone's. Named integrations cover several customer record platforms including their marketing suites, three marketing automation systems, two sales engagement platforms, a conversation intelligence product, messaging, calendar and scheduling tools, two human resources systems, an identity provider and a privacy management platform, with automated campaigns running through webhook triggered workflows.

Several of those products are separately recorded in this index, so a buyer can evaluate the pieces independently. Nothing scrapes a professional network, drives a browser extension against one or automates a social account. Held below the top band on two grounds. No conformance position is stated in the vendor's own words for any connected platform.

And the dependencies that actually threaten continuity here are not software: delivery across more than a hundred and eighty countries rests on carriers, customs regimes and import rules the vendor does not control, and a substantial fulfilment route runs through a large online retailer whose marketplace terms it also does not control. Nothing published describes what happens to delivery commitments or to that retail route if either changes. Ask what carrier, customs and retail marketplace dependencies underpin international delivery and what contingency exists when one changes.

An assistant that researches named individuals, and no stewardship position located. The capability builds a picture of a recipient from public information about their career, education, location and interests, generates a personal message to them, and translates it into their language, so model processing touches both an inferred profile of a person and the words that will be printed and sent to them.

Nothing established on this pass states whether recipient research, generated notes or campaign data train or tune any model, which provider processes them, what retention applies to prompts and generated output, or whether anything crosses a customer boundary.

No governance document, evaluation record, red teaming artifact or independently audited management standard for artificial intelligence was located, and no vendor trust surface was reached, so material may exist that this pass did not see.

One question is specific to this product shape and worth putting first: the assistant's research concerns a third party rather than the customer, so a buyer authorising it is authorising profiling of someone else, and the retention answer determines whether that profile persists after the gift is sent. Ask whether recipient research is retained after a send, whether it trains any model, and which provider processes it.

The recipient has more agency here than in most of this category, and the note attached to the gift may still misrepresent who wrote it. On the agency side the person is an active participant rather than a passive target: they are invited to confirm where they want the gift sent, they can decline an electronic gift and choose a different one, and they can direct its value to charity instead.

Those are real choices offered to someone who did not ask to be contacted, and they distinguish this product from one that simply dispatches an item. The authenticity question sits on the message. The assistant generates the note copy and translates it into the recipient's language, and the vendor's warehouse operation produces handwritten notes, so a recipient can receive what presents as a personal handwritten message in their own language whose words were produced by a model that also inferred their interests from public sources.

A handwritten card carries an implicit claim about effort, and that claim is precisely what is being automated. Nothing published states whether generated copy is approved before printing or whether any indication reaches the recipient. Ask whether generated notes are reviewed before printing, and what a recipient would be told about how the message and the gift choice were produced.

A broad named integration surface across more system categories than this product strictly needs, sitting on physical infrastructure a software competitor cannot copy quickly. The published list spans customer record platforms and their marketing suites, three marketing automation systems, two sales engagement platforms, conversation intelligence, messaging, mail and calendar, meeting scheduling, two human resources platforms, identity management and privacy request tooling, with automation through webhook triggered workflows.

The human resources connections matter because they support employee gifting as a genuine second motion rather than a claim. Underneath sits warehousing in several regions, supplier relationships and customs handling, which constitutes depth of a kind no connector list conveys. Two things hold it below the top band.

Independent reviewers describe the integration list as short, which contradicts the enumerated set found here and was not resolved on this pass, so a buyer should count it themselves against their own stack. And no public developer documentation or programmatic interface was located, so a customer wanting to build something the vendor has not built has no visible route. Ask for the enumerated integration list with which are native, and whether a documented interface exists.

Physical regionality is published and data regionality is not. The vendor operates warehousing in several regions and multi region workspaces that let a customer configure teams, warehouses and marketplaces by geography, so where goods sit and ship from is a configurable and stated part of the product.

Where records sit is unstated in every respect: no hosting provider, region, tenancy model, recovery objective or residency election was reached on this pass, and no vendor trust surface was retrieved. The gap is consequential because of what fulfilment requires.

Sending into more than a hundred and eighty countries means a recipient's name and delivery address reach a warehouse and a carrier in the destination country, so personal data crosses borders as an operational necessity rather than an architectural choice, and nothing published describes which entities receive it or under what arrangements.

A European customer sending within Europe through a platform headquartered in the United States has no published answer to the first question their data protection review will ask. Ask where records are hosted, which fulfilment entities receive recipient data for international sends, and whether regional processing can be specified.

Reachdesk runs a Vanta trust center listing SOC 2 Type I and Type II and GDPR. It offers the SOC 2 Type II report for 31 August 2024 to 1 September 2025, a May 2026 bridge letter, a 2025 to 2026 penetration test retest report, a 2025 disaster recovery test and data flow diagrams on request, alongside enumerated controls, a subprocessor list and an FAQ. Data is encrypted in transit and at rest and hosted on Amazon Web Services in Ireland. The report sits behind an access request rather than downloading directly.

Reachdesk publishes a starting price, with plans from $20,000 a year. Its three GTM platform plans, Core, Plus and Premium, include 5, 10 and 15 users, one, two and three gifting territories with matching fulfillment centers across the US, Canada, the UK, the EU and Australia, and 15, 30 and 45 externally sourced SKUs with unlimited Reachdesk sourced SKUs.

Plus and Premium carry no price, goods, shipping, customs and storage are charged on top of the platform, pricing varies with shipping origin and destination, and swag orders start at a $2,500 minimum. A first year guarantee promises 5x ROI on pipeline or the customer's money back.

The usual export questions apply and two exposures particular to this category matter more. The first is physical. Customers store their own branded merchandise in the vendor's warehouses, and nothing published states who owns that stock at termination, whether it is returned, at whose cost, or what happens if it is not collected. The second is monetary.

The vendor publishes wallets as a spend control, which implies funds held against a team or region ahead of use, and nothing states whether an unspent balance is refundable, whether it expires, or how quickly it is returned. Both are ordinary logistics terms and neither is visible before a sales conversation.

On the data side nothing was located covering export scope or format for send history, recipient records, campaign configuration or analytics, and no post termination retention or deletion timeline appears. One structural mitigation is worth crediting: attribution writes gifting events into the customer's own record platform, tying sends to meetings, pipeline and revenue there, so the commercially useful history already sits in a system the customer keeps. Ask whether unspent wallet balances are refundable and on what timeline, what happens to stored merchandise at termination and at whose cost, and what send history exports.

The strongest control on this axis in the gifting category, and it works by asking rather than guessing. Before dispatch the platform contacts the recipient through an email, a link or a branded page and invites them to confirm or update the address they would like the gift sent to, and the vendor states this works globally and exists to raise delivery and redemption rates by cutting undeliverable sends.

That is the correct control at the correct point: the most common cause of a failed physical send is a wrong or stale address, and asking the person removes the guess entirely rather than validating a guess after the fact. It also handles the case the vendor names directly, a recipient working from home whose address the sender does not have and should not have to ask for.

Alongside it, electronic gifts are charged only on redemption, so an unclaimed digital send costs nothing, and warehouse operations handle kitting and bundling of multi item packages in house rather than through a broker. Held below the top band on measurement and on coverage. No delivery success rate, on time rate or damage rate is published for any region, and no service level is stated for international sends.

Independent reviewers also report that the choice of items thins materially for recipients outside two major markets, which qualifies the global claim on which the product is sold. Ask for delivery success and on time rates by region, the catalogue depth outside the primary markets, and who bears the cost of a failed send.

Coverage is the product's whole proposition and most of it is stated concretely rather than claimed. The market is business to business, weighted to software, technology and services, at mid market and enterprise scale with multi person revenue and people teams.

Use cases are enumerated across outbound and account based campaigns, event and webinar incentives, customer onboarding and renewals, win back and pipeline acceleration, and employee engagement, and the human resources system integrations support the last of those as a genuine second motion.

Geographic reach is given in numbers rather than adjectives, with a physical marketplace stated across more than one hundred and eighty countries, electronic gifts across more than one hundred and seventy, warehousing in several regions, offices on two continents and a stated expansion into a third market. Multi region workspaces let a large customer run different catalogues and governance per territory. Two things hold it below the top band.

Independent reviewers report that item choice narrows appreciably outside two major markets, which qualifies the coverage claim precisely where it is the reason to buy. And no minimum programme size or budget is published while reported entry commitments run to five figures annually, so the smallest buyers are excluded without being told. Ask what catalogue depth exists in the buyer's specific target countries, and what annual send volume the entry commitment assumes.