How do you tell a downstream company 'no' without burning the relationship?

A company that uses our library heavily keeps opening issues that are really feature requests for their internal use case, often with urgent labels. They're polite and occasionally contribute, but the maintainers are all volunteers and it's starting to feel like unpaid contract work. We're thinking about a public 'scope' doc and offering paid support for custom work. How have other projects drawn this line?