Make the LG meeting 100 percent about understanding their problem - no selling, no refusing - and pull Justin in for that purpose only

August 11, 2026 at 2:49 PMstrategyhigh

Situation

After a Jul 30 pre-brief in which the sales team delivered what Peter called a giant mea culpa - we are sorry we have been pitching solutions that do not work, but we still want to do something for LG, and we have realised we do not understand LGs problem - Peter set the shape of the next meeting explicitly in his Justin 1:1. I want to make that meeting 100 percent about understanding their problem. Not telling them, no, we will not do this. Not telling them, no, we cannot. Just lets understand their problem. And then you and I will come back and we will write down what we think is a good thing for CIQ to do in response to that. One option might be walk away. One option might be, I do not know what. He was equally explicit about what the invitation was not: the signup is not, hey, Justin, look what you get to build. Step one is we are going to go chat, learn. He also drew the line he will hold once a response exists: I am going to stand on, if we provide it, we are giving some surety that it is supportable and that it will work. And even if we shake your hands on you are not going to come back and complain at us, we know you are going to. So I want to make sure we are staffed for that. He distinguished that from not blocking them - well, we are not going to stop you, and that is different from we are going to provide it. He admitted openly that he cannot currently explain what LG actually wants: they seem to want a repo that does not point at anything, and I do not understand why they would want it or what problem they think it is solving.

Reasoning

The failure mode he is designing against is one CIQ already committed - pitching before understanding, which is what produced the mea culpa. So he strips the meeting of every function except learning, including the tempting one of finally saying no clearly. Deferring the response to a written artifact afterwards, with walk away named as a live option, is what makes the no-selling constraint credible: Justin does not have to defend a position in the room because there is no position yet. The support line is the second half - it prevents the learning meeting from turning into an accidental commitment, because Peter has pre-declared that anything CIQ ships carries an implied warranty and therefore requires staffing. That converts a customer accommodation into a headcount question rather than a favour.

Additional Context

Peter had hosted the LG pre-brief the previous evening with Bjorn and the sales team. Justin observed that CIQ arguably already told LG you are asking for something that will not work, but we are not going to stop you - and Peter agreed that is a different statement from providing it. Justin also suggested that Elm, the prototype coming over from Product, would let LG trivially create their own selective mirror, and noted CIQ already has customers doing that. By Aug 10, Art reported Allie and Tommy were going on site and he was holding a line of either new news or this is the plan.

Observed Evidence

Direct transcript quotes from the Justin 1:1, plus Peters own account of the Jul 30 LG pre-brief in the same call. Corroborated by Arts Aug 10 Leadership Roundtable update that he had sent the plan to Bjorn and Peter.

Matching Patterns

48%
Purpose Is the Decision Procedure(defined the meeting by its single purpose and stripped everything else, declined to engage the specific ask on its merits until the purpose was served)
40%
Protect Engineering Capacity(anything provided carries a support obligation and therefore requires staffing)

Confidence Breakdown

33/35
Evidence
25/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:That a customer meeting can have exactly one job, and that the CTO will personally protect it from becoming a sales meeting or a refusal meeting. Also that being pulled into a customer meeting is not an implicit build assignment - he said so unprompted, because Justin would otherwise assume it was.
Who Affected:Justin, who is being loaned out with an explicit no-build promise. Bjorn and the sales team, whose instinct to close is being deliberately parked. LG themselves, who get a genuinely open conversation for the first time after being pitched wrong solutions.
Precedent:Sets that after a customer-facing mis-pitch, the recovery move is a learning-only meeting with the response written afterwards - and that walk away stays on the table explicitly, named in advance, so the learning is not motivated toward a yes.
Consequences:Real - Justins time is committed and the response artifact is owed. The support-surety line has teeth because it converts any LG accommodation into a staffing request that Peter must approve.
Timing:Immediately after the mea culpa, while the sales teams admission that they do not understand the problem is still fresh enough to make a learning-only meeting acceptable to them.

Source

reflection

AI Confidence

89%

Related Context

🎥
Justin <> Peter Weekly 1:1 - 2026-07-31

fathom

In the meeting, I want to make that meeting 100 percent about understanding their problem. Not telling them, no, we will not do this. Not telling them, no, we cannot. Just lets understand their problem.

🎥
Justin <> Peter Weekly 1:1 - 2026-07-31

fathom

I am going to stand on, if we provide it, we are giving some surety that it is supportable and that it will work. ... We know you are going to come back and complain at us. So I want to make sure we are staffed for that.

🎥
LG Pre-Brief - 2026-07-30

fathom

Pre-brief with Bjorn and the sales team in which the team acknowledged pitching solutions that do not work and that CIQ does not understand LGs problem.

Outcome

No outcome recorded yet.

Decision ID: 63030a76-9851-44bc-98d1-1269784ba451