tech stack lookup for gtm teams

See the tools behind
your prospect's
go-to-market.

A deep website scanner your agents and workflows call on demand, with evidence behind every tool it finds.

  1. the page
  2. consent banner and the requests after it
    • Cookiebot
    • HubSpot
  3. public app code
    • Sentry
  4. trust portal
    • Sentry
    • Vanta
  5. careers page
    • Greenhouse
  6. DNS and mail records
    • Google Workspace
    • SendGrid
  7. subdomains
    • Zendesk

The tools reveal
the strategy.

Cold outbound, paid growth, or enterprise sales. The mix of tools a company runs tells you which, and we show you the evidence.

schematics.shScanned: 2026-11-03

  • sales tool on a subdomain
  • lookalike sending domain
  • cold-email infrastructure
  • sending service in mail records

scaling cold email

alder.exampleScanned: 2026-11-02

  • hosting setup
  • edge network
  • trust portal
  • single sign-on on a subdomain

good security

fable.exampleScanned: 2026-11-01

  • ad pixels on the page
  • conversion tags after consent
  • landing pages on a subdomain
  • call tracking in the page

running paid acquisition

Design Your Play

competitive displacement

Hey, are you happy with HubSpot?

account scoring

  1. HubSpot Forms on /pricing, running +20
  2. Gong confirmed +15
  3. Intercom on the home page, running +10
  4. Marketo declared, not running 0

45qualified

customer churn alerts

  1. 2026-10-05 schematics.sh: no change
  2. 2026-10-12 schematics.sh: no change
  3. 2026-10-19 schematics.sh: no change
  4. 2026-10-26 schematics.sh: no change
  5. 2026-11-02 schematics.sh: Loopio workspace added

outreach timing alerts

  1. 2026-10-12 schematics.sh: no change
  2. 2026-10-19 schematics.sh: no change
  3. 2026-10-26 schematics.sh: no change
  4. 2026-11-02 schematics.sh: 3 sending domains added

find compatible stacks

alder.examplelooking for HubSpot, PandaDoc, Calendly

  • HubSpot seen
  • PandaDoc seen
  • Calendly not observed

find compatible ats

checking Greenhouse, Ashby, Lever

  • heron.example: Greenhouse
  • birch.example: Ashby
  • quill.example: Lever
  • elm.example: none of these observed

Tools for Your Agents

Connect over MCP or the API and it works out the rest.

API & CLI
  1. $ node scan.js
  2. → POST /v1/explore
  3. {"domains": ["schematics.sh"]}
  4. ← 202 "status": "running"
  5. → GET /v1/scans/:batchId
  6. ← 200 "status": "running"
  7. → GET /v1/scans/:batchId
  8. ← 200 "status": "completed"
  9. {"name": "PostHog", "confidence": "confirmed"}
chat
  1. hey which of these companies are heavy posthog users?
  2. explore alder.example, birch.example, cedar.example
  3. evidence filter "posthog"
  4. PostHog is running on 2 of 3: alder.example and cedar.example. A scan shows whether it runs, not how heavily.
autonomous agent
  1. Scheduled task: find 3-5 new accounts using Loopio
  2. web search 40 candidate domains
  3. save_config rfp-response
  4. scan 40 domains
  5. results
  6. Loopio seen on [N] new accounts. Shortlist ready.

Built for the tools
other scanners skip.

From CRM to RFP response and tender intelligence. New technologies added upon request.

1,170 vendors · 88 categoriesCatalog

Earlybird Benefits

Early pricing, a say in which technologies we detect next, and feature request priority.

Request access