# GTM

> GTM is a go-to-market platform where five specialist agents and a coordinator run a company's outbound motion end to end: sourcing the list against a licensed corpus and the operator's own LinkedIn account, scoring intent from observed evidence, writing each message from that evidence, sending through the customer's own sending domains, and working every reply toward a booked call. One preview before the motion starts and then automatic sending in Autopilot, with approval available in Supervised mode; a compliance gate on every send, enforced by a database constraint. Pricing: $2,000 or $5,000 one-time onboarding, then at least $250 monthly prepaid usage funding, fully converted into credits with rollover. Data credits cost $0.01 and action credits $0.0025 each. The optimization goal is one qualified booked call per $100 of usage, not a guarantee. Access is by waitlist at https://trygtm.com/join. OAuth sign-in at app.trygtm.com is for existing seats only.

Key facts:
- Email is sending domains and sender addresses you attach and verify, not a connected mailbox. LinkedIn is the customer's own account, connected inside the product.
- LinkedIn limits are stated and enforced: 5 invitations/day in week one, 10 to day 30, 20 to day 60, then the operator's own ceiling (~20–25/day warmed).
- SMS is the named next channel and is not open. Instagram is out of the motion. Meta requires the correspondent to initiate, so there is no compliant cold path.
- Five fixed agents per workspace: GTM Leads, GTM Intent, GTM Outbound (the only one that can send), GTM Copy, GTM QA.
- Two credit purses: data credits buy facts about a person (a contact reveal is 30), action credits buy the work (one cold email sent is 1). Agents pause at the allowance; overage is opt-in only.
- There is no approval queue. Supervised review is a per-campaign override, not the default.
- SOC 2 is a programme underway, not a certification held. Data is US-only, us-east-2.
- Data stored in the US (AWS us-east-2). Per-field provenance, retention anchored to collection date, permanent suppression.

Full page index: https://trygtm.com/llms-full.txt

## Pages

- [Home](https://trygtm.com/): GTM agents source the list, write from evidence, send through your own domains and work every reply toward a booked call.
- [Platform](https://trygtm.com/product): The whole outbound motion. Source, qualify, write, send, reply, book. Run by five specialists and a coordinator on a one-minute execution clock.
- [All features](https://trygtm.com/product/features): Every capability in the platform, grouped by where it sits in the motion.
- [Integrations](https://trygtm.com/product/integrations): Booking calendars, six CRMs, Slack, Zapier and signed webhooks. Every connection is verified against the vendor before it reads as connected.
- [Pricing](https://trygtm.com/pricing): $2,000 or $5,000 one-time onboarding. At least $250 monthly prepaid usage funding, fully converted into data and action credits with rollover.
- [How credits work](https://trygtm.com/pricing/credits): Data credits buy facts about a person. Action credits buy the work. Every metered action, priced, in one table.
- [Security & compliance](https://trygtm.com/security): Per-field provenance, retention anchored to collection, a pre-send gate enforced by the database, and suppression that survives every purge.
- [Solutions](https://trygtm.com/solutions): Who runs GTM, and what the motion looks like for each of them.
- [Industries](https://trygtm.com/industries): The same motion, framed for the market you sell into.
- [Compare](https://trygtm.com/compare): How GTM differs from the sequencers, the databases and the other AI SDRs. Described fairly enough that their customers would agree.
- [Blog](https://trygtm.com/blog): Notes on outbound, deliverability, channel limits and building GTM agents.
- [Guides](https://trygtm.com/guides): Playbooks you could run on Monday. ICP, deliverability, sequence design, agency operations.
- [Glossary](https://trygtm.com/glossary): The outbound vocabulary, defined the way the industry uses it rather than the way a vendor would like it defined.
- [FAQ](https://trygtm.com/faq): Straight answers on channels, credits, LinkedIn limits, compliance, and what GTM will not do.
- [About](https://trygtm.com/about): TryGTM is the company and the product: a go-to-market platform where five specialists and a coordinator run outbound.
- [Design partners](https://trygtm.com/customers): Who we are building with before launch, what we ask of a design partner, and what they get.
- [Careers](https://trygtm.com/careers): Open roles at TryGTM across engineering, AI, security, marketing and legal.
- [Partners](https://trygtm.com/partners): Agencies, consultants and platforms building on GTM.
- [Affiliates](https://trygtm.com/affiliates): 10% of the referred subscription for its life, 10% off their first month. Two numbers, both flat.
- [Press](https://trygtm.com/press): Company facts, the boilerplate, and where to reach us.
- [Brand](https://trygtm.com/brand): The mark, the wordmark, the colours and how to use them.
- [Changelog](https://trygtm.com/changelog): What shipped, in the order it shipped.
- [Roadmap](https://trygtm.com/roadmap): What is directed, what is designed and what is deliberately not being built.
- [AI information](https://trygtm.com/ai-info): What an answer engine needs to describe GTM correctly, including the pricing floor, the channel limits and the certifications we do not hold.
- [Support](https://trygtm.com/support): Reach the team. Questions, bugs, billing, partnerships. Answered by a person.
- [Book a demo](https://trygtm.com/demo): Twenty-five minutes, your ICP, and the product doing the motion live.
- [Talk to sales](https://trygtm.com/join): Get a seat when we open. Work email, one message, no spam.
- [Privacy Policy](https://trygtm.com/privacy): What TryGTM collects, why, where it is stored, and the categories of provider that touch it.
- [Terms of Service](https://trygtm.com/terms): How TryGTM offers GTM, and what you agree to when you use it.
- [Data Processing Addendum](https://trygtm.com/dpa): The processing terms, and where the controller line actually falls.
- [Subprocessors](https://trygtm.com/subprocessors): The categories of provider that touch customer data, and what each one is for.
- [Acceptable Use](https://trygtm.com/acceptable-use): What you may not send through GTM, and what happens if you try.
- [Lead sourcing](https://trygtm.com/product/sourcing): A prospect corpus answers who matches your ICP. Your own LinkedIn account answers who just did something interesting. Neither replaces the other, and they run on separate clocks so one failing vendor never takes the other's leads with it.
- [Intent signals](https://trygtm.com/product/intent): A sourced contact sits at heat 1 until something happens. Then a keyword fires, or they react to a post, or they answer, and the number moves. The outbound queue only takes contacts at 4 and above, so what is in flight is people showing intent right now, never the whole market you sourced.
- [Enrichment](https://trygtm.com/product/enrichment): Both lead paths enrich before the write. A corpus pull reveals every candidate before the import; the LinkedIn sweep reveals every gate-passed lead by profile URL before the contact insert. Only people an address came back for become contacts, so your list never holds anyone you cannot write to.
- [ICP & the fit gate](https://trygtm.com/product/icp): The gate runs on an Opus-class model and makes two judgements in one pass: a binary in-or-out call on ICP membership, and a 1–5 intent score for the ones that pass. Rejects never become contacts. That is why the flame on the contacts grid means heat, not fit.
- [Audiences](https://trygtm.com/product/audiences): Every pull lands on a list named for the ICP that produced it, so a month of sourcing reads as a set of decisions rather than one growing pile. A campaign points at one or more audiences, and the entry rule decides who leaves.
- [AI copywriting](https://trygtm.com/product/copy): Copy is written the moment a lead enters the queue, personalised from their own profile and the signal that warmed them. There is one writer: the same prompt stack answers a slash command, the scheduled rewrite pass and the queue's own drafting, so the voice cannot fork.
- [Templates](https://trygtm.com/product/templates): A template is the sequence definition. Ordered steps, a channel per step, the wait between them, branch conditions and parallel tracts. One per campaign. There is deliberately no second sequence-definition object, because two places to author the same graph is exactly how six code paths came to each re-derive today's chain and then disagree.
- [Campaigns](https://trygtm.com/product/campaigns): What happens when a lead gets high intent used to be hard-coded in three places and editable in none. A campaign is where that becomes a decision you make per motion. Alongside the goal it is measured against, the priority it runs at, the senders it leaves through and the date it ends.
- [Email & LinkedIn](https://trygtm.com/product/channels): Access is by waitlist. Once your seat opens, attach a sending subdomain, publish its DNS records, verify it and add a sender. LinkedIn uses a separate connected account with its own ramp and daily limits.
- [Sending domains & senders](https://trygtm.com/product/senders): A sending domain is a real connection row: pending until its DNS verifies at the vendor, with the records, the bare domain and the reply-to mailbox stored on it. A sender is one from-address on that domain. Rotation, daily pacing, workspace isolation and the age ramp all apply per address, because that is the unit a reputation attaches to.
- [Warmup & deliverability](https://trygtm.com/product/deliverability): New senders default onto the enforced age ramp. Warmup-enabled senders exchange AI-written, deliberately mundane traffic between your own domains under the same ceiling. Real sends, metered, logged, and never shown in your inbox. What this does not claim: reputation at Gmail and Outlook is built by mail landing in inboxes there, which a self-contained network cannot fake.
- [Sequences](https://trygtm.com/product/sequences): When the workspace has both channels and the contact has a profile URL, one entry covers the whole chain. The email goes first. A few hours later it moves to LinkedIn: their latest post gets a like. No follow, and the connection request goes out with a fresh note. On accept, the first message waits 24 to 30 hours and is written fresh from their profile.
- [The unified inbox](https://trygtm.com/product/inbox): LinkedIn arrives on the poller's tick and email arrives on an inbound webhook, and both land in the same conversation table under the same pipeline. So a LinkedIn reply stops a sequence, honours a prose opt-out and reaches your CRM under exactly the rules an email reply does.
- [Reply handling](https://trygtm.com/product/replies): When a reply lands and it is not an opt-out, the answer is drafted immediately. Qualifying, or proposing the call, and queued, so it leaves on the next tick through the same gate as everything else. One unsent answer per thread is what stops a second being written while the first is still waiting.
- [Booked meetings](https://trygtm.com/product/meetings): Connect Google Calendar, Calendly or Cal.com and that is what the outbound agent books against. The booked transition is an event: a contact record and a note reach your CRM, a message reaches Slack, and the funnel on the insights screen moves.
- [CRM & alerts](https://trygtm.com/product/crm): Twelve third-party accounts across booking, CRM and automation. Every one of them is a live call rather than a stored string: saving verifies against the vendor's own API before the row is marked connected, and the vendor's answer supplies the label on the card.
- [The agent roster](https://trygtm.com/product/agents): The workspace includes GTM CEO as coordinator, plus Leads, Intent, Outbound, Copy and QA specialists. Each role has a defined toolset and responsibility. Campaigns reuse these roles.
- [The agent screen](https://trygtm.com/product/agent-screen): The root route is a full-screen conversation. It absorbed the dashboard and the ask screen, because the page you land on should be the one you instruct. The docked copilot that used to float on every other route was removed rather than replaced. Two surfaces for the same conversation is the product arguing with itself about where you type.
- [The pre-send gate](https://trygtm.com/product/gate): Intent fires, the entry rule matches, and the sequence runs. What was removed is a hold, not a check. The queue in front of the gate asked a person to re-approve a draft the product had already written from evidence it had already gathered. The gate itself is untouched, and it is enforced one layer below the code.
- [Insights](https://trygtm.com/product/insights): Four boxed numbers read as four widgets. A strip reads as one sentence about the screen below it. Insights is the single retrospective surface. Sourced, contacted, replied, booked, plus which signals found them and which step is losing people. All against one period control.
- [MCP & API](https://trygtm.com/product/mcp): Everything else is negotiated: the client discovers the authorization server from a 401, registers itself, and authorises with PKCE. Fifteen tools cover workspace state, contacts, conversations, agents, signals, integrations and the prospect database.
- [Founders](https://trygtm.com/solutions/founders): You do not need a sequencer. You need the eight hours a week that outbound eats: the list, the research, the writing, the sending, the follow-up, the reply. Describe the company, confirm the keywords, connect a channel, and the motion runs without you opening it.
- [Agencies](https://trygtm.com/solutions/agencies): Isolation follows the workspace, not a filter on a shared list. Each client's connections are their own, sourcing searches from that client's connected account, and outreach can only leave through that client's connections or a pool you explicitly shared.
- [Sales teams](https://trygtm.com/solutions/sales-teams): The hard part of an SDR's day is not sending. It is knowing which fifty of four thousand accounts are worth a message today, and writing something that earns a reply. Agents do that continuously; your reps take the conversation from the point it becomes one.
- [Marketing](https://trygtm.com/solutions/marketing): You already know what people are reading. What you do not have is a way to turn a person engaging your topic on Monday into a relevant message on Tuesday, written from what they engaged with rather than from the segment they landed in.
- [RevOps](https://trygtm.com/solutions/revops): Sourcing leads ourselves makes us a controller in our own right, not merely your processor. That is a deliberate choice with a real cost, and it drives five things that cannot be retrofitted onto a tool that started as a sequencer.
- [Recruiting](https://trygtm.com/solutions/recruiting): Job search is the one LinkedIn search that returns a numeric company id, and the company profile is the one place a real website exists. That makes hiring the best-instrumented trigger in the product, and it works in both directions: companies hiring, and people who just got hired somewhere interesting.
- [Startups](https://trygtm.com/solutions/startups): The first SDR is a $90k bet on a motion you have not proven yet. Run the motion first, learn what actually earns a reply, and hire into a machine that is already turning.
- [Small business](https://trygtm.com/solutions/small-business): You do not need a sales stack. You need somebody working the phones who never gets sick, never forgets the follow-up, and never mails the person who asked to be left alone.
- [Enterprise](https://trygtm.com/solutions/enterprise): Nothing about the motion changes at scale. What changes is procurement: single sign-on, a data processing agreement your counsel drafted rather than ours, a named subprocessor list under NDA, an availability commitment and a volume you negotiated.
- [B2B SaaS](https://trygtm.com/industries/b2b-saas): A company hiring a data engineer is a company with a data problem, dated. Hiring is the only sourcing path that hands back a real company domain, which makes it the cleanest trigger in the product for anyone selling software to a function.
- [Professional services](https://trygtm.com/industries/professional-services): Consultancies, law firms and advisory practices sell judgement, and a generic first line contradicts the pitch. The whole point of writing from evidence is that the message proves the reader was looked at.
- [Staffing & search](https://trygtm.com/industries/staffing): A staffing desk runs two motions that look identical to a piece of software: find the right people, reach them on the channel they read, follow up without being annoying, and never lose the thread. Two audiences, two campaigns, one inbox.
- [Fintech](https://trygtm.com/industries/fintech): You need to be able to say, months later, who was contacted, on what basis, with what disclosure, and what happened when they asked to stop. That is a data model question, and it is answered at the write rather than reconstructed from logs.
- [Developer tools](https://trygtm.com/industries/dev-tools): The audience most hostile to outbound is also the one most reachable by a message that is obviously specific. Write from what they actually posted, keep it short, and do not pretend you have met.
- [B2B commerce](https://trygtm.com/industries/ecommerce): Buyer outreach, supplier outreach and partnership outreach are the same motion with different lists and different goals. One roster runs all three; the campaign is where they differ.
- [GTM vs Clay](https://trygtm.com/compare/clay): Clay is the best data orchestration product on the market and it is not close. If your problem is enrichment coverage. Chaining twenty providers, writing the fallbacks, scoring the result. Clay is what you want. GTM is answering a different question: not how do I enrich this list, but who should we be talking to today and what did they say back.
- [GTM vs Apollo.io](https://trygtm.com/compare/apollo): Apollo sells reach: a contact database and the tooling to mail it, in one self-serve seat. We license a larger corpus, over 700 million contacts, and filter it harder before anything reaches your list. The bigger difference is what happens after the query, because in Apollo that is where your work starts.
- [GTM vs Instantly](https://trygtm.com/compare/instantly): Instantly is very good at the thing it is for: many mailboxes, rotated, warmed, sending a lot of email. If your motion is already designed and your problem is landing it, that is a strong tool. GTM includes a sending stack, but sending is the last step of something larger rather than the product.
- [GTM vs Smartlead](https://trygtm.com/compare/smartlead): Smartlead is infrastructure: connect a lot of mailboxes, rotate them, warm them, and manage the replies in one place. It is a component. GTM is the motion that would sit on top of a component like that, with the component included.
- [GTM vs lemlist](https://trygtm.com/compare/lemlist): lemlist has done multichannel properly for a long time, and their personalisation surface. Images, videos, dynamic landing pages. Is more expressive than ours. The difference is who decides what to send and when: in lemlist you design the cadence, in GTM the cadence is a default that an agent runs and a quality agent rewrites.
- [GTM vs Outreach](https://trygtm.com/compare/outreach): Outreach is built around a rep: their day, their sequences, their calls, their manager's forecast. It is a mature enterprise product and it assumes people. GTM assumes the opposite. That the top of the funnel should be worked continuously by something that does not have a day.
- [GTM vs Salesloft](https://trygtm.com/compare/salesloft): Salesloft is a mature platform for orchestrating what humans do across a deal cycle. That is a genuinely different product from ours, and the honest comparison is about where your constraint is rather than which tool is better.
- [GTM vs Artisan](https://trygtm.com/compare/artisan): Artisan and GTM are aiming at the same outcome from different architectures. Theirs is a single AI employee that does the whole job. Ours is a fixed roster of five, one per role, where only one of them can send and the reviewer cannot fix what it finds.
- [GTM vs 11x](https://trygtm.com/compare/11x): Both products are autonomous by design, and we agree with the premise: a human clicking approve on a draft the machine already wrote from evidence it already gathered is a delay, not a check. Where we differ is what stands between an autonomous system and somebody's inbox.
- [GTM vs HubSpot Sales Hub](https://trygtm.com/compare/hubspot): This is the least adversarial comparison on the site, because most of our customers use HubSpot and we push data into it. The question is not which one. It is whether HubSpot's sequences are enough for the top of your funnel.
- [Your first outbound motion, in one afternoon](https://trygtm.com/guides/first-outbound-motion): A complete first motion. ICP, keywords, sending domain, sequence and the two numbers to watch. Set up in about four hours and honest about what week one will look like.
- [How to write an ICP that a database can actually answer](https://trygtm.com/guides/icp-that-resolves): Why most ICPs return nothing or everything, and the specific rewrite that turns a paragraph into a filter with a real count behind it.
- [Cold email that gets replies, without the tricks](https://trygtm.com/guides/cold-email-that-gets-replies): The structural things that move reply rate. Relevance, brevity, a single ask, and the tactics that used to work and now actively hurt.
- [The deliverability checklist, in the order that matters](https://trygtm.com/guides/deliverability-checklist): Authentication, domain strategy, warmup, volume and list hygiene. Ranked by how much each one actually moves inbox placement.
- [Sending domains, senders and why the distinction matters](https://trygtm.com/guides/sending-domains-explained): What a sending domain actually is, why a sender is the unit reputation attaches to, and how many of each you need for a given daily target.
- [Which intent signals are worth acting on](https://trygtm.com/guides/intent-signals-that-work): A ranked list of buying signals by how well they predict a reply, and how to act on each without sounding like you have been watching.
- [Designing a sequence that changes rooms](https://trygtm.com/guides/sequence-design): Touch count, intervals, channel switching, and the stop conditions most sequences are missing.
- [LinkedIn limits, and whose account pays for exceeding them](https://trygtm.com/guides/linkedin-limits): The real ceilings on connection requests, messages and searches, why they are not documented, and how to run volume without losing the account.
- [Outbound compliance without a legal team](https://trygtm.com/guides/outbound-compliance): What CAN-SPAM actually requires, where GDPR changes the answer, and the five mechanisms that make compliance a property of the system rather than a policy nobody reads.
- [Running outbound for ten clients without mixing them up](https://trygtm.com/guides/agency-outbound-operations): Workspace isolation, sender assignment, per-client review, and the economics that decide whether client eleven is profitable.
- [Ideal customer profile (ICP)](https://trygtm.com/glossary/icp): The description of the kind of company and person worth selling to, precise enough that a list can be built from it.
- [Intent data](https://trygtm.com/glossary/intent-data): Observed behaviour suggesting a buyer is in market. Content consumed, roles hired for, topics engaged with.
- [Buying signal](https://trygtm.com/glossary/buying-signal): A dated, public event that makes an account more likely to buy right now.
- [Trigger event](https://trygtm.com/glossary/trigger-event): The specific thing that happened which makes today the right day to reach out.
- [Lead scoring](https://trygtm.com/glossary/lead-scoring): Ranking contacts by how likely they are to convert, usually as a single number.
- [Waterfall enrichment](https://trygtm.com/glossary/waterfall-enrichment): Asking several data providers in sequence until one returns a result, to raise coverage above what any single vendor holds.
- [Email verification](https://trygtm.com/glossary/email-verification): Checking that an address exists and will accept mail, before you send to it.
- [Data provenance](https://trygtm.com/glossary/data-provenance): The record of where each field about a person came from, how it was collected, and when.
- [Data retention](https://trygtm.com/glossary/retention): How long personal data may be kept before it must be deleted, and the rule that computes the date.
- [Suppression list](https://trygtm.com/glossary/suppression-list): Addresses, domains and profiles that must never be contacted again.
- [Opt-out](https://trygtm.com/glossary/opt-out): A recipient telling you to stop, in any form, which you must honour.
- [CAN-SPAM](https://trygtm.com/glossary/can-spam): The US federal law governing commercial email: no deceptive headers, a working opt-out, a physical address.
- [GDPR](https://trygtm.com/glossary/gdpr): The EU regulation governing personal data, under which cold B2B outreach needs a lawful basis and a notice.
- [Legitimate interest](https://trygtm.com/glossary/legitimate-interest): The GDPR lawful basis most B2B outreach relies on, and the balancing test it requires.
- [Controller vs processor](https://trygtm.com/glossary/controller-vs-processor): Whether a vendor decides the purposes of processing (controller) or acts on your instructions (processor).
- [Deliverability](https://trygtm.com/glossary/deliverability): Whether your mail reaches the inbox rather than the spam folder or nowhere at all.
- [SPF, DKIM and DMARC](https://trygtm.com/glossary/spf-dkim-dmarc): The three DNS records that let a receiving server verify mail claiming to be from your domain.
- [Domain warmup](https://trygtm.com/glossary/domain-warmup): Ramping volume on a new sending domain slowly, so receiving providers build a reputation for it.
- [Bounce rate](https://trygtm.com/glossary/bounce-rate): The share of sends rejected by the receiving server. Hard for permanent failures, soft for temporary ones.
- [Reply rate](https://trygtm.com/glossary/reply-rate): The share of contacted people who answer. The only top-of-funnel metric that survives contact with reality.
- [Positive reply rate](https://trygtm.com/glossary/positive-reply-rate): The share of replies that express interest rather than a refusal.
- [Meetings booked](https://trygtm.com/glossary/meetings-booked): The number the whole motion is actually for.
- [Conversion rate](https://trygtm.com/glossary/conversion-rate): The share of one funnel stage that reaches the next.
- [Total addressable market (TAM)](https://trygtm.com/glossary/total-addressable-market): Every company that could plausibly buy, before any filter for who will.
- [Sequence](https://trygtm.com/glossary/sequence): The ordered set of touches a contact receives, with waits and conditions between them.
- [Cadence](https://trygtm.com/glossary/cadence): The rhythm of a sequence. How many touches, on which days, over what span.
- [Multichannel outbound](https://trygtm.com/glossary/multichannel): Reaching the same person across more than one channel in one coordinated motion.
- [Connection request](https://trygtm.com/glossary/connection-request): A LinkedIn invitation, optionally with a note, and the scarcest resource in social selling.
- [Rate limit](https://trygtm.com/glossary/rate-limit): The ceiling a platform puts on how much you may do per account per day.
- [AI SDR](https://trygtm.com/glossary/ai-sdr): Software that performs the sales development role. Sourcing, writing, sending and handling replies, without a person doing each step.
- [Agentic workflow](https://trygtm.com/glossary/agentic-workflow): A process where a model chooses which tools to call rather than following a fixed script.
- [Model Context Protocol (MCP)](https://trygtm.com/glossary/mcp): An open protocol for giving an AI assistant tools and context from an external system.
- [Human in the loop](https://trygtm.com/glossary/human-in-the-loop): A design where a person reviews or approves machine output before it takes effect.
- [Warm vs cold outreach](https://trygtm.com/glossary/warm-vs-cold): Whether the recipient has done something that makes contact expected, or has not.
- [Personalisation](https://trygtm.com/glossary/personalisation): Writing to a specific person from something specific about them, rather than merging a field into a template.
- [Sender rotation](https://trygtm.com/glossary/sender-rotation): Spreading volume across several from-addresses so no single one exceeds a safe daily rate.

## Blog

- [Your deliverability should belong to you](https://trygtm.com/blog/deliverability-belongs-to-you): How verified sending subdomains, sender pacing and inbound replies work in GTM.
- [The real LinkedIn numbers nobody prints](https://trygtm.com/blog/the-real-linkedin-numbers): About 20–25 connection requests a day on a warmed account. 5–10 on a young one. Anyone promising more is spending your account to say it.
- [One preview, then go](https://trygtm.com/blog/one-preview-then-go): How we designed human-in-the-loop for outbound: one approval that means something, instead of a hundred that mean nothing.
- [Compliant cold Instagram DMs do not exist](https://trygtm.com/blog/instagram-cold-dms-dont-exist): Meta requires the other person to message first. Every tool selling cold Instagram outreach at volume is describing something that breaks.
- [Compliance as product](https://trygtm.com/blog/compliance-as-product): GTM sources leads itself, which makes us a data controller on purpose. Five features follow from that choice, and none can be retrofitted.
- [Five specialist roles and one coordinator](https://trygtm.com/blog/why-five-agents): GTM CEO coordinates the workspace while five specialists own sourcing, intent, outreach, copy and quality.

## Open roles

- [Senior Software Engineer](https://trygtm.com/careers/senior-software-engineer): Own large pieces of the product across a TypeScript monorepo: Next.js App Router, Postgres with row-level security, and a runtime of scheduled agent jobs.
- [Senior AI Engineer](https://trygtm.com/careers/senior-ai-engineer): Own the model layer: the agent loop, the ICP gate, tool-calling belts, and the evals that keep a model between a prompt and a person honest.
- [Junior Software Engineer](https://trygtm.com/careers/junior-software-engineer): Ship real product from week one in a TypeScript monorepo, with senior review on every merge and a codebase written to be read.
- [Junior AI Engineer](https://trygtm.com/careers/junior-ai-engineer): Work on real agent systems. Prompts, tools, evals. Under a senior AI engineer, in a product where model output has consequences.
- [Junior Cybersecurity Engineer](https://trygtm.com/careers/junior-cybersecurity-engineer): Help secure a product that holds other people's inboxes and contact data. RLS, secrets handling, webhook signing, and the audit trail.
- [Chief Marketing Officer](https://trygtm.com/careers/chief-marketing-officer): Own the story and the pipeline for a GTM company. Where the marketing is the first proof the product works.
- [Chief Legal Officer](https://trygtm.com/careers/chief-legal-officer): Own the legal posture of a company that chose to be a data controller on purpose. Privacy, channel terms, commercial contracts, and the entity itself.

## Contact

- Support: https://trygtm.com/support (support@trygtm.com)
- Waitlist: https://trygtm.com/join
- Docs: https://docs.trygtm.com
- App: https://app.trygtm.com