This hits home. We're building business intelligence APIs around entity resolution, and the buyer/user split gets messy when you have engineering, product, and data science teams all involved.
Engineers immediately understand why matching messy company data is a nightmare, but executives just see delayed projects without grasping the technical complexity.
We're seeing more success lately with "your team burned N months on data matching that should've taken weeks" rather than explaining what entity resolution even is. We're talking to one company right now that's spent 10 years building their own entity resolution system and it still doesn't work well.
But even then, it depends on the company and what they're trying to do.
To be frank, that's the challenge we're working on now. To start, my partner and I were mostly tapping into our network for initial customers. Both of us have been in the Bay Area for 10+ years.
Now, we're working on more of an inbound strategy and have a bunch of ideas. We're debating on cold emailing, but as an engineer myself, I hate getting cold emails.
Engineers immediately understand why matching messy company data is a nightmare, but executives just see delayed projects without grasping the technical complexity.
We're seeing more success lately with "your team burned N months on data matching that should've taken weeks" rather than explaining what entity resolution even is. We're talking to one company right now that's spent 10 years building their own entity resolution system and it still doesn't work well.
But even then, it depends on the company and what they're trying to do.