Aegis / Ironworks Corp - Vendor Comparison Discussion
Customer weighs switching after outage; Aegis proposes RCA, SLA, Comply v2 demo.
Catherine Page and Russell Tang from Ironworks Corp expressed serious doubts about Aegis following the March outage, during which threat monitoring was down for roughly six hours with no proactive notification. Russell detailed the impact on their manufacturing/OT environment and the lack of communication, while Catherine framed the outage as a trust issue given upcoming ISO 27001 and SOC 2 requirements. Maria Santos acknowledged both the technical and communication failures, highlighted the new Comply v2 release, and proposed an OT security session and a Comply v2 demo. Catherine and Russell accepted, but made clear that rebuilding trust requires an RCA document, an SLA commitment for monitoring downtime, and demonstrated ISO 27001 reporting. Maria committed to deliver these and to send a summary email.
How the call went
External sentiment was predominantly negative due to the March outage and compliance reporting gaps, with an early churn threat, but closed on a cautiously cooperative note with agreed next steps.
Opening
-1Close
08 scored turns of 41. Hover a point for the model's reason, or read the transcript.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 12
- Questions they asked
- 9
- Turns
- 41
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Catherine Page?Matched on an initial rather than a full name, so attribution is weaker.
- Russell Tang?Matched on an initial rather than a full name, so attribution is weaker.
What happened12
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised4?A problem was brought up on the call.
Russell describes the March outage: six hours of zero threat monitoring, discovered by his team rather than by Aegis.
Catherine states the outage is a trust issue, given ISO 27001 and SOC 2 requirements in manufacturing.
Catherine reports that reporting functionality felt limited for compliance needs.
Catherine discloses active competitor evaluation with Fortiguard Pro, including two demos and a pending proposal.
Commitment4?Someone committed to doing something.
Maria proposes a technical session with an OT security specialist and a Comply v2 demo to address concerns.
Catherine specifies that rebuilding trust requires RCA documentation, an SLA for monitoring downtime, and Comply v2 reporting in action.
Maria commits to delivering the RCA this week, starting an SLA conversation, and scheduling the Comply v2 demo.
Catherine and Russell agree to the Comply v2 demo next Wednesday.
Decision1?A decision was reached.
Maria announces Aegis Comply v2 went GA on April 7th, adding on-demand compliance reporting for frameworks including ISO 27001.
Recap1?A summary of what was agreed.
Catherine reaffirms they are not looking to leave for its own sake but need Aegis to demonstrate stability.
Objection1?The customer pushed back on price, terms, or approach.
Russell notes Fortiguard's UI is cleaner but raises questions about how they handle OT environments like Siemens PLCs.
Escalation1?The matter was raised to a higher tier during the call.
Catherine reveals internal conversations about whether Aegis is still the right fit, putting the account at risk.
What was promised5
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Deliver RCA document for the March outage to Ironworks Corp | Maria SantosAegisCloud | 17 Apr 2026said “this week” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Schedule Comply v2 demo for next Wednesday | Maria SantosAegisCloud | 22 Apr 2026said “next Wednesday” | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. | ||
| Initiate SLA discussion with account executive and VP of Customer Success | Maria SantosAegisCloud | No date given | notify or loop in?Inform, flag, copy, connect, or give a heads-up to a person or team for awareness, including internal alerts and handoffs that are not formal escalations. | ||
| Follow up with summary email covering RCA timeline, demo schedule, and SLA next steps | Maria SantosAegisCloud | 14 Apr 2026said “this afternoon” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Set up OT security technical session with Ironworks team around manufacturing use case | Maria SantosAegisCloud | No date given | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. |
Left unanswered2
How will Fortiguard Pro handle OT environments such as Siemens PLCs?
CustomerSecurityCan Aegis provide an SLA commitment or credit structure for monitoring downtime?
AegisCloudReliability
Themes and issues4
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Renewal?Calls about contract renewals, churn risk, retention, and account expansion or cross-sell opportunities. | churn risk | competitor evaluation | |
| Outage?Calls about active service outages or downtime events. | outage | monitoring downtime | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | reporting limitations | |
| other?No shared value fits; the raw string is preserved in the fact table. | trust | communication gap |
Products mentioned
2 mentions
Competitors mentioned
1 mentions
Fortiguard Pro
Evaluating alternativethreat -2
their pitch was pretty compelling especially on the compliance and reporting side
Numbers stated on this call5
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Duration of March outage with no threat monitoring | “roughly six hours” | outage duration | Russell Tang | |
| Number of demos with Fortiguard Pro | “two” | count | Catherine Page | |
| Time since Fortiguard Pro reached out | “about six weeks ago” | duration | Catherine Page | |
| Comply v2 general availability date | “April 7th” | date | Maria Santos | |
| Period of stability since remediation | “three weeks” | duration | Russell Tang |
Coaching4
How the AegisCloud side handled the call.
Strengths (3)
Acknowledged the outage and communication failures directly, owning the mistake rather than deflecting.
Probed for the customer's specific trust criteria and evaluation status before proposing next steps.
Secured concrete next steps: RCA, SLA discussion, Comply v2 demo, OT session, and a follow-up email.
Improvement notes (1)
Customer was not informed about Comply v2 GA before the call; Maria took responsibility but should ensure proactive roadmap communication in the future.
Clarity?How clearly the rep explained things.FYI
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
10 min captured of 34 min stated. Anything said in the remaining 24 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
3 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 26.3% of a 33.9min meeting; 24.3min after the final turn is unaccounted for
The model's own note: Transcript is partial; the call may have continued beyond the recorded span.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 20,057 tokens