--- name: account-research-brief source: https://app.decimal.ai/s/account-research-brief@1/SKILL.md source_sha256: 9db5f99117dc --- # Account Research Brief The one-page dossier an SDR assembles about a target account *before* the first touch. Base models, asked to "research this account," default to a rambling company-overview paragraph — founding year, mission statement, product list, headquarters — most of which never changes how you'd open a conversation. A research brief is not an encyclopedia entry. Its job is to surface only what makes *this* account worth contacting *now*, in a form you can act on in thirty seconds. Compile the brief as these six fixed fields, in this order. ## 1. Firmographics The structural facts that shape the pitch: employee count / size band, industry, geography or markets served, business model (B2B / B2C / marketplace), and funding stage or ownership if relevant. Nothing else. - Keep only facts that change *how you'd sell*. Founding year, mission statement, and the full product catalog are overview filler — cut them unless one directly implies a pain or a fit. - One line each, not prose. ## 2. Technographic signals The tools, platforms, and technical choices the account uses that indicate fit, pain, or buying context — the CRM they run, the cloud they're on, a framework in their job posts, a competitor's product they've adopted. - Each signal must carry a "so-what": name the tool *and* what it implies for your pitch ("runs a legacy on-prem stack → migration pain you address"). A tool name with no implication is noise. - If you have no technographic data, write `Technographics: UNKNOWN` — do not invent a stack. ## 3. Recent trigger events Time-bound events in the last ~6–12 months that create a reason to reach out now. Scan for these categories: - **Funding / financing** — a raise, new debt, an IPO or acquisition offer. - **Leadership change** — a new executive in a role that owns your problem (new CFO, CISO, VP Eng); new leaders reset budgets and tooling. - **Expansion** — a new market, region, office, or product line. - **Product / launch** — a major release, platform shift, or pricing change. - **M&A** — an acquisition they made or one they were acquired into. - **Headcount** — a hiring surge in a relevant function, or conversely layoffs / restructuring. - **Regulatory / compliance** — a new certification effort, audit, or rule that now applies. - **Public results** — earnings, a metric they cited publicly, a viral moment, a bad review trend. Rules: - List only events you have evidence for, each dated or time-anchored ("Q2, announced a Series B"). Never fabricate a trigger — a plausible-sounding event you can't source is worse than none, because outreach built on it collapses on contact. - If nothing recent is known, write `Trigger events: none found` rather than manufacturing one. ## 4. Likely priority pains Two or three pains the account probably feels *right now*, inferred from the fields above — not a generic list of problems every company in the industry has. - Tie each pain to a specific signal or trigger ("just entered the EU → contract volume that now has to meet GDPR"). A pain with no thread back to the evidence is a guess. - Frame as the buyer's problem, not your feature ("can't onboard new hires fast enough", not "needs our onboarding module"). ## 5. "Why now" hypothesis Exactly one line linking a trigger → a pain → your relevance. This is the spine of the outreach: why this account, why this moment. - Format: *"They [trigger], which means [pain], and that's exactly when [your value] matters."* - One sentence. If you can't write it, you don't yet have a reason to reach out — say so. ## 6. Personalized opener hook One sentence the SDR can drop straight into the first line of a cold email — an observation so specific it could only have been written for this account. Draw it from the strongest trigger. - It must reference a concrete detail from the brief, not a pleasantry. "Saw you just opened a second distribution center" — not "I hope you're doing well." - Hand off one ready line, not a paragraph. The email itself is a separate step. ## Discipline that separates a brief from an overview - **So-what filter.** Every line must change how you'd approach the account. If a fact doesn't move the pitch, it doesn't belong in the brief — length is not thoroughness. - **Mark gaps, don't fill them.** Missing data is `UNKNOWN` or `none found`. Fabricated firmographics or invented trigger events are the one unrecoverable error: they make the outreach factually wrong the moment the prospect reads it. - **Everything threads to outreach.** Technographics imply a pain; a trigger drives the "why now"; the "why now" produces the opener. A brief where the fields don't connect is just a fact dump wearing a template. ## Worked shape Inputs: a 300-person logistics-software company; runs a self-hosted legacy ERP; announced last quarter it's expanding into Mexico and hired a new VP of Operations. A conforming brief: > **Firmographics:** ~300 employees; logistics SaaS; US-based, now entering Mexico; B2B. > **Technographics:** Self-hosted legacy ERP → integration and scaling pain as they expand. > **Trigger events:** Q1 — announced Mexico expansion; new VP Operations hired same quarter. > **Likely pains:** Cross-border logistics complexity; a new ops leader under pressure to > show early wins; legacy stack straining under new volume. > **Why now:** They just entered Mexico under a brand-new VP Ops, which means their legacy > stack is about to hit cross-border volume it wasn't built for — exactly when a modern > logistics layer matters. > **Opener hook:** "Saw you're expanding into Mexico this quarter — usually the moment a > self-hosted ERP starts creaking under cross-border volume." Notice: no founding year, no mission statement, no full product list. Every line either changes the pitch or feeds the opener, and the "why now" ties the trigger to the pain to the reason to call.