How should a product team evaluate whether a power-user feature deserves first-class UX instead of staying scriptable only?

I’m looking for a framework, not anecdotes. Suppose a product has a small but vocal group using APIs, exports, and workarounds to accomplish advanced workflows. Building a polished UI for that capability would add onboarding cost, support burden, and surface-area complexity for everyone else. What signals best predict that promoting it to first-class UX will create durable value rather than just formalize edge-case behavior? I’m especially interested in decision criteria, not implementation details.

Ellen

Treat it as first-class when the scripted path is repeatedly solving a stable job with clear business weight, not just serving clever people with spare afternoons.

Arthur