ABM account brief
Builds a target-account research brief for ABM plays by merging internal history from GBrain (prior touches, closed-lost context, existing relationships) with external signals (news, hiring, tech stack, filings). Use when the user mentions account research, ABM targets, "brief me on this prospect," territory planning, or prepping outbound to a named account.
When to run
- "Brief me on Meridian Industries" / building a target-account list
- Before sequence launch to a named account; territory planning
GBrain scopes
- CRM: any prior opportunities (won/lost with reasons), contacts, activity history
- Email + notes: past threads and meeting records with the domain
- External sync: news feeds, job postings, tech-stack signals, public filings where connected
Workflow
- Internal archaeology first: have we touched this account before? Surface prior deals with outcomes and stated loss reasons, dormant relationships, and any employee who used to work there or knows someone who does. The warmest path is usually internal and forgotten.
- External current-state: what the company does, size/segment, recent news, funding, leadership changes, relevant hiring (roles that signal our problem-space), stack signals.
- Hypothesize the wedge: which of our use cases their current state most plausibly needs, stated as a testable hypothesis with the supporting signals — not as fact.
- Map likely stakeholders by role for this play; note existing relationship paths.
- Draft three research-grounded opener angles referencing specific signals — angles, not sequences; the rep writes the words they'll own.
- Cite every claim; separate internal-record facts from external-signal inferences.
Guardrails
- Autonomy: L0. Research and drafting only; never contacts the account.
- Personal-data discipline: professional signals only — roles, public statements, company events. No scraping personal socials; no inferred personal attributes.
- Closed-lost context is for strategy, never for "last time you said" openers — flag it as internal-only framing.
Output
Account brief: internal history block → current-state snapshot → wedge hypothesis with signals → stakeholder map → three opener angles. Batch mode: ranked brief set per territory.Eval fixtures
- Set: 20 sandbox accounts with seeded internal histories (7 with prior lost deals, 4 with dormant relationships) and controlled external corpora.
- Rubric: internal-history recall (all seeded paths found); fact vs. inference labeling; wedge hypothesis grounded in ≥ 2 signals; zero personal-attribute inferences.
- Ship gate: internal recall 100%; labeling errors 0.
MORE SKILLS
GTM Engineering & Marketing Ops · L0
Competitor diff watch
Monitors competitor websites, changelogs, pricing pages, and sitemaps for changes and produces a weekly diff digest — new pages, messaging shifts, feature launches, pricing moves — with before/after evidence. Use when the user mentions competitor monitoring, competitive intel, "what did [competitor] just launch," pricing change alerts, or tracking competitor content strategy.
GTM Engineering & Marketing Ops · L2
ICP lead scorer
Scores inbound leads and accounts against the written ICP definition with a stated reason code per score — firmographic fit, use-case signal, engagement quality — and routes by band. Use when the user mentions lead scoring, ICP fit, inbound qualification, MQL routing, "is this lead any good," or wants the inbound queue prioritized.
