Customer Landscape and Case Studies
Know who uses Dagster, why they bought it, what pain they had before, and what outcomes they achieved.
Why this matters
Real customer stories are sales currency. You will use them in account research, in enrichment prompts ('does this account look like US Foods?'), in objection handling, and in sales enablement content. Two patterns that show up across multiple case studies become repeatable narratives — that is the gold.
Reading order (read all five in full)
- dagster.io/customers — landing page, scan all logos
- US Foods — enterprise, regulated, complex
- smava — fintech, high data trust requirements
- HIVED — logistics, scaling fast
- Mejuri — retail, modern stack
- Analytiks — services / analytics consultancy
Template to fill per case study (from memory after reading)
- Company:
- Industry:
- Team size (data team if known):
- Stack before Dagster:
- Pain before Dagster:
- Why they chose Dagster:
- Outcome (with metric if quoted):
Recurring themes to anchor on
Pain themes: cron-based brittleness, no lineage when something breaks, slow debugging, inconsistent metrics across teams, weeks-long onboarding for new data engineers, fear of touching the pipeline.
Outcome themes: 99%+ pipeline uptime, new engineer productive in hours not weeks, self-service data access for analysts and PMs, foundation that unlocks AI/ML use cases, reduction in on-call load.
Hands-on exercises
Fill the case study template for all five companies
Auto-savedAfter reading, fill the template (from memory) for US Foods, smava, HIVED, Mejuri, and Analytiks. Save all five here.
Pattern recognition
Auto-savedAfter completing all five: (1) what pain shows up in three or more case studies? (2) what outcome shows up in three or more? (3) what kind of buyer (title, team shape) shows up most often?
Self-check
Answer from memory first. Then reveal the model answer and grade yourself honestly.
Pick the case study that resonated most and tell its pain → solution → outcome arc in three sentences.
Name two pain themes that recur across multiple customers.
Name two outcome themes that recur.
Which case study would you reach for if a prospect said 'we are a small data team, we cannot adopt something this heavy'?
Which case study would you reach for if a prospect said 'we are already on Databricks, why do we need this'?