Preparing a 30-minute mock discovery call as a prospective LiteLLM enterprise AE, with a Head of AI Platform Engineering evaluating litellm.ai. Told LiteLLM does not do value-based selling given the product — how will the call go? Is it just answering questions and selling the benefits of Enterprise?
This playbook is built from 24 sourced findings across 5 independent hosts — LiteLLM's product, Enterprise docs, and pricing pages, current AE role listings, and one independent production-practitioner write-up — checked as of 14 Sep 2026. It gives a minute-by-minute plan, a question bank, an OSS-vs-Enterprise map, and a scorecard.
Hypothesis-led, ordered roughly as the call runs. Ask a handful well; do not interrogate.
The core gateway is the same MIT-licensed codebase. OSS covers the fundamentals; Enterprise is for scaled organizational governance, deployment options, support, and procurement. Never imply gateway basics are paywalled.
Rule: clarify the question, answer what the docs support, and book an SE/engineering follow-up for anything deeper. Overclaiming to this buyer ends the evaluation.
"Thanks for the time — I know you can grab a 30-day Enterprise trial key yourselves without talking to us, so my goal today isn't to gate anything. I'd like to understand how you route LLM traffic now, see whether Enterprise is even relevant at your scale, and if it is, leave with a trial plan your team actually cares about. Sound fair? Anything you want to make sure we cover?"
"Given what you've described — self-hosted OSS proxy, roughly forty teams on virtual keys, SSO past the 5-user free tier, and a multi-region requirement — three things you named sit on the Enterprise side: SSO at your scale, audit logs, and multi-region under one license. The routing and fallbacks you asked about are already in the open-source core, so you don't buy those. Want me to walk through just those three?"
"Here's what I suggest: I email the 30-day trial key today, you validate SSO with your IdP and the admin/worker multi-region split in staging, and we set the bar now — say, p99 overhead and a passing security review. I'll bring an engineer to a 45-minute working session next week and loop in whoever owns procurement, since AWS or Azure Marketplace may let you use existing commit. Does Thursday work?"
| Category | Finding | Call implication | Source |
|---|
Method: 24 sourced findings, one per factual consideration, drawn from 5 independent hosts (official LiteLLM product, Enterprise docs and pricing pages, current AE role listings, and one independent production-practitioner article), checked as of 2026-09-14. The most-cited single URL (LiteLLM Enterprise docs) backs 6 of 24 rows (25%). Call-plan timings, scripts and scorecard are coaching guidance built on those findings; each factual claim links its source. Nothing was cut; all 24 rows appear in the evidence table.