At a glance
An account research brief should answer the campaign question you commissioned it to investigate. Ask for relevant business context, stakeholder responsibilities, existing relationships and a recommended next action, with sources and uncertainties visible. Use this guide to brief your researcher and assess the result with your sales team.
You’ve selected a priority account and commissioned the research. The document arrives with company history, revenue figures, executive names and recent announcements. Yet your team still can’t agree who to approach or what would make the conversation worthwhile.
A company profile helps you recognise an account. A useful research brief helps you decide what to do with it. It should connect the business context to a plausible buying problem, identify the people you need to understand and show which assumptions still need checking.
Require a decision trail before accepting the research
Our account-prioritisation approach connects the commercial objective, available evidence and delivery feasibility. Our experience-planning methodology then uses account insight to assess creative options against the brief. A commissioned research document should make that connection visible enough for your team to challenge.
Our recommended acceptance test is to take its main recommendation and trace it backwards through four questions: which customer decision does it support, which observation makes that decision relevant, what alternative explanation remains, and what would change the proposed action? A list of accurate facts can still fail this test if no one explains why they matter.
For an illustrative acquisition brief, an announced integration programme may justify investigating ownership. It does not establish that a new platform is required. The existing systems might already support the programme; the researcher needs to check before recommending a technology-led conversation. A useful research recommendation therefore identifies the responsibility to clarify and the evidence needed before proposing technology work.
If the document cannot resolve that question, it can still be a good deliverable: state the gap, the most suitable way to investigate it and the consequence for activation. Ask for revision when uncertainty is hidden or when the suggested campaign does not follow from the evidence. Do not reject honest unknowns simply because another provider offers a more confident narrative.
Tell your researcher what you need to decide
Before collecting material, define the question. Are you deciding whether to select the account, which use case to propose, whom to approach or what proof is missing before a meeting?
These are different assignments. A selection brief needs enough evidence to compare accounts. An activation brief needs a credible reason for contact and a route to a particular buying group. A proposal brief may need detailed constraints and evaluation criteria.
Write the decision at the top. For example: “Should we propose a workshop on integrating regional service operations, and which function should sponsor it?” This sets a useful boundary and prevents research from expanding into every available fact about the company.
Keep the brief short enough to use
| Brief section | What it should contain | What to avoid |
|---|---|---|
| Decision | The action under consideration and who owns it | A broad ambition to increase awareness |
| Account context | Relevant objectives, changes and constraints | A copied company profile |
| Problem hypothesis | Why a specific issue may matter now | An asserted need unsupported by evidence |
| Buying responsibilities | Known roles, influence and gaps | A title list presented as a confirmed committee |
| Relationship position | Existing access, introductions and perception | Assuming familiarity means support |
| Proposed play | Message, proof, channel and next action | Creative ideas disconnected from the problem |
| Evidence boundary | Sources, dates, contradictions and unknowns | A confidence score with no explanation |
Keep the main brief readable in a working meeting. Put longer extracts and source records in an appendix. The purpose is to enable challenge, not to force everyone to reread the entire research trail.
Separate facts, interpretations and questions
Use three explicit labels in the working notes. A fact is directly supported by a source: the business announced a regional consolidation. An interpretation connects that fact to your proposition: consolidation may create inconsistent reporting processes. A question identifies what must be validated: who owns harmonising those processes?
Watch what happens when research moves into copy. “This acquisition may create reporting challenges” can quietly become “your reporting is fragmented”. The second sentence sounds more confident, but the evidence hasn’t improved. Ask your writer to preserve the difference between a public fact and your interpretation of it.
HG Insights’ technology-install documentation distinguishes verification dates and installation locations. That kind of source detail illustrates why an account brief should preserve context rather than reducing evidence to “uses product X”.
Where sources disagree, retain the disagreement. A recent company page may conflict with an older database field. The brief should explain which source governs the current decision and why, or leave the point unresolved.
Turning account evidence into a useful first conversation
Consider a fictional service business that has announced two acquisitions. Its public materials emphasise consistent customer experience, while a current job advertisement asks for integration experience. A sales contact says regional teams still operate independently.
The fact pattern supports investigating integration as a priority. It doesn’t prove that the company has allocated a software budget or selected a delivery partner. The proposed play could be an operational workshop exploring how regional differences affect customer handoffs.
The brief would identify an operational sponsor as a role to verify, a technical reviewer as a likely contributor and the current sales contact as a possible introduction route. Its first action would be to validate ownership and relevance, not send a fully specified transformation proposal.
For that first conversation, a practical transition example and questions about implementation would be more useful than a generic product brochure. Your research has earned its place when it changes the evidence you bring or the question you ask.
Research relationships as carefully as organisations
Record who knows whom, the nature of the relationship and when it was last active. A historic meeting is different from a current sponsor. A friendly contact is different from someone who can introduce the team to the relevant function.
Ask sales and delivery colleagues what the account believes about your organisation. Existing customers may associate you with one narrow capability. New stakeholders may have no knowledge of successful work elsewhere in the business.
Edelman and LinkedIn’s 2025 study examines influence beyond the most obvious decision-maker. For the brief, the implication is a question to investigate: who needs useful evidence even if they don’t appear in the current contact list?
Avoid treating a missing profile as a missing role. Some relevant functions are difficult to identify publicly. Mark the gap and choose a legitimate introduction or research route rather than assigning responsibility to the nearest visible executive.
Turn the research into a campaign recommendation
A useful recommendation specifies the audience, proposition, supporting proof, channel, owner and next step. It also states what needs to be confirmed before activation.
For example, “create a personalised landing page” is an output. “Help the operational sponsor compare two transition approaches before an internal planning meeting” is a purpose. The second statement tells the team what the page needs to contain and whether a page is even the best format.
Link the play to your wider ABM content strategy. Reuse existing material where it answers the account’s question. Commission new material where a specific proof gap remains.
Keep the supporting sources accessible
For every material observation, retain a short source record: the claim, URL or internal reference, publication or conversation date, date checked, entity concerned and a note on what the source doesn’t establish. The campaign writer should be able to trace a statement without repeating the research from scratch.
Give sales conversations an appropriate internal reference and limit access to colleagues who need it. A researcher should be able to explain the evidence behind a recommendation without circulating private correspondence in a widely shared campaign brief.
Distinguish independent sources from repeated coverage of the same announcement. Five articles quoting one press release add distribution, not five separate confirmations. The ledger should point back to the original evidence where possible.
Record the strongest contradictory observation as well. If an account announces investment in a capability but a later statement says the programme is delayed, the brief needs both. Selective research can make an attractive play look more certain than it is.
Ask for a recommendation you can challenge
Use a short closing memo with four statements: what we know, what we believe, what we need to confirm and what we recommend doing now. Add an owner and the evidence that would change the recommendation.
For the fictional integration account, that might read: the acquisitions and public consistency objective are known; operational fragmentation is a plausible hypothesis; responsibility and project timing need confirmation; the next action is a sponsor-led discovery discussion.
A good brief gives each colleague something specific to challenge. Your account owner can question the relationship assumption; your delivery team can test feasibility; your content team can identify missing proof. That discussion tells you more about the research’s value than its page count.
When the next conversation resolves an unknown, update the memo and retain the earlier version. The value of the brief is the quality of the decisions it enables over time.
Review for actionability, not volume
Before approving the brief, ask a colleague to explain the proposed action without reading the appendix. If they can’t identify the problem, evidence and next step, the synthesis needs work.
Then challenge the strongest claim. Can it be traced to a source? Does the source support that exact wording? Is its date relevant? Does it describe the operating entity being targeted? This is especially useful for technology, financial and organisational claims.
Finally, set a review trigger. A new conversation, organisational change or contradictory source can alter the account plan. The brief should remain a working decision document rather than a static research deliverable.
Talk to ABM Logic about account research and activation when you need evidence that leads to a practical campaign choice.
