Buying Signal Watcher — New B2B Tool Adoption Alerts

STATUS: published, $0.25/result (PAY_PER_EVENT). See "Known limitation" below — Playwright rendering fixed the original plain-HTTP coverage gap (1/6 → 4/6 real test sites), not a 100% guarantee (some sites still won't show a signal even when Playwright-rendered, e.g. custom in-house widgets with no known signature, or truly no high-value tool present).

Watch a list of company domains and get alerted the moment one of them adopts a new high-value tool (Stripe, Intercom, HubSpot, Calendly, Salesloft...) — a real buying-intent signal: fresh budget, right timing to reach out. Run on a schedule; only genuinely new adoptions are reported after the first baseline check, not the same tools every time.

Why this angle

Existing "website technology detector" actors on Apify (5+ found in market research, 08/08/2026) do a one-off inventory scan of 130+ generic technologies. This actor is narrower on purpose: a curated list of ~15 high-value B2B signal tools, checked on a recurring schedule, reporting only what changed since last time — an alert feed, not a static lookup. Persists per-domain state across runs via a named Apify key-value store.

Input

• Domains (required) — company websites to watch, e.g. acme.com.
• Categories — filter to payment, chat_support, marketing_automation, sales_scheduling, sales_engagement, data_infra. Leave empty for all.
• Request timeout.

Output

One row per detected tool: domain, tool_detected, category, change_type (baseline_first_check on the first-ever run for a domain, newly_added on every run after that — only newly_added rows are the real buying signal).

Known limitation, and the fix actually shipped (08/08/2026)

First version used plain HTTP (httpx, no headless browser, same design as the rest of this portfolio). Tested live against 6 real company homepages (close.com, gumroad.com, buffer.com, clearbit.com, loom.com, zapier.com): only 1 of 6 showed a detectable tool. Root cause confirmed by inspecting the raw HTML: most of these sites load third-party tags (Intercom, HubSpot, etc.) dynamically through Google Tag Manager, invisible to a static fetch.

Fixed by switching to Playwright (apify/actor-python-playwright:3.11 base image, headless Chromium, wait_until="networkidle" so GTM has time to inject before we read the DOM). Retested against the same 6 sites: 4 of 6 now show a detectable tool. First deploy also hit a real infra bug — the base image's preinstalled Chromium build didn't match the pinned playwright pip version (Executable doesn't exist at /pw-browsers/... in prod) — fixed by adding playwright install chromium explicitly in the Dockerfile after pip install, so the browser always matches whatever playwright version pip resolves, regardless of what's baked into the base image.

Why $0.25/result, not the portfolio's usual $0.02: this actor only bills on a genuine newly_added signal (never on an empty/no-change run, matching the rest of the portfolio's "never charge for nothing found" rule) — but most scheduled checks won't find a new signal (companies don't add tools every week), and Playwright rendering costs real compute on every check regardless of outcome. Priced to cover the amortized compute cost across the "silent" checks that lead up to one billable signal, not just the compute of the one that hits. Estimate, not measured — revisit once real usage data comes in.