Signal › Contributors

Ben Crawford

I got into RevOps before it was called RevOps. In 2016, I was a sales operations analyst at a mid-size SaaS company in Austin, and my job was to keep the CRM clean, build reports for the VP of Sales, and figure out why our pipeline numbers never matched reality. The answer was always the same: data hygiene. Reps weren't logging activities. Stages weren't standardized. The "close date" field was aspirational fiction. I spent 80% of my time cleaning data and 20% analyzing it.

I joined Outreach in 2018 as their second RevOps hire. Outreach was growing fast, really fast, and the operational infrastructure was held together with duct tape and Zapier. My job was to build systems that could scale. Over three years, I built the lead routing engine, the territory model, the commission calculator, the pipeline inspection framework, and about 200 Salesforce automations that I still see referenced in LinkedIn posts by people who don't know I built them.

The most important thing I built at Outreach was the revenue model, a bottoms-up forecasting system that predicted quarterly revenue within 3% accuracy by analyzing pipeline velocity, stage conversion rates, and rep-level patterns. Before that model, forecasting was essentially the VP of Sales asking each director, "How do you feel about the quarter?" and averaging the results. The model replaced vibes with math, and it was the single most impactful operational improvement in my career.

In 2021, I moved to Gong as Head of Revenue Operations. Gong was the perfect environment for a data-obsessed RevOps person because the product literally records and analyzes every sales conversation. I had access to data that most RevOps teams dream about. We built an operational framework that connected marketing attribution to sales conversations to customer success outcomes, a full-lifecycle view that most companies claim to have but almost none actually do.

I left Gong in 2024 because I'd become increasingly frustrated by the gap between RevOps discourse and RevOps reality. On LinkedIn, RevOps is all about "aligning revenue teams" and "driving predictable growth." In practice, it's about fixing a broken Salesforce workflow at 11 PM on a Friday because the quarter closes Monday and the CEO just realized the dashboard is wrong.

I write about the unglamorous operational work that actually drives revenue. Not the strategy decks. The Salesforce formulas.

I live in Austin with my wife and our golden retriever, Quota. (He always overachieves.)

Experience

Articles by Ben Crawford (7)

The Real Reason Your Company's AI Pilot Never Went to Production87% of enterprise AI pilots never reach deployment. It's rarely the model. It's data access politics, security review bottlenecks, the sponsor who lef · Mar 11, 2026The Negative CAC Playbook: How the Best Companies Get Paid to Acquire UsersA small number of companies have achieved the impossible: their customer acquisition cost is negative. They make money on the act of acquiring each ne · Mar 16, 2026The $100M AI Researcher Package Quietly Died. Here's What Replaced It.Through 2024 and 2025, top AI labs paid eye-popping cash and equity packages to retain a handful of researchers. May 2026 data shows the headline numb · May 20, 2026B2B Marketplace AEO: When Procurement Asks ChatGPT for VendorsEnterprise procurement teams are using AI assistants to build vendor shortlists before any RFP goes out. The B2B platforms that own these citations ow · May 25, 2026GraphQL vs REST for AEO: Why API Schema Shapes LLM DiscoverabilityAngi, Thumbtack, and HomeAdvisor are losing lead share to AI assistants that hand users three pre-vetted contractors in a single answer. The trades th · May 25, 2026HTTP/3 and QUIC: How AI Crawlers Now Prefer Sites That Support the New TransportMortgage, ROI, retirement, and savings calculators get cited by ChatGPT and Perplexity at roughly four times the rate of equivalent static articles in · May 25, 2026Medium Publications for AEO: The Honest TradeoffApp Router's streaming model is a performance win for human users and a citation risk for AI crawlers. The teams getting cited treat Suspense boundari · May 26, 2026