Watch for product teams: competitors' launches and the requirements that reach the design

Which product decisions depend on what happens outside?

• Prioritising features. What goes into the next version depends on what competitors already offer and on what is about to become mandatory.
• Setting the design freeze. A requirement that applies after that date forces a redesign or a delayed launch.
• Withdrawing or redesigning references. Products that will not be able to meet a new requirement, or that a competitor has made obsolete.
• Positioning against competitors. Which attributes to defend when another manufacturer launches something similar.
• Deciding on components. If a component with digital elements or AI changes regulatory regime, the cost of maintaining it changes too.

Which EU requirements affect product design between 2026 and 2028?

Ecodesign product groups are specified one by one in delegated acts. For a product team, what has to be watched is not only the framework regulation, but the consultation and adoption of the act that affects its category.

How to watch competitors without confusing an announcement with a launch

A single product leaves traces in different sources as it advances. Recording the stage each development is at avoids reacting to what is still an intention:

1. Protection. A patent application or related registration; it indicates a line of work, not a product.
2. Announcement. A press release, a presentation at a trade fair or a statement by an executive.
3. Datasheet or catalogue. The product appears on the manufacturer’s website with its specifications.
4. Availability. It can be bought, or appears in an awarded tender.
5. Withdrawal or incident. The product disappears from the catalogue or appears on Safety Gate, the EU rapid alert system for dangerous non-food products, formerly known as RAPEX^[3].

The full sequence for each competitor, with dates, shows where its range is heading better than any single launch.

How to bring the watch into the roadmap review

1. Open each review with what has changed outside since the previous one: launches, withdrawals, new requirements and substitute technologies.
2. Record each requirement with its application date, scope and owner. Which references it affects, and who confirms the impact with quality and regulatory affairs.
3. Keep the history by competitor instead of redoing the comparison at each review.
4. Separate substitution from competition. A technology from another sector that solves the same problem is watched with its own criteria, not as just another competitor.
5. Write down the signal behind each decision, so that it can be reviewed when the facts change.

What Innguma offers a product team

Innguma monitors competitors’ websites, regulation and Spain’s Official State Gazette (BOE), patents, news and specialist sources. Innguma’s AI groups duplicates and classifies each signal by entity, technology and type of event, so that each competitor’s moves can be browsed separately in AI Feed. What the team validates is kept in the Library, with tags and comments: that is where the history by competitor and by requirement is built, always with the source linked.

The product newsletter is sent from the Library. Innguma also offers connectivity through the Model Context Protocol (MCP), currently compatible with ChatGPT, Claude, Microsoft Copilot and Gemini: if your organisation enables it, before a roadmap review you can ask your assistant to summarise and compare what has been validated about a competitor or a regulation.