marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
master-zapier-plan-draft/research/zapier/docs/contacts-summary.md
George Lambert b4150c8250 Milestone 0: import zappier billing, Verae middleware, and Zapier research 
Compose-ready workspace: packages/zappier (rate card, portal, Stripe),
packages/verae-zapier-middleware (timestamp + NATS), packages/verae-zapier
(CLI app), vendor/zapier-platform, and research/zapier vendor corpus.

Gate 0 structure checks pass. Product code and research are not yet wired.
2026-09-09 02:37:36 -04:00

3.5 KiB
Raw Blame History

CONTACTS.md — what was collected

Source file: CONTACTS.md (A–Z table + 15 vertical sections)
Machine copies: contacts.csv, contacts.json (256 brands)
Snapshot: 17 August 2026
Parent brief: Vendors.txt (15 verticals) → live Zapier catalog filter

This is the deeper 15-vertical subset, not the 9,985-app dump. Contacts come from official about / legal / contact pages. Personal employee inboxes were omitted. — means not published first-party.

Why it exists

Vendors.txt named verticals and counts, not companies. The catalog was matched to products that create contemporaneous records (signatures, inspections, claims, filings, recordings, certificates). Result: 270 placements / 256 unique brands (some products sit in more than one vertical in the research narrative; the contact JSON is 256 unique slugs).

Coverage (256 unique brands)

Field Count Share
Brand / website 256 100%
Sales / demo / contact URL 252 98%
LinkedIn 248 97%
Support URL 246 96%
HQ address 215 84%
Legal / company name 204 80%
Email 164 64%
Phone 147 57%

Unique legal entities with a published name: 193. Several parents own more than one Zapier-listed product.

Shared parents (switchboard once)

Brands Legal / parent
3 8am, LLC (CasePeer, DocketWise, MyCase)
3 Filevine, Inc. (Filevine, VineSign, …)
3 Zoho Corporation
2 Paperform Pty Ltd
2 Workday, Inc.
2 Canvas Solutions, Inc. (Device Magic / GoCanvas family)
2 Intellistack, LLC
2 SurveyMonkey Inc.

Also called out in the directory: Vertafore, Applied, Nemetschek/GoCanvas, SafetyCulture, OneTrust, Smarsh, Pearson/Credly.

How the file is organized

  1. How to use — OEM starts at Sales / demo, then sales@ / partnerships@ if listed.
  2. All vendors A–Z — one table: company, brand, phone, email, sales URL, HQ.
  3. Fifteen vertical sections — the same companies grouped as in Vendors.txt, with per-vertical contact tables.

Vertical headings in CONTACTS.md:

  1. E-Signature and Execution
  2. Contract Lifecycle Management
  3. Inspection, Safety and Field Evidence
  4. Construction and Change Orders
  5. Legal Practice and Case Management
  6. Insurance and Claims
  7. Accounting, Audit and Tax
  8. HR, ATS and Employment Records
  9. Property, Title and Mortgage
  10. Meeting and Call Recording / Transcription
  11. Document Generation and PDF Automation
  12. Credentials and Certificates
  13. Forms and Field Data Capture
  14. GRC, Compliance and Risk
  15. Logistics and Chain of Custody

How to use it

  • Partnership / OEM: sales form first; confirm the number on the linked page before dialing.
  • Do not email personal employee inboxes (they were never collected).
  • Full catalog outreach (non-vertical): CONTACTS-ALL.md / contacts-all.csv.
  • Why this vendor / what record they mint: VENDOR-RESEARCH.md and profiles/01–05.

Limits

  • Numbers and inboxes change.
  • Many SaaS vendors only publish a form — that URL is the contact path.
  • A few brands have no sales URL (rare).
  • This file is not a capability dump (no trigger/action lists). See CAPABILITIES.md.

Related

  • Full directory: CONTACTS-ALL.md
  • Fit, USP, Zap counts, “record they create”: VENDOR-RESEARCH.md
  • Long dossiers: profiles/
  • Mongo: zapier.apps filtered by the same slugs