Fork the Core42 engagement into two SOWs and let nothing delay the first - land the GB300 paper now, put the expanded security architecture in a separate SOW
Situation
On the Aug 19 CIQ-C42 Gap Analysis Part 2 call, Alex Trafton (Core42 CISO, roughly 10 weeks into the role) opened a scope far wider than the existing SOW - PAM consolidation across 4-plus tools, continuous vulnerability management, AI-specific security, physical and OT telemetry correlation, and future AMD MI350X deployments. The room read it as a much larger opportunity. Peter, facilitating, held the immediate GB300 deployment SOW as a closeable unit on its own and pushed the expanded scope into a separate second SOW. In the debrief immediately after the call he put it to Adam Jackson directly: But you agree, Adam, that for the next couple of days, it is just about getting that first SOW across. Adam: Yeah, 100 percent, Peter, 100 percent. Peter: I just do not want to put anything in the way of that. The same instinct had been set the night before in the pre-call, where the agreed play was to propose a second SOW or a simple addendum rather than expand the current paper.
Reasoning
Peter reads Core42 as unprepared rather than sophisticated - in the channel during the call he wrote These guys have none of this thought through. I have no idea what their plan was before talking to us, and Signing up for constant fire fighting. An unprepared counterparty produces scope that keeps growing, and every increment of growth is an increment of delay on a deal that is already the largest thing in front of the company. Splitting the paper converts an open-ended negotiation into a closeable one without refusing any of the new work - the expanded scope is not declined, it is queued behind a signature. Peter also does not trust the counterparty to reciprocate the goodwill: his stated worry to Bjorn was that they plumb us for feedback on how they should architect this DC and then go with their other provider. Getting SOW 1 signed converts free architectural consulting into a paid relationship before that risk can play out.
Additional Context
Alex Trafton and Maxim Zhurbin attended from Core42, alongside Mike and Scott Shinn from CIQ Federal. The agreed CIQ deliverable out of the call is an HLD plus control matrix by Thursday, owned by Brian Dawson and Michael Shinn, with a Fuzzball demo to follow. Bjorn had to drop at 9 and asked Peter to handle the executive component; Peter took it.
Observed Evidence
Direct quotes from the Peter-recorded debrief transcript, from the #temp-c42-gap-analysis backchannel during the live call, and from the Bjorn DM thread. Corroborated by the Fathom summary of the main call, which records the SOW fork as a key takeaway, and by the prior evenings pre-call summary which had already set propose-a-second-SOW as the scope-creep play.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
People Involved
Source
reflection
AI Confidence
94%
Related Context
fathom
Peter: But you agree, Adam, that for the next couple of days, it is just about getting that first SOW across. ... I just do not want to put anything in the way of that.
fathom
SOW Fork: SOW 1 (GB300) a focused immediate deployment to meet a 2-month deadline; SOW 2 (Expanded) a separate larger scope for a comprehensive long-term security architecture.
fathom
Drive for a PO tomorrow. Avoid expanding the SOW or delaying paper. If new work is needed, propose a second SOW or a simple addendum.
slack
Peter: These guys have none of this thought through. I have no idea what their plan was before talking to us....
slack
How hard do you want to push to get to paper. My biggest worry here is they plumb us for feedback on how they should architect this DC... and then go with their other provider.
Outcome
Holding but requires re-assertion - Peter had to restate the two-SOW fork on 8/24 when the team drifted back toward reopening settled scope.
Rating: 3/5
Decision ID: 86019015-a8d4-44e9-9084-5d4ca37fe3e8