The biggest pinpoint is having 10 different service that gives you quite the same answer but:
1) they cover different needs and you need a patchwork to customize to what you need (and when you are small it is not even sure you know what you need so the patchwork is biggest than needed).
2) they measure things in slightly different way making comparison difficult.
3) they have vastly different interfaces, thus requiring a lot of time to learn them (I like to learn new things, but my time is valuable and better spent on product features)
4) they create a mess in your code. This is the problem segment try to solve. It is relevant but not top priority. Actually, I'm not totally sure of the effect of inserting a level of abstraction doesn't actually make more complex to solve point 1 and 2 (it is not a critic, just a real problem I faced when I tried to abstract the analytics call in the app with few functions).
So you put Google Analytics on your website, then you need the tracking code from Facebook for the ads. And you add Flurry because it provides different analytics (e.g: Funnels and Cohort Analysis). We also logged on the DB some actions difficult to capture on analytics. Then you need mobile ads, so you add in your app the framework to track the install. And, I forgot, you have another platform to track your mailing lists.
The final result: for every business question you have data in at least 3 different platform that gives you three different answers. Even worst, when you are still struggling with the product your "hard tech" co-founder could not understand why you push to re-implement the analytics framework (not necessarily building it in house) while your business co-founder decide to don't ask questions and doesn't understand why you want better data. If it looks like a recipe for disaster is because it is.
We really need better analytics platform, easy to use like Google Analytics and MixPanel for the beginning but with the ability to build custom analysis for the growing biz.