Documentation
TryGTM
A GTM agentic platform. Agents source an ICP, write to it on the channels you connect, handle the replies, and work toward booked calls.
Review your company essentials, connect an email sender and choose a starter batch that fits your credits. Activate the campaign when you are ready for real work. The runtime checks outreach, sourcing, intent, replies and calendar reconciliation every minute. Nothing waits for intent: email reaches the whole audience, and LinkedIn connection requests go to every contact with a profile, from day one. Every campaign sends on its own through the same sending checks, and you can read, edit or stop any message before it goes.
What runs on your behalf
Seven scheduled jobs, deliberately separate rather than one loop. Sourcing, queueing and sending are distinct ticks, so a bad source produces a queue you can inspect rather than mail that has already left.
- Signal sweep — runs due signals against LinkedIn search through your own connected account, gates candidates on ICP membership, and writes the ones that pass.
- Queue filler — enters today’s contacts into the outreach queue against the daily cap.
- Queue launcher — drafts, checks the blocklist, and sends. This is the only path that contacts a person.
- Reply poller — pulls inbound mail, classifies it, and stops the sequence. Any reply skips every pending queue row for that contact.
- Connection health, experiment analysis and retention purge — account status, per-step reply rates, and deletion of contacts past their retention window.
What the channels can and cannot do
Once your seat opens, email requires a verified sending domain and sender before it can start. LinkedIn is ramped rather than instant, and Instagram is inbound and engagement only — Meta requires the correspondent to initiate, so there is no compliant cold DM path.
This documentation
Access is by waitlist. Guides cover setup after your seat opens. Platform pages explain the parts that are load-bearing and cannot be configured away — sourcing, the ICP gate, and compliance. The API reference documents the REST API, and MCP covers connecting an AI assistant to a workspace. The two are the same set of operations behind two doors.