Every application has to decide what should happen when somebody calls a particular address. That mapping is called routing. In Laravel it sits in files of its own and reads like a table of contents for the application: this address shows a list of invoices, that one accepts a form, a third delivers data to an app.
For a conversation about a project it is the most useful entry point there is. Reading the route file shows you in a few minutes what an application can do, without understanding a line of logic.
Why this is a business decision
Addresses are visible from outside and stay for a long time. They turn up in bookmarks, in emails, in search results, in other systems pointing at your application. A structure that mirrors the business lasts for years. One that mirrors the database tables becomes embarrassing as soon as the tables change.
So the address structure belongs at the start of a project and not at the end. For interfaces serving other systems that goes double, because other people’s programs depend on them. How we build that is under API and backend development.