Write an account brief a teammate can use

An account brief should help the next person make a decision without repeating all the research. A page of company trivia rarely does that. A colleague needs to know why the account belongs in the segment, what evidence supports a relevant conversation, which assumptions remain untested, and what action makes sense next. Everything else competes for their attention.

Treat the brief as a handoff between two people with different jobs. The researcher is collecting and interpreting evidence. The person handling outreach is deciding whether and how to contact someone. A useful document lets the second person inspect the reasoning, correct it, or decline the proposed action. It should not force them to trust a summary they cannot trace.

Put the decision at the top

Start with the account name, its official website, the date researched, and the researcher's name. Follow those fields with a one-sentence recommendation: investigate further, ready for review, or exclude. Add a reason that refers to your segment criteria. “Public implementation service matches our target category; responsible practice owner still needs verification” is a usable recommendation.

Avoid beginning with a long corporate history. Founding dates, award lists, office counts, and mission statements belong in the brief only when they affect the decision. A company may have a fascinating origin story and still be irrelevant to the planned conversation. The header should tell a colleague what they can safely do with the document today.

Include a specific question the research was meant to answer. For example, “Does this firm appear to support implementation partners in our target region?” That scope makes a short brief honest. It also explains why the document contains evidence about partner services but no analysis of unrelated product lines.

Build a source trail people can follow

Use first-party sources when checking what a company says about itself: its service pages, product documentation, current job listings, newsroom, partner directory, and investor materials where applicable. Record the page title, exact URL, publication date if shown, and the date you checked it. A source without a retrieval date can look current long after the page changes.

As a concrete example of source discovery, Microsoft's investor relations annual-report archive organizes reports by year. A researcher examining a public company can use its equivalent archive to locate a dated report rather than relying on a search snippet. The existence of a report does not mean every statement in it applies to every team or buying decision.

Keep the claim narrower than the source. A service page can establish that a service is publicly offered. It does not establish current revenue, spare capacity, customer satisfaction, or an intention to purchase your offer. A job listing can establish that a role was advertised when checked. It cannot establish the complete staffing plan or the reason a position is open.

Separate facts, assumptions, and questions

Give these three categories their own short sections. A fact is something supported by an identified source. An assumption is your interpretation of what that fact could mean. A question is what you would need to learn before treating the interpretation as true. This separation prevents speculation from becoming personalized copy by accident.

Consider the difference between “The company lists a new regional implementation service” and “The company is struggling to generate regional demand.” The first may be verifiable on a dated announcement. The second describes a problem the company has not necessarily reported. It belongs under assumptions, if it belongs at all, and should not appear as a confident opening line in outreach.

Use confidence labels sparingly and explain them. “High confidence” should mean the specific fact is directly supported by a suitable source, not that the whole account is a good prospect. If sources conflict, show the conflict. A current service page and an older press release may describe different periods, or the company may simply have changed its offer.

A worked brief for a fictional account

Here is a hypothetical account, Northbank Systems, used only to demonstrate the format. The segment is regional consultancies with a named implementation practice. The decision is “further research.” The supporting fact is that an imagined official services page lists implementation work in the target region. In a real brief, the researcher would attach the actual page and date.

The next fact is that an imagined team page names a practice director. The assumption is that this director may influence commercial partnerships. The open question is whether partnership development sits with that person or with a central business team. The proposed action is to verify responsibility before selecting a recipient. No revenue estimate or inferred operational difficulty is necessary.

The brief's conversation angle could read: “Explore whether the practice considers introductions from complementary providers.” The draft question could be: “Who handles potential delivery partnerships for this practice?” That is a responsibility question, not a disguised claim that the firm needs help. If the official site already names the appropriate process, use that process instead.

Give every detail a purpose

For each item, ask what it changes. A regional office matters if your offer depends on local delivery. A technical certification matters if your service requires compatibility. A leadership appointment matters only if you can explain a legitimate connection to the conversation. Interesting facts that do not change account selection, recipient choice, or the next question can leave the brief.

Keep personal information proportionate to the business task. A public professional role may be relevant to choosing a contact. A person's family, private routine, or unrelated social activity is not useful account research. Building a connection from an irrelevant personal detail can make an otherwise reasonable message feel intrusive. Favor role-based relevance that a recipient can recognize immediately.

Set a research time budget appropriate to the decision. A short screening brief should not become an unpaid consulting report. If an essential fact cannot be found within the allotted effort, mark it unknown and recommend a next step. Continuing to browse without a decision rule often produces more detail without reducing the uncertainty that matters.

Make the handoff testable

Ask a teammate to read the brief and answer four questions: Why this account? Why this person or process? What is actually known? What should happen next? If they need a verbal explanation for all four, the brief is not ready. Rewrite the missing reasoning rather than adding more links or expanding the company overview.

The recipient should also be able to reject the recommendation. Add an exclusion reason field and a place to record corrections. If outreach discovers that a named person has changed roles, update the source record and the next action. Do not leave the old brief circulating while the correction lives only in a chat thread.

Assign an owner and a review date. Fast-changing facts, such as a contact's role or an open job listing, deserve a fresh check close to use. More stable background may need less frequent review. Choose the refresh schedule according to how much a stale fact would affect the message or decision, rather than applying one blanket expiry date.

Finish one before designing a library

Complete a single brief for an account you are already considering. Keep it to the fields that support the immediate decision, and preserve links in the same place as the claims they support. Then hand it to someone who did not do the research. Watch where they hesitate, what they question, and which sections they ignore.

Use that feedback to revise the template before producing dozens more. The best account brief is not the one with the most headings. It is the one a colleague can inspect quickly, use responsibly, and improve when new information arrives. That standard is concrete enough to test on the next account in your queue.