211–220 of 251 posts
I've found Asana to be a much, much nicer product to work with than Jira (at least as a developer, not sure about from the management side.) I genuinely wish them success and hope they're able to grow their marketshare.
Wow, this is a torrent of IPOs today. Investors / boards are wanting to get money out before things turn south I feel. Aside from that, I'm surprised how much it costs Asana on engineering R&D, for essentially a ticket management system. How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status? (ok yes I'm oversimplify…
> How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status? As with most of these companies, user-facing feature development is only a small part of the engineering workload. I would assume the majority of those engineers are working on less visible tasks: Devops, build systems, infrastructure monitoring, security, bac…
Earlier quoted context omitted.
I didn't believe that was an actual quote from the article until I read it. It sounds like a joke and I can't imagine anyone reasonable would say that. There are definitely good reasons to build your own framework but performant and stable applications isn't one of them. Usually it's a solution looking for a problem.
By this logic nobody would ever build a framework designed around performance and stability?
I have no idea what any of this means. It's grandiose and therefore, upsetting.
According to the filing Asana has 1.2m paying users. Each user is worth maybe $1000. That puts Asana at 1.2bn. The median forward revenue multiple for public enterprise SaaS companies is 10x, and with 2020 revenues of 150mn that results in a 3bn market cap. A third data point is they raised 75M 16 months ago at a $900m post money valuation. With growth at 100% annually that puts their current valuation at 2.5bn or so…
Their business plan is $30 a month, so I'm tempted to say each paying user is definitely not worth $1000. Given their revenues of 142M and 1.2M paid users, that's an average a tad below $120 a year per user, which would actually be less than their cheapest plan. That doesn't add up, it smells of free trials counted as paid users.
Earlier quoted context omitted.
Their business plan is $30 a month, so I'm tempted to say each paying user is definitely not worth $1000. Given their revenues of 142M and 1.2M paid users, that's an average a tad below $120 a year per user, which would actually be less than their cheapest plan. That doesn't add up, it smells of free trials counted as paid users.
Asana's pricing is per user per month - https://asana.com/pricing
Wow, this is a torrent of IPOs today. Investors / boards are wanting to get money out before things turn south I feel. Aside from that, I'm surprised how much it costs Asana on engineering R&D, for essentially a ticket management system. How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status? (ok yes I'm oversimplify…
Earlier quoted context omitted.
"Our founding engineers had learned from their experience working at Google and Facebook that to ensure a performant and stable application, they would need to build their own framework" Wow. Interesting.
I didn't believe that was an actual quote from the article until I read it. It sounds like a joke and I can't imagine anyone reasonable would say that. There are definitely good reasons to build your own framework but performant and stable applications isn't one of them. Usually it's a solution looking for a problem.
When they built Luna stuff like react didn't exist.
Investing in developer tooling including frameworks is a fine use of time and often pays off hugely. There wasn't a better alternative 11 years ago.
Wow, this is a torrent of IPOs today. Investors / boards are wanting to get money out before things turn south I feel. Aside from that, I'm surprised how much it costs Asana on engineering R&D, for essentially a ticket management system. How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status? (ok yes I'm oversimplify…
> How does a team grow to ~300+ developers ($89M R&D) to figure out how to attach PDFs and videos to tickets, and email people when there's a change in status? As with most of these companies, user-facing feature development is only a small part of the engineering workload. I would assume the majority of those engineers are working on less visible tasks: Devops, build systems, infrastructure monitoring, security, bac…
Kik messenger had 300M users and a tiny team. Same with WhatsApp - and it's reliable.
Asana scales more or less horizontally, meaning that they don't do anything much at the scale of all of Asanas customers. No individual customer repo should be massive (unlike say Facebook, where a user search searches the entire world.)