Platform · Signals architecture
Two thousand sources. Zero extra tabs.
Nobody reads two thousand sources. PYRAMYD collects new signals every day, classifies each one, and keeps its source, so the moves in your market, among your competitors, and at your accounts reach the product, marketing, and sales teams who act on them.
2,000+ cataloged sources · ten signal categories · five-step matching · 0–100 significance
What it listens to
A watchlist you control — including their whole website.
This isn't “we monitor the news”. Every source is named and versioned, and you decide the mix per competitor.
Core — on by default
The spine every competitor is watched with, including CWCS — the competitor website classification system: we crawl their site, classify pages by surface (pricing, products, customer proof, careers), snapshot them, and diff them. A quiet pricing edit becomes a signal. Page checks are paused today; the newest recorded change is from 16 Aug 2026.
CWCS crawl & diffs · SEC EDGAR · Crunchbase · USPTO · ATS job boards · WARN notices · GDELT · GitHub · CVEs · status pages · OpenCorporates
Catalog — 2,000+ sources
Every source classified into one of the ten signal categories. Switch on what your market needs — regulatory feeds, marketplaces, analyst observers, regional registries.
capital · talent · technology · commercials · marketing · sales · customers · ecosystem · observers · governance
Custom — yours alone
Point the engine at any URL, RSS feed, or API with your own keywords and credentials, aimed at the competitors you choose, and choose which surfaces it feeds. Run it whenever you want fresh results.
include in → competitor refresh · battlecard refresh · customer refresh
The engine
One article in, a sourced signal out.
Raw pages aren't intelligence. Each item is read the way an analyst would read it: classified, matched to the right companies, and scored for significance, with provenance kept at every step. (Scoring and matching run again when the current pause on automated jobs ends.)
| Stage | What happens | In the product |
|---|---|---|
| 1 · Fetch & parse | Pull the article, filing, job post — or a page from the competitor's own site via the CWCS crawl — and strip it to clean text. API-first, with a certified scrape fallback. | per-source query strategies |
| 2 · Extract | Source-tuned prompts pull the event out of the prose, and it becomes a signal with its source. | signal extractor |
| 3 · Classify | Each signal lands in one of ten MECE categories, keyed to which actor caused it. | capital · talent · technology · commercials · marketing · sales · customers · ecosystem · observers · governance |
| 4 · Ground | Anchored to the graph's taxonomies — category, industry, country, role — so a signal knows its market context before anything consumes it. | taxonomy grounding |
| 5 · Resolve | Five-step matching turns mentions into hard graph links: exact identifiers, aliases, domains, strict names, then LLM ballots over taxonomy definitions. Below the confidence floor it doesn't ship. | five-tier resolution |
| 6 · Score & dedupe | Scored 0–100 for significance with critical/high bands, then near-duplicates across sources collapse into one signal carrying many citations. | signal scoring service |
Several articles carrying the same signal collapse into one with many citations. That discipline is why everything downstream can trust the output.
Why ten categories
Classified by who caused it, not what it's about.
Topic tags multiply forever and overlap. Keying each signal to the actor behind it keeps the set mutually exclusive and collectively exhaustive — so counts mean something and nothing lands in two buckets.
Resources
capital · talent
What they have to spend and who they're hiring.
Offering
technology · commercials
What they build and what they charge.
Go-to-market
marketing · sales
How they reach a buyer.
Market
customers · ecosystem · observers · governance
What the world does back to them.
Where signals land
One signal, every surface that needs it.
Competitor 360
New signals land in the Pulse feed; rerun the 360 or its forecast to re-score the dimensions they touch.
Battlecards
Signals can propose an edit for the card owner to approve or dismiss on the card. (The sweep that drafts new suggestions is paused for now.)
Account 360
The same engine, pointed at the companies you serve: leadership changes, layoffs, funding, incidents.
Comparisons
Posture and evidence feed the vendor comparisons your buyers see.
Newsletters
The week's material moves from every hub, ready to drop into your next issue.
Win/Loss & deal risk
Win/Loss shows win rates and pipeline risk by competitor, read beside the signals on each rival. (Win/loss risk alerts are paused for now.)
Alerts & webhooks
Set rules that send matching signals to Slack, email, or your own systems. (Delivery is paused for now; new signals show in the feed.)
APEX
Every answer APEX's agents give can cite the signal it came from.
Name a competitor and a source we should be watching.
We'll wire it up live and show you what comes out the other end — split into signals, categorized, kept with its source, and routed to the surface that needs it.