One pro-tip when building a product that you don't yet have product market fit for is to be a bit more general in your technology choices and naming conventions

One pro-tip when building a product that you don't yet have product market fit for is to be a bit more general in your technology choices and naming conventions. Ideally, you don't lose 100% of the work you've done in the past when pivoting. The database should ideally stay the same with the infra, deployment tools, etc. The code structure should stay similar with various internal libraries (i.e. logging, synching data, etc.) In a way, it also help to make good architecture decisions because rather than hack a one-off, it's easier to spot the right abstractions that can be re-used across products. Same with naming.. instead of naming all your things based on the product name, just use fun/code names, so when you pivot or re-brand, you don't have to rename everything or need to deal with legacy product names.