Data engineers crave uniformity. One schema, one pipeline, one model that works for everyone – that is the whole shape of the toolchain they live in.Customers, it turns out, do not care. They want their own content, their own attributes, their own ways of slicing their data – and they expect the analytics to follow, instantly, every time they change something. Now do that for more than 300 tenants at once.Kathryn Smith presents a production case study from Thrive Learning – a multi-tenant learning experience platform serving 3 million users – on how to build embedded analytics that are bespoke per tenant and automated end-to-end, and what breaks in the stack when a team commits to that path.The talk covers two interlocking problems most multi-tenant SaaS data architectures do not have to solve. First: bespoke reporting at scale – how do teams deliver custom-pivoted data per tenant when every standardised tool in the stack assumes uniformity and the dbt state file grows linearly? Second: end-to-end automation – how do teams keep all of it working when customers reconfigure their platforms and expect their dashboards to follow immediately, every time, with no human in the loop?The talk walks through the architecture that emerged: how Thrive Learning fans tenant data out into per-tenant Snowflake schemas at scale, the role-based security that locks each tenant to their own schema, and the semantic layer built on top to power Cortex-based AI on properly isolated data.Attendees leave with: • A reference architecture for bespoke multi-tenant embedded analytics • A framework for what belongs in dbt versus what should be handled outside dbt at tenant scale • Patterns for end-to-end tenant provisioning across Snowflake, Terraform, and ThoughtSpot • Honest production gotchas that do not show up in vendor case studies