GTM skills for your coding agent

Rebuild an Apollo list on Cargo and price the two side by side before you move anything.

Rebuild a Clay table on Cargo — map every Clay enrichment column to its provider action, price the run before it happens, and keep the result as version-controlled code instead of a spreadsheet.

Rebuild a ZoomInfo list on Cargo and measure the coverage you actually lose or gain before the renewal.

Build a total addressable market list of companies filtered by industry, headcount, and geography.

Find B2B leads by job title, company, and keyword, and return them as a structured list.

Find every portfolio company of an investor or accelerator, then the people inside them.

Find the buying committee at a target account — every stakeholder matching a set of titles, seniorities, and departments.

Enrich a list of companies with firmographics — industry, size, geography, founding year, and headquarters.

Turn a LinkedIn profile URL into a full person profile plus a verified work email in a single call.

Resolve a person's LinkedIn profile URL from their name and company, with an identity-validation gate that rejects wrong matches.

Find a verified work email address from a person's name and company domain.

Verify a list of email addresses so you stop sending to bounces.

Cascade one lookup through several vendors in priority order, so a row the first source misses falls through to the next instead of being lost.

Find companies by the technology they run or the roles they are hiring for.

Watch a list of target accounts for the public events that mean someone is in market — hiring for the role you sell into, saying something new, or turning up in a detection feed, each with a date and a link.

Track which companies recently raised funding, with round, amount, and investors.

Detect which of your contacts have changed jobs, and where they went.

Research one company before a meeting and hand back a briefing — what it does, what it publicly says is hard right now, and who it names as competition, each line traceable to where it came from.

Score a list of companies against your ideal customer profile and rank them — every row gets a number, the reason behind it, and a tier, so the bottom of the list can be dropped before anyone spends time on it.

Keep every account scored and tiered against your written ICP by a deployed agent that re-scores as accounts arrive and as the ICP changes, writing the rationale back to the CRM.

Deploy an agent that holds email conversations with leads: a sending domain, a mailbox, native sendEmail and listEmailEvents on the agent, a native email trigger on reply and unsubscribe, and a heartbeat that checks thread status when nothing inbound happened.

One agent the whole team @mentions in Slack, sitting on top of your GTM repo and workspace: it answers from context, cadence and live runs, turns change requests into pull requests, and hands work to the other deployed agents only after a go in the thread.

Every call the team records is collected into the cadence layer each morning, scribed into a log entry, and — once a claim repeats — promoted into the context knowledge layer, as one reviewable pull request against your GTM repo. Nine recorders ship; a tenth is one adapter file.

Keep CRM accounts and contacts duplicate-free: audit company and person identity, run recurring deduplication plays directly on CRM models, merge safe exact matches, and route uncertain clusters to manual review.

Keep CRM accounts and contacts filled and refresh them when they go stale. The contact pipeline uses one enrichment play with three gated tools: Cargo-native Find Email, Cargo-native Find LinkedIn Profile from Email, and custom Contact LinkedIn Enrichment.

Every evening the GTM day is recapped into the cadence log and a digest is posted to Slack, as one reviewable pull request against your GTM repo.

Stand up your account universe as a deployed pipeline: an AI Ark company search shaped by your ICP, sized for free before it bills, then tiered A / B / C / disqualified by an agent that reads your rubric from the workspace context and web-searches the evidence the sourced row does not carry.

Every Monday last week's GTM work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull request per initiative — or one workspace pull request when there are none.