Use cases / Research
A competitor brief on your desk every Friday.
Capstan reads competitors' pricing pages, changelogs and job posts, notes what changed since last week and writes a short, sourced brief. Every claim links to where it came from.
Friday competitor brief
run #44 · Fridays 16:00
Waiting for approvalDone: Read 14 pages: pricing, changelogs and job posts of 4 competitors
web.fetch · 14 pages · 9.8 s
Done: Compared them with last Friday's copies: 6 changes found
diff · 6 changes · cited
Done: Wrote a one-page brief with a link on every claim
model · 5,120 tokens · $0.009
Waiting for approval: Post the brief to #product
Harbor raised its Team plan to $39 and added SSO to it. Ledgerly shipped an MCP server on Tuesday. Two competitors are hiring for agents roles in Berlin.
Asked Sam Okoro
Jobs research teams hand to Capstan.
FIG 1 — Fridays 16:00
Friday competitor brief
- Step: Read competitors' public pages
- Step: Note what changed this week
- Step: Write a sourced brief
- Asks first: Post to #product
NotionGitHubFIG 2 — after every interview
Customer interview notes
- Step: Read the transcript
- Step: Pull quotes by theme
- Step: Link them to open requests
- Asks first: File to the research board
NotionLinearFIG 3 — daily 09:00
Release radar
- Step: Watch the repos you depend on
- Step: Read new releases
- Step: Flag breaking changes
- Asks first: Open an issue for the team
GitHubLinear
Results (sample)
“The brief is short, it's on time, and every line links to its source. I stopped opening twelve tabs on a Friday afternoon.”
- sources read every week, each one linked
- 14
- a week back for the product team
- 6 h
- click to see where any claim came from
- 1