Competitor research done once, used by everyone
Research and writingFounder and a small team
We asked Claude to compare how Mem0, Letta and Zep price a five-person team. It searched, read the pricing pages and wrote a table, about 35k tokens. Two days later a cofounder asked Codex nearly the same question.
How can my cofounder's AI agent reuse competitor research my agent already did?
Have the first agent save its result with complete_task and its sources, and ArcRoom hands it to the next agent through find_task with its date. Prices go out of date, so set an expiry setting with arcroom rule --idle-days and old answers drop out.
Also asked as: We keep paying our AI agents to redo the same competitor research. How do we stop? · How do I share AI research results across a small team? · Can Codex reuse research that Claude already did?
The first agent saves its result with complete_task, with the sources it used.
- Reused answer
- Saved answer
- Expiry rule
find_task → reuse (saved by priya, claude, 2 days ago)
Step by step
- The first agent saves its result with complete_task, with the sources it used.
- The cofounder's agent checks find_task and gets the table with its date.
- If the question is about something that changes often, like prices, the team sets an expiry setting so old answers drop out.
What the agent sees
find_task → reuse (saved by priya, claude, 2 days ago)
"Mem0: free tier + usage; Letta: …; Zep: …" · sources: 3 pricing pages
saved 35k tokensCompared with today's tools
Notion page + a Slack link
Save the comparison table to Notion and share it in Slack; the cofounder pastes it into Codex.
- Setup
- 0 min
- Ongoing
- ~5 min to file it, and the cofounder must know it exists
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 per person (npx arcroom init)
- Ongoing
- None
Notion is a better home for the table; ArcRoom lets the second agent find it without anyone knowing to look, though neither knows when pricing pages change.
Where it stops
Web facts go out of date and git hashes can't tell. Use arcroom rule --idle-days to expire them.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.