Not all company briefs are useful. A CRM note that says "SaaS company, 50 employees, fundraised in 2023" tells a sales rep nothing they couldn't get from a 20-second Google search. A brief that tells them "recently expanded into EMEA, has open SDR roles in London, just migrated off Salesforce, and their Head of RevOps posted about pipeline quality two weeks ago" — that's something they can use. The difference between those two isn't how much data you have. It's what you've synthesised it into.
Good intel briefs have a specific anatomy. There's a company overview layer that covers the basics — stage, size, sector, primary product — in under 100 words. There's a signals layer that pulls recent triggers: hiring patterns, technology changes, funding events, news mentions. There's a contact layer that maps the buying committee relevant to your ICP. And there's an action layer that translates the signals into specific conversation angles — not generic talking points, but things a rep can reference in the first 60 seconds of a call that make it immediately clear they've done their homework.
The full article will show what each of these layers looks like in practice, with real examples of what gets written into each HubSpot property field when the Intel Engine runs. It will also cover the failure modes — briefs that are too long to scan, briefs that are too generic to be useful, briefs that are technically accurate but commercially irrelevant — and how to design the research logic to avoid them. If you're thinking about building an intel layer into your CRM, this is the spec to start from.