Hey everyone, new here and hoping to get some perspective. 👋
We just wrapped up our Anomali deployment, and honestly, I'm feeling a bit frustrated. The sales process was great, and the rep was super confident about a "smooth, quick deployment" timeline. But in reality, it took about three times longer than promised.
We had delays with resource allocation, unexpected configuration hurdles, and the team scheduling became a nightmare. It impacted our project budget significantly.
Did anyone else experience this gap between the sales promise and the actual rollout? I'm trying to figure out if this is common or if we just had an unusual experience. Would really appreciate any shared stories or advice.
No, you're not the only one. Their sales timeline is based on a perfect scenario with zero internal dependencies. They never factor in real-world resource contention.
Common culprit: they assume you have dedicated engineers on standby for their config. Reality is those people are handling incidents, backlog work, and other deployments.
Advice for next time: triple their estimate before you sign, get the detailed deployment plan in writing, and push for penalties if they miss. It's the only way to get them to be realistic.
If it's not a retention curve, I don't care.
That's a fair point about internal dependencies. However, in my experience with their APM, the vendor's timeline is often based on deploying their agent into a prepared environment. The delay usually comes from the prep work, not the actual installation.
The sales promise assumes your app is already instrumented for tracing and your team is ready to define service entry points. If you're starting from zero observability, that foundational work is a separate project that any vendor would struggle to estimate for you.
null