Frontal's GTM API directory is the biggest thing on the site: 235 URLs (52 API reviews, 103 comparisons, 57 alternatives pages, 4 costed stacks), more than the 172 URLs of everything else combined. Its readers are people choosing enrichment, sending and CRM APIs, which is the exact work Frontal sells as GTM engineering. Yet on the five directory pages we read, every in-content button goes to a vendor ("Visit Apollo", "Try Clay") or to another directory page. None has a "Book a call" button, a link to a service or case study, or an email form. The closing blocks say "Run the waterfall in Clay" and "Wiring this up yourself? Build it in Clay." The line "Frontal is a Clay Elite Studio Partner" is plain text with no link. The play pages already solve this with a closing "Have us run this play" block; the directory has no equivalent. A smaller sign that the section has outgrown its template: the hub's description still says "26 GTM APIs" while the page shows 52.
First action
Write the closing block once and add it to the stack template, the smallest section, to test it.
How to measure it
Directory-sourced intro calls
- Now
- –
- Target
- 10 a month
- By
- 60 days
Steps
Count the baseline
Pull sessions on /gtm-apis pages and bookings whose first page was in the directory, for the last 30 days.
Operations Manager 1 day
Write the block
One headline, two lines, a Book a call button, a link to the Clay agency page and one case study. Keep it below the existing vendor block, not in place of it.
Content Lead 1 day
Add it to the stack pages
Four pages. Word it as "Have us build this stack" and name the stack in the booking note.
GTM Engineer 1 day
Roll out to reviews, comparisons and alternatives
One change per template covers the other 212 pages. Match the case study to the category where one exists.
GTM Engineer 2 days
Link the partner line
Turn "Frontal is a Clay Elite Studio Partner" into a link to the Clay agency page on every page.
GTM Engineer 2 hours
Fix the hub description
Change "26 GTM APIs" to 52 and take the number from the same data the page uses so it cannot drift again.
GTM Engineer 1 hour
Tag the bookings
Pass the page and section as source tags to the booking flow so directory calls show up in the CRM.
Operations Manager 1 day
Review after 30 days
Calls, qualified calls and which page types produce them. Move the block higher on the best ones.
Co-founder & Head of GTM monthly
Why it works
Add one reusable closing block to every directory template: "Want this built in your own workspace? We are one of six Clay Elite Studio Partners." with a Book a call button, a link to the Clay agency page and one matching case study. Make the partner line a link. On the four stack pages, add "Have us build this stack" beside the vendor buttons, since a costed stack is already a project scope. Tag every booking that starts from the directory so pipeline from it can be counted. Fix the hub description to say 52.
A reader comparing two enrichment APIs on cost per record is mid-build and has budget. Some will build it themselves, and the vendor buttons serve them. The ones who would rather have it built have no next step today. The block costs nothing, changes no content, and the plays section shows the pattern already fits the site.
Ready to use
CopyDirectory closing block
Headline: Want this built in your own workspace? Body: We build and run these stacks for B2B tech teams, inside your Clay, HubSpot or Salesforce. Frontal is one of six Clay Elite Studio Partners. Button: Book a call Links: See our Clay work | Read the AirOps case study Small print: For B2B tech companies from Series A onward, with a sales team.
Risks and how to handle them
The directory starts to read like a sales page and loses trust
One block at the end of each page, clearly labeled, with the reviews themselves unchanged.
Calls from builders who are too small
State "Series A onward, with a sales team" in the block, as the FAQ already does.
Evidence
- Your websiteDirectory pages read on November 18, 2026 (the Apollo API review, Apollo vs Clay, Apollo alternatives, the waterfall enrichment stack and the MCP servers page): every in-content button goes to a vendor ("Visit Apollo", "Try Clay") or to another directory page. None has an in-content "Book a call" button, a link to a service page, the Clay agency page or a case study, or an email form. Closing blocks read "Run the waterfall in Clay" and "Wiring this up yourself? Build it in Clay."; "Frontal is a Clay Elite Studio Partner" appears as plain text with no link.Source
- Your websiteDirectory sitemap (235 URLs, checked November 18, 2026): 52 API reviews, 103 comparisons, 57 alternatives pages, 4 costed stacks and 10 topic pages. The main sitemap lists 172 URLs for everything else on the site.Source
- Your websiteDirectory hub: the description line says "26 GTM APIs researched from their own pricing pages and docs" while the page says "52 providers reviewed" and "Showing 52 of 52"; "44 of the 52 now publish an MCP server" and "23 of the 52 can be used at zero cost".Source
- Your websitePlays library: "28 go-to-market plays, each with its workflow diagram, its numbered steps and the tools it runs on. Every step is open to read." Plays are numbered 01 to 43 with gaps. Each play page ends with "Have us run this play" and a "Book a call" button; the Closed-Lost Revival play has 7 steps, no downloadable template and no email capture.Source