RFC: What competitive advantage do we want to emphasize for this project?

[zspencer]

As we resume investing in this repository, it'd be good to think through and discuss the options for what particular competitive advantage we want to push for. While our "Open-ish" licensing and community ownership model has cost-reduction advantages; it's unlikely to be a satisfactory one from an attracting revenue perspective.

There are ~4 levers I could see us pulling from a generative competitive advantage perspective:

1. Nuance: How well do we solve particularly poignant pain points? Do we have deep empathy with our core personas?
2. Breadth: Do we go general purpose (i.e. instead of paying for X, Y and Z, pay for Support! It's not great at everything but it's serviceable!) or special purpose ("We focus entirely on ").
3. Flexibility: How "Rigid" do we want the design to be? Do we have a strong enough understanding of the problem domain to make informed decisions about how to manage a customer-community? Or should we focus more on being flexible enough to play well across existing systems?
4. Accessibility/Usability: Do we want to
5. Cost: Do we want to focus on high-paying customers who may benefit from our ability to tailor features directly for them (which will require a bit more of an emphasis on Co2Co or Co2B or Co2E sales) or do we want to stay in line with our broader pricing strategy which is more about making the services we build and maintain affordable and accessible with a progressively steeper price for clients who are generating more revenue?

What do the folks in @zinc-collective/core think?