An Account Research Brief Before Every First Call
Walk into every first call already knowing the company, the person, and the angle — a one-page research brief built from your ICP, not a generic company summary.
A research brief isn't a company summary. It's the three things that change how you run the call.
Anyone can paste a company's About page. The useful brief filters everything through your offer: what's going on with them that you can help with, who you're talking to, and the one angle worth leading with. Stored ICP turns generic research into a brief aimed at a sale.
Showing up with a Wikipedia-level summary signals you did homework for everyone, not for them. Buyers can tell the difference in the first two minutes.
Research is only useful when it's filtered through what you sell and who you sell to.
The brief is a starting point, not a script. It gets you oriented fast so you can actually listen on the call instead of fishing for context.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~20 min first time · ~3 min per account after that |
| Best for | Founder or sales lead who runs their own calls — B2B services and agencies |
What this solves
First calls burned on questions public research could have answered — and briefs so generic they could be about any company.
The problem
You’ve got a first call in twenty minutes and you know almost nothing about the company. So you skim their website, glance at the person’s LinkedIn, and walk in with a vague sense of “software company, mid-size, seems fine.” The call opens with you asking questions you could have answered yourself, which burns the prospect’s patience and your credibility. Or you over-prepare — forty minutes of reading that leaves you with facts but no angle. Either way, you’re not walking in with the one thing that makes the call land: a reason this conversation is relevant to them right now.
The research isn’t the hard part. Aiming it is.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe researches across sources and assembles a brief — multi-step work that runs in Cowork
- Claude Projects — What you sell and who you sell to doesn't change account to account. A Project stores your offer and ICP so every brief is filtered through them automatically
How it works
You research a new account constantly, but your offer and your ideal customer are fixed. A Project stores those so Claude filters every company through what you actually sell — turning raw research into a brief aimed at a conversation.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “Account Research” or “Sales Prep” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
offer.mdandicp.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
offer.md
What you sell, in problem terms — the situations where you’re the obvious fit and the outcomes you deliver. This is what lets Claude spot a relevant angle instead of summarizing trivia.
Example: “We help B2B services firms stop losing deals to slow follow-up. We’re the fit when a team is growing faster than its process — leads slipping through cracks, reps re-keying data, no single view of pipeline. Outcomes: faster response, cleaner handoffs, forecast you can trust.”
icp.md
Who you work best with and the signals that someone fits — so the brief flags the relevant ones instead of treating every fact as equal.
Example: “Best fit: 20–200 employees, services or agencies, recently raised or expanding headcount. Signals worth flagging: new sales leadership, hiring reps, a recent funding round, public complaints about response time. Poor fit: pre-revenue, enterprises with entrenched systems.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before the call:
- The angle is specific to them. “They could use better software” is not an angle. “They just hired three reps but still run pipeline in a spreadsheet — that’s the response-time gap we close” is. If the angle would fit any company, send Claude back for the version that fits this one.
- Inferences are labeled. A confident-sounding claim about their priorities that’s actually a guess will embarrass you on the call. Confirm Claude separated what it knows from what it’s inferring, so you don’t repeat a guess as fact.
- It’s a page, not a dossier. If the brief is three pages, it failed at the job — which is to orient you fast. Ask for the tighter version. You want to walk in oriented, not buried.
Before you dial: does the angle match anything you already know that isn’t online? If a colleague mentioned this account, fold that in. Public research plus your own context beats either alone.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“I have a first call with [company] — here's their website [link or paste] and the person I'm meeting [name/title or LinkedIn]. Using `offer.md` and `icp.md`, give me a one-page brief: what they do, what's changed recently that's relevant to us, who I'm meeting and what they likely care about, and the single angle I should lead with. Flag anything you're inferring vs. confirmed.”
“Draft two discovery questions that open the angle you recommended without sounding like a pitch.”
A one-page brief with four labeled parts: what the company does in two sentences, the two or three recent changes that matter to your offer, who you're meeting and what they likely care about, and one recommended angle with the reasoning behind it. Confirmed facts and inferences are labeled separately. If it runs past a page or the angle would fit any company, it missed — send it back.
- It doesn't replace discovery. The brief gets you oriented; the call still has to find what public information can't.
- It only knows what's public plus what's in your files. A colleague's offhand comment about this account beats anything Claude can find — fold that in yourself.
- It doesn't write to your CRM. Logging the call and updating the record is a separate recipe (and worth doing — see Extra Credit).
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
offer.mdoricp.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The brief reads like a Wikipedia summary — your
icp.mdis too vague to filter with. Sharpen the signals (“hiring reps,” “new sales leadership”), name a poor-fit profile, and run it again. The brief is only as aimed as the ICP behind it. - A guess shows up stated as fact — the prompt’s last line does the work: “flag anything you’re inferring vs. confirmed.” If it’s missing the labels, ask: “Separate confirmed facts from inferences and label each.”
Extra credit
Small additions that pay back the next time you run it.
- CRM connector — if the account is already in your CRM, connect it so Claude folds prior notes and touches into the brief automatically. See the Connectors guide.
- Calendar connector — point Claude at tomorrow’s calendar and have it produce briefs for every first call on the schedule in one pass.
- Pair with call prep — feed the brief into the Call-Prep Dossier recipe to turn it into a full agenda when the meeting is bigger than a first touch.
“The goal of pre-call research isn't to know everything. It's to know the one thing that makes the call relevant.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Stored context turns research into aim. The reason generic research feels useless is that it’s unfiltered. An offer.md and icp.md mean Claude evaluates every fact against whether it matters to you — which is the difference between knowing about a company and knowing why to call them.
Label the guesses. The most dangerous output in sales prep is a confident inference you repeat as fact. Asking Claude to separate confirmed from inferred keeps you from walking into a call armed with a plausible-sounding wrong assumption.
Speed is the point. A three-minute brief you’ll actually run beats a thorough one you skip because there’s no time. The recipe wins by making good prep fast enough to do before every call, not just the big ones.
Who this is for
Founder or sales lead who runs their own calls in B2B services and agencies (5–100 employees).
The pain: Walking into first calls with a vague summary instead of an angle
The outcome: Every first call opens with one relevant angle and two discovery questions ready
Published June 15, 2026 · 0 views