Why we ask providers for maintenance stories, not demo dazzle

MetricHarbor interviews providers with a simple prompt: show how a team keeps a cohort artifact alive six months later. We look for change logs, office hour rhythms, and examples of teams rewriting assumptions when data drifts.

Demo dazzle without maintenance guidance earns a polite pass. Our marketplace exists for operators who already tasted generic libraries that looked brilliant in week one and frayed by week six.

We also request references from learning departments, not only executives. Coordinators see friction that leaders miss—timezone pain, unclear rubrics, missing subtitles—and we weight those signals heavily.

The bar is high because buyers deserve honest previews. If a bundle cannot articulate how busy teams sustain practice, it is not listed here.