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
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
Confidence Breakdown
Reasoning Depth Analysis
People Involved
Source
reflection
AI Confidence
92%
Related Context
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.
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.
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