Who was the main engine behind it, what was driving it, what were they trying to accomplish, who profited from the gamble. Toughts???
3 replies (most recent on top)
The security team is causing as much grief with our own core teams as you mention in Wrike. They have no clue how to support the kinds of products we sell. I'm convinced that they don't even KNOW what kinds of products we sell.
Wrike must be laughing that they got Citrix to buy them for a crazy amount. Who makes a business decision like that? Because of that decision hundreds were laid off.
The CFO. He was unhappy that as a "SaaS" company our earnings reports showed very little income from SaaS.
The plan was to buy an up and coming SaaS company that was showing huge growth and success. We'd then study their business model to understand what they're doing right so we could apply it to Citrix and happily report their earnings as our SaaS earnings.
They were supposed to be left alone.
Unfortunately, as is often the case, that last message didn't go out and the id--ts in the security org got to run roughshod and insist on applying all of our controls on them and remove their access to everything and force them onto our systems even though they weren't ready.
This caused huge headaches on the Wrike side and people started leaving by the hundreds (they only had 1,000 to begin with). Decisions were waffled back and forth repeatedly which caused even more angst.
Now, Wrike performance is suffering because the same mo--ns that mess up Citrix are giving equal treatment to Wrike.
This is why they announced we're going to be rolling back many of the "integrations" (F-Ups) we applied to them and hopefully get them to recover to their previous solid performance.
Side note: I don't care how fast they're growing, this is not a billion dollar product or company and no one's ever heard of them before.