The Competitive Positioning Radar: Inferring Strategy From Open Signals

Most competitive intelligence reads like a news wire. "Acme launched a new dashboard." "RivalCo hired a VP of Sales." "CompetitorX raised their enterprise tier by 15%." Each observation stands alone, stripped of context, delivered weeks after anyone paying attention already noticed.

That approach misses the point entirely. The real value of competitive intelligence lives in the space between individual signals — in the pattern that emerges when you overlay a hiring spike in healthcare compliance roles with a changelog entry for HIPAA audit logging and a pricing page that just added a "Regulated Industries" toggle.

No single data point tells you much. But collectively, those three signals suggest a deliberate bet on healthcare verticals, probably timed for a Q3 compliance certification announcement. That inference, delivered six weeks before the press release, gives your team enough runway to accelerate your own healthcare roadmap, adjust positioning, or lock down accounts before the competitor's sales team even has new collateral.

Job postings are among the most revealing open signals a company produces. Before a competitor announces a new product, expands into a new region, or targets a new segment, they typically start hiring for it. The rate of change in postings tends to matter more than the absolute count^[3] — a company that jumps from 3 to 12 engineering postings in a single month is often signaling something about their next 6-12 months, though this isn't guaranteed (hiring can also reflect attrition or reorganization).

Breaking roles down by department sharpens the signal. An engineering and product hiring spike often points to a build phase or platform overhaul. A sales cluster in a specific geography may signal territory expansion. A burst of marketing hires focused on demand generation could suggest a category-creation play. Each pattern offers a directional hypothesis — combine multiple signals before acting on any one of them.

The difference between a competitive intelligence system that produces summaries and one that produces strategic inferences comes down to prompt design. Most teams make the mistake of asking "what happened?" when they should be asking "what does this combination of events imply about where this company is heading?"

Effective inference prompts share three structural elements. First, they present signals grouped by competitor with explicit instructions to look for cross-channel convergence. Second, they demand that every inference cite a minimum number of supporting signals from different channels. Third, they require a confidence assessment tied to the diversity and strength of the evidence, not just its volume.

The temptation with any intelligence program is to measure output volume — number of briefs published, signals collected, competitors tracked. These vanity metrics reveal nothing about whether the radar changes behavior.

Three metrics actually matter. First, prediction accuracy over 90 days: what percentage of your medium-and-high-confidence inferences proved correct when you scored them against actual outcomes? Based on practitioner reports, healthy programs tend to maintain roughly 55-65% accuracy at medium confidence and 70-80% at high confidence^[1] — these are approximate benchmarks, not guarantees. Below those thresholds, your signal collection or inference prompts need recalibration.

Second, time-to-action: when you publish a high-confidence inference, how many days pass before a stakeholder takes a measurable action (adjusts a roadmap, modifies positioning, reaches out to an at-risk account)? If briefs sit unread for two weeks, distribution and formatting need work, not the intelligence itself.

Third, competitive win-rate delta: over a rolling quarter, compare win rates on deals where the team had advance intelligence from the radar versus deals where they did not. A well-run program may produce a measurable improvement — practitioners have cited improvements in the range of 8-15 percentage points — but results vary significantly by deal complexity, team size, and how well inferences are operationalized.

The fastest path to a working competitive positioning radar takes less than a week of setup. Pick your top two competitors. Map their career pages, changelog URLs, and pricing pages. Set up weekly diff monitoring on each URL — tools like Visualping, Changeflow, or simple cron-based scripts that capture page snapshots all work.

Write a single inference prompt using the template in this article. Feed it your first week of collected signals. The output will not be perfect. It will, however, be dramatically more useful than a Slack channel full of "hey, did you see CompetitorX launched a new feature?" messages.

After four weeks, you will have enough baseline data to set meaningful anomaly thresholds. After eight weeks, you will start seeing your prediction accuracy stabilize. After twelve weeks, you will wonder how your team ever operated without it.

The companies that gain a sustained edge in competitive markets are not the ones with better products — they are the ones that see strategic shifts six weeks before everyone else and use that time to act.