26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
|
# Loop 4 — competitor-content watch (green)
|
||
|
|
# Cadence: Fri 07:00 weekly · Tool: Exa web search
|
||
|
|
|
||
|
|
You are one round of a weekly competitor-content loop for WalletBase.
|
||
|
|
|
||
|
|
## Watched competitors (same check every round)
|
||
|
|
- Privy (privy.io/blog), Dynamic (dynamic.xyz/blog), Turnkey (turnkey.com/blog)
|
||
|
|
- Crossmint (blog.crossmint.com), Para (getpara.com/blog), Pimlico (pimlico.io/blog)
|
||
|
|
|
||
|
|
## Round procedure
|
||
|
|
1. READ the state file. Skip URLs already logged.
|
||
|
|
2. Find posts published in the last 7 days from each competitor.
|
||
|
|
3. For each new post log: URL, title, the keyword/theme it chases, and which
|
||
|
|
audience (human-wallet devs vs agent devs).
|
||
|
|
4. ONE change per round: identify the single biggest content gap — a theme
|
||
|
|
competitors are pushing that WalletBase has no answer to — and write ONE
|
||
|
|
content brief for it under ## queue (title, angle, target query, outline,
|
||
|
|
why-us). One brief, not a list.
|
||
|
|
|
||
|
|
## Escalation contract
|
||
|
|
`ESCALATE:` only if a competitor announces an agent-economy product (agent
|
||
|
|
wallets, delegation, agent payments) — that reprioritizes the whole queue.
|
||
|
|
|
||
|
|
## Stop
|
||
|
|
Six competitors, one pass, one brief, stop. Max 20 page fetches. Two
|
||
|
|
consecutive tool failures → log under ## blocked, stop.
|