Aegis / Nimbus Platform - Comply v2 Preview
Aegis previews Comply v2; Nimbus commits to first-wave upgrade
Kevin O'Brien gave Keith Donovan a sneak peek of Aegis Comply v2 ahead of its April 7 GA, highlighting on-demand SOC 2/PCI DSS reporting and cross-module evidence pulls. Keith's team is expanding into financial services, where PCI DSS is now a priority; he committed Nimbus to the first-wave upgrade. They agreed on a migration timeline starting the week of April 7, with go-live targeted for April 21, and dedicated onboarding support from Aegis. Kevin also proactively flagged a March Detect outage and the reliability fixes shipped since. Nimbus will connect its security engineering lead for technical coordination.
How the call went
Customer was engaged and enthusiastic about Comply v2, with strong praise for time savings and operational gains; only brief frustration was about the legacy manual process.
Opening
+1Close
+114 scored turns of 49. 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
- 7
- Questions they asked
- 8
- Turns
- 49
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Keith Donovan?Matched on an initial rather than a full name, so attribution is weaker.
What happened9
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Commitment3?Someone committed to doing something.
Kevin describes a 1–2 week migration path with a dedicated Aegis onboarding specialist, not a self-serve setup.
Keith commits to having his security engineering lead Priya contact Kevin directly after the call.
Kevin commits to sending a recap and onboarding guide that afternoon and holding a first-wave slot.
Decision1?A decision was reached.
Keith requests first-wave upgrade; Kevin proposes and Keith accepts a timeline with upgrade the week of April 7 and go-live by April 21.
Risk1?A risk to the account, project, or system was surfaced.
Kevin proactively discloses a March 10–18 Detect availability incident and the architecture changes made since.
Expansion signal2?Interest in buying more, or in a broader rollout.
Keith explains that Nimbus's new financial services partnership creates compliance reporting demands, including a recent CFO question he couldn't fully answer.
Kevin highlights multi-framework support including PCI DSS; Keith says this changes the PCI conversation at Nimbus entirely.
Praise2?The customer said something positive.
Keith compares the four-minute report generation to the three days his team spent on the last SOC 2 audit and says the tool saved his head of security engineering about three months of work.
Keith praises the cross-module evidence pull from Protect and Detect into compliance reports as a 'massive operational improvement'.
What was promised5
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Share the Comply v2 demo recording with head of security engineering. | Keith DonovanCustomer | No date given | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Send recap and onboarding guide to Keith. | Kevin O'BrienAegisCloud | 1 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. | ||
| Have security engineering lead Priya contact Kevin directly after the call. | Keith DonovanCustomer | 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. | ||
| Introduce the dedicated onboarding specialist to Priya once she emails. | Kevin O'BrienAegisCloud | 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. | ||
| Schedule Comply v2 upgrade for the week of April 7, run onboarding sessions the week of April 14, and target full validation by April 21. | Kevin O'BrienAegisCloud | 21 Apr 2026said “April twenty-first” | project tracking?Create, break down, or update tickets, epics, sprint boards, milestone plans, or roadmaps, including managing project trackers and task lists. |
Themes and issues5
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 | |
|---|---|---|---|
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | on-demand audit reporting | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | multi-framework compliance support | |
| Product Roadmap?Calls about the product roadmap, planning, launch, release, and delivery of new capabilities. | product launch | first-wave upgrade planning | |
| Reliability?Calls about overall system reliability, availability, resilience, capacity, and performance, excluding specific outages or incident response. | reliability | service outage recovery | |
| Onboarding?Calls about customer onboarding, adoption, configuration, demos, and initial product usage. | onboarding | dedicated migration support |
Numbers stated on this call5
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Time to generate a SOC 2 Type II report in Comply v2 | “between, uh, ninety seconds and about four minutes” | duration | Kevin O'Brien | |
| Time Nimbus spent pulling data for its last SOC 2 audit | “three days” | duration | Keith Donovan | |
| Work saved by not having to build an internal compliance reporting tool | “three months” | effort | Keith Donovan | |
| Comply v2 onboarding window for an account of Nimbus's size | “one to two week window” | duration | Kevin O'Brien | |
| Detect availability outage period in March | “March tenth through the eighteenth” | outage duration | Kevin O'Brien |
Coaching4
How the AegisCloud side handled the call.
Strengths (3)
Proactively disclosed the Detect outage and explained the infrastructure changes before the customer had to ask, which built trust.
Tailored the demo to Nimbus's stated business drivers (financial services expansion, CFO reporting need, PCI DSS).
Moved the call to a concrete action plan with a timeline, owner, and dedicated resource.
Improvement notes (1)
Once Keith mentioned the CFO's reporting question, Kevin could have probed what specific outputs or metrics the CFO expects to tailor the pitch further.
Discovery?How well the rep drew out the customer's situation.FYI
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
12 min captured of 54 min stated. Anything said in the remaining 42 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
2 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 21.0% of a 54.3min meeting; 42.1min after the final turn is unaccounted for
The model's own note: Transcript is partial (12.1-minute span); the conversation may have continued beyond the recorded excerpt.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 29,883 tokens