Competitor Watch & Battlecard

On the schedule you choose, a research agent sweeps tracked competitors, writes a delta memo of only what changed, refreshes the sales battlecard, and updates competitor memory for you to approve.

Saves you ~3.2 h / week

What it installs

Agents 2

  • Competitive Research Agent

    A competitive researcher who sweeps tracked competitors, writes a delta memo of only what changed, refreshes the battlecard, and updates competitor memory.

  • Competitor Watch & Battlecard Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Competitor Watch & Battlecard quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 1

  • Sweep, diff, draft, self-check, approve

    Sweep the competitor surfaces, diff against memory, draft the delta and battlecard, self-check the sourcing and honesty bar, and hand off for approval.

Documents 2

  • Battlecard (living)

    The living, sales-ready battlecard the agent keeps current each run. Seeded here with one card per competitor; edit the rows and proof points to match your real positioning, and the agent maintains it from the sweep.

  • Competitor list & memory

    The competitors to track (and what to watch on each) plus the dated, append-only memory log the sweep diffs against.

Goals 1

  • No material competitor move goes unseen

    Every run catches the material competitor changes since the last sweep and turns them into a current, sales-ready battlecard.

Skills 3

  • competitors

    Research competitors honestly and in depth for positioning and sales enablement: profile each rival's product, pricing tiers, and weaknesses; mine G2/Capterra/Reddit reviews for recurring praise and complaint themes; go depth-over-surface (explain why differences matter, not just a feature checklist); and keep competitor data as a single dated source of truth. Adapted from coreyhaines31/marketingskills/competitors.

  • competitive-analysis

    Analyze competitive dynamics like a strong product leader: expand the competitive set to include the status quo and workarounds (≈40% of B2B deals are lost to 'no decision'), determine whether the real threat is features, distribution, or business model, find asymmetries rivals cannot copy, and avoid blindly copying competitor moves. Adapted from refoundai/lenny-skills/competitive-analysis.

  • competitive-battlecard

    Build a concise, sales-ready battlecard against a specific competitor: company overview, an honest us/them/winner comparison table, where-we-win with proof points, where-they-win with our counter, an objection-and-response table, landmines to plant, and win/loss patterns — scannable enough to reference live on a call. Adapted from phuryn/pm-skills/competitive-battlecard.

Schedules 1

  • Competitor sweep

    Runs the competitor sweep on the schedule you choose. ## Professional quality control Objective: complete the recurring Competitor Watch & Battlecard operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Open cited sources, verify that each decisive passage supports the claim, check freshness and provenance, seek disconfirming evidence, and distinguish fact from synthesis. Reject fabricated citations, one-sided conclusions, generic AI phrasing, filler, and confident narrative that outruns the evidence ledger. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Folders 1

  • Competitor Watch

Requirements

What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • Web search and fetch access for competitor research — The agent sweeps competitor sites, pricing, changelogs, blogs, and reviews through worker web search and fetch tools, and pauses for your approval before the update lands. If web tools are unavailable it halts rather than inventing pricing or features.
  • Browser access for JS-heavy or gated pages (fallback) — When a pricing page or changelog is JS-rendered or blocks plain fetches, the agent falls back to browser access to read the rendered public page; it only reads public pages and never logs in on your behalf.

Setup guide

How to Automate Competitor Tracking and Battlecard Updates

A practical guide to competitor tracking with an agent: scheduled sweeps, delta memos of what changed, a living battlecard, and approval on every update.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *



Takes a minute · no account needed

Install Competitor Watch & Battlecard and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.