Why we read the docs before we score the tool

Every GTM vendor publishes three sets of documents, written for three different audiences. Marketing pages are written for prospects. Help docs are written for paying customers. API docs are written for engineers. Almost nobody reconciles them, and the gaps between them are where the truth sits.

The pattern that started this site: a tool whose homepage promised complete account safety while its own help center carried a step-by-step guide to recovering a restricted account. Both pages were live at the same time. Neither linked to the other.

So that’s the method. For each tool we capture everything the vendor publishes, from the pricing page down to the Chrome extension’s permission manifest. We archive it with dates, compare the documents against each other, and score what they actually support.

Wireframe contour diagram
marketing claims plotted against what the help docs actually say

We start with LinkedIn outreach tooling because that’s where the marketing drifts furthest from the operational reality, and where the buyer has the most to lose. Enrichment, deliverability, CRM and the rest of the stack follow.

Three commitments from day one. Every finding carries its source and capture date. Every vendor sees the findings before publication and gets space to respond. And corrections are public and dated, never silent.

Build a GTM tool and want it covered? Email reviews@gtmstreet.com or read how listing works.