That&#x27;s not quite right what I have in mind. It solve part of the issue, the maintainability of 10+ integrations, but it is not really the biggest pain point.<p>The biggest pinpoint is having 10 different service that gives you quite the same answer but:<p>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).<p>2) they measure things in slightly different way making comparison difficult.<p>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)<p>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&#x27;m not totally sure of the effect of inserting a level of abstraction doesn&#x27;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).