Why this matters
An SDR on your team spends forty minutes researching an account before a first call. Most of what they find is already in your CRM, in a call note nobody re-read, or in a support ticket from February. The rest is from the web, some of it three years old.
You are about to hand that job to an agent. Pause first. Run it like the hygiene pass and you will produce something worse, faster, at higher volume.
Everything this lesson uses came in the practice pack from the course page; if you have not downloaded it, do that first.
What you will be able to do
- Score account research on the fit test and name the factor that nearly disqualifies it.
- Explain the one decision in the brief that makes it safe to run.
- Say what counts as a source in your workspace, and what does not.
The factor that nearly kills this workflow
| Factor | Account research | Why |
|---|---|---|
| Volume | 5 | Every account, every quarter, and again before every first meeting |
| Judgment density | 3 | Assembling is mechanical. Deciding what matters is not. |
| Cost of being wrong | 5 | It goes to a customer, with your name on it |
| Specification cost | 3 | An hour to write the brief properly |
| Checkability | 1, unless you force it | A generated paragraph about a company has nothing to check it against |
A low Checkability score is a veto: by the fit test, this job should not be handed over at all. It passes for one reason: the brief manufactures checkability. Every claim carries a source line naming where it came from; anything without one is written as "unknown". That turns an unverifiable paragraph into statements you can each check in under a minute.
The move generalises, and it is worth more than the workflow: when a task fails on Checkability, do not abandon it and do not ignore the score. Change the output shape until it is checkable. You are not making the agent more accurate. You are making its output falsifiable.
What counts as a source
Decide up front what the agent may draw on, and name it in the brief. In order of trust:
- Your own supplied data. Here: accounts, contacts, opportunities, activities, product usage,
support tickets, call notes, QBR documents. Highest trust, usually half of a good brief. Cowork
reads, creates and modifies files only inside the folders you grant, so
10-data/is exactly the universe. - Documents you explicitly provide. A press release the customer sent, an RFP, a security questionnaire.
- Live web research, if you enable it. More below.
- Connectors, if authorised. Connectors are MCP servers wired to your tools. Gmail, Google Drive, Slack and a Zoom connector are the ones we can name; check what yours can actually read before you list it as a source.
Not a source, and this is the important line: the model's own recollection of a company. It will produce fluent, specific, plausible statements from nothing at all, and they sound exactly like the ones from your CRM.
The rule goes in the brief verbatim:
PERMITTED SOURCES
10-data/ (all files), and documents in 15-provided/.
<web research: enabled | not enabled>
Every claim in the output carries a source line: file or URL, plus the record id
or the section.
A claim with no source is not written as prose. It goes in the "unknown" section.
Do not use general knowledge about any company, product or person.
Browser research: an option with a cost
Claude in Chrome is a Chrome extension that lets Claude read pages, click, type, fill forms and move between tabs. It is in beta, free to install, available on all paid plans. Tasks launch from the Chrome side panel or from Cowork or Claude Code. It is officially supported on Chrome and may work on Chromium browsers such as Edge and Brave. It draws on your account's usage allowance, one pool shared across chat, Claude Code and Cowork.
Three honest things:
- It changes the failure mode, it does not remove it. A sourced claim with a URL is checkable, a real improvement. It is not the same as a true claim. Pages are stale, republished and wrong.
- It is a beta with its own setup. Everything in this module and in
LAB-07, the exercise sheet inlabs/LAB-07of your practice pack (start with its README), works without it. No browser? Fill the external-context section by hand, or mark it unknown. That is a legitimate finished state. - It costs allowance, from the same pool as everything else. Research across forty accounts is a triage decision first.
If you use it, one extra rule in the brief: the source line for a web claim is the URL and the date it was read. A URL with no date is a claim about a page that may no longer say that.
Try this now
Set up the research workspace, and make each choice on purpose.
- Put the CRM exports plus
notes/, all from thedata/folder of your practice pack, into10-data/. Includenotes/call-notes/andnotes/qbr/: the highest-value internal facts live there, unread since they were written. Leave out finance files and anything with pricing approval: whatever is in the folder can end up quoted in a draft that goes to a prospect. - Run the cheapest possible probe before writing any brief:
List every file in 10-data/notes/. For each: filename, size in lines, and the
first line verbatim. Then report which account_id or opportunity_id values
appear in each file. Do not summarise the contents. Do not write any file.
What you should see: an index of sixteen call notes and three QBR documents mapped to the
accounts they concern. You will need it in L7.3. It also shows what a summary would hide:
inconsistent filenames, one with spaces, .txt and .md mixed (documented in
data/DATA-DICTIONARY.md in your practice pack). If it starts
summarising instead, say: "Stop. Do not summarise. Only list filenames, line counts, first lines,
and the ids in each file."
Worth knowing: a file missing from that index is missing from every brief you write afterwards. Better to find out now than in a meeting.
What you keep
Two blocks at the top of 40-reference/icp-rules.md, which you start in the next lesson:
- Permitted sources, by name, with web research marked enabled or not enabled.
- The source rule: every claim carries a source line; anything without one goes to "unknown".
Check yourself
- Your manager says research is "low risk because it is only a draft". Answer using the two factors in the fit test that actually apply here.
- An account brief contains: "They recently expanded into the Nordics." What is the minimum you need before that sentence is allowed to exist, and what happens to it if you cannot get it?
- You have browser research enabled. A brief comes back with a claim sourced to a URL. Name two ways it can still be wrong.
Where this goes next
L7.2 writes the ICP as rules you can test and argue with, not adjectives.