3 things to know about building with no-code

Maker Insights:

"The Kollecto experience starts with the Typeform form, where customers select their favorite types of art and enter their contact details."

"Zapier then sends that data to a Google Sheets spreadsheet, where Google Scripts help categorize users and show which art types to recommend.""
""Art advisors on the Kollecto team then add art to a SurveyGizmo survey and their Campaign Monitor emails include a customized link to the survey...(for ea customer)"

"Art advisors on the Kollecto team then add art to a Survey Gizmo survey, and their Campaign Monitor emails include a customized link to the survey that sends each customer to the new art that'd fit their profile based on the Google Sheets data."

per https://zapier.com/blog/prototype-app-zapier

What I learned:

1. Another OG Titan in the no-code world is Tara Reed the Maker of this product. People often worry about the viability of no-code because you are building on top of tools that are companies that could one day vanish. This is a risk of no-code. However, its largely becoming a less of concern now that major players in the no-code space like Airtable and Bubble and Webflow all are dominant healthy and mostly venture funded businesses. This stack made by Tara years ago uses a host of different tools all of which are still viable today. This stack would still be able to be used. Which is a testament to no-code.

2. My biggest takeaway is that Tara maximizes automating parts of the experience so that she can give more value and effort towards doing things that only humans can do and applying all her value there. This is a huge advantage over competitors and the reason why I believe she was successful in launching because no-code is so new, it allows you to do things that the competition and mainstream are not even aware of.

3. Tara does a great thing in her early prototype. She builds in time to do the manual part of the experience. It's not automated and thats okay. Especially when starting I see a common mistake that Maker's try to automate everything in the beginning. This is a mistake and a valuable lesson we can learn from this project. Use automation when necessary but allow yourself to build in processes that may not scale in the beginning to add exceptional value, and quality. Your early adopters won't care. You don't have to build for mainstream, you need to build for early adopters. This is an example of how.