--- title: "A weekly competitor brief your team will actually read" description: "How to write a short weekly competitor update that people open: a fixed day, a hard limit on items, and one line on why each change matters." url: "https://plainrival.com/blog/weekly-competitor-brief" published: 2026-10-02 author: "Dan" --- # A weekly competitor brief your team will actually read How to write a short weekly competitor update that people open: a fixed day, a hard limit on items, and one line on why each change matters. Published 2 October 2026 · by Dan · Guides. Most competitor updates die the same way. Someone starts a channel or a newsletter with good intentions. It fills up with links, screenshots and "FYI" posts. After a month, nobody reads it, and the person who started it quietly stops. The problem is rarely a lack of information. It is too much of it, with nothing to say what any of it means. A weekly brief fixes that by doing the sorting for the reader. This guide shows how to write one people open every week. ## Why competitor updates go unread Before the format, it helps to name what goes wrong: - **Everything is posted.** A new blog post, a changed headline and a price cut all get the same weight, so readers can't tell which is which. - **There is no "so what".** A link to a competitor's page asks the reader to work out why it matters. Most won't. - **It arrives at random.** An update that might come any day is easy to ignore on every day. - **It lives in the wrong place.** A separate tool or a folder people never open loses to the inbox and the team chat they already check. A good brief answers each of these: it is selective, it explains, it is regular, and it goes where people already are. ## The format ### One day, one time, every week Pick a day and send it then, every week, even when little happened. Monday morning works for teams that plan their week then; Friday works for teams that review. Regularity is what turns it from a notification into a habit. A quiet week gets a short brief: "Nothing important this week. 9 small changes, none that affect us." That line is worth sending. It tells the team someone is watching, and that they don't need to. ### A hard limit on items Set a maximum and keep to it. We use 7, because it fits on one screen and forces a ranking. Your number might be 5. What matters is that the limit is real: when there are more changes than slots, the least important ones drop out. The limit is what makes the brief worth reading. If everything goes in, the reader has to do the filtering, and that is the job the brief was meant to do. We wrote more about this in [why the brief stops at 7 items](https://plainrival.com/blog/why-the-brief-stops-at-seven). ### Ranked, most important first Put the change that matters most at the top. Many readers will only read the first two or three items, so make those count. If you mark importance, use two or three levels at most (high, medium, low) and be strict about "high". ### Four lines per item Every item follows the same shape: 1. **What changed**, in one plain sentence. "Acme CRM cut its entry plan from €29 to €19 per seat." 2. **Why it matters to us**, in one or two sentences. "We lead with price for small teams. We are now more expensive for teams under 5 seats." 3. **One thing to do.** "Sales: lead with onboarding time, not price, for small deals. Product: look at a lower entry tier next quarter." 4. **The source**: a link to the page and the date the change was seen. The second line is the one that makes a brief worth reading. It is also the hardest to write, because it needs you to know your own positioning. If you can't say why a change matters, that is a sign it may not belong in the brief. ### Say what you left out End with a count: "Also seen this week: 12 other changes, none important." It shows the brief is a filter, not a summary of whatever someone noticed. Link to the full list for anyone who wants it. ## An example Here is a short brief for a fictional company that sells help desk software. The competitors are made up. > **Competitor brief, week 39** > > **1. Cedar Support added a free plan (high).** One seat and 100 tickets a month, no card needed. Small teams who compare us on price will now see "free" next to our trial. **Do:** add a line to the pricing page on what the trial includes and when a team outgrows a free plan. [Source: pricing page, seen 21 September] > > **2. Acme CRM launched a help desk add-on (medium).** Sold only to existing Acme customers for now. It is a threat to accounts that already use their CRM. **Do:** tag open deals that use Acme and give sales the comparison sheet. [Source: launch post, seen 23 September] > > **3. Harbor Desk changed its homepage headline (low).** Now "Support for fast-growing teams" instead of "Support for small teams". A sign they are moving up-market. **Do:** nothing yet; watch their pricing page. [Source: homepage, seen 24 September] > > Also seen: 8 other changes, none important. Three items, a few minutes to read, and every reader knows what, if anything, is theirs to do. ## Who writes it One person owns the brief, even if others contribute. Ownership is what keeps the day and the limit. Give it to someone who understands your positioning well enough to write the "why it matters" line: often a product marketer, a founder, or whoever runs sales enablement. Expect most of the time to go into deciding what to leave out, not into writing. ## Where to send it Send it where your team already reads: an email on the chosen morning, a post in the main team channel, or both. Avoid a separate tool people have to remember to open. If sales lives in the CRM, link the brief from there too. Keep past briefs in one place. After a few months they become a history of the market: when a competitor started moving up-market, when prices shifted, which launches turned out to matter. ## Check that it works After three or four weeks, ask a few readers two questions: did you read the last brief, and did you do anything because of it? If the answer is no, cut the brief shorter before you add anything. A brief that is read beats a thorough one that isn't. ## Doing it with less work The hard parts of a brief are watching the pages every day and ranking what changed. Plainrival does both. It checks your competitors' public pages daily, drops the noise, and sends a weekly brief of at most 7 items, each with why it matters to you and one suggested action. It also tells you how many changes it filtered out. You can read it by email, in the app or in Slack, or ask your AI assistant about it through the Plainrival MCP server. _Product preview: an illustrative example. Companies and changes are fictional._ However you produce it, the rules stay the same: same day every week, a hard limit, the most important first, and a clear "why it matters" for every item.