Is this competitor research allowed? Six questions

A sales rep asks if they can sign up for a competitor's free trial with a Gmail address. A new PM wants to interview three people who left that competitor last month. Someone found a shared login to the rival's customer portal in an old Slack thread.

Each of these lands in your inbox with the same question: is this okay?

The good news is that almost everything useful about a competitor is public. Pricing pages, careers pages, docs, changelogs, status pages and trust centers answer most of the questions a product or sales team has. The risky moves are rare, and they usually trade a small gain for a large problem. Here are the six questions we ask before any research move that feels even slightly grey.

This is a practical framework, not legal advice. If a question involves contracts, employment law or access to systems, ask your lawyer.

Would you be comfortable if the competitor saw exactly what you did?

This is the fastest test, and it catches most problems. Reading their public pricing page passes easily. Every competitor expects that, and most read yours too.

Signing up under a fake name and a fake company does not pass. Neither does asking a support agent "just a few questions" while you pretend to evaluate their product. If the plan depends on the other side not knowing who you are, treat that as the answer.

Is the information behind a login, a paywall or an agreement?

Public means anyone can see it without an account. Once you need a login, you have usually accepted terms of service, and many of those terms forbid competitive use outright.

That includes free trials, customer portals, gated webinars and partner programs. A trial under your own name and work email, where the terms allow it, is a different case from a trial under a disguise. When in doubt, stay on the public side of the login screen. It is where most of the signal lives anyway, as our list of what to baseline on a new competitor shows.

Are you asking someone to break a promise they made?

Former employees are the classic trap. Talking to someone who used to work at a competitor is fine. Asking them about the roadmap, the pricing model behind the public tiers, or a customer list is asking them to break a confidentiality agreement.

The same applies to customers. A customer who tells you why they left is giving you their own experience. A customer who forwards you the competitor's private contract or pricing proposal may be breaking their own NDA. Set a rule: you ask about experience, never about documents.

Could you name the source in front of the whole company?

Every claim in a battlecard should point to where it came from, a habit we argue for in every competitor claim needs a source link. That habit also works as an ethics filter.

"Their pricing page, captured on 14 October" is a source you can show anyone. "Someone I know there" or "a doc that was going around" is not. If you cannot write the source down in plain words, the claim does not go into shared material.

Does your method put load or risk on their systems?

Reading a page is not the same as hammering it. Aggressive scraping, attempts to reach unlinked URLs by guessing, and tools that try to get past rate limits all move from observation into interference.

A sensible monitoring setup reads public pages at a polite interval and does nothing else. That is how Seeto works: it checks public surfaces on a schedule, records what changed, and flags the diff as a discrete event. It does not log in, it does not fill in forms, and it does not pretend to be a buyer. Most teams find that this covers the large majority of what they need to know.

Who decides when the answer is "maybe"?

Grey cases need an owner, not a debate in a thread. Pick one person, usually the program lead with a line to legal, who makes the call and writes it down. The written answer becomes a precedent, so the next rep with the same question gets the same answer in minutes.

This is also one more reason the job needs a senior owner, as we argued in don't hand competitor tracking to your newest hire. A new hire who wants to impress is the person most likely to say yes to the fake-trial idea.

The question underneath all six

Every risky move in competitive research promises a shortcut to information you could mostly get in public, a little slower. So the real question is short: what does this shortcut give you that patience and a public page would not?