Competitive intel agent
Hear competitors
move first.
harvest watches competitor changelogs, pricing pages, job posts, and repos — then distills the noise into ranked signals. You learn what changed, and why it matters, before their customers do.
harvest · signal distillation · 40+ sensor types
Why teams install
What harvest earns back
11-day median signal lead
From a competitor's commit to your inbox — before their announcement.
‹d44b0c9›Diffs, not noise
Pricing-page changes land as structured deltas with before/after captures.
‹93ce517›Every claim is sourced
Each signal carries the URL, the timestamp, and the capture hash.
‹6f1e8a4›How it works
Three steps. No faith required.
01
Watch
Point harvest at rivals: sites, repos, job boards, app stores.
02
Distill
Raw changes become ranked signals with confidence and blast radius.
03
Brief
A weekly battlecard updates itself. Big moves page you the same day.
Proof band
One packet. Every claim accounted for.
packet rig/harvest · signal 6f1e8a4 source competitor-x.com/pricing · captured 04:12Z change "Pro tier +18% · annual discount removed" rank blast-radius HIGH · confidence 0.94 witness PASS — capture hash verified ‹93ce517› themis SEALED — battlecard updated
Every harvest run emits a packet like this — hash-chained, verifier-signed, and queryable from your own dashboard. How ProofPackets work →
Buyers
Who runs harvest
PMM
B2B SaaS, crowded category
Head of Strategy
marketplace, 3-sided
Founder
9 direct competitors
Before you install
The obvious objections
Q Isn't this just RSS feeds and Google Alerts with extra steps?
Alerts fire on keyword matches; harvest ranks every change by blast-radius and confidence, sources 40+ sensor types beyond RSS — pricing diffs, job posts, repo commits — and rolls the raw noise into a self-updating battlecard. The 11-day median lead is measured against a competitor's own commit timestamp, not a marketing estimate.
Q How do I know the 11-day signal lead isn't a cherry-picked outlier?
Every packet carries the source URL, capture timestamp, and hash logged the moment the sensor fires — not backdated for the sales page. Disable the sensor on a target and the lead collapses to zero on every re-run, which is the planted-failure regression baked into the gate.
Q What happens when harvest misreads a competitor's move?
witness re-verifies the capture hash before a signal is allowed to rank; a mismatch blocks it from the battlecard entirely instead of shipping a wrong read. A blocked signal still leaves the raw capture in the packet — it doesn't vanish.
Pricing
Start free. Pay when it pays.
Generalist ships today. Domain Expert adds vertical memory + priors. Custom is built to your stack.
Free
Priced after a short conversation
3 competitors watched. Weekly digest.
Team
Priced after a short conversation
10 targets, live battlecards, same-day paging.
Governance
Custom — Priced after a short conversation
Dedicated analyst, private sensor network, SLA on signal lead time.
Runs well with
