Tofu

Breadth across four ecosystem classes, and integration is the delivery mechanism rather than a convenience. Native connections span CRM through Salesforce and HubSpot, marketing automation through Marketo and HubSpot, sales engagement through Outreach, Salesloft and Gong Engage, and advertising and social through LinkedIn, with custom data connectors alongside and content pushed into the customer's content management system.

The homepage puts the four principal logos, HubSpot, Marketo, Salesforce and Outreach, beside the promise to automate always-on campaigns inside the existing GTM stack. The architectural point matters more than the list: Tofu positions itself as running inside the customer's martech rather than replacing it, so the Launch Agent's execution is entirely mediated by these connections, and integration depth determines whether the product can act at all. The same architecture pushes the record of what happened into those systems.

Sourcetofuhq.com/platform and tofuhq.comread 2026-09-02

Three named agents running a chain that ends in a campaign going out. Research reads the account, content creates the personalized assets, and the Launch Agent is the step that matters: triggers are configured once, after which it sequences emails, stages leads, fires campaigns and updates the CRM without a human in the chain. That is unattended multi-step execution ending in a sent campaign.

The vendor's framing is automate your always-on campaigns inside your existing GTM stack, and customers describe cross-functional teams aligning on a brief after which Tofu creates per-segment content and executes everything from one place. Execution happens through HubSpot, Marketo, Salesforce and Outreach rather than natively, so the send is Tofu's decision and the sending is the connected platform's. Tofu's own category essay describes some platforms, itself included, as AI-powered automation systems rather than true agents, while the product page documents autonomous execution.

Sourcetofuhq.com/platform and tofuhq.comread 2026-09-02

The Playbook is a real structured grounding layer over the customer's own material and is the strongest part of the product. It holds brand voice, ideal customer profile, personas, messaging frameworks and existing assets, and every generated asset is constrained by it, which is what keeps per-account output on brand at volume rather than drifting.

A research step pulls per-account context before writing, and follow-ups are grounded in past objections, prior interactions and recorded lost reasons drawn from the connected CRM, so the corpus includes the customer's own deal history rather than only their positioning. It is a persistent, customer-owned brand and context layer applied as a constraint at generation time rather than a prompt library, and it is why one brief can produce a coherent multi-format campaign per account. The agents read it as the standing basis for what gets written.

Sourcetofuhq.com/platform and tofuhq.comread 2026-09-02

A pre-generation constraint and no approval gate. The Playbook bounds what the agents produce, brand voice, ICP, personas and messaging frameworks, authored once and applied across every asset, which is a customer-controlled constraint. The Launch Agent sends once its triggers are set, sequencing emails, staging leads, firing campaigns and updating the CRM, and no approval step, review queue, escalation logic or policy engine before a campaign goes out is documented.

Sourcetofuhq.com/platform and tofuhq.comread 2026-10-01

The homepage carries a security section headed security that you can trust and displays an AICPA SOC badge for service organizations, a first-party attestation claim. The badge does not say which report it refers to.

No type, period, auditor or report availability accompanies it, and there is no trust center, security page, certification page, sub-processor list or downloadable report anywhere in the site navigation, which runs to platform, use cases, resources and two legal pages; an attestation asserted without a type is unverified rather than assumed to be Type II.

Security material at trust.gotofu.com, publishing ISO 27001:2022, PCI DSS, GDPR and AWS Frankfurt hosting, belongs to Tofu2 Limited of Hong Kong, a different company, and hiretofu.com is a third Tofu selling ATS fraud detection; none of it describes this vendor.

Sourcetofuhq.com homepage and tofuhq.com/privacy-policyread 2026-09-02

No audit log, agent action log, activity trail, run history or reporting surface is documented anywhere on Tofu's own product pages or in its complete site navigation. Because the Launch Agent executes by writing into the customer's own CRM, marketing automation platform and sales engagement tools, the record of what it did lands in those systems; that is their audit trail, not Tofu's. Running inside someone else's stack pushes the record out of the product along with the measurement, so a buyer cannot answer what the agent did from inside Tofu.

Sourcetofuhq.com/platform and tofuhq.com complete site navigationread 2026-09-02

A persistent context layer and CRM history, not agent memory. The Playbook holds brand voice, ICP, personas and messaging frameworks across campaigns, which is grounding material. The Research Agent draws on closed-lost reasons, form fills, deal stage and seller notes, which are the customer's CRM records. Configuration and business records are not memory: no memory construct the agents write and read back, and no retention or forgetting control, is documented.

Sourcetofuhq.com/platformread 2026-10-01

No deployment or residency control is documented. The complete site navigation contains no security or trust page that names regions, running only to platform, six use-case pages, resources and two legal documents, and no on-premises, air-gapped, single-tenant or private VPC option appears anywhere. Hosting statements naming AWS Frankfurt and Google Cloud that surface on a search for Tofu belong to gotofu.com, Tofu2 Limited of Hong Kong, a different company, and contradict each other; neither describes this vendor.

Sourcetofuhq.com complete site navigationread 2026-09-02

Three named agents ship, research, content and launch, but they are the product rather than a library: there is nothing to browse, nothing to select between and no way to add a fourth. The Playbook is a real template system holding brand voice, ICP, personas and messaging frameworks and instantiating whole campaigns from one brief, but it is authored and stocked by the customer.

The six published campaign types, outbound, lead nurture, event follow-up, sales acceleration, re-engagement and expansion, are use-case pages in the site navigation rather than in-product plays a buyer picks from. No catalog a buyer browses and selects from is evidenced, only a customer-stocked template layer.

Sourcetofuhq.com/platform and tofuhq.com use-case pagesread 2026-09-02

Configured triggers wake the Launch Agent. The platform page says "Set your triggers once. The Launch Agent sequences emails, stages leads, fires campaigns, and updates your CRM", so after setup the work starts on the trigger rather than on a person asking.

Coverage is three channel classes the homepage names, email, landing pages and ads, delivered through the customer's HubSpot, Marketo, Salesforce and Outreach rather than sent natively, and Tofu originates no intent data of its own. Asset formats such as whitepapers and decks are not channels. The events that can serve as triggers are not documented.

Sourcetofuhq.com/platform and tofuhq.comread 2026-10-01

No model choice, routing, bring-your-own-model or bring-your-own-key documented. Tofu describes itself as AI-native and agentic but names no model provider anywhere on the homepage, the platform page, the six use-case pages or the legal pages, discloses no routing logic and offers the customer no selection.

For a buyer, this is single-provider dependency with the provider undisclosed, which is weaker than a vendor that names its provider. For a content generation product whose whole output goes out under the customer's brand, the undisclosed provider is itself a procurement question, and it sits alongside a security posture that cannot state its own attestation type.

Sourcetofuhq.com/platform and tofuhq.comread 2026-09-02

No documented interface makes Tofu callable from outside. The complete site navigation runs to Platform, six use-case pages, a resources set, login, and Privacy Policy and Terms in the footer, with no developer portal, documentation subdomain, API reference, SDK, webhook documentation, MCP server or partner program anywhere on the property.

Custom data connectors are Tofu reaching outward into a customer's systems, and bidirectional sync with CRM and marketing automation means Tofu calling those platforms' APIs; neither makes Tofu callable from outside, and no API access is published. Tofu is architected to run inside other people's platforms rather than to be a platform others build on, which is a coherent product choice.

Sourcetofuhq.com complete site navigation and tofuhq.com/platformread 2026-09-02

No evaluation tooling ships, and the reason is architectural. No sandbox, evaluation harness, experimentation engine, A/B testing framework, regression suite or output scoring surface is documented on any Tofu product page or anywhere in its complete site navigation.

Because the Launch Agent executes by pushing assets into the customer's CRM, marketing automation platform and sales engagement tools, campaign measurement necessarily happens in those systems rather than in Tofu, so running inside someone else's stack pushes evaluation out of the product along with the audit record.

That is a structural consequence of the delivery model rather than neglect, and it means a buyer wanting to know whether the agent's output performs must assemble the answer from the tools underneath.

Sourcetofuhq.com/platform and tofuhq.com complete site navigationread 2026-09-02

No browser control, computer use, screen operation or robotic process automation of any kind documented.

Tofu acts entirely through native integrations with CRM, marketing automation, sales engagement and content management systems, and its own framing is that campaigns run inside the customer's existing stack, which is the correct architecture for a content generation and campaign execution product and not a gap in any practical sense.

The Launch Agent executes through HubSpot, Marketo, Salesforce and Outreach rather than by operating any interface. Nothing across the homepage, the platform page, the six use-case pages or the resources section describes an agent driving software that exposes no programmatic route.

Sourcetofuhq.com/platform and tofuhq.comread 2026-09-02