Competitor Meetings: Focus on Technical Standards?

Yes, keep competitor meetings focused on technical standards rather than business plans. This approach prevents antitrust risks, keeps discussions productive, and aligns with the legal boundaries that allow competitors to collaborate on interoperability and safety without colluding on market strategy.

Why the Distinction Matters

Competitor meetings are common in industries that rely on shared standards—think telecommunications, software, automotive, and medical devices. Companies often need to agree on technical specifications so their products work together, connect to the same networks, or meet regulatory requirements. However, the same meeting can become legally dangerous if the conversation drifts into pricing, market allocation, customer targeting, or future business strategies. Antitrust laws in most jurisdictions, including the U.S. (Sherman Act) and the EU (TFEU Article 101), prohibit agreements that restrain trade. Technical standards discussions are generally pro-competitive because they enable interoperability, but business plan discussions can easily cross into illegal collusion.

The Legal Framework: What Is Allowed and What Is Not

Antitrust authorities recognize that standard-setting is beneficial, but they draw a clear line between technical collaboration and commercial coordination. Allowed topics include:

• Technical specifications, protocols, and interfaces
• Testing procedures and certification requirements
• Safety standards and environmental compliance
• Patent licensing terms under fair, reasonable, and non-discriminatory (FRAND) commitments

Prohibited topics include:

• Pricing, discounts, or terms of sale
• Market division, customer allocation, or territorial restrictions
• Production capacities or output levels
• Future business strategies, R&D plans, or marketing campaigns

Even informal comments about “how the market is going” can be misconstrued. If a competitor says, “We’re thinking of raising prices next quarter,” that could be seen as an invitation to collude, even if no explicit agreement is reached. Keeping the agenda strictly technical avoids these ambiguities.

Practical Benefits of Staying Technical

Beyond legal compliance, a technical focus yields better outcomes. When engineers and technical leads meet, they solve real problems: aligning on a connector type, agreeing on a data format, or harmonizing test methods. These discussions are concrete and measurable. Business plan discussions, in contrast, are often speculative and can devolve into posturing or competitive intelligence gathering. By limiting the agenda, you also protect your proprietary strategy. If you share your product roadmap, a competitor could adjust their own plans accordingly—or even copy your approach. Technical standards are often published anyway, so sharing them costs little. Business plans are not public, and sharing them gives away your competitive advantage.

How to Structure a Compliant Meeting

To keep meetings focused and safe, follow these steps:

1. Set a written agenda in advance, listing only technical topics. Circulate it before the meeting and stick to it.
2. Invite only technical staff—engineers, scientists, and technical managers. Avoid sales, marketing, and senior executives who might be tempted to discuss strategy.
3. Use a neutral facilitator or an independent standards body (like IEEE, IETF, or ISO) to run the meeting. This adds a layer of separation.
4. Take minutes that record what was discussed, but only in technical terms. If a business topic arises, note that it was out of scope and move on.
5. Have a legal advisor present or at least review the agenda and minutes. They can flag risky comments in real time.
6. Leave early if the conversation drifts. If a competitor starts discussing pricing, excuse yourself and document why you left.

Common Pitfalls and How to Avoid Them

Even with good intentions, meetings can go off the rails. A common pitfall is “sidebar” conversations during breaks. Two engineers might chat about a new product feature that hints at future pricing. Another is using vague language—saying “we’re going to focus on high-end customers” could be interpreted as market allocation. To avoid these, remind participants before the meeting what is off-limits, and consider having a “chaperone” who is trained in antitrust compliance. If a sensitive topic comes up, the facilitator should immediately redirect to the technical agenda. Also, be careful with social events: a dinner after the meeting is still a competitor meeting, and the same rules apply.

When Business Discussions Are Inevitable

Sometimes, business topics are intrinsically linked to technical standards. For example, patent licensing terms are a business matter but are part of standard-setting. In such cases, the discussion should be handled separately, with legal counsel present, and ideally in a different session. The key is to separate the technical agreement from the commercial terms. Similarly, joint ventures or partnerships may require business discussions, but those should be conducted under a separate, more formal agreement with its own antitrust safeguards. The general rule remains: if the meeting is about standards, keep it technical. If you need to discuss business, schedule a different meeting with a different purpose.

Frequently Asked Questions

Can I ask a competitor about their product roadmap?

No. Product roadmaps are future business plans and are off-limits. Discussing them could be seen as an attempt to coordinate on product features, timing, or markets. Stick to existing or proposed technical standards.

What if a competitor brings up pricing during a standards meeting?

You should immediately stop the conversation, state that pricing is out of scope, and ask that the topic be dropped. If the competitor persists, leave the meeting and document the incident. Report it to your legal team.

Are all technical discussions safe?

Mostly, but not all. Discussions about future technical capabilities could be used to signal business intentions. For example, saying “we’re developing a low-cost version” might hint at pricing strategy. Keep discussions to current or proposed standards, not your internal R&D projects.

Do these rules apply to informal meetings or trade shows?

Yes. Any interaction with a competitor—formal or informal—is subject to antitrust laws. A casual conversation at a trade show can be just as risky as a formal meeting. Treat all interactions with competitors as potentially subject to scrutiny.

Can I share my company’s technical data with competitors?

Only if it is necessary for the standard-setting process and is not competitively sensitive. Sharing proprietary technical data that gives you a competitive advantage is not required and could be harmful. Share only what is needed to achieve interoperability.

What is the role of a standards organization?

Standards organizations like ISO, IEEE, and IETF provide a neutral platform for competitors to collaborate. They have their own antitrust guidelines and often require participants to agree to a code of conduct. Using these organizations can help ensure compliance, but you still need to follow your own company’s policies.

Related

• DeepSeek AI Explained: How It Works and Which Model to Use
• How to Choose an AI Assistant for Work, Study, or Life
• AI Infrastructure: Why the Chip Is Only Part of Performance