competitor-teardownlisted

# Competitor Teardown ## Core principle Evidence in, actions out. Every claim in your output carries a date and a source URL taken from the trace report. Never fill gaps from your own knowledge of the company — plausible training-data stories about "how X grew" are exactly the thing this workflow exists to replace. Report or nothing. ## Step 0: Check the tools Look for the Tracetify MCP tools: `search_reports`, `read_report`, `start_trace`, `get_trace`, `unlock_report` (clients may prefix them, e.g. `mcp__tracetify__search_reports`). **If they are missing, print this setup guide and stop:** ``` claude mcp add tracetify -e TRACETIFY_API_KEY=ttfy_... -- npx -y tracetify-mcp ``` - Create a key at https://tracetify.com/dashboard (AI & MCP page — sign-up takes an email, no card). - Reading any report that has already been traced is free; only fresh traces draw credits. Do NOT attempt the teardown from web search or memory instead. A teardown without trace data is a guess wearing a suit. ## Step 1: Aim You need the competitor's domain. If the user hasn't said where their own product stands, ask one question: pre-launch, just launched, or already has traction? The stage decides which slice of the competitor's history to mine. What a product did at 500 visits a month is usually copyable from zero; what it does at 500K rarely is. Copy the launch-stage moves, not the current-stage ones. ## Step 2: Free first — spend only with consent Call `search_reports` with the doma