RIVEXA FIELD GUIDE
Build competitive intelligence people can trust.
Twenty-four practical guides for choosing what to watch, preserving the evidence and turning market change into a defensible decision.
How to use this library
Start with Foundations if you are designing the program. Use Signals to build a reliable collection workflow. Workflows and Reporting show how to deliver the result to product, marketing, sales and leadership without creating another feed to check.
Topic cluster
Foundations
Competitor monitoring: a practical guide for teams that need decisions, not alerts
A useful monitoring program is deliberately narrow. It watches the sources tied to a decision, preserves the evidence, and gives every signal an owner.
Read the guideA competitive intelligence process your team can actually run
The classic intelligence cycle still works. The failure usually happens between collection and action, where links pile up and nobody owns the conclusion.
Read the guideThe competitor monitoring checklist: from watchlist to weekly review
Use this checklist when launching a program or auditing one that has become noisy. It is designed to expose missing ownership and weak evidence.
Read the guideCompetitive intelligence vs. competitor analysis: the useful distinction
One is a recurring operating system; the other is a focused piece of analysis. Confusing them leads to annual decks that become stale almost immediately.
Read the guideHow to choose competitors to monitor without building a useless giant list
A competitor is not simply a company that resembles yours. The useful question is how that company could change a buyer’s decision.
Read the guideTopic cluster
Signals
Competitor website monitoring: detect the change and understand the move
The hard part is not detecting that HTML changed. It is deciding whether a buyer-facing promise, package or product fact changed.
Read the guideCompetitor pricing monitoring: track packaging, not just the number
A price can stay the same while the offer changes completely. Entitlements, limits, billing units and sales language belong in the same record.
Read the guideHow to track competitor product launches before and after launch day
Launch day is the loudest moment, not always the most informative one. Documentation and packaging often reveal the actual scope.
Read the guideCompetitor positioning monitoring: turn copy changes into market insight
Positioning is a repeated pattern across audience, problem, promise, proof and alternatives—not a single homepage sentence.
Read the guideCompetitor news alerts without inbox overload
News monitoring fails when every mention is treated as a new event. One announcement can become dozens of links without adding evidence.
Read the guideCompetitor social media monitoring for strategy, not vanity metrics
Follower counts describe an audience. The more useful intelligence is what the company repeatedly says, who says it first, and where the language changes.
Read the guideHow to monitor competitors on X without trusting search snippets
Discovery and verification are different jobs. Search can find a candidate post; the native post or API should establish who published it and when.
Read the guideFounder and executive monitoring with a defensible identity trail
People often reveal the reasoning before the company publishes the polished announcement. The value disappears if the identity match is wrong.
Read the guideCompetitor ad monitoring: a research workflow using public ad libraries
Public ad libraries show creative and activity. They usually do not tell you whether a commercial campaign was profitable.
Read the guideCompetitor hiring signals: what job posts can and cannot tell you
A job post is evidence of a hiring intention. It is not proof that a team exists, a product will ship, or a market entry will succeed.
Read the guideTopic cluster
Workflows
Competitive intelligence for startups: the minimum useful system
A startup does not need an intelligence department. It needs a small evidence loop connected to product, positioning and live deals.
Read the guideCompetitive intelligence for product marketing that stays close to the market
Product marketing becomes the translation layer: public market evidence enters; positioning, enablement and launch decisions come out.
Read the guideCompetitive intelligence for sales: answer the deal, not the entire market
Sales intelligence is useful when a rep can find the right question or response during a deal. Encyclopedic profiles usually fail that test.
Read the guideTopic cluster
Reporting
How to build a sales battlecard reps will use
The job of a battlecard is not to document a competitor. It is to improve the next customer conversation.
Read the guideHow to keep competitive battlecards updated without quarterly fire drills
A battlecard becomes stale claim by claim, not all at once. Monitor the evidence behind volatile sections and update only what changed.
Read the guideHow to write a daily competitive intelligence brief people will read
The brief should compress research, not merely forward it. On a quiet day, the correct output may be no material changes.
Read the guideA competitive intelligence report template built for a decision
A report should make its reasoning inspectable. The reader needs to see how the evidence supports the conclusion and what remains unknown.
Read the guideThe right competitor monitoring cadence for each signal
Collection frequency and delivery frequency are separate decisions. A source can be checked daily while its low-priority findings wait for a weekly review.
Read the guideHow to turn competitor signals into actions without overreacting
Most competitor activity deserves observation, not reaction. The discipline is knowing what would change a decision before the signal arrives.
Read the guide