The standard B2B sales motion has reps spending 90 minutes researching an account before they reach out. Most of that time is opening browser tabs, copying paragraphs, and trying to remember what the ICP looks like. AI compresses it to 10 minutes — but only if you set up the workflow correctly. Here's exactly how.
Most reps treat Claude like a research analyst they're meeting for the first time: "Here's a URL, tell me about this company." The output is a generic Wikipedia-style summary. Useful as a refresher; useless as a sales tool.
The shift is to treat Claude like a research analyst who works for your company. Someone who knows your ICP, your value proposition, and what "good fit" looks like. The brief they produce reads completely differently — it's not "what does this company do" but "why does this company match our ICP, what signals of timing exist, and what would resonate in outreach."
The difference between those two outputs is one document and twenty minutes of setup. Let's walk through it.
Create a Project called "Account Research — [Your Company]." Load these into the knowledge base:
1. Operational ICP definition. Not a tagline — the actual 15–25 structured fields you care about: company size, industry, growth signals, tech stack patterns, etc.
2. Buyer persona docs. Who you're typically selling to. Title patterns, pain patterns, what they care about, what they ignore.
3. Three to five anonymized winning briefs. Actual research briefs that led to closed deals. The AI learns what "good" looks like from examples.
4. Your value proposition + differentiated positioning. Two paragraphs.
System prompt:
You are an account research analyst for [Company]. We sell [what we sell] to [who]. When researching an account: 1. Verify fit against the ICP fields in the knowledge base 2. Identify signals of timing (recent hires, funding, product launches, churn signals, regulatory changes, leadership changes) 3. Identify the likely buyer persona and what they care about 4. Surface what we'd say in outreach — specifics from the research, not generic value-prop language 5. Flag anything that suggests this is NOT a fit so the rep can disqualify quickly Output format: 1-page structured brief (sections: Fit · Timing · Buyer · Angle · Risk). If a key data point is missing, write [Unknown: source needed] rather than guessing.
For each account, pull together:
— The company URL
— LinkedIn URL of the likely buyer (or 2-3 candidates)
— Anything recent from a news search ("[Company] funding", "[Company] hires CRO")
— Their most recent press release or blog post if findable
Drop them as URLs into a new chat inside the Project.
Claude with web search: If you're on Claude Pro or Team, web search is built in. You can just paste the company name + URL and Claude will pull the rest. If you're on Free, paste the page content directly.
Once you've used this workflow manually for ~20 accounts and you trust the output, the next step is to wire it directly into your sales engagement tool (Outreach, Salesloft, Apollo). The brief gets generated automatically when an account moves to "prospect" stage, drops into the rep's queue, and they review rather than create. This is what Treetop typically builds during the Outbound Intelligence phase of an Implementation engagement.
One sentence:
Research [Company Name] using the URL [url] and the LinkedIn profile [url]. Use the standard brief structure. Flag any data points you can't verify.
Claude returns a structured brief. Roughly 1 page, organized exactly the way your team has agreed to read.
This is the only manual work left. Read the brief. Verify:
— Two specific claims about the company. Open one tab, check one fact. If wrong, the rest of the brief is suspect.
— The "Angle" section. Is it specific, or did Claude default to generic value-prop language? If generic, ask Claude to rewrite using only specifics from the research.
— The fit verdict. Trust it cautiously — if Claude says "strong fit" but something in the brief contradicts that, dig in.
Then tag with priority (A/B/C) and route to the right rep. Total time so far: ~8 minutes.
The brief needs to live somewhere the next workflow can read it. Three options, in order of how scalable they are:
Manual paste into CRM activity note — fine for early days.
Save to a shared knowledge base or Notion — better once you have 50+ accounts in motion.
Wire to CRM via Zapier or native integration — best, but requires a real workflow build.
The point: don't let the brief die in a Claude chat. The whole compound of AI in sales is that this brief becomes input to the next workflow (sequence personalization, call prep, reply triage). Treat it as data, not a one-off output.
1. No ICP in the Project. Without it, Claude returns generic summaries. The whole differentiation of this workflow is using YOUR ICP.
2. Treating Claude output as truth. Especially on recent events, financials, and specific people. Verify two claims per brief. Always.
3. Skipping the "Angle" section. The whole reason to do research is to know what to say in outreach. If your brief format doesn't force that synthesis, you're just doing AI-flavored Wikipedia.
4. Researching companies that aren't qualified. AI research is so cheap that reps will start researching everything. Build the disqualification step into the prompt — "if any of these conditions, output DISQUALIFY: [reason]."
5. Not closing the loop. The reps need to feed back: which briefs led to good first calls? Which were misleading? That signal goes back into prompt refinement. Otherwise the workflow stays at its day-one quality forever.