ExternalProgressedTuesday, 7 Apr 2026·Clearwater Medical

Aegis / Clearwater Medical - Comply v2 Deployment Kickoff

Clearwater Medical and Aegis kick off Comply v2 deployment, plan Thursday review

The call was a deployment kickoff for Comply v2, which went GA the same day. Aegis introduced on-demand reporting and multi-framework support, and Clearwater shared their compliance priorities: HIPAA now, PCI DSS for the patient portal, and ISO 27001 later. They agreed to complete connector setup early in the week, run a baseline HIPAA report by midweek, and reconvene Thursday to review the first report. A clear next-step timeline was set with action items for both sides.

Read the full transcript →44 turns · 9 min captured of 43 min stated

How the call went

External participants expressed consistent enthusiasm for Comply v2 features and deployment speed, with no negative signals.

Opening

+1

Close

+1
Overall+1
+2+10-1-2start of callend

8 scored turns of 44. 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.

AegisCloud 65%Customer 35%
Questions we asked
7
Questions they asked
4
Turns
44
Longest silence
2s

Who was on the call

Customer

  • Ajay Mehta?Matched on an initial rather than a full name, so attribution is weaker.
  • Natalie Simmons?Matched on an initial rather than a full name, so attribution is weaker.

What happened6

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.

  • Ajay recounts a late-night scramble for HIPAA audit evidence; on-demand reporting is welcomed as a major improvement.

Commitment2?Someone committed to doing something.

  • Both sides commit to getting connectors live early in the week and schedule a Thursday review of the baseline HIPAA report.

  • Mike commits to sending a CloudFormation template so Clearwater can create the IAM role and provide the role ARN.

Expansion signal1?Interest in buying more, or in a broader rollout.

  • Natalie outlines Clearwater's compliance roadmap: HIPAA now, PCI DSS for the patient portal, ISO 27001 targeted for end of year.

Praise2?The customer said something positive.

  • Ajay praises the unified control mapping, saying it eliminates maintaining separate spreadsheets per framework.

  • Natalie is pleasantly surprised that connector setup takes hours rather than days.

What was promised5

CommitmentOwnerDueAction type
Send the CloudFormation template for IAM role creation to Natalie.Mike RomanoAegisCloud
7 Apr 2026said “today
send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over.
Create the IAM role with read permissions using the template and send the role ARN to Mike.Natalie SimmonsCustomerNo date givenengineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration.
Confirm that CloudTrail multi-region logging is enabled.
Natalie SimmonsCustomerNo date giveninternal review or investigation?Conduct QA, audit, verification, investigation, post-mortem, root-cause analysis, or assessment, including testing and analyzing to understand or validate something.
Send the calendar invite for the Thursday review call.
Aisha JohnsonAegisCloud
9 Apr 2026said “Thursday
schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance.
Run the baseline HIPAA report after connector setup is complete.No owner
8 Apr 2026said “Wednesday or Thursday
internal review or investigation?Conduct QA, audit, verification, investigation, post-mortem, root-cause analysis, or assessment, including testing and analyzing to understand or validate something.

Themes and issues4

What the call was about, and the specific issue recorded under each theme.

ThemeAs 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.complianceon-demand reporting
Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness.compliancemulti-framework support
Engineering Process?Calls about engineering process, sprints, estimation, tech debt, scope, timeline, and project management.deploymentconnector setup timeline
Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness.complianceaudit cycle planning

Products mentioned

1 mentions

  • Comply2

    Interest expressedsaid “Comply v2

Numbers stated on this call5

Values are shown exactly as they were spoken.

ClaimAs spokenMetricStated by
Time for initial connector setupa few hoursdurationMike Romano
HIPAA audit advance noticethirty daysdurationAjay Mehta
SOC 2 type 2 observation periodsix month observation perioddurationAjay Mehta
Share of cloud environment on CloudPrimeeighty percentpercentageNatalie Simmons
Time to create IAM role with CloudFormation templateabout five minutesdurationMike Romano

Coaching4

How the AegisCloud side handled the call.

Strengths (3)

  • Aisha proactively asked about Clearwater's compliance priorities and audit cycle, uncovering HIPAA, PCI, ISO 27001 and SOC 2 type 2 needs.

  • Mike gave concrete and time-bound deployment steps with clear prerequisites.

  • Aisha closed the call with a concrete timeline and scheduled a Thursday review.

Improvement notes (1)

  • Customer-side prerequisites (IAM role, CloudTrail verification) were listed but not tied to a named owner in the moment; Natalie took them on verbally.

    Accountability?Whether the rep took ownership.FYI

How far to trust this call

Every fact above was extracted from the captured portion of the transcript only.

Transcript coverage20%

9 min captured of 43 min stated. Anything said in the remaining 34 min is absent from this page.

Mean transcription confidence93%

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 19.7% of a 42.8min meeting; 33.6min after the final turn is unaccounted for

The model's own note: Transcript is partial and spans 9.1 minutes; the captured portion is the kickoff agenda.

Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 21,659 tokens