Jerry YangBuilds idempotent GTM automation platforms at Block

“I stopped trusting automations that launch without an owner and a health metric. At Block, every GTM automation ships with a runbook, an alert, and a named on-call before it goes live, because the ones that survive are watched like production systems.”

William ArmstrongBuilt GTM automation pipelines that saved a small business $50K annually

“The automations that survive are the ones I can iterate on fast. My $50k QuickBooks sync took 30 versions in three days because the real friction lived in 15-year-old edge cases, not the base case. I ship the dumbest end-to-end flow first, then rebuild around exceptions.”

Alina VandenbergheBuilt AI agents that automate GTM workflows

“The automations that survive past month one are the ones tied to a real metric someone checks weekly, not the ones we celebrated at launch. At Chili Piper, our automate-everything channel ships fast, but the projects that stick are the ones where ops, data, and GTM share ownership and can see if pipeline actually moved.”

Matteo TittarelliBuilt warm-up outbound motion at Airbyte that sustained pipeline growth

“The automations that keep working are the ones tied to a real signal, not a one-time setup. At GTM Engineer School, we see this constantly: workflows built on a single trigger decay fast, but a system that stacks signals into a sales-readiness score and routes the right context to the right rep keeps compounding.”

Spencer TahilChief Growth Officer - AI Enthusiast in GTM, RevOps, and ABM

“The automations that last are the ones built around a clear desired state and handed off with documentation, not the ones that need a hero to babysit them. I’ve seen a VP of sales keep a system running months later because we spent the extra week writing down why each trigger existed, not just what it did.”

Khari HarperGTM Engineer

“The automations that last are the ones you build simple first and then upskill, with Zapier for the boring repeatable stuff and N8N only when you actually need dynamic logic. I write every step out by hand before I touch a tool, because the ones that break after month one are usually the ones I tried to build complex and reverse into simple.”

Martín Ramírez

“The automations that last are the ones tied to a real outcome, not a neat diagram. I've watched GTM engineers spend weeks stitching enrichment tables to avoid a five-minute call, then wonder why pipeline is flat. If it doesn't move win rate, CAC, or sales cycle, it's just a prettier way to not make calls.”

Brian NzauSenior AI Strategy and Solutions Manager at revlogic

“The automations that survive past month one are the ones wired to a real signal, not a static list. I have watched too many teams ship a sequence, high-five, and come back 90 days later to a CRM full of decayed contacts and reps ignoring the alerts. The fix is not fancier logic; it is building the loop so the automation learns from what actually happens.”

Rachel LaiGTM Engineer driving innovation in AI startups

“The automations that survive past month one are the ones I can debug without re-learning the whole flow. At Olive, I built our outreach sequences so every step left a breadcrumb, because a 0.1% reply rate meant the tool was already broken and we just hadn't noticed.”