Profound 
-
The problem
Profound paid an outside marketing agency to run its Google Ads. Nick, who had run Google Ads for large SaaS companies, wanted to bring that work in-house with agents of his own.
-
What they built
A set of agents, each covering one part of running Google Ads, that run on a schedule. They watch campaign performance, review the search terms ads showed for, look for new keywords, check ad copy, location, device and scheduling splits, and gather competitive information. Findings go to Slack with a button to act on each one. The agents never change the ad account on their own; a person decides.
-
So what
Paid search gets checked on a schedule, suggested changes land in Slack, and a person approves every change.
Under the hood
For GTM engineers
Individual agents built on the Google Ads API, each scheduled with GitHub Actions, posting recommendations into Slack with an action button. Human-in-the-loop by design: no agent writes to the ad account directly.
More examples
Other systems GTM engineers have built, or see all of them.
-
Sequel.io Turns a product brief into a full launch kit, from blog post to sales messaging and BDR emails, so a four-person team can launch weekly
Kathleen Booth · VP of Marketing -
LangChain Every Monday, each LangChain rep gets a rundown of what changed at their accounts and the top things to do about it
Vishnu Suresh · Software Engineer - Sequel.io
Sales has battle cards for all 19 competitors that mostly keep themselves current each week, without a product marketer on the team
Kathleen Booth · VP of Marketing
Hiring someone who can build like Nick?
We search for GTM engineers who have shipped systems like this one, and Joe speaks to every candidate before you do.