What your competitors ship, confirmed.
Add a competitor's website and Euler re-reads it every week or two: products, features, pricing and positioning. A change is reported only once it holds across two scans, and it lands as cited evidence in the project you pick.
Northwind competitor
https://northwind.example
Send competitor evidence to
Creator Platform
Changes
Reported once a change holds across two consecutive scans.
Sep 30 → Oct 7 · 4d ago
Products (3)
Features (14)
From a URL to cited evidence.
- 1
Add a competitor
Paste its website. Euler reads the homepage and up to three of its pricing, plans, features, products or solutions pages.
- 2
Re-read on a schedule
Each competitor gets its own fixed slot, every 7 to 14 days. A site that keeps failing is retried less often, then paused until you rescan.
- 3
Confirmed before it's news
Something new must still be there on the next scan, and something gone must stay gone. One-off differences are recorded, not reported.
- 4
Routed into your evidence
Pick a project, and each reported change becomes a competitor note there, citing the site and the two scans it came from.
A change log you can believe
Added, removed, repriced, repositioned and released. Price moves under 5% and rewritten descriptions are recorded but never reported, and everything Euler saw but doesn't believe yet is one click away.
- Scans that read different pages aren't compared, so a page that failed to load never reads as a removal
- A relaunch with more than ten changes at once stays in the change log and sends no notes
- A scan that finds nothing keeps the last good results
Sep 30 → Oct 7 · 4d ago
▾ 2 more observed, not reported
seen once; not material until a later scan confirms it
62% changed and held across two scans, but description wording is not a reliable signal
Pricing behind a click, and their changelog
Click Find hidden pages and Claude looks through the site for pricing that only shows after a click: a yearly toggle, plan tabs, a full comparison table. Euler also finds the changelog from the site's own links. Keep the pages you want, and each is re-read on every scan and compared on its own.
- Claude clicks and reads; typing is switched off
- Held to the competitor's own site, with robots.txt checked on every page it opens
- A new changelog entry is reported once two scans have listed it
Pages behind clicks
Saved pages are read on every scan and compared one by one.
northwind.example/pricing
Found just now
northwind.example/changelog
Latest: Workflows 2.0 · Faster exports · Guest access
Competitor news next to customer evidence
A competitor note sits in the same project as your interviews and tickets, so it clusters with the requests asking for the same thing, and a PRD can cite it.
- Always neutral: it can never trip a theme's severity alert
- Never raises a theme's confidence
- Nothing is sent until you pick a project
Scheduled workflows · 3 signals
“We rebuild the same weekly report by hand. Every. Week.”
Can workflows run on a schedule?
Northwind published “Workflows 2.0” (Oct 2).
The details.
- Every 7 to 14 days
- Each competitor has its own fixed slot, so scans spread across the week. Rescan any time.
- Two scans to call it
- A product appearing or going, a price move, a new headline: each must hold on the next scan.
- robots.txt, honoured
- Checked before every page Euler reads. Disallowed pages are skipped, and a disallowed homepage stops the scans.
- Up to four saved pages
- Three pages behind a click and one changelog per competitor, each compared on its own.
- Changelogs without a browser
- A changelog is found from the site's own links and read like any other page.
- Context, not corroboration
- Competitor notes count toward a theme's reach, never its confidence.
Where it stops.
Public pages only
Nothing behind a sign-in, and no G2 or Capterra reviews.
Renames aren't news
A renamed product is matched to its old self when the two read alike, and then nothing is reported. When they don't, it shows as one removal and one addition.
A wipe looks like a failure
If a site suddenly lists nothing, Euler can't tell that from a broken scan, so it keeps the last results and reports nothing.
Newest first
Changelog entries are read top down. A changelog that lists its oldest entries first reports nothing new.
Hidden pricing needs the browser
Finding pricing behind a click uses a hosted browser. Where it's off, only changelogs are found.
Questions, answered.
Each one every 7 to 14 days, in its own fixed slot. Rescan whenever you like; a rescan also resumes scanning that was paused.
One scan can be wrong: a page that loaded slowly, or a model that read it differently. Waiting for the next scan keeps your evidence free of that noise, and everything seen so far is in the change log.
No. On a competitor's site it can click and read but not type, and it stays on the competitor's own pages.
Into the project you route the competitor to, as competitor notes. Until you pick one, Euler just keeps the change log.
Stop drowning in feedback. Start shipping the right thing.
We're putting the agents through their paces. When early access opens, the waitlist hears first.