E6 — Gabe — Pricing & Portfolio Brief

Prepared: 11 July 2026 · Revised: 12 July 2026 · Date not confirmed — intended week of 13 Jul, sequence 1st (before Sam r2). Slot is Amir's.

Executive Brief

Mission — Close the keystone: map where pricing authority actually sits by order type, so I know what I can commit to a key account.

Win Condition - [ ] Proposal, approval and final decision rights mapped for term, tender and spot business, including actual escalation thresholds. - [ ] One recent transaction used to distinguish the documented process from how approval works in practice. - [ ] Margin-truth seam named: do Pricing and Finance see the same customer margin, and who reconciles?

Working Hypothesis — Pricing authority changes by order type, commitment size and risk, but the precise proposal, approval and escalation boundaries remain unconfirmed. Pricing and Finance may also operate with different customer-margin views. Tests G5 and G7; moves pricing_boundary, pricing_mechanics and margin_truth.

Critical Unknowns - Escalation triggers and what senior approval actually covers. - Tender and spot authority versus the term-contract path. - Pricing-versus-Finance customer-economics basis.

Priority Questions 1. Walk me through one recent term-contract quote from feedstock mark to customer offer. At each point, who recommends, who can change the position, and who gives final approval? 2. What specifically moves approval from you to Alvin, Shashi or Group — deal value, duration, margin, volume commitment, credit exposure or something else? 3. How does that authority path differ for a tender and for spot business? In a tender, where can you still shape the position versus simply submit an approved number? 4. When Pricing and Finance both look at the economics of an account such as Nestlé, what does each include? Where do the views differ, and who owns reconciliation? 5. When two important customers compete for scarce capacity, what customer-value evidence does Pricing provide, who makes the decision, and is that the same person when the month moves off plan?

Decision Watch - Offer to co-map the boundary → take as learning, not authority. - Invite to opine on a live pricing call or bulk-vs-value → defer.

Political Signals - Does he distinguish quote-safe cost from headline margin? - Does he name authority clearly or describe only process? - Is the Finance-reconciliation seam discussable?

Red Lines - Map authority; do not negotiate it or imply a reporting line. - Do not treat Pricing's margin as Finance-approved profitability.

Immediate Follow-up - Debrief G5/G7 evidence, named authorities and unresolved seams. - If warranted, scope the Finance conversation and proposed Model moves.

Layer 1 — AI Working Notes

Purpose analysis. Gabe is the last open node on the commercial spine and sits on the single keystone unknown — the central-vs-local pricing boundary (Primer checklist item 1; Frontier Central vs Local Pricing Boundary still [OPEN]). The 11 Jul capture reframed the boundary from a single line into a per-order-type question: contracted/term (frame) business runs a conversion-cost + approval-chain path (escalating by amount/period, up to Group President; credit committee on new/limit-increase), while spot runs faster on a reference in the moment. This meeting exists to validate that captured [HYP] and turn the Pricing node from [HYP,central] toward [FACT].

Charter validation frame. Primary gates: G5 — Pricing Boundary and G7 — Economic Truth. Supporting evidence for G6 — Allocation Authority. Gabe is the process authority for the pricing mechanics he operates, but may not be the decision authority for senior escalation limits, Finance methodology or capacity allocation. A gate moves only if the discussion produces named roles, actual triggers and a recent example.

Fact / assumption / hypothesis split. - [FACT] (E7 Nik) Trading publishes daily CPO/CPKO marks feeding Gabe's quotes — feedstock cost is the upstream input to every quote. - [FACT] (Gabe SMR mtg, 10 Jul) Pricing runs a commercial Excel build not reconciled to SAP/Finance; a reconciliation project is active. Margin quoted from Pricing must state its basis. - [FACT] (LR workshop) ~USD20/MT gap vs local peers on conventional & LMG; margin-reporting gap across Pricing (ex-S&D) / Finance / Trading, all landing in one LR P&L. - [HYP — Amir, 11 Jul] Two order types with distinct approval paths; the three agreed frame terms (conversion cost, lift-off reference price, volume-confirmation timing). - [ASSUMPTION] Gabe has the authority visibility to describe the escalation thresholds precisely (he may only know his own ceiling).

Question triage — what was cut and why. Kept the five that only Gabe can answer and that move a load-bearing claim. Cut: "what's tank-top avoidance in practice?" — useful but not keystone; pick it up only if time allows. Kept tender mechanics narrowly through the authority question in Q3: the point is not the platform process but where Gabe can still shape the outcome. The margin-truth question (Q4) remains below the boundary questions because it hands to Finance; the meeting still succeeds on Q1–Q2 alone.

Sequencing logic. Q1 opens with a real transaction (low-threat, high-yield) and distinguishes documented process from lived authority. Q2 isolates the escalation triggers. Q3 tests whether tender and spot follow different paths. Q4–Q5 cover the economics and allocation seams — valuable but sacrificeable if time dies. If the meeting collapses after Q2, the keystone still moves materially.

Pressure test. Risk: Gabe describes process, not authority — mitigated by asking who can change the position, who approves and what triggers escalation. Risk: he treats the economics comparison defensively — that itself is a political signal to log, not a failure. His allocation answer is supporting evidence only; do not treat it as confirmation unless he is the decision authority. Asking where Amir's authority should sit remains deliberately excluded.

Scenario branches. - Boundary is clean and central: charter claim 5 confirms; role influences price, doesn't set it — feeds the Shashi prep (E12) "what I own vs influence." - Boundary is fuzzy/contested: higher-value — a live seam the role could legitimately help govern; log as candidate. - A customer-margin view exists after all: charter narrows; Finance conversation may be redundant. Unlikely given two prior signals, but stay open.

Judgment-call audit trail. Held back any "what should the KAM own" framing (premature; Shashi's to define). Kept triangulation questions verbatim per Instruments/Charter_Validation.md (G5, G7 evidence standards). Ranked the margin-seam below the boundary so the meeting is robust to time collapse.

Success tests. 5-min: pass (brief reads cold in <2 min). 30-sec: pass (Mission→Win→Hypothesis refreshes the keystone). Live: pass (Priority Questions + Red Lines glanceable). Post-meeting: pass (Win/Hypothesis/Decision-Watch/Follow-up are the debrief skeleton).