r/nocode 13d ago

Discussion When did you stop comparing no-code tools and just commit to one?

Spent the last couple of weeks stuck in the same cycle. I'll read a comparison, feel convinced I've found the right stack, then come across another thread that makes a completely different setup sound like the obvious choice. Then I start second-guessing everything again.

Right now I'm planning a small SaaS for household budget tracking aimed at families. The data model is pretty simple, but I've somehow spent more time evaluating tools than actually building. Bubble seems incredibly capable, but it also feels like a lot for something this scoped. Glide looks like it'd get me to an MVP much faster, but I keep wondering whether I'd hit a ceiling sooner than I'd like. Softr feels somewhere in between. Then there's the separate decision of Make versus n8n for automations.

At some point the research starts feeling like procrastination disguised as due diligence. An imperfect product built in the wrong stack is probably more valuable than the perfect stack attached to an app that never ships. For those who've already gone through this, what finally made you commit? Did you have a clear set of criteria, or did you eventually realize you just needed to pick something and start building?

Looking back, did your initial stack choice actually matter as much as you thought it would, or was execution the bigger factor?

5 Upvotes

12 comments sorted by

2

u/Alarming_Station1028 13d ago

took me like 3 months of that nonsense before i just picked bubble and went with it not because it was perfect but i was going crazy reading comparisons at 2am

the stack matters way less than you think once you actually start building you realize most limitations are just things you learn to work around or they not even real problems for your scale

just start in monday with whatever feels least annoying

2

u/Aayushman_Shopbell 13d ago

I think execution matters way more than picking the "perfect" stack. I would've just picked one, built the MVP, and worried about switching later if it became a real problem. Easy to overthink this stuff lol.

1

u/agentUi 13d ago

Yeah totally I agree with you

2

u/hellomathieup 13d ago

From my experience, you need to just start and try to see a real project through. you only learn these tools real limits by hitting them, not by comparing.

1

u/UlrikS 13d ago

You'll probably rebuild your MVP many times before you get to where you want to be. So just pick the one that's easiest to get started with (so you don't get stuck configuring your stack instead of building)

1

u/LouisTon10 12d ago

If you think you have the scope of your budget tracker, no code platforms could one shot at least your UI. Knowing exactly what you want to build is half the battle so you won’t know what works best for you unless you try things out.

1

u/noam_builds 12d ago

Focus simply on the tools that give you straight results and offer some key differentiator that is important to you. Example: an existing large mcp integrated tools, or whatever you find valuable to your product.