4 ms·
you do need to match them need-for-need I disagree. In particular, you may not be addressing the same niche that the "competition" addresses. To use an examp
by patio11 17y ago
you do need to match them need-for-need
I disagree. In particular, you may not be addressing the same niche that the "competition" addresses.
To use an example I've been thinking a lot about today: it is stupid and suicidal for any startup to go head to head with Google on a core Google competency, right? Well, Wingify just released an A/B testing product which is about 5% as featureful as the Google Website Optimizer/Google Analytics tag team o' doom. It lacks on enterprise features, it doesn't have the Google ops team backing it, etc etc. It also won't be free due to a cross-subsidy from Google AdWords.
Instead of trying to reach feature or need parity with Google, they said "There is a portion of the market here which is untechnical and knows they want to do A/B testing but whom are undeserved by EVERY vendor. We're going to make A/B test easy enough for them to incorporate it into their businesses in a few minutes." With respect to those users, they're going to eat Google's lunch. Granted that might only be a couple hundred thousand customers but, well, how many customers do you really need, anyhow. ;)
- nroach 17y agoWell, my surreply would be that for those customers, there is only one one need, and Google's feature matrix attempts to address more needs than actually exist in that segment of the marketplace. But segmentation is a good point that I hadn't really addressed. I'd presumed competitors going after the same market. A more mature competitor may simply be seeking a bigger market (and thus requires more features). If you're satisfied with attacking just one segment, everything else is extraneous.