Comply v2 - Adoption Metrics Review
Comply v2 adoption review shows strong metrics and cross-sell signals
AegisCloud's internal team reviewed Comply v2 adoption two weeks after launch. Megan Lawson reported 847 tenants generating reports, roughly 38-39% adoption, beating the internal 25% benchmark. The team discussed framework usage, support volume, and cross-sell interest in Identity and Protect. They agreed to prepare an exec one-pager and start GDPR scoping conversations.
How the call went
No external-side turns in this internal call; sentiment not scored.
Opening
0Close
0No turn-level sentiment was scored for this call, so only the opening, close, and overall figures above are available.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 18
- Questions they asked
- 0
- Turns
- 41
- Longest silence
- 1s
Who was on the call
Customer
- Internal call
What happened8
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised1?A problem was brought up on the call.
Brian Cho reported support volume manageable; nav discoverability spike dropped to zero, with ISO 27001 formatting edge cases remaining.
Commitment1?Someone committed to doing something.
Megan agreed to prepare an exec one-pager; Diana volunteered to pull testimonial quotes.
Decision1?A decision was reached.
Team discussed GDPR framework; Megan said adoption data supports resourcing it sooner, and Brian committed to starting internal scoping.
Recap3?A summary of what was agreed.
Tom Bradley noted the Comply v2 launch went smoothly, crediting redundant processing changes after the March Detect outage.
Framework breakdown surprised the team: SOC 2 most popular, HIPAA second, PCI DSS third.
Brian summarized action items and the call closed positively.
Expansion signal2?Interest in buying more, or in a broader rollout.
Megan Lawson reported 847 tenants generated reports, about 38-39% adoption, beating the 25% internal benchmark.
Diana Reeves shared that four customers asked about Identity after seeing IAM gaps in Comply v2 reports, driving natural cross-sell.
What was promised4
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Prepare one-pager for exec review on Comply v2 adoption and cross-sell signal | Megan LawsonAegisCloud | No date given | document or write up?Write, draft, compile, update, or finalize a document, report, runbook, case note, plan, or summary, including creating shared docs and drafting communications. | ||
| Deploy ISO 27001 report formatting fix in next patch | Tom BradleyAegisCloud | 1 May 2026said “end of next week” | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Pull customer testimonial quote for exec one-pager | Diana ReevesAegisCloud | No date given | document or write up?Write, draft, compile, update, or finalize a document, report, runbook, case note, plan, or summary, including creating shared docs and drafting communications. | ||
| Start internal conversation on GDPR framework scoping | No owner | 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. |
Left unanswered1
What is the timeline for adding GDPR to Comply?
AegisCloudProduct Roadmap
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 | |
|---|---|---|---|
| Onboarding?Calls about customer onboarding, adoption, configuration, demos, and initial product usage. | product adoption | on-demand report adoption | |
| Renewal?Calls about contract renewals, churn risk, retention, and account expansion or cross-sell opportunities. | cross-selling | compliance report driving cross-sell | |
| Product Roadmap?Calls about the product roadmap, planning, launch, release, and delivery of new capabilities. | product roadmap | future compliance framework planning | |
| Support?Calls about customer support interactions, escalations, workarounds, and support experience. | support volume | post-launch support ticket analysis |
Numbers stated on this call5
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Unique tenants generating at least one on-demand report as of April 21 | “847” | account count | Megan Lawson | |
| Eligible accounts for Comply v2 | “roughly 2,200” | account count | Megan Lawson | |
| Adoption rate at two-week mark | “38, 39 percent” | percentage | Tom Bradley | |
| Internal benchmark adoption at two-week mark | “25 percent” | percentage | Megan Lawson | |
| Share of reports using SOC 2 framework | “nearly half” | percentage | Megan Lawson |
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
7 min captured of 31 min stated. Anything said in the remaining 24 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.9% of a 30.9min meeting; 23.4min after the final turn is unaccounted for
The model's own note: Transcript marked partial; call appears to wrap up within captured portion.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 14,608 tokens