Thin and Rich
I was thinking about the saying "You can never be too thin or too rich" the other day and it reminded me of many of the marketing project management solutions I run across on a day-to-day basis. This saying doesn't apply to some of them, it seems, in that many of them are way "too thin" (not enough functionality) or "too rich" (bloated functionality).
Your feature set is dictated by your users, your target market, and the marketplace. It's a fine line, especially in the SaaS model where literally thousands of users use (essentially) the same software. Sure, you can have account/client level configurations, but that can become overly complex from a development and support standpoint.
So is a feature that only serves a small percentage of your users worth adding?
Things I'd consider:
How much business does that "small percentage" represent?
Will it help gain new business?
Will it positively impact retention?
Will it give you a competitive advantage?
Are you doing it right?
What's the development effort?
What other enhancement(s) will be delayed if you focus on this one?
I'd be interested in any thoughts - thanks!