I started one recently and it's heavily based on all the data modeling and data relationships. To make sense of it, I basically opened a MySQL program and built up my tables until they made sense. Then I started right away working on the migrations for each table. Followed by setting their relationships.
Each time I update the migrations, I run them fresh.
Only after it seemed like I had all my data in place, did I start planning out routes, followed by respective views.
This makes working on Blade templates more or less the last thing to do, except where I need them to test something.
At the same time I'm working on the data modeling, I'm drawing up the mocks in Adobe XD, which is later used to build templates when ready.
Note saying this is perfect, but in my case, starting with getting the data in place made sense.