What advantage do you have using this stack? Isaac provides helpful advice: "Iteration/Speed: NoCode is lightning fast. If I built RingDaddy with code, it would have taken several weeks. Instead, I built it over a single weekend. This gave me time to get to market quicker and focus almost entirely on the business/marketing logic."
I spent 1,000+ hours talking with 150+ No-code Founders, who have generated millions of dollars with their businesses without actually writing code.
How are they doing it?
I spent years researching and building on what they do. I wrote The Lean Side Project so you can build and launch your product.
Ring Daddy - marketing superpowers for live streamers
What advantage do you have using this stack? Isaac provides helpful advice: "Iteration/Speed: NoCode is lightning fast. If I built RingDaddy with code, it would have taken several weeks. Instead, I built it over a single weekend. This gave me time to get to market quicker and focus almost entirely on the business/marketing logic."
1. No-code tool feature: Zapier - I've used the part of this stack in a previous project: Zapier and Twilio. Zapier is key to simplifying sending text messages with Twilio. Twilio is a bit intimidating if you are not a developer and you'd like to try and send text messages. Zapier is a gamechanger to be able to send text messages because you can build the entire workflow in Zapier.
There is another stack in review in this database for a text message sending application made by Max Katz. He used a little bit different backend that I would recommend checking out because it uses Parabola. Parabola has a lot more flexibility in the things that you can do to add, filter and customize the text or information that you'd be sending out as part of your product.
2. Product Strategy: Demo - What Isaac does a great job of is lowering the risk to trying his product out by providing a live demo: https://www.ringdaddy.net/subscribe/isaac. As a user landing on the sell page, I'd recommend that this was displayed more prominently or even a short video displaying the capabilities to really send the preview over the top and reduce the barrier to customer purchase. You can check out a short demo about the product here: https://youtu.be/90lqKbMLh7g.
My takeaway is everything needs to be more bitesized. For example, in a later product version Isaac took out the video and created short gif of what the product can actually do. I thought this was well done because it did not feel overwhelming and showing is always > telling. I think that when you first launch the v1 of the page, don't worry about getting things like this finely tuned. Your goal will be to validate it in an ugly form. Because your goal is to get a tight feedback look before you finish developing the product. And in order to do that you need to ship with your product not yet complete. But you can ship with parts of your product complete. I write more exactly about how to execute on this in The Lean Side Project framework. But the idea is breaking your product down into smaller bite size segments so that you can focus on what at time. Which shortens your feedback loops and allows you to iterate faster.
3. No-code tool feature - Memberstack - Isaac uses Webflow as a the framework for a web page and uses Memberstack as an ability to login and give specified access to certain authorized pages for paid users only.
This works well in Webflow because the web pages are static and not dynamically updating or the user is not having to update their information and have it save dynamically in a page. If you are needing more dynamic ability for users to save information to their profile I would recommend Bubble.
Once a user logs in that user has access to their own instance of the product to be able to send text messages to their users by providing the user their own link to text message.
Once a week, valuable and actionable insights, no bs -- promised.
