Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian Acquires Loom

atlassian.com

Post reply on HN
Print view View original

301–310 of 408 posts

Re: Atlassian Acquires Loom

#301

Post by jschumacher »

tootie wrote: post #165
Atotalnoob wrote: post #155

Earlier quoted context omitted.

They are worth $1 billion due to their customer base.

I think the concern is more that they have such a small moat. Their product seems too easy to copy. But given that they are first to market, did a very a good job with what they offer and have acquired a lot of customers, that is all worth a lot of money. Is "a lot" $1B? Hard to say.

Once you host your videos with Loom and link them everywhere, the moat ain’t that small anymore. Also, their AI features are excellent.

But certainly agree that more competition entered the space in the last couple of years.

Re: Atlassian Acquires Loom

#302

Post by throwanem »

tqi wrote: post #279
simlevesque wrote: post #269

Earlier quoted context omitted.

> but comes at the expense of requiring more effort from the people consuming the content. Before that you got an issue saying "There's a bug on the notification list" and you needed to figure out how to reproduce it. Now you get a video showing exactly how to reproduce it. It's a life changer and the opposite of what you describe.

Like I said, there are definitely cases where showing is easier than telling, and bug reports often fall into that category. But as an alternative to more durable documents (design explorations, PRDs, etc), I often find that docs are more thoughtfully organized.

I would be very surprised to see anyone try to put a Loom in place of a PRD or RFC!

Re: Atlassian Acquires Loom

#303

Post by theogravity »

mattpratt wrote: post #299
theogravity wrote: post #294

Earlier quoted context omitted.

In some cases, they probably have lost money if they early exercised at that valuation.

They wouldn't have exercised at that valuation. The options would be priced based on the 409a, which would be much much less than 1.5B.

Depends on when the 409a was performed and when the exercise happened. When the startup I work at got our Series A, a new 409a was done and increased the share price by roughly the same multiple of the new valuation, and now I have a wide spread for AMT should I exercise my options because of the new 409a.

So it's possible for employees to have joined after the new 409a when it was valued at 1.5bln and early exercised against that value.

Re: Atlassian Acquires Loom

#304

Post by kbos87 »

jschumacher wrote: post #301
tootie wrote: post #165

Earlier quoted context omitted.

I think the concern is more that they have such a small moat. Their product seems too easy to copy. But given that they are first to market, did a very a good job with what they offer and have acquired a lot of customers, that is all worth a lot of money. Is "a lot" $1B? Hard to say.

Once you host your videos with Loom and link them everywhere, the moat ain’t that small anymore. Also, their AI features are excellent. But certainly agree that more competition entered the space in the last couple of years.

The brand also becomes a reinforcing moat in an interesting way when you become a household name. When your employees think to themselves "I want to send a quick video update to team X" and they instantly default to downloading Loom, IT's decision for which vendor to buy a solution like this from is practically made for them.

Re: Atlassian Acquires Loom

#305

Post by torton »

TheRealDunkirk wrote: post #21
athorax wrote: post #4

Who is asking for this? As Atlassian consolidates Loom into its platform, engineers will soon be able to visually log issues in Jira, leaders will use videos to connect with employees at scale, sales teams will send tailored video updates to clients, and HR teams will onboard new employees with personalized welcome videos

Good grief. If the age of YouTube has taught us anything, it's that creating good video of something takes a lot more skill than writing something decent about something. Trying to find the relevant issue in a bunch of unrelated info, within a long writeup, which a user necessarily edits, at least a little, by the nature of writing something out? Pretty easy. Trying to find it in a rambling, 15-minute video? Welp! Go…

The standards are not nearly the same. A team-internal Loom is not intended to be a viral polished social media clip.

Here's a sample scenario from one of my previous jobs: a PR is not getting reviews. After a day I record a three-minute Loom where I walk through the problem and the solution, and post it on the team's channel. A few hours later the PR is approved, without any synchronous work and without me having to spend twenty minutes thinking out and typing out a blog sized post on Slack on the same topic. If anyone ever feels the need to dig out that commit again, the Loom is still accessible.

Loom found a way to solve real problems without more typing or more meetings, and that's why it's been successful. Slack, by the way, has a "record a clip now" feature that I liked even more than Loom for the purpose; but by that point we already standardized on Loom and Loom is better at organizing clips.

Re: Atlassian Acquires Loom

#306

Post by itslennysfault »

jahnu wrote: post #20
bayindirh wrote: post #9

Earlier quoted context omitted.

Well, being able to screen record a reproduction of a bug is practical, and it's easy to do it in macOS or Linux, but I'm not sure about this on Windows. Maybe a unified tool with a better integration will allow better bug reports, but pep talks by management at scale? No, thanks.

Is it easy to do on macOS if system sound is needed to demonstrate the bug?

Not sure with the OS tool, but QuickTime is on all Macs and it's screen recorder can record system audio and/or microphone audio easily.

Re: Atlassian Acquires Loom

#307

Post by j45 »

jedberg wrote: post #134
j45 wrote: post #84

Earlier quoted context omitted.

Agreed. The loom integration has been useful to attract some users who don’t use Jira otherwise. I just wish Jira-1369 would get solved after 20 years because users refuse to adopt Jira or confluence when they’re getting waterboarded with notifications instead of a timed digest that can be set.

Jira-1369 was closed four years ago.

As one of jira’s bigger brain farts, it seems it’s was recreated and continued in a new ticket.

Open: https://jira.atlassian.com/browse/JRACLOUD-1369

Closed: https://jira.atlassian.com/browse/JRA-1369

The original JRA-1369 was opened in 2003. Addressed a little in 2019, but not the digests to solve it all. Odd since plug-ins have to. closing this is one way to improve optics I guess.

Ps, I don’t hate Jira. Wasn’t a huge fan and it took a few years to see the light of what it does that so few platforms do when it comes to being able to absorb complexity as it evolves.

Managing evolving complexity is a real thing, and the pain can be reduced by having more in one tool vs not. It’s a tough space, and I think Aha.Io is one tool suited to win their prize and grow into Jira’s space.

Their worst sin remains how many people are subjected to an out of the box install compared to one that is setup to your processes. Tweaking it makes such a difference.

Re: Atlassian Acquires Loom

#308

Post by theogravity »

sida wrote: post #296
Aurornis wrote: post #255

Earlier quoted context omitted.

They raised $200M and sold for $1B. Options from the last raise would be under water, but they operated for years before that raise. There are likely a lot of employees doing reasonably well.

I don't think you can just say that bout the last raise. Depends on the exercise price. Exercise price is lower than the preferred price that the investor paid. Due to the fact that investors get preferred shares. 409a can often be 20% of the preferred valuation.

Preferred vs common only matters when the company is sold at loss? The preferred shareholders get priority in terms of being made whole before the common shareholders.

In this case, since series C was 1.5bln and sold for $975m, then the preferred shares were bought during C would be made whole first (assuming the prior rounds were made whole first and there's enough left over for series C preferred) before those who exercised right after the valuation for common shares.

Edit: I forgot that preferred shares also come with liquidation preferences too, meaning that in a loss situation, later employees are highly unlikely to get something

Re: Atlassian Acquires Loom

#309

Post by tqi »

throwanem wrote: post #302
tqi wrote: post #279

Earlier quoted context omitted.

Like I said, there are definitely cases where showing is easier than telling, and bug reports often fall into that category. But as an alternative to more durable documents (design explorations, PRDs, etc), I often find that docs are more thoughtfully organized.

I would be very surprised to see anyone try to put a Loom in place of a PRD or RFC!

Oh sorry, I don't mean replacing the documents entirely. what I've seen is loom videos replacing sections of those documents (where in the past you would have expected screenshots + text to explain decisions or a design). To me, there may/may not be more total information, but the information density is much lower. I think my hierarchy as a reader is: document with good screenshots and text > doc with good loom video > doc with bad loom video > doc with no screenshots / bad text.

Re: Atlassian Acquires Loom

#310

Post by simantel »

tqi wrote: post #261

If this[1] is accurate (a big if) 2023 rev is 35M, which would make this a ~30X multiple!? [1] https://getlatka.com/companies/loom

1. Those numbers on Latka, ZoomInfo, etc. are often educated guesses.

2. The graph on Latka shows that $35M figure as being from 2021.

3. The 2021 fundraising announcement[0] said they grew revenue 1100% YoY that year, so the 30x multiple might be warranted.

[0] https://a16z.com/announcement/investing-in-loom/

Post reply on HN