News for hackers. Stuff that matters.
Re:Slack S-1 by cupofjoakim on Friday April 26, 2019 @09:56AM (#19757490)
Well, these guys do have a good way to make money. Enterprise contracts are worth their weight in gold. As you could see from the quote, their revenue has increased more than their losses - which mean that they are on their way to become profitable. Arguably they could be now, if they didn't invest in growth as much.
Re:Slack S-1 by Radim on Friday April 26, 2019 @10:21AM (#19757787)
> their revenue has increased more than their losses

But "net loss" already takes revenue into account! "Loss" is not the same thing as "expenses".

The revenue increased substantially, but so did expenses, resulting in a slight decrease in loss over the past 3 years.

At the current rate, the company would reach break-even profitability around the year 2070.

Re:Slack S-1 by viscanti on Friday April 26, 2019 @12:00PM (#19758914)
They're investing in growth. It's unclear if that investment is good or bad, but looking at quarterly accounting numbers won't tell us. All we can see here is that they're investing more than they're making.

If you created a business that simply bought $1M worth of Stocks (e.x. ETFs) and bonds, the first quarter when you made the initial investment you'd show a "loss" of $1m. You might sell those 10 years later for $2m (or maybe the value goes to $0). You wouldn't know if it was a good or bad investment until much later. Seeing a $1M quarterly loss from that first quarter of investing wouldn't give you any insight at all.

To make matters worse here, the way that quarterly accounting works generally hides what are investments and what are actual losses. Some pre-profitable companies do better than others here but it's fairly difficult to understand what parts of spending are investments and what parts are just burning money when looking at quarterly accounting statements.

Re:Slack S-1 by rgbrenner on Friday April 26, 2019 @04:23PM (#19761415)
If you created a business that simply bought $1M worth of Stocks (e.x. ETFs) and bonds, the first quarter when you made the initial investment you'd show a "loss" of $1m.

No, that's not how accounting works. If you buy $1M in stocks, then you move the amount from one asset account (cash) to another asset account. You have $1M in assets both before and after, with no losses.

Re:Slack S-1 by canes123456 on Friday April 26, 2019 @11:38AM (#19758627)
That is not how SAAS economics works. You spend a lot money upfront and revenue is earned over years. They can stop investing in sales/marketing tomorrow and be profitable.
Re:Slack S-1 by dahdum on Friday April 26, 2019 @02:33PM (#19760546)
They quadrupled their revenue while keeping their losses flat in just 3 years, for a sticky high margin enterprise product.

With just modest revenue growth they'll be able to optimize towards profit whenever they choose.

Re:Slack S-1 by FPGAhacker on Friday April 26, 2019 @04:47PM (#19761600)
Since we are talking about net losses being flat, it means their expenses are going up as fast as their revenue.
Re:Slack S-1 by kgwgk on Friday April 26, 2019 @05:28PM (#19761911)
Expenses are growing "as fast as revenue" in millions, but "slower than revenue" in growth rate (percentage).
Re:Slack S-1 by tw04 on Friday April 26, 2019 @10:32AM (#19757903)
I'd be curious if it's remotely sustainable. We started on Slack ~3 years ago. We're now moving (albeit slowly) to Teams. 18 months from now Slack will be gone entirely. I can't believe we're the only ones. And unlike Dropbox vs. Ondrive, Slack isn't markedly better in any area than Teams from my testing.
Re:Slack S-1 by zedpm on Friday April 26, 2019 @10:49AM (#19758099)
Oh no, turn back while you still can. My team is in full revolt due to a company-wide migration from Slack to Teams. Teams is worse in almost every way. We're seeing lots of missing functionality, bizarre UI bugs, random crashes, extremely slow sync, you name it. Teams is in no way a viable replacement for Slack unless your use case is one or two plaintext messages per day.
Re:Slack S-1 by cdolan on Friday April 26, 2019 @11:03AM (#19758238)
I don’t know your use case but my team of 20 moved from Slack to Teams and has been very very happy with it.

Video chats and screen sharing are better (Screenhero is all that was around on Slack and it stunk). Video recordings save right to OneDrive for important meetings...

Oh and if you use Office 365 it’s a no brainer, everything is integrated!

Re:Slack S-1 by duggan on Friday April 26, 2019 @11:39AM (#19758646)
Teams is truly mediocre, other than when it rises to irritating. I have no idea how anyone using it could prefer it to Slack.

It is imposed on people whose organizations have Office 365 subscriptions, it is not chosen.

Re:Slack S-1 by maxxxxx on Friday April 26, 2019 @11:04AM (#19758239)
I would agree. Teams is pretty half baked. It sort of works but the main reason for using it as that it’s cheap if you have office 365 already.
Re:Slack S-1 by KeenFox on Friday April 26, 2019 @11:04AM (#19758241)
It's a gamble: stay with Slack and potentially be forced into an "Our Incredible Journey" migration in the future, or migrate now and shamble along until 40+ year old and profitable enterprise juggernaut Microsoft figures out how to make their product work right. Neither option is great.
Re:Slack S-1 by markmark on Friday April 26, 2019 @09:38PM (#19763222)
Microsoft will never make Teams great, it will be just good enough that corporate bean counters won't let you pay for a competitor when you already get Teams "free".
Re:Slack S-1 by Gene_Parmesan on Friday April 26, 2019 @12:57PM (#19759558)
As a drop-in replacement for Slack (or our dearly departed friend Hipchat), Teams is a poor choice. It makes more sense when used organization-wide -- for meetings, sharing/accessing documents, and so on. The chat portion works usually but it's probably its weakest point.

The bugs do need mentioned though. It constantly crashes for me, constantly loses sync, will just straight-up freeze for no discernible reason, will decide it doesn't really feel like actually sending my messages, and so on. It does not at all feel like a mature product.

Our team dropped HipChat and has moved to Teams along with the rest of the org. Our dev team (of 7) had used HipChat as a simple persistent chat app, sandboxed away from the rest of the company. Now we are on Teams with not only Ops guys, but also HR, marketing, and so on. It's fine at being sort of an organizational tool, but we dearly miss having our own private chat-only app that we can make use of as we want/need. Partly this is contextual to our organization, but the way we use Teams now feels far more formalized, and not in a good way.

Re:Slack S-1 by sct202 on Friday April 26, 2019 @12:06PM (#19758996)
Yeah, Teams is fine when it works, but it definitely has a lot of syncing issues that seem to last for hours and then magically resolve.
Re:Slack S-1 by freewilly1040 on Friday April 26, 2019 @10:39AM (#19757986)
The cost of migrating away from something like slack for an enterprise org is enormous compared to what it costs.

Teams might have parity in a vacuum, but everyone already knows what slack is and how to use it, including people you might hire in the future.

Re:Slack S-1 by jvagner on Friday April 26, 2019 @10:52AM (#19758130)
Two years ago a company we were at had Slack and it was used vigorously. They hit a user limit and couldn't get the CEO to pony up whatever it cost to extend Slack. (This company was the kind of company that had unlimited budgets for conferences and sales calls, but could hardly ever get a CC# for a dev team need...)

They switched to MS Teams, but at least two years ago, it felt unusable. Or, the team's Slackness couldn't translate. No one used it.

Neither Slack nor MS made money in this exchange.

Maybe Teams has gotten better and more usable, but I wonder if Teams is taking off in business environments, whereas Slack definitely is more common in tech environments?

Re:Slack S-1 by freewilly1040 on Friday April 26, 2019 @11:13AM (#19758345)
Your example demonstrates my point. Your CEO made a terrible decision in making you switch. Your co spent much more paying people to migrate to something worse than it would have spent just ponying up for the license.
Re:Slack S-1 by jvagner on Friday April 26, 2019 @11:33AM (#19758560)
Agreed. But if Teams comes with Office365, Slack may have trouble getting CEOs to pay more per-user monthly fees.

And I pay for both Office365 and G Suite at my business, and Google just invited me to Currents. I know better than to dump something like Slack for any new (like, first 3 years) Google product, but... Slack's getting some real competition.

Re:Slack S-1 by ilikehurdles on Friday April 26, 2019 @12:27PM (#19759206)
This is the first I heard of Currents, but Google naming their Yammer-clone replacement for G+ after an already-failed Google product is really setting themselves up for success.
Re:Slack S-1 by freewilly1040 on Friday April 26, 2019 @08:55PM (#19763044)
That’s fair and I agree that’s their biggest competitive threat. But investment wise that downside is mitigated by the possibility of being acquired
Re:Slack S-1 by cco on Friday April 26, 2019 @11:40AM (#19758657)
Anecdotally did your team's productivity or quality of work suffer to a large extent after moving to Teams?
Re:Slack S-1 by maxxxxx on Friday April 26, 2019 @01:17PM (#19759728)
I would guess that the choice of chat tool has almost no impact on productivity or quality.
Re:Slack S-1 by cco on Sunday April 28, 2019 @07:15PM (#19774434)
That is mostly my thought as well, meaning that the parent's boss made the right move in saving money with no loss in productivity.
Re:Slack S-1 by tw04 on Friday April 26, 2019 @07:29PM (#19762659)
To be blunt: if someone who knows slack can't figure out teams, we won't be hiring them. It's a chat app, not a new programming language.
Re:Slack S-1 by nik736 on Friday April 26, 2019 @10:53AM (#19758140)
Teams is super buggy and I hated using it. We are now back at Slack (and actually happy paying customers).
Re:Slack S-1 by calabin on Friday April 26, 2019 @11:10AM (#19758310)
Same - we used Teams for 2-3 weeks before switching back. The syncing was horrendous, the mobile apps were terrible, and a litany of other things I've forgotten.
Re:Slack S-1 by stone-monkey on Friday April 26, 2019 @10:40AM (#19758001)
> Slack isn't markedly better in any area than Teams from my testing.

Is it markedly worse in any area? Seems like for any business that's already entrenched in slack there isn't much incentive to move off. I'm assuming in your case there must have been some large benefits in order to spend a multi-month effort forcing a migration.

Re:Slack S-1 by opencl on Friday April 26, 2019 @10:52AM (#19758131)
An Office 365 subscription includes Teams, email hosting, the Office suite, and 1TB storage per user for less than the price of Slack alone. So I would call that markedly worse pricing.

Sure for companies already using Slack there's probably not a whole lot of reason to move off. But Slack seems to be relying on continued huge growth numbers to become profitable.

Re:Slack S-1 by samnwa on Friday April 26, 2019 @10:46AM (#19758065)
That's what people said when they were on Hipchat. And every other chat before Slack. Chat is commoditized software at this point.
Re:Slack S-1 by ec109685 on Friday April 26, 2019 @10:54AM (#19758153)
HipChat was utter crap. At some point things are good enough.
Re:Slack S-1 by wbl on Friday April 26, 2019 @12:03PM (#19758952)
IRC was fine. Really. And the clients didn't chew ram.
Re:Slack S-1 by javagram on Friday April 26, 2019 @01:23PM (#19759798)
IRC’s main issue is not working well with phones or multiple devices I think? (Yes, IRCCloud is a thing but if you’re going with a SaaS already, you may very well just go with a proprietary solution).
Re:Slack S-1 by wuliwong on Friday April 26, 2019 @11:12AM (#19758339)
>Chat is commoditized software at this point.

I don't think I follow your logic. Why would this lead to Hipchat being completely shutdown?

Re:Slack S-1 by outside1234 on Friday April 26, 2019 @10:31AM (#19757886)
I guarantee you that Microsoft has not lost money on Teams at the same growth rate. Why does Slack get a pass for that?
Re:Slack S-1 by maxxxxx on Friday April 26, 2019 @10:32AM (#19757905)
How about Atlassian? Did they lose money for years?
Re:Slack S-1 by mises on Friday April 26, 2019 @10:42AM (#19758026)
Atlassian actually had decent numbers and was profitable when they went public. Source: https://techcrunch.com/2015/12/10/hipchat-maker-atlassian-be...
Re:Slack S-1 by AjithAntony on Friday April 26, 2019 @11:28AM (#19758515)
But they are abandoning hipchat
Re:Slack S-1 by wuliwong on Friday April 26, 2019 @04:07PM (#19761315)
How are you able to guarantee that?
Re:Slack S-1 by anonu on Friday April 26, 2019 @10:52AM (#19758125)
That $50mm a year AWS bill seems pretty high - I think some optimizations there could easily cut this big expense...
Re:Slack S-1 by ec109685 on Friday April 26, 2019 @10:53AM (#19758141)
But why? Their revenue is growing faster and they aren’t running out of money.
Re:Slack S-1 by smolder on Friday April 26, 2019 @11:53AM (#19758817)
At that scale, I suspect there are some ~$10k engineering-time efforts that could save them $1m a year in costs, if they already have the people on staff with the expertise. In my limited experience, a lot of opportunities like that get missed because:

- an optimization is considered lower priority than feature work and bugs, so never gets staffed

- it's considered risky even when it's not

- it's difficult to quantify the value until the works done

Aside from that, just because it may be more cost effective to use 1000 servers and 1 developer versus 200 servers and 3 developers, doesn't mean it's a sound choice. One invests in people using their brains, the other mostly disappears into raw material supply chains, building servers and infrastructure and burning fuel to run them.

Re:Slack S-1 by marcosdumay on Friday April 26, 2019 @12:32PM (#19759275)
Head count is not infinite. I don't agree with the GP's claim that they aren't running out of money (if they don't show a profit, they are running out of money, by definition), but developer time is a limited resource that must be carefully allocated.

They have a very hard problem on their hands of estimating the revenue growth new features will bring, and compare them to costs savings from better code. I don't think anybody here has enough data to decide on this - it's not impossible that nobody there has enough data either.

Re:Slack S-1 by smolder on Friday April 26, 2019 @05:05PM (#19761726)
I just wanted to say I fully agree with what you said; it's a very hard problem.
Re:Slack S-1 by tomstoms on Friday April 26, 2019 @12:54PM (#19759503)
Also, buying cpu power is a lot easier than recruiting devs.
Re:Slack S-1 by gist on Friday April 26, 2019 @11:07AM (#19758274)
> which mean that they are on their way to become profitable.

Never will be sure of the exact numbers but a great deal of the sales is no doubt driven by startups and cash they are spending (do they still call this runway?). When that stops what happens?

Re:Slack S-1 by ttul on Friday April 26, 2019 @05:16PM (#19761807)
I’d love to see - and I didn’t check the S-1 so lazyweb me - their lifetime value estimation. I bet that $400M is worth > $5B billions over the lifetime of all customer cohorts.
Re:Slack S-1 by derwiki on Friday April 26, 2019 @10:13AM (#19757689)
> Arguably they could be now, if they didn't invest in growth as much.

Bingo bango

https://qz.com/1196256/it-took-amazon-amzn-14-years-to-make-...

> Keep in mind that Amazon consistently lost money for its first several years as a public company. It first reported a quarterly profit in the fourth quarter of 2001 [...]

Re:Slack S-1 by mises on Friday April 26, 2019 @10:44AM (#19758043)
Amazon massive economies of scale due to operating a highly efficient worldwide supply chain. I don't see Slack's average variable cost per unit going down in that same way. Amazon also made a lot of money on things like AWS by reinvesting, which is why they weren't profitable. They were burning that money by reinvesting it, not for operating expenses.