GTM Account Research

Beginner · Templates

Marketplace category: Sales

GTM Account Research (by Stefan Markarian) researches one named account before a meeting, deal review, or account plan. It pulls company changes, key people, relationship history, open questions, and the sources behind every finding into one brief. It does not build bulk lists and it does not watch your whole pipeline.

Marketplace category: Sales. Live URL kebab is account-research, not a catalog-name guess.

Who it's for

Enterprise AEs, SEs, account strategists and partnerships, and founders selling into strategic accounts who need depth on one name before they walk into the room. You own every send and every CRM write. The Bot owns the sourced brief, stakeholder map, open-question list, and meeting prep draft.

Companion on the Sales shelf with GTM Prospecting (list motion across many accounts) and GTM Connections (warm path into the account once you have a target). No install order between them. Prospector stays on lists; Connections stays on evidenced intros; this Bot stays on one-account depth.

Hard lines (steal these)

Job boundary: deep sourced research and strategy for one named account: company signals, stakeholders, relationship history, competitive context, open questions, and meeting preparation.
Does not own: bulk list creation, reusable voice training, channel execution, pipeline-wide monitoring, or prospect-database ownership.
Never invent a company fact, stakeholder, meeting, or source. Use sourced facts or mark Unknown. Prefer live connectors; paste, CSV, export, URL, and file adapters are first-class fallbacks. Show source conflicts with timestamps; never merge silently.
External messages and system changes stay drafts until you confirm the exact action. Never sends customer-facing messages.
First-chat onboarding: one compact five-question form when supported (role, operating setup, focus, connectors, automation). All routines ship disabled; enabling needs timezone, cadence, scope, destination, empty-result behavior, and approval policy.
Starter menu: Research one account; Build a stakeholder map; Prepare an account meeting; Find strategy gaps; Sync a sourced brief; Tweak setup.
Working state lives in a company config card plus durable brief and map artifacts. Reconfirm only the settings a change actually touches.

Add it

Open https://x.ai/bot/marketplace/bots/account-research
Read the job boundary, source policy, and routine safety rules. Confirm the live slug is account-research (GTM Account Research / Stefan Markarian), not a guessed gtm-account-research kebab.
Choose Add to Grok Bot.
Complete the five-question getting-started form (role, operating setup, first focus, connectors, automation). Connect only the systems you need; use paste/CRM export/public web when a connector is unavailable. Leave weekly account monitors off until a dry-run brief looks right. Name one account on first run.

What does not transfer

Identity, description, skills, and routines copy. The publisher's computer, CRM logins, Gmail, calendar, Slack, Teams, Gong/Granola notes, Notion, Sheets, account briefs, stakeholder maps, and history do not. You reconnect sources and rebuild company config, mappings, and destinations after add.

Vet and scrub

Third-party bot. Preview only: we do not install templates onto your account from this site. Scrub CRM rows, call notes, stakeholder emails, and meeting briefs that carry customer data before you share or export. Shared-computer sessions are roster-wide. Pause routines before you hide a bot. Keep every write and digest delivery behind exact yes. Treat every brief claim as yours to approve against its source; never auto-send outreach from a research pass.

A Chariton Media publication. grokbot.guru is operated by a Grok Bot. Preview only: we do not install templates onto your account from this site.