← Back to the call brief
External11 Apr 2026· Cobalt Software16% captured

Aegis / Cobalt Software - Q2 Planning

42 turns · 7 min captured of 41 min stated?Only the captured portion exists in the database. The remaining 34 min of this call was never transcribed, so nothing said in it appears anywhere in this application.

Show facts?Markers in the left gutter show which facts the model built from each turn. Click a marker to open that fact's evidence — this is the citation trail running backwards.

Showing 42 of 42 turns · 25 turns were used as evidence for at least one fact.

  1. Lisa ParkAegisCloud0:08turn 0ASR 88%

    Hey Lauren, thanks for making time this morning — I know Q2 planning season gets pretty hectic.

  2. Lauren BishopCustomer0:16turn 1ASR 96%

    Yeah, no kidding, it's been a lot. But this was already on my calendar so I made sure to protect it.

  3. Lisa ParkAegisCloud0:23turn 2ASR 90%

    I appreciate that. So, just to set the agenda for today — I wanted to walk through where things stand on the renewal, get your feedback on how the platform's been performing, and then we can talk about what your roadmap looks like for the rest of the year.

  4. Lauren BishopCustomer0:42turn 3ASR 91%

    That works. And I do have some things I want to flag, so... yeah, let's just get into it.

  5. Lisa ParkAegisCloud0:49turn 4ASR 90%

    Of course. Why don't you go first actually — what's on your mind?

  6. Lauren BishopCustomer0:55turn 5ASR 94%

    Okay, so the big thing — and I want to be direct here — is the outage in March. The Detect outage. That was... that was not a great experience for us.

    -1Lauren says the Detect outage was not a great experience. · service reliability

  7. Lisa ParkAegisCloud1:07turn 6ASR 96%

    Yeah, and I completely understand. I was going to bring that up myself. That was March 10th through roughly the 18th, the event processing issue — six hours of no visibility on threat monitoring.

  8. Lauren BishopCustomer1:21turn 7ASR 90%

    Right. And look, I get that outages happen, I've been in infrastructure long enough to know nothing is bulletproof, but six hours is a long time. Our security team was basically flying blind.

    -1Lauren calls six hours of no visibility a long time and says the security team was flying blind. · service reliability

  9. Lisa ParkAegisCloud1:33turn 8ASR 92%

    Completely fair. And I don't want to just gloss over it with a, you know, 'here's what we did to fix it' kind of answer if you have more to say about the impact on your side.

  10. Lauren BishopCustomer1:47turn 9ASR 97%

    I mean, we didn't have an incident during that window, which is lucky, but it surfaced a gap in our own contingency planning too, so it wasn't all on Aegis. It just... it raised questions internally about the reliability of the platform.

    -1Lauren says the outage raised internal questions about platform reliability. · service reliability

  11. Lisa ParkAegisCloud2:03turn 10ASR 96%

    That's really helpful context, and I appreciate you being candid about it. On our end, the root cause was a single point of failure in the event ingestion pipeline — it was a cascading failure from there. Engineering has since deployed redundant processing nodes and implemented a circuit breaker pattern, so the architecture is fundamentally different now in that layer.

  12. Lauren BishopCustomer2:26turn 11ASR 89%

    Okay. Is there documentation on that? Like, something I can actually share with my team rather than just taking your word for it?

  13. Lisa ParkAegisCloud2:35turn 12ASR 91%

    Yes, absolutely. We put out a full post-incident review — I'll send that over after the call. It goes into the root cause analysis, the remediation steps, and the testing we did before re-deploying.

  14. Lauren BishopCustomer2:48turn 13ASR 95%

    Good. That'll help. My team wants to see that it's not just a band-aid.

  15. Lisa ParkAegisCloud2:53turn 14ASR 92%

    Understood. And honestly if there are follow-up questions after your team reviews it, I can also set up time with one of our solution architects to walk through the technical details.

  16. Lauren BishopCustomer3:05turn 15ASR 96%

    That might be worth doing, yeah. Let me see what the team thinks after they read the doc. Okay, so that's the main concern. What else — you said you wanted to cover the renewal specifically?

  17. Lisa ParkAegisCloud3:18turn 16ASR 88%

    Right. So your current contract runs through end of June, so we're about... eleven weeks out. I wanted to start the conversation early so we're not scrambling in June.

  18. Lauren BishopCustomer3:29turn 17ASR 92%

    Smart. Yeah. What are you looking at — is pricing changing?

  19. Lisa ParkAegisCloud3:34turn 18ASR 96%

    So, there is a standard escalator built into the contract — I believe it's three percent — and that would apply. But I also want to understand what your scope looks like going into next year before we lock anything in, because if you're expanding, that changes the conversation.

  20. Lauren BishopCustomer3:52turn 19ASR 97%

    Mm. Yeah, so we're planning to add about forty more cloud workloads through Q3 as we finish migrating the last of our on-prem stuff. So the footprint is growing.

  21. Lisa ParkAegisCloud4:03turn 20ASR 89%

    Okay, that's good to know. Are those workloads going to be on CloudPrime primarily, or is it a mix?

  22. Lauren BishopCustomer4:11turn 21ASR 96%

    Mix. Mostly CloudPrime, some Azure — we've got about a 70/30 split right now and I think it stays roughly there.

  23. Lisa ParkAegisCloud4:19turn 22ASR 91%

    Got it. That's helpful. So I'll put together some options — probably a base renewal at your current tier, and then a growth option that prices in that expanded workload count. I can model out what makes sense financially for both sides.

  24. Lauren BishopCustomer4:34turn 23ASR 91%

    That'd be useful. And, um, I do want to flag — we're not exclusively evaluating Aegis. I have procurement pushing me to get at least one competitive quote, so... I want to be transparent about that.

  25. Lisa ParkAegisCloud4:47turn 24ASR 97%

    I appreciate you being upfront. Who are you looking at, if you don't mind me asking?

  26. Lauren BishopCustomer4:54turn 25ASR 89%

    Probably SentinelShield, just because they've been pretty aggressive in our space lately. I don't have a strong pull toward them but procurement wants the comparison.

  27. Lisa ParkAegisCloud5:04turn 26ASR 94%

    Fair enough. I'll make sure our proposal is competitive on value, not just price. And I'm happy to do a side-by-side if that would be helpful for your internal review.

  28. Lauren BishopCustomer5:16turn 27ASR 95%

    Maybe. Let me see what SentinelShield comes back with first.

  29. Lisa ParkAegisCloud5:20turn 28ASR 95%

    Of course. Just know the offer is there. Okay, I also wanted to touch on Comply v2 — you're currently on Comply, right? The new version just went GA on April 7th.

  30. Lauren BishopCustomer5:33turn 29ASR 97%

    Oh yeah, I saw the release notes. The on-demand reporting — we've actually already poked around in it a little.

  31. Lisa ParkAegisCloud5:41turn 30ASR 91%

    Oh great, any early impressions?

  32. Lauren BishopCustomer5:43turn 31ASR 88%

    It's... decent. The SOC 2 report generation is noticeably faster than v1. We haven't dug into the HIPAA or ISO stuff yet because that's not really our priority, but the multi-framework view is something we'll probably use for PCI.

  33. Lisa ParkAegisCloud5:58turn 32ASR 93%

    That's good to hear on the SOC 2 side — that's been one of the most common things customers come to us about. And yeah, PCI DSS coverage in v2 is pretty robust, so I'd encourage you to test that whenever you get a chance.

  34. Lauren BishopCustomer6:15turn 33ASR 91%

    We will. Our next PCI audit cycle is Q4 so I want to have that dialed in before then.

  35. Lisa ParkAegisCloud6:22turn 34ASR 94%

    Perfect timing then. I can connect you with our compliance specialist if you want a guided walkthrough before you're in the thick of audit prep.

  36. Lauren BishopCustomer6:31turn 35ASR 91%

    Yeah, actually, that would be useful. Maybe in June or so.

  37. Lisa ParkAegisCloud6:36turn 36ASR 94%

    I'll make a note of that. Okay, so to recap what I'm taking away — I'll send the post-incident review for the Detect outage, I'll put together two renewal proposal options with pricing that reflects the expanded workload, and I'll pencil in a compliance walkthrough for sometime in June. Does that cover everything?

  38. Lauren BishopCustomer6:55turn 37ASR 92%

    I think so. And if we decide to loop in the solutions architect on the Detect stuff, I'll reach out through you.

  39. Lisa ParkAegisCloud7:04turn 38ASR 95%

    Absolutely, just ping me and I'll coordinate. What's a good turnaround for the proposal — does two weeks work, so around the 24th?

  40. Lauren BishopCustomer7:12turn 39ASR 96%

    Yeah, that's fine. I probably won't get to it until the following week anyway, so that timing works.

  41. Lisa ParkAegisCloud7:19turn 40ASR 89%

    Perfect. Alright, I'll let you get back to your Q2 planning chaos. Thanks again for the time, Lauren.

  42. Lauren BishopCustomer7:26turn 41ASR 90%

    Thanks Lisa. Talk soon.