Account research one rep did, reused by the next
SalesB2B sales team doing account research in Claude Code
Our AE Meera asked Claude Code to research Northwind Logistics before a first call: annual report, hiring pages, the tools in their job ads. It took about 40k tokens and produced a one-page brief. Six weeks later the expansion rep, Arjun, asked Codex for 'a quick read on Northwind' and it started from zero.
How can our sales reps reuse account research another rep's AI agent already did?
Have the first rep's agent save the brief with complete_task and its sources, and ArcRoom hands it to the next rep's agent through find_task with its date and author. Set arcroom rule --idle-days 60 so research nobody uses drops out. The brief lives in the playbook, not the CRM, so copy the final version to the account record.
Also asked as: Our reps keep paying an AI to research the same accounts. How do we stop? · How do I share AI account briefs across a sales team? · Can my AI agent see research a teammate did on this company weeks ago?
Meera's agent saves the brief with complete_task, with the pages it read.
- Reused answer
- Saved answer
- Freshness check
- Expiry rule
find_task → reuse (saved by meera, claude, 41 days ago)
Step by step
- Meera's agent saves the brief with complete_task, with the pages it read.
- Arjun's agent checks find_task first and gets the brief with its date and author.
- The team sets arcroom rule --idle-days 60 so company research nobody uses drops out instead of going quietly wrong.
- Arjun's agent only refreshes what has changed, like new job posts, and saves the update.
What the agent sees
find_task → reuse (saved by meera, claude, 41 days ago)
"Northwind Logistics: 1,200 staff, moving off on-prem WMS, hiring 4 data engineers" · sources: annual report, careers page
saved ~40k tokensCompared with today's tools
CRM account notes (Salesforce or HubSpot)
The rep pastes the brief into the account record, and the next rep pastes it back into their agent.
- Setup
- None
- Ongoing
- Copy-paste both ways, ~5 min per account, often skipped
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
The CRM is the right record, but Codex never reads it on its own; Mem0 would keep only the facts an LLM extracted from the chat, not the whole brief with its sources and age, and nothing expires it after 60 idle days.
Where it stops
Web facts can't be checked with git hashes, so expiry settings do the job. The brief lives in the playbook, not the CRM; copy the final version to the account record.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.
More in sales
- Proposals built from approved sectionsSales engineers writing proposals in a git repo of Markdown templates
- RFP answers reused, but only while they're trueMid-size SaaS team answering security questionnaires and RFPs with Claude Code
- Call prep that builds on the last callAccount executive running a five-call enterprise deal