Teardown No. 100 · Newsletter

44 Subscriber Tags, None Set by Hand: How Adam Schoenfeld runs newsletter audience ops with coding agents and beehiiv

Adam Schoenfeld runs Adam's GTM Report as a one-person business and serves about 20K GTM leaders, builders and practitioners. He uses Codex and Claude Code with beehiiv's API and MCP to segment subscribers, enrich their profiles and set up engagement paths. For the small group of subscribers who work at companies in his market Index, his agents enrich the subscriber, match them to the company, check verification status and contact history, and prepare a Gmail draft asking them to claim their company's profile. He reviews and sends each draft himself. He now has 22 custom fields and 44 subscriber tags in beehiiv, and he writes that he didn't configure a single field or tag by hand.

Adam Schoenfeld · schoenyVerified Nov 10, 2026Markdown copy

The problem

He serves about 20K GTM leaders, builders and practitioners, which he calls a large, diverse audience with a wide TAM. Inside it is a much smaller group of marketers and execs at the GTM Tech brands in his Index. When they subscribe, he has an extra objective: ask them to claim and verify their company’s profile through his Brand Portal. He moved from Substack to beehiiv because he “couldn’t have more control over how I manage and communicate with my audience.” He is not an engineer. He writes, “I hadn’t touched a terminal until October last year. I didn’t have a GitHub account until January.”

The blueprint (as he describes it)

  1. beehiiv at the center. He manages subscribers, publishes and runs workflows to different segments at key moments in the journey in beehiiv. Codex and Claude Code build those workflows through beehiiv’s API and MCP.
  2. Enrich and match new subscribers. His agents use ZoomInfo and FullEnrich (both via API) for subscriber enrichment. Custom code matches subscribers to Index companies, then the workflow checks verification status and contact history.
  3. Draft, don’t send. The workflow prepares a Gmail draft. “My job is to review and send it.” He personalizes the emails a bit and sends at his convenience.
  4. Hand off to automation after action. Once a subscriber takes action, an automated workflow takes over based on the steps they’ve taken. Enriched details go back to beehiiv, including claim status and interest in partnerships.
  5. A night shift. His /night-gtm skill starts a scheduled process at 10:30 p.m. Scripts pull posts, jobs, feeds and website changes and update metrics. Agent skills enrich saved links, look for hiring patterns, update wiki pages and edit new research. A final stage checks freshness, links, failures and unfinished work, prepares a research summary and the morning emails, sends a completion update on Telegram, and leaves decisions that need him on an admin page.
  6. Save the correction. “A repeated mistake becomes a better instruction, a check, or a script fix.” He writes that running it again doesn’t teach it anything; saving the correction does.
  7. Two agents, one context. Claude Code and Codex share the same context and skills in a local workspace synced to GitHub. They can work on different tasks or review each other’s work.

Stated results

  • 22 custom fields and 44 subscriber tags in beehiiv. “I didn’t configure a single field or tag by hand. My agents built it all.”
  • A Drafts folder of prepared outreach emails after a week of running the workflow.
  • The morning report shows market changes, research progress, content performance (including beehiiv opens and clicks) and where he needs to make a call.
  • No numbers stated for drafts sent, profiles claimed or subscribers gained.

Caveats

  • Self-described system; no outcome numbers for the outreach workflow.
  • beehiiv sponsors the newsletter. He writes that he was building on it before they became partners, and the post includes a beehiiv discount code and an Apify partner signup link.
  • The post opens with a sponsored spotlight for another company.
  • He is a solo operator and writes that his details probably won’t fit a bigger company’s environment.
  • Handles: X @schoeny (bio links adamgtm.com) and LinkedIn /in/adamschoenfeld (linked from posts.adamgtm.com), verified 2026-11-10. A Bluesky account schoeny.bsky.social exists but has no name or link, so it is not used. No Instagram, TikTok or Mastodon account checked as his.

FAQ

How does Adam Schoenfeld use AI agents for his newsletter?

He uses Codex and Claude Code with beehiiv’s API and MCP to build workflows that segment subscribers, enrich them with ZoomInfo and FullEnrich, and prepare personal Gmail drafts for a narrow group of subscribers. He reviews and sends each draft himself.

Do the agents send emails on their own?

No. The workflow prepares a Gmail draft and his job is to review and send it. Automation takes over only after the subscriber takes action.

What results has he shared?

22 custom fields and 44 subscriber tags in beehiiv that his agents built, with none configured by hand. He doesn’t state how many profiles were claimed or how many drafts were sent.

Do you need to be an engineer to build this?

He says he isn’t one. He hadn’t touched a terminal until October last year and didn’t have a GitHub account until January.

Sources

Want agents like these working your distribution? Get It Built. Get new teardowns weekly: subscribe (double opt-in).

Get one teardown a week.

Same format, a new operator every issue. Double opt-in.