# Competitive Intel Watch — Worked Example (Industrial)

All companies, products, URLs, and figures are **fictional**. Industrial sibling of
[`sample.md`](sample.md): this run diffs against the Northfield snapshot of 2026-08-28. Note the
cadence difference from SaaS — industrial signals move slower, so this is a **quarterly** watch,
and the SIGINT layer (pricing pages) gives way to filings, registries, and customs data. One of
this run's finds is the same Helix "Foresight" re-scoping documented from the inside-out view in
`company-intel/examples/executive-signal-refresh.md` — two skills, one fictional event.

**Invocation:** `Competitive intel watch — prior snapshot pasted (Aug 28); this cycle I'm watching
for Meridian channel-building moves. [snapshot]`

---

# Competitive Watch Report

## 1. Run Header
**Scope (from prior snapshot):** Northfield vs. retrofit-automation competitors; decision context: software-led retrofit line
**Prior snapshot date:** 2026-08-28
**This run date:** 2026-11-06
**Competitors checked:** Helix Motion Systems, Meridian Freight Systems, Corvid Industrial

## 2. Changelog (Material Shifts Only)

### Helix — Foresight re-scoped to aftermarket-only; digital leadership departed
- **What changed:** Q3 call assigned Foresight to Aftermarket Services with an installed-base-first scope ("we'll expand from our installed base rather than chase greenfield" — CFO); the VP of Digital Transformation departed in September; digital-twin job postings fell ~40 → 6 — **Fact** ([Q3 transcript](https://example.com/helix/q3-transcript); [departure announcement](https://example.com/news/helix-vp); job boards, Oct 2026)
- **Evidence:** URLs + dates above
- **So what:** the snapshot's #1 competitive risk — "Helix opens Foresight to third-party equipment" — just moved sharply *less* likely: an aftermarket-scoped, installed-base-first program is the opposite of a mixed-vendor land grab. Roadmap owner acts: the mixed-vendor software window is wider than planned.
- **Confidence:** high (three independent signals, one story)

### Meridian — safety certification filing for plant-floor equipment class
- **What changed:** a Meridian subsidiary appears in the certification body's public register with an "in process" listing for a plant-floor equipment class — **Fact** ([registry entry, Oct 2026](https://example.com/certregistry/meridian)); component import volumes up again per customs data — **Fact** ([trade data](https://example.com/tradedata/meridian))
- **Evidence:** URLs + dates above
- **So what:** certifications are a 12-36 month runway signal — the manufacturing entry moved from architecture-inference to committed-spend evidence. Doesn't change this year's plan; changes next year's. Roadmap owner logs a dated tripwire.
- **Confidence:** medium-high (two channels agree; no channel/distributor motion yet — the gating factor the snapshot named)

_Corvid Industrial: nothing cleared the bar. Reorg-flavored employee reviews continue (below bar; unchanged trend)._

## 3. Update Flags
| Downstream artifact | Sections needing update | Driven by |
|---|---|---|
| Battle card | Thirty-Second Read; Watch Out For (Foresight scope now a documented limitation, not a looming threat) | Helix re-scoping |
| Roadmap assumptions | Mixed-vendor window duration; Meridian entry timeline (now dated: registry + 12-36mo) | both shifts |

## 4. Watchlist for Next Run
- Meridian: distributor listings or integrator partnership announcements (the channel signal that starts the real clock)
- Helix: any Foresight compatibility-docs change adding third-party equipment (the reversal tripwire)
- Corvid: post-split product-leadership hires (the distraction-window-closing signal)

### Assumptions to Validate
- Foresight's installed-base-first scope survives Helix's next planning cycle
- Meridian's certification class maps to *discrete manufacturing*, not just warehouse-adjacent gear (registry class codes are ambiguous — needs a TECHINT read)
- The integrator-margin assumption (open since August) — still unvalidated, now flagged twice

---

## Why this example works

- **The cadence matched the physics.** SaaS pricing pages justify monthly sweeps; filings,
  registries, and customs data move quarterly — so the watch runs quarterly and doesn't
  manufacture weekly noise from a slow-moving market.
- **A risk got *demoted*, and that's reported as material.** Most watches only escalate. The
  Foresight re-scoping made the snapshot's top risk less likely — which changes roadmap posture
  just as much as a new threat would, and clears the materiality bar for exactly that reason.
- **Cross-skill coherence:** this run reads the Foresight event from the outside (transcript,
  departures, job posts) while the `company-intel` refresh example reads the same event from a
  dedicated single-company deep dive — showing where the watch's altitude ends and `company-intel`
  begins.
- **An assumption flagged twice gets called out.** The integrator-margin question has now survived
  two artifacts unvalidated; the watch names the streak instead of quietly re-listing it.