Building the Automation Backbone of a Product-Led Growth Motion

We recently launched a new AI assistant product line at CampusESP. We've never supported an in-product sales motion, and we needed our Development team focused on actually building the AI Assistant, so they didn't have time to work on the purchasing motion. I built an automation that uses the purchase signal from the product to reflect important details in our CRM, HubSpot, which then triggers native HubSpot messaging and sales workflows. The other half of the story starts when that deal closes. We used to pay a contractor firm to generate and send invoices. I replaced that with an n8n workflow that automatically creates the QuickBooks invoice the moment a deal is marked Closed Won - pulling contract terms, resolving the right customer and billing contact, and writing invoice details back to HubSpot. Once that was working for the PLG motion, I extended it to cover our other four pipelines (Direct, Add-On, Partnership, Renewals), each with its own billing logic. This talk covers both pieces: the low-lift deal-creation automation that made a new sales motion possible without dev work, and the invoicing automation that replaced a paid contractor, cut turnaround time, and improved data accuracy in HubSpot. I'll walk through the actual logic and tradeoffs - where automation should just run, and where it should stop and flag a human instead.