Examples

Example 1: Start Tracking a Competitor

A new SaaS client has come on board, and the account manager wants to track two rivals: one closely, one loosely.

Step 1: Add the first rival in Slack. She types:

@Agenteous track rival-one.com as priority 1, watch for launches and pricing changes

Competitor Intel replies that it added rival-one.com to the client's watchlist and will watch for launches and pricing changes.

Step 2: Add the second in the app. Under Marketing, Visibility, on the Competitors screen, she enters rival-two.com as the Competitor Domain, adds a name, and clicks Add Competitor. She leaves the optional Feed Address blank. The row appears in the table with its Watch column reading "Not Watched: No Feed Address".

Step 3: Confirm the list. Back in Slack:

@Agenteous who are we watching?

Competitor Intel lists both competitors with their domain, priority, activity score, and status. The roster entry and the Slack entry appear in the same list.

Step 4: Know what to expect. Neither competitor has a feed address (she did not include one in Slack; she could have, or can still ask Competitor Intel to set it), so the agent's 6-hourly check will not read them and no moves will be recorded for them; had she filled in the Feed Address on the Competitors screen, that one would be watched. The one added on the Competitors screen is also on the roster that the visibility recon watch follows, so changes for it can show up under Competitor Changes.

Example 2: Review Competitor Changes

A week later, the account manager opens Moves & Recon for the client's brand.

Step 1: Read the changes. The Competitor Changes section lists changes the recon watch detected on the roster. Each shows the competitor, the type of change, an urgency, a significance out of 10, how long ago it was detected, a summary, and a recommended action.

Step 2: Acknowledge what you have seen. She reads each, then clicks Acknowledge on the ones she has handled so that the list shows only what is new.

Step 3: Look at the watchlist. Below, the Competitor Intel table lists the rivals she added with their priority, velocity, and status.

Example 3: Queue a Move as a Topic

An agency has a competitor whose feed address is on file, so its moves are recorded. The account manager opens the competitor's detail page.

Step 1: Read the moves. Recent Moves lists the competitor's items, newest first, each with a label and a one-sentence summary:

• Launch: "Released a new analytics dashboard for mid-market teams."
• Pricing Change: "Introduced a lower-priced starter tier."
• Publish: "Published a guide on measuring campaign attribution."

Each title links to the source, so she opens the launch announcement to check the details.

Step 2: Queue the launch. She clicks Queue Topic next to the launch. The button changes to a Queued link.

Step 3: What it created. A topic titled "Respond to" the competitor and the launch now sits in the SEO topic queue. It is an idea for the team to consider. Nothing has been written or published.

Step 4: Normal review takes over. A writer can pick up the topic, draft a response, and send that draft through the usual approval before anything goes out.

Example 4: Pause a Competitor

The client acquires one of its rivals, so the account manager wants to stop checking it.

Step 1: Open the competitor. On Moves & Recon, she clicks the competitor's name.

Step 2: Pause. She clicks Pause Watching. The status changes to Paused. Its history stays on the page, and it is skipped when competitors are checked.

Step 3: Resume later. If circumstances change, Resume Watching starts the checks again.