BEFORE SENDING
Research cannot become a campaign by accident.
Website analysis and prospect research are read-only. A list and its message version must be reviewed before the first delivery. Sensitive actions remain in the project activity log.
TRUST AND CONTROL
Outbound stays under your control.
GTM Garden is built for research, review, and deliberate sending. These are the controls available in the private beta today.
MAILBOX ACCESS
Your mailbox remains yours.
Delivery uses the Gmail or Microsoft 365 identity you connect. OAuth refresh tokens are stored in Supabase Vault and are never returned to the browser or your chat. Disconnecting a mailbox deletes the stored credential and disables future sends from it.
PROJECT BOUNDARY
Every product keeps its own operating memory.
Contacts, evidence, campaigns, approvals, and results are scoped to one project. GTM Garden does not merge one product’s prospect data into another project.
CURRENT LIMITS
The beta is controlled, not autonomous bulk sending.
LinkedIn execution remains manual. Live email starts with an owned mailbox and explicit approval. This page describes the current product controls; it is not a security certification or a promise of unattended scale.
WHO OPERATES GTM GARDEN
Built by Shapers in France.
Shapers builds practical systems for teams working with AI. GTM Garden is its MCP-first go-to-market product and is currently operated as a private beta.
CURRENT BETA SERVICES
A short, inspectable stack.
The current beta runs on Vercel and Supabase. Payments are not open during prelaunch. Google or Microsoft receives access only when you choose to connect the corresponding mailbox.