Support heard about the competitor before we did

A customer wrote in asking whether we could "do the thing [competitor] does with shared views." That was March. The feature didn't hit the competitor's changelog until June — it had been in a closed beta the whole time, and our customer was in it.

Nobody outside support saw that ticket. It was answered, tagged, and closed in eleven minutes.

Customers describe competitors better than analysts do

A positioning deck tells you what a competitor claims. A support ticket tells you what a customer did with the product, in their own words, usually while mildly annoyed. There's no spin in it. Somebody typing "I need this to work like [competitor] does when I'm bulk-editing" has just handed you a feature gap, a use case, and a rough sense of how much it hurts.

Three ticket shapes are worth pulling out:

• The comparison question. "Do you have X? [Competitor] has it." A gap, stated by someone who cares.
• The migration question. "We're moving off [competitor] — can you import their export format?" That's a churn signal about someone else's product, arriving on your desk for free.
• The unfamiliar feature name. A customer using vocabulary you don't recognize. That's usually a beta, a partner program, or a page that hasn't shipped publicly yet.

The third one is the good one. It's the only intel source I know of that routinely runs ahead of a competitor's own public surfaces.

Why it dies in the queue

Support is measured on time-to-resolution. Reading tickets for strategic pattern is unscored work, done by someone whose queue is not getting shorter while they do it. So the signal gets logged as "answered" and buried under six thousand other answered things.

The fix isn't a process document. It's one tag — mentions-competitor — and someone who actually reads what's under it every two weeks. Ten minutes. If the tag is empty, that's information too.

This is also the half of the picture that tooling can't reach. Seeto watches competitors' public surfaces continuously and turns what moves into discrete change events — a pricing edit, a new page, a changelog entry. It does not read your support queue and never will. The outside signal and the inside signal come through different doors, and most teams have only built one of them. Pair the tag with what you already track on the competitor you weren't watching, and the two lines start explaining each other.

Worth asking your support lead this week: when was the last time somebody outside support read a ticket that mentioned a competitor by name? If the honest answer is "never," you've been paying for research you already own — and memory won't reconstruct it later.