Armature has published about 291 library pages. Each one asks whether coding agents recommend a named product and answers with its install share, its rank, splits by agent and persona, and how many sessions considered it but picked a rival. The page for the payments leader shows 75 such sessions. The person most likely to read a page like that works at the vendor it names. Yet every page ends with the same three generic links ("See the service", "Read the results", "All library pages"). There is no form, no email capture and no link to the 45-check readiness scan. The GTM job post says research brings customers today but there is no repeatable way to find the next ones. These pages, already published and indexed, can be that repeatable way.
First action
Hand-add an "Is this your product?" form to the ten library pages with the most traffic this week.
How to measure it
Library-page report requests
- Now
- –
- Target
- 30 a month
- By
- 60 days
Steps
Pick the fields
Install share, rank, considered-but-not-chosen count and the top rival, from the existing page data.
Founding Engineer, Product 1 day
Write the block
One line showing the vendor's own loss, one promise, one work-email field.
Founding GTM 1 day
Build the template
Generate the block on all of the roughly 291 vendor pages and on every leaderboard row.
Founding Engineer, Product 3 days
Prepare the report
A private page with the losing runs, the winning rival and the docs the agents read, drawn from recorded traces.
Founding Engineer, Applied AI Research 1 week
Route requests
Match work-email domains to vendors; low-share vendors reach a founder within a day.
Founding GTM 2 days
Follow up
Offer a call built on the report that leads into the week-1 audit.
CEO (co-founder) ongoing
Measure
Requests, calls and Growth contracts by page, category and share band.
Founding GTM monthly
Why it works
Generate a block on every vendor page from the data the page already has: "Is this your product? Agents considered <product> in <N> sessions and chose someone else. See every losing run: which rival won, for which persona, and which docs the agent read." A single work-email field, with product and category prefilled, sends the vendor a private report built from the traces Armature has already recorded, and offers a call. Put the lowest-share and most-lost vendors first in line for a founder. Add the same block to every vendor row on the 43 leaderboards.
The reader arrives with their own numbers on screen, the strongest opening a $5,000-a-month service can get. The traces already exist, so each report takes minutes, and the work-email domain tells Armature exactly which vendor is asking.
Ready to use
ChecklistVendor block for library and leaderboard pages
[ ] Headline: "Is this your product?" [ ] Their line: "Agents considered <product> in <N> sessions and chose <top rival>" [ ] Promise: "See every losing run, the persona and the docs the agent read" [ ] One work-email field, product and category prefilled [ ] Private report page built from recorded traces [ ] Link to the 45-check readiness scan [ ] Same block on each leaderboard row [ ] Tracking by page, category and share band
Risks and how to handle them
Vendors dislike being profiled
Leave the public numbers as they are and send traces only to work emails at the vendor's own domain.
Free reports replace paid audits
Share where the vendor loses and keep the fixes for the audit.
Evidence
- Your websiteLibrary page for the payments leader (published October 14, 2026): install share 88% (578 of 657 judged sessions), rank 1 of 9, 75 sessions in which agents considered it and did not choose it, with splits by agent and by persona (junior developer 100%, enterprise team 83%, senior engineer 77%); closing links "See the service", "Read the results" and "All library pages"; no form, no email capture, no link to the readiness scan, no author.Source
- Your websiteSitemap (465 URLs, checked November 10, 2026): about 404 /library pages, about 291 of them "do-coding-agents-recommend-<product>" pages, plus guides such as "how-to-win-the-enterprise-persona"; 43 leaderboard pages (latest November 9, 2026), including pages for individual new models; 3 blog posts; /compare plus eight library "armature-vs" pages (Profound, Peec AI, Scrunch AI, Otterly, Ahrefs Brand Radar, Semrush AI Toolkit, hiring a devrel, LLM observability tools), none for Gauge or Amplifying; no case study pages.Source
- HiringFounding GTM (Paris, frequent trips to San Francisco): "Our customers are mostly US devtool companies, with high ACV." "Most of our customers find us through this research." "Our research brings customers to us today, but we haven't yet built a repeatable way to find the next ones." The role turns each study into a lead magnet with the research engineer, builds automations to find, qualify and reach prospects, and runs first calls.Source
- Your websitePayments leaderboard (updated September 29, 2026): 657 runs by five coding agents on 11 codebases; nine providers ranked, the bottom four with 1 to 3 wins each; links to an interactive board showing every run's session, diff and judge verdict, and a Markdown copy; no "is your product here?" prompt and no email capture.Source