Slack — Go-to-Market — Product Case Questions

Role context: Senior Data Scientist, Slack Go-to-Market (Sales Strategy & Programs) · Est. study time: 60 min · 5 questions

How to approach product cases here

Every case follows one chain: understand the business goal, turn it into a data problem, pick the metric or method, name the bias and the trade-off, and land on a decision a go-to-market leader can act on.

Four facts about Slack's go-to-market sit under nearly every case:

• Two engines. Teams adopt for free and upgrade on their own; sellers turn spreading usage into company-wide contracts. Many outcomes could come from either, so credit is always contested.
• Net new ARR has four parts. New, expansion, contraction and churn. Most surprises live in the parts people aren't watching, usually contraction.
• Programs act through people. Reps and customer success managers choose which accounts to work, and they pick the promising ones. Comparing touched with untouched accounts measures that choice, not the program.
• Revenue is concentrated, slow and back-loaded. Large accounts carry half the revenue, deals take months, renewals come once a year, and bookings pile up at quarter end.

The metrics that matter: net new ARR and its parts, pipeline coverage, win rate, net dollar retention, gross revenue retention, seat utilization, discount depth, and active AI users.

Traps specific to this domain:

• Reading "pipeline sourced" or "accounts touched" as revenue caused.
• Judging a quarter at week 7 without the back-loading curve.
• Missing that a falling metric is a mix shift between segments.
• Booking expansion that returns as contraction a year later.

This role weights all five shapes because GTM leaders ask for all of them: one each of Diagnose, Measure impact, Launch or not, Measure success, and Forecasting, since planning cycles depend on a bookings forecast leadership can trust.