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

Clockwise acquired by Salesforce

getclockwise.com

Post reply on HN
Print view View original

41–50 of 82 posts

Re: Clockwise acquired by Salesforce

#41

Post by santoshalper »

apparent wrote: post #36
paxys wrote: post #24

Salesforce has lost half its market cap in the last ~year. Spending time and money to acquire a calendar scheduler shows just how badly they have lost the plot. I know this is an HN meme but can someone look at https://www.getclockwise.com/overview and explain why an internal team couldn't build this in a couple of weeks? And it's not like Salesforce is lacking engineers - they employ 83,000 (!!) people globally.

Typically when a company is acquired and the product is swiftly shut down, the value sought was the team. Although Salesforce has plenty of engineers, they may not have a team that does what the Clockwise team does.

Or they may just think the clockwise team is great and is willing to pay a small premium to get them.

Re: Clockwise acquired by Salesforce

#43

Post by neuronexmachina »

CoastalCoder wrote: post #17
pmdr wrote: post #2

> it has been our mission to help the world make time for what matters. We've built a business to be proud of There must be a lot of pride and meaning in being run over by Saleforce's money truck.

> There must be a lot of pride and meaning in being run over by Saleforce's money truck. Worst. Isekai. Idea. Ever.

I had stepped out of the high-rise office into the blinding San Francisco sun, a freshly minted millionaire wrestling with the crushing guilt of sunsetting my own creation. We built a business to be proud of, I tried to tell myself, clutching the signed term sheet. There must be a lot of pride and meaning in this.

That’s when I heard the roar of the engine.

Re: Clockwise acquired by Salesforce

#44

Post by bitwize »

paxys wrote: post #24

Salesforce has lost half its market cap in the last ~year. Spending time and money to acquire a calendar scheduler shows just how badly they have lost the plot. I know this is an HN meme but can someone look at https://www.getclockwise.com/overview and explain why an internal team couldn't build this in a couple of weeks? And it's not like Salesforce is lacking engineers - they employ 83,000 (!!) people globally.

Because the features need to be planned by product people, broken down and turned to stories in JIRA. The dev teams need to get together and play planning poker to determine who gets what story and approximately how long it should take. They need to coordinate with the DevOps and security teams in order to ensure it complies with company requirements/best practices concerning authz/authn, o11y, etc.

The good news is the company is headed into a bright and glorious future of productivity. The CEO has been completely one-shotted, and over last weekend he vibe-coded together a companywide TODO app. The submit button glitches out of existence and it authenticates any company email address without even a password, but its existence means the CEO is a dev now just like you. Token and SLOC count KPIs will be implemented next quarter.

Re: Clockwise acquired by Salesforce

#45

Post by apparent »

santoshalper wrote: post #41
apparent wrote: post #36

Earlier quoted context omitted.

Typically when a company is acquired and the product is swiftly shut down, the value sought was the team. Although Salesforce has plenty of engineers, they may not have a team that does what the Clockwise team does.

Or they may just think the clockwise team is great and is willing to pay a small premium to get them.

Yeah, the question is how much they paid and what other options the Clockwise team had. I wasn't going to speculate about that, since I've no idea.

Re: Clockwise acquired by Salesforce

#46

Post by tedivm »

Eufrat wrote: post #28
ares623 wrote: post #27

Earlier quoted context omitted.

Is the Clockwise founder mates with anyone in Salesforce?

Probably. The Clockwise folks were from a startup that was bought out by Salesforce before they left to do this. IMHO, the problem with Clockwise is that there was never a compelling product or a moat they could build with in the space. It was trivial for Google or anyone else to just implement similar enhancements.

I interviewed with Clockwise years ago and was offered a position, but ultimately I decided to pass for this exact reason. This system is great, and I actually used it and loved it, but it was a feature rather than a product.

Re: Clockwise acquired by Salesforce

#48

Post by jacquesm »

santoshalper wrote: post #41
apparent wrote: post #36

Earlier quoted context omitted.

Typically when a company is acquired and the product is swiftly shut down, the value sought was the team. Although Salesforce has plenty of engineers, they may not have a team that does what the Clockwise team does.

Or they may just think the clockwise team is great and is willing to pay a small premium to get them.

That means that for the acquirees that was the only option on the table so GP is likely right.

Re: Clockwise acquired by Salesforce

#49

Post by [deleted] »

santoshalper wrote: post #41
apparent wrote: post #36

Earlier quoted context omitted.

Typically when a company is acquired and the product is swiftly shut down, the value sought was the team. Although Salesforce has plenty of engineers, they may not have a team that does what the Clockwise team does.

Or they may just think the clockwise team is great and is willing to pay a small premium to get them.

[deleted]

Re: Clockwise acquired by Salesforce

#50

Post by kgwgk »

darth_avocado wrote: post #10
pmdr wrote: post #2

> it has been our mission to help the world make time for what matters. We've built a business to be proud of There must be a lot of pride and meaning in being run over by Saleforce's money truck.

Being proud and being acquired aren’t mutually exclusive things. You can be proud of projects that are not viable financially. They are proud of what they built and are also moving to a place where they can continue building more. Continuing to struggle for money isn’t a requirement for building cool stuff.

> You can be proud of projects that are not viable financially.

Projects may not be financially viable but it seems the minimum for a business.

Post reply on HN