3 ms·
A lot of other comments are bashing you guys, and I'm not interested in doing that. Of course, I have some questions that I often ask myself when I'm brainstorm
by peteforde 15y ago
A lot of other comments are bashing you guys, and I'm not interested in doing that. Of course, I have some questions that I often ask myself when I'm brainstorming and perhaps they will help you as well.
1. Is this a product or a feature? Realistically, what's stopping Twilio from providing these features if you prove that there is a market? Or what if someone implements this functionality as an open source gem out of spite? (See: Growl's painful movement away from free)
2. What is your unfair business advantage? And why you instead of someone else? Do you have years of experience working with Twilio or SMS in general? Are you super wealthy or connected politically in an advantageous way? Are any of your employees or founders former Twilio folks?
3. Is there a market here big enough to justify the existence of your company? Even if your CAC is low and your LCV is high, are there more than 1000 people that need this, and are they willing to pay a premium for what you offer?
I'm genuinely curious what kind of customer development you've done to demonstrate that you're solving a hair on fire problem. I'm had no idea there were so many Twilio SMS apps under current or future development.
- ashrust 15y agoThanks for the questions, I'll do my best... 1. The API is certainly one of our suite of features, you can also use SendHub via the web or any sms enabled cell phone. We expect to see more competition in the space and will be doing our best to contribute to open source ourselves. 2. A lot of our users have tried other SMS products and found them to be a poor experience - based on the feedback we get. We try to spend our time focused on building the best possible product and let that, rather than our backgrounds, do the talking. 3. We believe so, and our initial sales are reflective of that.