It makes sense for back-end too though, especially in the context of a larger organization.

Teams A, B and C need features X, Y and Z from the back-end team. Back-end team says they will cost 3, 5 and 8 story points respectively. Back-end team's product owner talks to the teams to ask about priority. Z is planned for next sprint, X and Y for the one after. Teams A, B and C plan their work that depends on those features accordingly.

Everybody happy. We work with SAFe where that process of inter-team dependencies are formalized in quarterly "sprints" subdivided into 3-4 3-week team sprints. That's easy enough to explain at least, it's a shame the website makes it look so bad: https://scaledagileframework.com/