Ask HN: Which features make great open source support?

Hi! I have a consulting business with a focus on open source and "big data" and our clients often hold support contracts from Cloudera, Confluent, Elastic, Datastax, etc.

We'd like to know if there's a market for something slightly different:

- "use-case" based support (e.g. moving data from Kafka to Elasticsearch and HDFS would require two or three subscriptions in the product-based world) for a defined set of (Open Source) tools and architectures that often go together

- Relatively loose SLAs (e.g. Next Business Day)

- Pricing would not be node/core/etc.-based (we're still not sure what it should look like to be fair, e.g. X tickets/month), reasonable low monthly or yearly which can be canceled anytime

- No "value-added" software

- Relatively little guarantees (this being Open Source we cannot guarantee that any changes required will be accepted by the projects, and we wouldn't want to fork a product but work within the existing ecosystem)

Is this something that you or your company would be interested in? If not: What would we need to offer for this to become interesting (if ever) or in the spirit of the title: Which features make great open source support?

There's lots left to be defined (e.g. when would we consider a ticket 'closed', what exactly is a ticket etc.). We're still collecting ideas and are trying to evaluate whether this makes sense at all. Happy to post a more elaborate description & questions but we wanted to keep it short.

Thanks HN!