You firstly establish a purpose of your solution. Thinking the job to be done, the users, the features..
Then you do a design. Likely you have a design team, that does research and creates wireframes or high fidelity mock ups.
Then you establish requirements for the various layers in your stack.
So what I described is a fairly typical process. It is front to back.
I can't imagine someone building a product, starting with a myopic focus on the database, followed by rest contracts, etc...