Redirect the entire Core42 solution-review effort away from the people on the call and toward whoever watches the recording afterward - and make every answer technical, never personal

August 13, 2026 at 10:42 PMstrategyhigh

Situation

Peter reframed the Core42 engagement in his Nathan 1:1 and again in the group prep. His read: the Core42 security team is married to a Red Hat solution and is using the calls to collect disqualifying gaps, so there is no answer that converts the room. He therefore instructed the team to assume the people on the call are antagonistic, to stop optimizing answers for them, and to tailor everything to the decision-makers who will review the recording. Concretely: stay calm, concise and confident; give less detail rather than more; say yes we can do that repeatedly; and convert every rebuttal from a personal challenge into a technical statement - the FreeIPA docs confirm session recording is possible, not why are you saying it cannot. He also killed Bjorn framing that the win depends on having the best prepared answers.

Reasoning

Peter separated the question of whether the answers are good from the question of whether answers decide the outcome. Once he concluded the room is not the decision-maker, answer quality stopped being the lever and audience did. His line to Bjorn: the right answer could be unicorns and sunshine, and nobody else has unicorns and sunshine, and it is not going to help. The technical-not-personal rule follows from the same read - a personal challenge gives an antagonistic room a legitimate reason to disqualify on tone, which is exactly the disqualifying gap they are hunting for, whereas a technical statement survives review by a third party who was not in the room. He priced the whole thing honestly at 10 to 15 percent.

Additional Context

Core42 engineering has already signed a statement of work naming CIQ over Red Hat, Canonical and WWT. The blocker is the security organization. Peter believes the deal is Stargate-scale and business-making, and is playing it as a low-probability, high-payoff shot rather than a deal to be closed by effort.

Observed Evidence

Peter to Nathan: I would assume that the people on the call are antagonistic. They are going into the meeting to torpedo us. And so there is no path where we finish the meeting and these people say you guys are the solution. And: there is a giant difference between saying it is documented and it works, and saying it is documented, why are you saying it is not - that is a personal attack. And on probability: if we get this, this is Stargate. This deal is enough to make our business. So we take our shot, but I am at like 10, 15 percent.

Matching Patterns

68%
Purpose Is the Decision Procedure(refuses to engage the specific questions on their merits, restates what the meeting is actually for and derives behavior from that)
44%
Executive Sponsorship for Strategic Partnerships(same category, CTO takes point on a strategically decisive customer engagement)

Confidence Breakdown

35/35
Evidence
22/30
Pattern
20/20
Source
15/15
Corroboration

Reasoning Depth Analysis

Org Signal:Tells the team that losing this call is not their failure - it decouples individual performance from an outcome Peter believes is already largely determined, which is why he could praise Nathan performance in the same breath as predicting a loss.
Who Affected:Bjorn, whose answer-prep framing was overridden; Brian Dawson, who now facilitates rather than argues; and the CIQ Federal framing Mike and Scott adopt on the call.
Precedent:Establishes that when the room is not the decider, CIQ optimizes for the record rather than the conversation - a reusable move for any procurement fight with a hostile technical gatekeeper.
Consequences:Real behavioral change, not emphasis: it changed who speaks, how much detail is given, and whether the team rebuts assertions directly.
Timing:Now because the Aug 13 call had already exposed the pattern and the next call is the last realistic shot before the security team writes its recommendation.

Related Context

🎥
Nathan <> Peter Weekly 1:1

fathom

We are not actually talking to the people on the call. We are talking to the people on the call boss who watches the meeting afterward. ... To me that is the only path to us winning.

🎥
Core42 Group Prep

fathom

Project confidence in a flexible toolkit, not a rigid solution. The call primary audience is the meeting recording, which will be seen by decision-makers beyond the room.

💬
Core42 prep group DM

slack

At the end erik said engineering is a yes, let us get through the security concerns quickly and please do not hold up this process. I am paraphrasing, but that was the message.

Outcome

The C42 HLD final review completed and closed on implementation is coming soon - the engagement advanced to implementation rather than being disqualified by the security team.

Rating: 4/5

Decision ID: 611eeaec-6f0f-4c73-8cf9-5127782bb63a