Just saw the announcement about the new CEO coming from a big sales org. Gotta be honest, my first reaction was a sinking feeling. We've been wrestling with some clunky integrations and UI lag for months, and the roadmap keeps getting pushed.
My worry is that with a pure sales leader at the helm, the pressure will be all on new features and big logo acquisitions to hit numbers. What about the underlying platform stability? The tech debt feels like it's piling up, and I'm not sure a sales-focused CEO will prioritize the unglamorous, necessary work of modernizing the core.
I love what Anomali can do for threat intel, but our team spends too much time on workarounds. Will this shift mean even more duct tape behind the scenes to slap shiny new features on top?
Has anyone else had this concern? Or maybe there's a silver lining I'm not seeing—could a sales background actually mean better resource allocation if they listen to engineering?
~jennam
Less hype, more data.
Your concern is completely valid, and I've seen that dynamic play out before. It's a common worry when leadership shifts towards a purely go-to-market focus.
That said, a CEO from sales could be the catalyst for finally funding the foundational work, but only if they're convinced it directly impacts revenue retention and expansion. Your experience with workarounds and lag is the exact data point needed. When renewal conversations start highlighting these stability issues as a risk to continued business, that's when the budget for tech debt often gets unlocked.
The real test will be in the first few product roadmap meetings. Will they just ask "what's new?" or will they ask "what's blocking our biggest customers?" My advice is to be very direct in your feedback through account managers and surveys - frame the stability work not as an engineering wishlist, but as a requirement for you to expand your usage. That's a language a sales leader understands.
Stay curious, stay critical.
You're right about framing it as a revenue issue, but that's a dangerous game in my experience. It turns engineering roadmaps into a negotiation exercise where you need a customer complaint to justify every foundational fix.
I've watched teams waste cycles instrumenting dashboards to "prove" that a 300ms API latency spike is causing churn, when we already knew the query pattern was unsustainable. The sales mindset often demands this immediate, quantifiable link to a financial metric before greenlighting work.
The better outcome is when a sales leader understands that platform stability isn't a cost center-it's the product's gross margin. You can't scale deals on a shaky foundation any more than you can scale a factory on cracked floor slabs. The trick is getting them to see the infrastructure as the factory floor, not just the shiny widgets rolling off the line.
--perf