Account Research Brief
Walk into your next discovery already mapped — vendors, spend, stakeholders, signals, all cited.
A $16M managed cloud contract expires in 122 days — with only 50% renewal odds
| Contract | Expiry | Renewal odds | Annual value |
|---|---|---|---|
| 🎯 HCLTech — Managed Cloud | Sep 7, 2026 | 50% ⚠️ | $5.3M |
| Microsoft Azure / AI-PLM | May 14, 2027 | 85% ✅ | $6.3M |
| Accenture BI Ops (expired) | Dec 5, 2023 | Not replaced | $36.7M |
Overview
Your enterprise AEs need everything mapped before they walk into a discovery — vendors, IT spend, named stakeholders, recent SEC signals, two opening angles. This workflow pulls 30+ data points from HG Insights' firmographic, technographic, IT spend, FAI, contact, and SEC tools into one cited brief, in 90 seconds. Every claim sources back to a specific tool call.
Use cases
Pre-discovery for your AEs
Your enterprise AEs need intel before their first call with a prospect. This workflow surfaces 30+ data points in 90 seconds — firmographic profile, top tech-stack additions in the last 6 months, IT spend by category, named buying-committee stakeholders, and recent SEC-filing language about strategic priorities. Every claim cites the HG tool that produced it, so reps can defend the brief in a CRO review.
Account-plan kickoffs your team can defend
When your account team kicks off a quarterly plan, the brief replaces 'I think they use Salesforce' with HG technographic intensity scores, contract expiry dates from SEC filings, and named CIO/CTO contacts from FAI. The plan stops being a memory exercise and becomes a data exercise — and the QBR review actually trusts it.
View workflow prompt
# Account Research Brief
## Parameters
- `{{domain}}` *(required)* — Target company domain HG Insights uses for lookup. Example: `siemens.com`
## Purpose
You are an AE preparing for discovery or an account-plan kickoff with {{domain}}. Produce one brief that gives the AE everything to walk in already mapped: firmographic context, current tech stack with recent movement, IT spend posture, named stakeholders, strategic signals, and two outreach angles tied to live data points. Cite every claim.
## Process
1. **Firmographic profile** — `company_firmographic` for {{domain}}. HQ, employees, revenue, industry, parent/subsidiary, fiscal-year end.
2. **Technology stack** — `company_technographic` + `company_cloud_spend`. Top 10 vendors by intensity; flag products first-seen in the last 12 months as "recent signals." Note multi-cloud posture and any AI-observability tools (GenAI productionization signal).
3. **IT spend** — `company_spend`. Total IT spend, top 10 categories by dollar, and security spend as % of total IT (benchmark 8–12% for critical-infra; flag underinvestment).
4. **Buying committee** — `contact_search` for IT/tech decision-makers. Top 8 by seniority with title, location, LinkedIn. Group by budget owners (CIO/CTO) vs operational buyers (Engineering).
5. **Functional Area Intelligence** — `company_fai` to identify which department actually owns the dominant cloud workload — this is the *operational* buyer even when the CIO holds budget.
6. **Strategic signals** — `sec_filing_section` + `sec_full_text_search` for recent 10-K/8-K/proxy disclosures. Non-US filers: `web_search` against IR page + annual report. Surface 3-5 signals that change the buying environment (M&A, restructuring, leadership shifts, new initiatives).
7. **Contracts intelligence** — `company_contracts`. Flag any active contract within 12 months of expiry (highest-urgency displacement) and any expired-but-not-replaced category (whitespace).
8. **Outreach angles** — close with two specific, signal-tied opening lines. Each must (a) reference a named, dated event; (b) target a stakeholder by name + title; (c) explain *why it lands* in 2-3 bullets.
## Output Format
Markdown with these sections in order:
- `# {{domain}} — Account Research Brief` (header with data-as-of date)
- `## Section 1 — Firmographic Profile` (table)
- `## Section 2 — Technology Stack` (vendors table + recent signals table + cloud architecture bullets)
- `## Section 3 — IT Spend by Category` (totals + top categories table + security-gap callout)
- `## Section 4 — Buying Committee Map` (stakeholders table + FAI department breakdown + engagement strategy)
- `## Section 5 — Strategic Signals` (filing summary + "what these signals tell you")
- `## Section 6 — Targeted Outreach Angles` (two angles: signal + opening line + why-it-lands bullets)
- `## Appendix — Contracts Intelligence Summary` (table)
Cite every data point inline. HG tools first; `web_search` only when HG is sparse.
## Quality Checklist
- Every numeric claim cites its source (HG product or URL)
- Recent-signal section lists *date first seen* for any new tool
- Buying committee separates budget owners from operational buyers
- Both outreach angles target a *named* stakeholder, not a role
- Security spend flagged when under 5% (lean) or over 12% (heavy)
- No fabricated emails/phones; LinkedIn URLs only