The point being that this is very different when you work for a company that is a third-party analytics company.
Because instead of a few data sources, you’re likely dealing with 50, 100, 1,000, etc. companies who all are sending data to you, and this is the first place where you can easily make mistakes. (View Highlight)
Anyone can scrape websites and rebuild your solution if they feel it is worthwhile. But very few companies can go through the effort of reaching out, making contacts and relationships, and developing trust with customers. Thus, a massive competitive advantage is created by directly accessing the actual first-party data sources. (View Highlight)
Accuracy - Whenever I have worked on a project using some form of proxy data set, it’s okay but never right. Now if you plan to take those insights and sell them back to that same client, you risk showing them data they flat-out know is wrong. And you don’t have the data to prove it, but they do. (View Highlight)
Once you have your data layer and ingestion set up, now you’ll need to create transforms to both standardize and create the product.
If you’re lucky, you were able to get your client to commit to a standard schema that helped reduce the layers of processing required to map column names. But even if you map column names, you likely can’t map column values. What one company might call “Category A” another company might call “Group A,” and you need to map it all into one. (View Highlight)
In fact, I have seen many companies use standard metrics like churn, per patient per month, monthly revenue and forecasts, and other pretty standard metrics to build their product (View Highlight)
If you just show these metrics without driving your customers to take action (View Highlight)
The most common way is to provide a dashboard from which users can easily go and get their insights. Perhaps you provide some drill-down ability, but the goal is to create a very succinct dashboard that anyone can drill into quickly (View Highlight)
Another common service is to provide insights back to your customers via an API. Perhaps you perform some machine learning, customer classification, fraud detection, etc. Whatever it might be, a great way to create a well-integrated system is via an API. That being said, I will add that it does look like having the ability to share data via Snowflake or other data platforms is becoming more common (View Highlight)
A great product to create when you first start your third-party analytics service is just a simple set of CSVs or reports. Perhaps it’s a list of fraudulent actors or super users. Yes, this isn’t the most advanced approach, but when building an MVP, why try to build out an entire API when you don’t even know if people want your product? Instead, find a group of businesses that you can build with (View Highlight)
