Brian Johnson

Hey guys,

I've spent the last year building MVPs using no-code/low-code tools ( @n8n @Retool @Softr etc.) to validate ideas quickly before committing to full development cycles. My take is that these tools have been game-changers for speed, but I've noticed a pattern that's rarely discussed :

The faster you can build, the harder it becomes to know when to stop iterating and start rebuilding.

On social media, we're constantly hearing about individuals who never knew how to code and were able to vibecode a product within a short period of time.

Whenever I come across these posts, I always wonder if their product is truly marketable and profitable. Or, they are just selling the dream.

Ever been so annoyed by a problem you thought someone needs to fix this ? That s where a ton of great products start. However how do you really know whether this frustration is worth building a product around, or if it's just a personal annoyance?

This was the first question @mwamedacen and I asked ourselves when we considered launching 1Stroke - an AI tool that generates and rephrases smart replies anywhere on the web with just a right-click.

Our pain point? We used to spend hours writing and rewriting professional emails and social media content, only for them to be read in mere seconds.