In the startup, we had a small team where everyone was aware of the agile processes, and the delivery timelines were based on the estimates.
In the larger org, agile processes and story points meant a change in the culture from the traditional waterfall-oriented process they followed. And larger team sizes meant it took a longer time to change the culture and thinking. Also, due to the nature of the business, the delivery timelines are stricter, and sometimes already decided before IT was involved. Projects also often involve multiple non-IT teams (sales, marketing, customer service, etc.), and it is easier to communicate in hour-based estimates to them. We still do agile development as much as possible, but settled on hour-based estimates.
1 point: can be done within a week
2 points: 1 week to 2 weeks
3 points: needs more research and breakdown, possibly an epic
1 and 2 tend to be picked up and worked on directly, for 3 someone picks it out and the goal is to create more tickets based on it and not do the solution directly.
On this [0] article they tried to find the correlation between story points they used 25 projects from 4 different organizations ande there isn't any.