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.
The first wedge is outbound. You describe the company, confirm the keywords the agents should watch, and connect at least one channel. From there the runtime is continuous: sourcing sweeps every fifteen minutes, the queue fills, and the launcher sends. There is one human checkpoint — a preview of the ICP and the first three messages — and after that agents send without per-message approval unless an agent is explicitly left on approve_before_send.
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, runs the compliance gate, 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
Email is the only channel that can genuinely start within a minute of connecting. 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
Guides cover the path from signup to first send. 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 public API on api.trygtm.com.