Cool. Love the product. Gives developers a lot of flexibility.

This is some quite clever marketing. I definitely learned a lesson or two. I built https://natterGPT.com (which is a similar AI phone bot product but not as flexible in terms of how I packaged it) more than a year ago but I've struggled with marketing (especially when I don't have any budget). I'll copy this playbook in the future for sure!

Haha so glad you liked it! Initially we were just gonna post a standard demo of a voicebot, but figured making it a challenge would be interesting.

You are right. We'll work on some demos. Thanks for the feedback.

This allows customized flows based on username/email. From what I've seen, there are mostly two use cases 1. different flows based on organization e.g. Microsoft Office 365 2. different flows based on guest vs user so the website can capture the emails if it's not a registered user e.g. tumblr

Makes sense thanks

I found this idea really interesting and I completely agree with you that stores want insights / actionable data instead of aggregated metrics.

Maybe start by focusing on one specific field (grocery store? fashion?), or become the technology provider to enterprise clients?

$2,400 for a 2b apartment in upper Manhattan? I want that apartment!

If flight capital from China really were the only/major use case, most of these people would probably convert at least 50 percent of their bitcoins into a different currency once they moved the capital overseas. However, nearly 99 percent of the transactions are paid by CNY. These look more like domestic transactions to me.

Need a lot more info. You need to find data that answers the following questions: 1. Any major changes/events within the past 6 months? (or, is your product still as good as it was 6 months ago?) 2. Any new competitors? Any existing competitor had a major update/upgrade on their product? 3. How is the industry your product serves doing? 4. Any (strategy or metrics) changes on marketing? 5. How are your customers doing?

Also, it helps a lot to schedule some calls with customers who left.

You are essentially building a marketplace so you'll need both suppliers and consumers. This is hard because one side relies heavily upon another. Typically, you need to boost one side first and then the other side might catch up. In other words, you need to build up either 1) the consumer side (say, if you can make this app so easily to use that people will love it despite a poor supply of UI components) or 2) the supplier side (for example, if you can somehow import 20k React components from npm or github to your marketplace)

Thanks, that is exactly what I'm thinking about. I made the first part, but not many developers like it so far. That's why I will start making the next part - importing components.

That's awesome! You might also want to rethink what your market is. Is your users going to be engineers who build web app for their company, engineers who build their side projects, some developer-designers or maybe some technical product managers/product engineers? You can still catch all of them eventually, but in the beginning focusing on one or two groups might help quickly get more users and also help on morale.

Yes, you are quite right. And I already decided the following. Acting as market we will be focusing on engineers who build web apps and freelancers. And as a company with own product we will provide development teams with something like component generator service (installed on internal server) for Structor - this is for enterprise customers.