Took the Fuzzball pitch to Axiom Space himself rather than letting Sales carry it - and set the closing path at NDA then contract
Situation
On the 7/28 Axiom Space CTO introductory call (Mark Seigle and Ethan Leas, with Tom Shingler, Ramesh Srinivasan and Bjorn on the CIQ side), Peter learned Axiom is building an orchestration platform for sovereigns and immediately concluded CIQ needs to get Fuzzball in front of them. When Bjorn asked whether Tom was pitching it, Peter answered I did. He read out the technical fit in real time - they will need post-quantum work which is already on the roadmap and they seemed happy with that, and they will need Ascender plus updates to run well over low-connectivity satellite links - set the next step as sign an NDA and start talking contract, and named the strategic window: they are just starting, so they are in a position to choose OS cleanly right now. Mark said he wants to close in weeks. Peter told Bjorn yeah if we lose this we suck and posted in the deal channel sounds like it is ours to lose. Ramesh confirmed Axiom is moving forward with the NDA.
Reasoning
Peter had told Sarah beforehand that the call was an easy one - an introduction with a friendly that has already met Max and likes us - and that he did not know why we are having the call other than Bjorn really wants their business. He took the pitch anyway once the sovereign-orchestration detail surfaced, because that turned a relationship call into a product-fit call inside CIQs own domain. The strategic logic is greenfield timing: a company that is just starting can choose its OS cleanly, so the cost of switching them later is the cost of not being there now. His ours to lose framing sets the accountability rather than the odds - the risk is CIQ execution, not competitive threat. Committing the post-quantum roadmap and the Ascender low-connectivity work in the room means engineering scope is being set by the CTO on the call rather than negotiated back afterwards.
Additional Context
Axiom Space had already met Max Spevack. The call was booked by Tom Shingler as an introductory CTO-level conversation. Peter was simultaneously in the middle of the Google payment escalation and told Bjorn he was in a spicy mood. Bjorn was briefed by Kelly in parallel so Peter stood down from a follow-up call.
Observed Evidence
Live play-by-play in the Bjorn DM during the call including the explicit I did when asked who pitched, the deal-channel post, Rameshs independent confirmation of NDA progress, and Peters own pre-call framing in the recorded Sarah sync.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
People Involved
Source
reflection
AI Confidence
89%
Related Context
slack
Also axiom is building an orchestration platform for sovereigns... so we obviously need to get Fuzzball in front of them asap -- (Bjorn: Is tom pitching it?) -- I did ... they will need some post-quant stuff from us, but it is on our roadmap and they seem happy with that. They will need Ascender. And they will need a couple of (awesome) updates to it to allow it to run well again low-connectivity satellites, etc. ... yes. next step is sign an NDA and start talking contract ... They are just starting, so they are in a position to choose OS cleanly right now. ... Yeah if we lose this we suck ... Mark is saying he wants to close this in weeks
slack
Ramesh: Good call with Mark Seigle at Axiom...we are moving forward with their NDA... Bjorn: Peter was live texting. Sounds big. Lets close asap -- Peter: Sounds like it is ours to lose.
fathom
(Sarah: And you are good to have this call with Axiom?) Yeah, it is an easy one. Introduction with a friendly that has already met Max and likes us. I dont know why we are having the call other than Bjorn really, really, really wants their business, but it is not a hard call for me.
calendar
Attendees: ethan.leas@axiomspace.com, bhovland@ciq.com, tshingler@ciq.com, ramesh@ciq.com, pnelson@ciq.com, mark.seigle@axiomspace.com
Outcome
Smaller deal closing immediately per Ramesh on 8/31, with expansion conversations on Ascender Pro and other products already underway.
Rating: 4/5
Decision ID: de22179a-ca62-4eda-99a2-17e985a1fa61