4 ms·
Well I wasn't really thinking about "integrated" solutions like ERP systems (ala SAP) but something simpler but not that much. I guess what you are saying the
by rudasn 16y ago
Well I wasn't really thinking about "integrated" solutions like ERP systems (ala SAP) but something simpler but not that much.
I guess what you are saying the "sweet spot" for a "simple" app is to do exactly one set of things that each one of them cannot/should not be done separately (eg. milestones and project management) and be separated from other stuff (like contact management). In this way, a business that cannot afford (or doesn't want) one of these should not forfeit the other.
But is it best (for both the vendor and the client) to have these as two different applications or have them as plugins or upgrades? The end result is the same ("you pay for what you need for as long as you need it") but it's how you get there that bothers me.
To be more specific, is it best to say "pay me $x more per month to have contact management" or "if you want contact management have a look at this other app I make".