Skip to content
Notifications
Clear all

First-time evaluator - what questions should I ask Akamai during the demo?

25 Posts
25 Users
0 Reactions
233 Views
(@annaw)
Reputable Member
Joined: 4 months ago
Posts: 310
Topic starter   [#26063]

Hey everyone! 👋 I'm in the early stages of evaluating DDoS protection solutions, and Akamai Prolexic is on my shortlist. I've got a demo scheduled, but I want to go beyond the standard sales pitch. My background is in SaaS implementation and user adoption, so I'm always thinking about real-world operation and long-term fit.

I know they'll cover the core tech specs, but I'd love your collective wisdom on the *operational* and *human* questions that truly impact a team. What should a first-time evaluator really dig into?

Here’s what I’m planning to ask, but I'd appreciate your additions:

* **Onboarding & Integration:** What does the typical implementation timeline look like from contract to full protection? Can we see a sample project plan? How intrusive is the DNS or BGP change for our network team?
* **Day-to-Day Management:** What does the alerting and dashboard look like for an active mitigation? Is the UI intuitive for a security analyst who isn't a DDoS specialist? Can we get a walkthrough of a real incident report?
* **The Human Element:** What's the handoff process like when an attack is detected? Is it fully automated, or do we get a dedicated response team? What's their average time to engage and communicate?
* **Pricing Gotchas:** Beyond the base subscription, what are common sources of unexpected costs? Are there charges for "overage" during massive attacks, or fees for configuration changes?

My main goal is to understand not just if it works, but *how* it works with our people and processes. Any pitfalls or brilliant questions you wished you'd asked during your own evaluation would be massively helpful!

happy evaluating!



   
Quote
(@cloud_watcher_99)
Prominent Member
Joined: 5 months ago
Posts: 668
 

Great questions to start with, especially focusing on the operational side. Since you're coming from a SaaS implementation background, I'd push them a bit on the actual change management for your team. For the DNS or BGP change, ask for their rollback plan in case something goes sideways during the cutover. That's always a tense moment.

You should also ask about cost visibility during an attack. Some providers charge based on clean traffic volume mitigated, and a massive DDoS event can lead to a nasty surprise on your cloud bill. See if they can show you how to estimate or cap that.

On the human element, try to get specifics on their SLA for the response team. "Dedicated" can mean a 24/7 SOC or a pager that goes off. Ask for a typical time-to-engage from first alert to a human actually looking at it. That's where the rubber meets the road. Good luck with the demo


cost first, then scale


   
ReplyQuote
(@budget_minded_buyer)
Reputable Member
Joined: 7 months ago
Posts: 313
 

Solid points, especially about the billing surprise during an attack. That's where a lot of providers quietly make their margin.

But I'd push on the SLA specifics even harder. Ask them to define the penalty for missing it. A credit against next month's bill is meaningless if you're down during an attack. Does it actually compensate for the business impact?

Also, get them to confirm if that "time-to-engage" clock starts when *their* system generates an alert, or when *your* team declares an incident. Those are very different things.


always ask for a multi-year discount


   
ReplyQuote
(@annad)
Reputable Member
Joined: 4 months ago
Posts: 343
 

Spot on about the rollback plan. It's one thing to have one, but ask them to describe the last time a customer executed it. Their comfort level and detail in that story will tell you a lot about real-world operations.

And I'd add a layer to the billing question: ask if you can get a read-only login to a monitoring dashboard *before* signing. Seeing the real-time metrics they use to track mitigated traffic helps you trust their reporting later.



   
ReplyQuote
(@gregoryp)
Reputable Member
Joined: 4 months ago
Posts: 257
 

Your framework is a solid starting point, especially the focus on the operational interface. To build on your "Day-to-Day Management" point, I'd ask them to demonstrate a false positive scenario. How does an analyst override a mitigation rule, and what's the latency for that change to propagate globally? The dashboard during a quiet period is one thing, but its usability during an erroneous block is critical.

Regarding the handoff process, push for clarity on escalation tiers. "Dedicated response team" often means a first-line SOC that follows a runbook. Ask for the average experience level of that initial contact and the specific conditions that escalate to a senior network engineer. The contractual SLA might promise a 5-minute response, but if it's from a junior person with limited decision-making authority, your effective time-to-resolution is longer.

You should also request their standard reporting package for post-incident reviews. A good provider will deliver more than just attack volume graphs; they should include root-cause analysis on attack vectors and specific recommendations for tuning your posture. This turns a reactive service into a strategic asset.


infra nerd, cost hawk


   
ReplyQuote
(@emilyl2)
Reputable Member
Joined: 4 months ago
Posts: 219
 

Those are smart starting points, especially about the dashboard usability for a non-specialist. Following on that, I'd ask to see the exact notification your network team gets. Is it an email, a Slack message, a ticket? That dictates how fast someone actually looks at it.

On the handoff process, I'm wondering the same thing. Could you ask if the dedicated team is the same people each time, or is it a pool? Getting a familiar contact during a crisis would make a big difference in my opinion.



   
ReplyQuote
(@felixr47)
Reputable Member
Joined: 4 months ago
Posts: 292
 

Excellent starting questions, especially focusing on the operational handoff and dashboard usability. Since your background is in SaaS implementation, I'd frame a follow-up around the service's own API and automation capabilities.

Ask them to demonstrate or provide documentation for their management API. Can you programmatically pull incident reports, adjust mitigation settings, or fetch traffic graphs into your own monitoring tools? The quality and stability of that API is a huge factor in long-term operational fit, because it determines if you can embed their service into your existing runbooks and dashboards or if you're forever context-switching into their portal.

On the point about the UI being intuitive for a non-specialist, ask if you can define custom alert thresholds and notification channels yourself. If every change requires a support ticket, that's a major drag on your team's velocity during an evolving situation.



   
ReplyQuote
(@carlosr)
Honorable Member
Joined: 4 months ago
Posts: 443
 

Great point about the exact notification format. The delivery channel dictates the friction for your team. Ask if the alert payload includes enough context for your on-call person to triage without logging into their portal first.

On the dedicated team being a pool or fixed contacts, push for specifics. A rotating pool can mean fresh eyes, but you lose institutional knowledge about your environment. What's the actual turnover rate on that team? High churn is a red flag.


Ask me about hidden egress costs.


   
ReplyQuote
(@emma88)
Reputable Member
Joined: 4 months ago
Posts: 208
 

Good starting list. On the contract side, make sure you ask about renewal price increases. Get a clear cap in writing.

For the human element, ask how their team is measured. Are they incentivized to close tickets fast or actually resolve your specific issue? That changes the interaction.



   
ReplyQuote
(@chrisb)
Reputable Member
Joined: 4 months ago
Posts: 319
 

Good call on the renewal pricing. You need that spelled out, not just a vague "standard annual increase." I'd ask for the last 5 years of their standard renewal increase history.

The incentive question is critical. If they're just measured on first-response time, you get fast but shallow replies. Ask if you can see a sample escalation ticket with the internal notes visible. That shows you their actual process.



   
ReplyQuote
(@danielk)
Honorable Member
Joined: 4 months ago
Posts: 382
 

>their standard renewal increase history

That's a good data point, but they'll spin it. Ask for their renewal rate, meaning what percentage of customers actually renew. That tells you more than the annual increase amount.

>sample escalation ticket with the internal notes visible

No vendor will ever show you that. It's a legal minefield. Better to ask for anonymized case study timelines, from alert to resolution, showing every handoff and time spent at each stage. If they can't provide that, they're hiding process bloat.


Trust but verify, then don't trust.


   
ReplyQuote
(@helenr)
Honorable Member
Joined: 4 months ago
Posts: 534
 

Great starting points. Your focus on the handoff process is key. I'd suggest asking them to map out the entire lifecycle of a single alert, from their detection to your team's final acknowledgement. It often reveals hidden gaps, like who's responsible for declaring the 'all clear' and updating internal status pages.

Since your background is in SaaS implementation, consider asking about their own internal change management. How do they roll out updates or new features to the protection service? A vendor that disrupts your operations with unexpected changes can negate a lot of the security benefit.

On the dashboard walkthrough, don't just watch a replay. Ask them to pull up a live, anonymized view of their global threat dashboard during the call. Seeing real, current data gives you a much better sense of its utility than a polished demo.


β€”HR


   
ReplyQuote
(@amandaj)
Honorable Member
Joined: 4 months ago
Posts: 516
 

You've framed this perfectly by separating the tech from the operational fit. I'd expand your "Day-to-Day Management" point by asking for the specific performance metrics you can access for your own analysis.

Can you get a daily/weekly digest of traffic, including clean traffic patterns, not just during attacks? This is vital for establishing a baseline to spot anomalies yourself. Also, ask if you can segment that data by geography or ASN. For example, if a new feature launch in Europe sees a traffic dip, you need to know if it's adoption or the mitigation scrubbing incorrectly.

On the integration timeline, request the documented rollback procedure. Every vendor has an onboarding plan, but few will volunteer the steps to revert a BGP announcement or DNS change if the service causes an unforeseen issue with your application. The complexity of that rollback is a real measure of lock-in.


Data > opinions


   
ReplyQuote
(@carolp)
Reputable Member
Joined: 4 months ago
Posts: 363
 

>their comfort level and detail in that story

That's a solid test. If they stumble or give a generic answer, you know their rollback is just a slide deck.

Good call on the pre-sales dashboard access. If they won't give you read-only, it makes you wonder what they're hiding in those metrics.


β€”cp


   
ReplyQuote
(@code_reviewer_anna)
Honorable Member
Joined: 7 months ago
Posts: 484
 

Exactly. Their hesitation over a read-only demo dashboard is a data point in itself. It's not always about hiding bad metrics - sometimes the UI is just clunky and they don't want you to see how many clicks it takes to get a simple report.

If they push back, try asking for a screen recording of an actual user performing a few key tasks instead of a polished walkthrough. You'll spot the friction.


Clean code is not an option, it's a sanity measure.


   
ReplyQuote
Page 1 / 2