Gather runs 6 LinkedIn ads for Grapevine that promise smarter sales, but the click lands on a GitHub repo

This is one of the sharpest scent breaks we have seen. Gather is running a LinkedIn campaign to sales leaders under the promise of Smarter Sales with Grapevine, a Slack-native answer engine that plugs into GitHub, Google Docs, HubSpot, and Notion. Every element of that copy is aimed at a revenue leader who wants their reps to stop digging for answers.

The click, however, does not land on a marketing page. The destination getgrapevine.ai/use-case/sales-teams resolves through to the gathertown/grapevine GitHub repository, with the repo file tree, an Uh oh error banner, and a README fragment about installing mise for toolchain management. A VP of Sales who clicks Learn more sees a source-code page for engineers, not a sales-teams use case. That is why the message match score comes in at 1.6 out of 10.

The URL getgrapevine.ai/use-case/sales-teams reads like a use-case page for sales teams, but the captured content is a GitHub repository view for gathertown/grapevine. The visible H1 is simply Grapevine. The rest of the first viewport is repo navigation: Folders and files, a Latest commit table, and directory names like connectors, docs, js-services, kustomize, migrations, scripts, src, supabase, and tests.

The README fragment that follows describes Grapevine as a self-hostable realtime unified context system, with Quick Start instructions to install mise for toolchain management and edit a .env file. That is documentation for developers who plan to deploy Grapevine themselves, not a sales-team pitch.

There is no hero framed around sales outcomes. There is no Slack demo. There is no integrations proof strip. There is no visible primary CTA that matches the ad's free 30 minute deploy offer. The page does not continue any of the four promises the ad earned the click on.