Show HN: The pitch deck we're raising $800k with (localizejs.com)
I believe strongly that information should be shared as freely as possible. This is one of the big reasons I started Localize, to make it an order of magnitude easier for information or knowledge to transfer from person to person, despite a difference in language.
On openness, we've decided to share things companies normally don't share.
We're starting with the pitch deck we're using to pitch investors for a $800k seed round we just started raising, plus snippets of our traction and growth charts.
Why do this? The more we share, the more exposure other people have to our work. If our work is good, they can learn from us, if our work isn't good, we can learn from them! It's a win-win.
So check out our video pitch, our deck, and let me know what you think.
8 comments
[ 4.2 ms ] story [ 34.0 ms ] threadGiven this, we've decided to share things companies normally don't share.
We're starting with the pitch deck we're using while raising our $800k seed round, plus an overview of our traction and growth charts that have been confidential up until now.
Why do this? The more we share, the more exposure other people have to our work. If our work is good, they can learn from us, if our work isn't good, we can learn from them! It's a win-win.
So check out our video pitch, our deck, and let me know what you think.
There is another startup I saw on here that is semi-automating the translations. I think the cost saving that you could get by doing that well, by reducing the human input would be a place to get a distinct advantage.
The devil is in the detail, and if I were to choose a tool like this vs. a competitor, it would be in how easy it is to integrate with existing code, how good it is at finding all the possible captions in advance even if they are rarely shown, and if it can work on other platforms like native mobile, C#, ruby, java etc.
I appreciate the approach of managing translations outside your backend code, but I wonder about whether the translated content can be indexed by search engines.
So it was: User types stuff.. stuff goes in a database... a translator gets notified that there is new work.. and he would do it and insert back into the database.. which would eventually make it out to a site.
Google translate style is OK for google results, but not for a professional website.