Hold the Core42 commitment at five weeks, signal two-to-three as likely, and trade the compression for topology data

Situation

Core42 sent an overnight message via Anand asking CIQ to pull in the deployment timeline because HPE is running double shifts and the delay is causing them problems. Bjorn Hovland called an impromptu Zoom with Nathan Blackham and Peter, said he wanted to pull the previously quoted five weeks into two to three, and asked Nathan to confirm his notes that two to three weeks was reasonable for a bare greenfield deployment with none of the Scott Shinn extras. Nathan agreed it was reasonable if Ansible scripts and prep work started now. Peter then set the terms of what could actually be said to the customer, in three parts. One - the estimate is fine but the commitment is not: I think two or three weeks is reasonable and possible. I would be really careful about committing to it when it is the first time we have done this with these resources. One thing goes wrong and that timeline is blown. Two - keep the contracted number and frame the gap honestly: I am really comfortable with you telling them five weeks was our padded... so it covers something goes wrong. But we think it is likely to land in the two to three week range. I am fine with that. I just would not commit to two or three weeks. Three - convert the customer urgency into an input: I would leverage it a little bit with them and say, yeah, we can probably bring it into two or three weeks. By the way, guys, the more you can give us about your topology, the more information then that you can feed us now, the way more likely we are to hit two or three weeks. Later that morning in DM he restated it: I would be VERY careful about how we word commitment around something tightly timed like this. I do not think we CAN hit this timeline, and when Bjorn said Nathan had originally said two weeks, Peter corrected the provenance of the number - No he did not. He answered a question about how fast it MIGHT go if everything went perfectly. he gave a range. the minimum side of that range was 3 weeks... There is a reason under promise and over deliver is a phrase.

Reasoning

Peter is drawing a line between an engineering estimate and a customer commitment and refusing to let the first silently become the second. The specific defect he names is that the two-to-three week figure was a best-case answer to a hypothetical, produced by people who have never run this deployment with these resources, and a best case has no padding in it by construction - one failure consumes the entire margin. He is not disputing the number, he is disputing its status. That is why he is comfortable with the five weeks being described out loud as padded and the two-to-three being described as likely: honesty about the padding costs nothing and preserves the contractual floor. The third part is the one that turns a defensive position into a productive one - rather than absorbing the customer pressure, he hands it back as a condition, because the largest single risk to the compressed timeline is missing topology detail that only Core42 can supply, and Nathan had just said the BOM may not include networking gear and that the policy-compliance list from Alex still had not arrived. Making speed contingent on their inputs converts their impatience into the thing that actually makes speed possible.

Additional Context

This is the second time in twelve days Peter has intervened to stop a compressed Core42 timeline from being said out loud - on Aug 19 he pre-empted a three-week figure in DM before the deal closed. The situation is now inverted: the SOW is signed at five weeks and the pressure is coming from the customer rather than from the sales conversation. Erik at Core42 framed the stakes to Bjorn as if you get cluster one, you get clusters two through 50. In the customer-facing call an hour later, Adam Jackson told Core42 only that the deployment would be shorter than originally discussed with no definitive date - consistent with the line Peter set.

Observed Evidence

Fathom transcript, Peter verbatim: My word, Bjorn, is only... I think two or three weeks is reasonable and possible. I would be really careful about committing to it when it is the first time we have done this with these resources. One thing goes wrong and that timeline is blown. And: I am really comfortable with you telling them five weeks was our padded... so it covers something goes wrong. But we think it is likely to land in the two to three week range. I am fine with that. I just would not commit to two or three weeks. And: I would leverage it a little bit with them and say, yeah, we can probably bring it into two or three weeks. By the way, guys, the more you can give us about your topology, the more more information then that you can feed us now, the way more likely we are to hit two or three weeks. Bjorn: Yeah, no, I think I think that is fair.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis