How Magic Runs 75 Custom Insights in Airspeed | Revenue Execution Series

Most teams start with yes/no insights: was the competitor mentioned, was budget discussed. Magic took it much further. They now run around 75 prompt-based insights across sales, support, CS, and key accounts, and every one of them has to drive a business action. In this session of the Airspeed Revenue Execution Series, our customer user group, Adam Blech (Customer Success Lead, Airspeed) talks with Alex Wilson, who leads sales support, customer success, RevOps, and sales enablement at Magic. Alex walks through how his team builds, governs, and evolves Custom Insights so they deliver real behaviour change and pipeline impact, not just more data. What we cover: Why prompt-based insights capture what was actually meant, not just what was said Using call tags to trigger the right insights on the right calls Three ways Magic uses insights: tracking team behaviours, running controlled experiments (pricing included), and silent baselines that don't change how reps behave Keeping 75 insights manageable with Groups, a QA stage, and a review every 30 days Syncing to HubSpot with append and AI merge so deal properties build up over time Keeping a human in the loop on CRM fields, and the "team deal" alert that protects revenue Feeding discovery call quotes into personalized HubSpot email sequences Alex's rule: if you ask a question more than twice, make it an insight, a scorecard, or an agent Alex's advice for teams getting started: before you add more insights, pull up a few real calls and ask what action each insight should lead to. If it doesn't drive a decision, it probably doesn't belong. Want to go through your own insights with us? Reach out to your Customer Success Manager, or learn more at goairspeed.com.