The competitor research you keep meaning to do.

The research always loses to the sprint.

Competitive analysis is the work that never has a deadline. There is no ticket for it, nobody is blocked on it, and it is the first thing to fall out of the week. So it gets done properly once — during planning, or after a lost deal — and then not again for a quarter.

The cost shows up later, and indirectly. A feature you were about to scope has already shipped somewhere else. A gap you were defending on has been closed. Someone on a sales call says a competitor now does the thing your differentiation slide says only you do.

The signals that actually move a roadmap.

Most competitive monitoring watches announcements. Announcements are the last step — by the time there is a launch post, the decision was made two quarters ago. The useful signals are earlier and duller:

• Documentation and API reference. New endpoints appear in docs before they appear in a changelog, and long before they appear in marketing. A competitor documenting webhooks is a competitor about to talk about integrations.
• Changelog cadence, not just contents. How often a team ships tells you how big it is and where its attention is. A changelog that goes quiet in one area and busy in another is a reprioritization you can see from outside.
• Job postings. Roadmap and go-to-market intent, months early. Nobody hires a solutions architect and a security engineer in the same week by accident.
• Pricing and packaging. Seat caps, limits and trial length are product decisions wearing a commercial hat. A tightened free tier tells you what they have decided is valuable.

What lands on Monday.

Five to eight items in a normal week, each with a line explaining why it cleared the bar, and a closing paragraph on what the week means for what you are building. Not a feed, not a digest of everything that changed, and not forty notifications you learn to mute.

In a quiet week the brief says the week was quiet. That is the point of a brief rather than a dashboard: it is allowed to be short.

What this is not.

It is not a roadmap tool. It does not write specs, score features, or tell you what to build — it tells you what changed outside and leaves the judgment about your own product where it belongs.

It also only reads public pages. If a competitor's plan exists only in a private beta or a sales deck, Norrel will not know about it until it reaches a page anyone can visit.