Antimetal has 79 integration pages, each a good answer to "does it work with my stack?". But the two main buttons on those pages are "Connect" and "Read the docs". "Connect" opens the customer app at overlook.antimetal.com, which only helps someone who already has an account; Antimetal's own launch post tells everyone else to "book a demo and we'll get you set up". "Book a Demo" sits only in the header, and the demo form never asks which tools the visitor runs, even though it promises a walkthrough "on your own environment". The visitors who arrive already naming their stack are the ones the page gives no next step.
First action
Open five integration pages while signed out and record where each main button leads; then count last quarter's demo requests that started on an /integrations/ page.
How to measure it
Integration-page demo requests
- Now
- –
- Target
- Double the current monthly count
- By
- 60 days
Steps
Measure the baseline
Sessions on /integrations/ pages, clicks on "Connect" by signed-out visitors, and demo requests that began there, for the last 90 days.
Marketing (Growth) 1 day
Change the signed-out button
On all 79 pages, signed-out visitors see "See Antimetal on your <tool> setup" linking to /book-a-demo?stack=<tool>; signed-in customers still see "Connect".
Design Engineer 2 days
Add the stack question
A multi-select on the demo form fed by the same 79-tool catalogue as the integration pages, pre-ticked from the link. Input: tool names only, no credentials.
Design Engineer 2 days
Build the stack brief
An automation that takes the form answers (company, size, tools), looks up each tool's published page for permissions and setup steps, and writes a one-page brief into the CRM record and the seller's Slack channel.
Sales Development Representative 1 week
Draft the confirmation email
The same automation drafts a reply to the prospect listing the read-only access each of their tools needs before the call. The SDR reviews and approves every email; nothing is sent automatically.
Sales Development Representative 3 days
Handle missing tools
If a prospect names a tool outside the 79, log it as an integration request for the Platform Engineer and say so honestly in the brief.
Platform Engineer 1 day
Review weekly
Success measures: demo requests from integration pages, share of first calls that include a live connection, and time from request to first call.
Marketing (Growth) weekly
Why it works
For visitors who are not signed in, replace the main button on every integration page with "See Antimetal on your <tool> setup", linking to the demo form with that tool already selected, and add a "which tools do you run?" multi-select built from the 79-tool catalogue. Then build a small automation behind the form: when a request arrives, it assembles a one-page stack brief for the seller (which of the prospect's tools Antimetal connects to, the permissions each needs, and the setup steps already written on those pages) and drafts a confirmation email to the prospect with the same checklist, so the first call can be the promised walkthrough on their environment. A person approves each email before it is sent. Signed-in customers keep the current "Connect" button.
A buyer on an integration page has already told you their stack and their intent. Meeting them with a button written for existing customers wastes that. Carrying the tool through to the form and the first call removes a round of discovery and makes the demo specific, and the setup content needed for the brief is already published on the pages themselves.
Ready to use
CopyStack brief (one page per demo request)
Company / size: Came from: /integrations/<tool> Tools they run that Antimetal connects to: <list> Tools they named that are not in the catalogue: <list, logged as requests> Access needed before the call (from each integration page): <tool: key type, read-only scopes> Suggested first investigation to show: <one alert type common to their stack> Proof to mention: published customer results on the homepage Open questions for the call: <three at most>
Risks and how to handle them
Customers lose the quick "Connect" link
Keep it for signed-in sessions and in the docs.
A longer form lowers completion
Make the stack question optional and pre-ticked from the page the visitor came from.
Evidence
- Your websiteIntegration pages (checked November 16, 2026): the index lists 79 tools, each with its own page of setup steps and permissions. On the Datadog and PagerDuty pages the two main buttons are "Connect" (to the signed-in app at overlook.antimetal.com) and "Read the docs"; "Book a Demo" appears only in the site header and nothing addresses visitors who are not yet customers. The index has no way to request an integration.Source
- Your websiteDemo page: "Tell us a little about your team and we'll set up a walkthrough of Antimetal on your own environment."; "A 30 minute walkthrough of the platform"; six required fields (first name, last name, work email, company, company size from 1-50 to 5000+, how did you hear about us); button "Request a demo"; no calendar, customer logo, testimonial or question about the visitor's tools.Source
- Your websiteCoding agents post (April 16, 2026): "A single MCP for the runtime context your coding agent is missing."; "If you're an Antimetal customer, install the plugin from github.com/antimetal/skills and bring it to your coding agent today." "If you're not, book a demo and we'll get you set up." The public skills repository shows 3 stars and asks for an Antimetal account at first use.Source
- HiringSales Development Representative (NYC, posted May 11, 2026, open): "Own a book of ~50 target accounts", "researching personas, crafting tailored outreach, and adjusting segmentation based on response data."; "Feed manual workflows into automation pipelines;" "partner on tooling selection and integration."; "support closing SMB deals with polished collateral (decks, one-pagers, talk-tracks)."; "Track SDR KPIs (volume, response rate, SQL conversion, meetings booked)"; "instrumenting real-time dashboards and alerts".Source