If you're bootstraped, does that mean you already have something? What is it and why do you want to replace it? Beware of large greenfield remake projects, these often fail spectacularly.
replies(1):
I'm planning to build a SaaS product loosely in the B2B logistics space - it needs to be relatively low cost to build/maintain, look slick and be extensible.
It would be customer facing, meaning each customer would need a login/account (or perhaps many, if a whole team is using our product).
I've looked at Retool and it looks quite epic but it looks like it's designed primarily for internal apps.
Has anybody used, or attempted to use Retool for a production, user-facing app?
Would really appreciate advice, war stories or recommendations.
I've done a large greenfield rebuild before, which was a success - but I will never do that again. It ate my life.
I do have a bootstrapped product already in the market, but this is a second, unrelated product for a different audience....a new project entirely.
First project is Node + React but considering Retool for a v1 for this next project.
We've got one product in the market, but launching that product and talking to customers has given us insight into a potentially larger, more lucrative problem to solve.
So we're currently allowing idea #1 to tick over, while validating idea #2.
We plan to only focus on one of the two ideas going forward, but are first trying to do enough discovery on idea #2, so that we can choose the best one to take forward.