Build a competitor battlecard in HubSpot with Claude, from dated evidence

A battlecard goes stale because nobody owns the refresh. MarketBetter's Claude Code guide describes the usual cycle: a product marketer researches the competitor, the card is shared as a document, and it is out of date within 30 days, at which point reps stop trusting it. That 30 day figure is the vendor's own claim, not a measured one, but the pattern is familiar to anyone who has kept a card library.

Hubjoy's HubSpot guide adds the control that matters most: every battlecard needs an owner and a review date, and it should link to current product evidence. The fix is therefore two things, not one. A scheduled source of fresh evidence, and a visible date on each claim so a rep can tell a stale line from a current one.

Claude can do the drafting in minutes, as Claude Academy shows with a prompt that reads closed-lost deal notes and builds a card per competitor. What it cannot do alone is know what changed at the competitor this week. That is the data Linkeddit supplies.

Claude Academy's example asks Claude to search the web for competitor sites and reviews at the moment you ask. Linkeddit keeps a weekly record instead. On the test project, the brief for the week of 26 October 2026 covered 5 monitored competitors and 19 signals: 2 high priority, 9 worth watching and 8 low. Each signal has a category such as launch or messaging, a source name, a source link and a short note on why it matters.

Reviews are stored separately, as the review sites show them, with the site, rating and publication date. Linkeddit does not summarise or score them, so Claude reads the raw text and you can check it. Look at the dates before you quote one. The two Matomo Trustpilot reviews in the run were published in 2022 and were only stored in October 2026, so they are history, not news.

The run also shows gaps you should know about. Ten of the 19 signals carry no signal date, and the Capterra fetch for Matomo returned no results. A good battlecard says so. The prompt above tells Claude to mark undated items, so the card does not present them as new.

Keep the brief as text on the competitor's company record. HubSpot's help page lists notes as readable, creatable and updatable through the connector, so the card can live as a note where your team already looks, with no file to attach and no extra tool. The connector can read companies, deals and their notes, so the same note can be found by a rep before a call.

Hubjoy's structure is a good template for the content. For each frequent rival: the buyer situation where they are strong, where your offer differs, questions that reveal fit, proof you can show, and claims the team must not make without verification. Add one line from this week's signals and one from the stored reviews, each with its link and date.

If you want the evidence searchable in reports, Hubjoy suggests a few custom properties, such as competitor name and primary objection, with controlled options so one rival is not spelled three ways. HubSpot's page says the connector can read and create properties but not update them, so create them once in HubSpot and let Claude fill them.

Start with one record. HubSpot's own best practices say to update a single record before making bulk changes and to review every change Claude proposes before confirming. Bulk creates and updates through the connector are limited to 10 records at a time, which suits a small battlecard library anyway.

Keep claims traceable. Hubjoy warns that a competitor's website claim is not the same as a buyer's reason for leaving, and that notes filled in only after a loss bias the data. Label each line as buyer evidence from HubSpot or competitor evidence from Linkeddit, with a source link.

Do not publish a win-rate promise. Hubjoy's advice is to measure whether sellers use the guidance and whether the quality of competitive notes improves, not to assert a universal improvement. Writes made through the connector are attributed to both you and the Claude connector in HubSpot's audit log, so changes can be traced.