AIDiveForge — Workflow Pack Implementation Guide

Weekly Competitor Update Brief

Build a source-linked competitor update with a clear separation between facts and interpretation.

Difficulty: Intermediate Tools: 3 Updated: October 17, 2026

Research Large Language Models Writing Tools Productivity

Tools Required

#	Tool	Role	Website
1	Your web browser	Collect first-party source pages	https://www.mozilla.org/firefox/
2	Your AI assistant	Draft the evidence-linked brief	https://chatgpt.com/
3	LibreOffice or your document editor	Review and save the final document	https://www.libreoffice.org/

In This Guide

1Overview 2Requirements 3Steps 4Worked example 5Acceptance checks 6Limits 7Suggested tools

# Weekly Competitor Update Brief

Build a source-linked competitor update with a clear separation between facts and interpretation.

1Overview

A one-page brief, evidence table and next-week watch list.

2Requirements

Use an assistant, a browser and a document editor. No API key or X Premium subscription is required for the manual workflow.

3Steps

1. 1. Choose the competitors, week and decisions the brief should inform; write those at the top of the evidence sheet.

2. 2. Collect current first-party announcement, pricing and documentation URLs. Record retrieval dates and exact plan scope.

3. 3. Have the assistant extract only supported changes into a fact table with a source for every row.

4. 4. Compare with the previous brief and label implications as interpretation. Preserve unknowns and contradictory evidence.

5. 5. Review the cited pages, then save the brief and watch list in your existing workspace; distribute only after approval.

4Worked example

6. Input

```text Week: October 12–16. Competitor A release note: CSV export added October 14. Competitor B pricing page: no dated change notice. Previous brief: A had no CSV export. ```

7. Expected result

```text Change: A added CSV export on October 14 (release note). B: no supported change established from the supplied pricing page. Implication: reassess the export gap for customers who need CSV. Watch next week: verify A’s plan availability. Distribution: draft pending review. ```

5Acceptance checks

Every change has evidence and a date; B is unknown rather than unchanged; facts and implications remain separate.

6Limits

Web research and final review are manual unless you build and test a separate integration. API access uses each provider’s own developer console and billing; consumer subscriptions do not establish API access.

7Suggested tools

Your web browser: Collect first-party source pages
Your AI assistant: Draft the evidence-linked brief
LibreOffice or your document editor: Review and save the final document