GTM Engineer: Ryan CRO @ Quotapath

Ryan Milligan started at Quotapath as Director of RevOps, spent four and a half years building the data and systems foundation, and is now CRO. His team has run at 100% blended quota attainment in 8 of the past 10 quarters, never below 90%, and has grown closed ARR per rep 1.7x in 18 months. The GTM engineering team doing most of the building is two people.

In this episode, Ryan gets specific about how the whole system works: the data architecture decision he made on day one that still underpins everything, how he splits Dust and Claude into distinct roles across the sales cycle, and why he thinks the current wave of everyone building their own tools is a bubble with a painful correction coming. He also makes a sharp case that comp plan design is one of the highest-leverage tools a CRO has for changing the mix of revenue being closed, not just paying people.

Topics discussed:

• Processing data in the warehouse nightly and reverse ETL-ing into CRM so both always speak the same language

• The build vs. buy litmus test: uniquely bespoke and relatively fixed vs. everything else

• Rep-built V1 prototypes handed to RevOps for productionizing and org-wide rollout

• Dust as system of record, Claude as system of action, and how they split across the sales cycle

• Thursday multi-thread standup: every rep required to arrive with all multi-threads queued for active opps

• The "what would it take to close twice as many deals" framework for identifying which agents to build next

• Warm outbound architecture using Clay, Unify, and product interaction data as intent signals

• Comp plan design as a lever for changing the shape of revenue reps close, not just incentivizing volume

• Why data architecture is the only real defense against confident AI hallucination

• GTM engineer defined as the owner of the full prospect-to-renewal lifecycle

Listen to more episodes: 

Apple 

Spotify 

YouTube