Systematized competitor-video analysis pipeline using AI tools and saved collections

Opens by pre-empting the obvious objection ('sounds like a nightmare') to lower resistance, then immediately pivots to the method as the payoff. Middle delivers a numbered, tool-specific workflow (folder → save → paste → analyze → extract) that makes the process feel replicable and low-effort. Closes with four concrete AI prompt categories and a DM-gated CTA that gates the full setup behind a keyword reply.

Keyword-trigger DM CTA: viewer types a single word ('method') in comments to receive the creator's exact setup and prompt list , lowers friction to near-zero and drives comment-section engagement signal simultaneously.

- Open by quoting a real objection from your comments verbatim, then immediately reframe it with 'the truth is' + a counter-claim in the same breath - Use the phrase 'I have a method' as a bridge between the objection and the tutorial , it signals structure without revealing it yet, sustaining curiosity - Name your specific tools (Claude, Notion, TalkScript) rather than generic categories; tool-specificity reads as credibility and makes steps feel actionable - Structure the instructional middle as a numbered list of 4 or fewer items; each item should be a single imperative sentence a viewer could execute today - Frame the AI prompt categories as questions you 'ask' the tool, not features the tool has , keeps the human as the agent, which is more relatable to non-technical audiences - Gate the full resource behind a one-word comment keyword; this converts passive viewers into comment-section engagers and gives the algorithm a signal spike - End with a self-deprecating physical detail ('my sweatshirt is inside out') after the CTA , it resets the tone, makes the creator feel human, and rewards viewers who watched to the end