E10 — Sam (Round 2) — Customer Economics + Growth Constraints Brief

Prepared: 11 July 2026 · Revised: 16 July 2026 · Date not confirmed — intended week of 13 Jul, sequence 2nd (after Gabe). Slot is Amir's.

Executive Brief

Mission — Understand Sales' Nestlé economics and growth constraints without a pricing audit.

Win Condition - [ ] Sales-side commercial view for Nestlé and its link to Pricing's data identified. - [ ] Tight-margin LMG/Olein lines understood, including approval and recovery logic. - [ ] Nestlé's share-of-wallet and growth constraint understood; future ownership untouched.

Working Hypothesis — Pricing holds customer × product margins, but Sales may lack a reconciled Nestlé view across mix, service and realised outcome. Tests G7; informs margin_truth and account_economics.

Critical Unknowns - Sales' Nestlé view and its link to Pricing's data. - Whether tight product margins are deliberate, and how they are governed. - Nestlé share-of-wallet and the real constraint on profitable growth.

Priority Questions 1. When you decide on Nestlé, what commercial view do you use — and can you see Pricing's underlying data? 2. Could we use the LMG/Olein book as an example? When a line is tight, how do we judge a deliberate trade-off and where it is recovered? 3. Where can you see logistics, service complexity, payment terms and customer-specific effort alongside that view? 4. What share of Nestlé's total demand do we hold — sole supplier, primary or one of several — and where is it maintained? 5. With plants generally not full, what stops a good Nestlé opportunity becoming profitable volume: share of wallet, product fit, technical approval, price, credit, logistics or something else?

Decision Watch - Product-level pricing data ≠ all-in account economics → take as Finance-scoping input, not confirmation of G7. - Any price exception → explore, not an error or realised loss claim. - A capacity issue → test whether it is a specific product/line exception, not a standing premise. - Drift to future account ownership → defer to Shashi.

Political Signals - Book-owner versus custodian language. - Whether Pricing's data is seen as usable commercial intelligence or Pricing's private tool. - Whether exceptions are openly owned, explained as relationship choices or avoided. - Whether growth constraints are described as demand conversion or defaulted to production scarcity.

Red Lines - Describe today's model; do not negotiate the future account line. - Keep it warm and make no pre-mandate commitments.

Immediate Follow-up - 30 min: capture what Sales can see, use and not reconcile. - Today: decide whether Finance needs a Nestlé worked-example agenda. - This week: carry confirmed economics evidence into the Shashi point of view.

Layer 1 — AI Working Notes

Purpose analysis. Round 2 with Sam is now a sharper G7 test and a practical role-design read. Gabe's live Pricing workbook shows customer × product data, including two tight-margin Nestlé LMG/Olein lines; the remaining question is not whether any margin data exists, but whether Sales uses it alongside the things that make an account economically sound or unsound. Broad plant under-utilisation is the operating read, with SMR adding prospective headroom, so the role should be tested against demand conversion rather than assumed capacity rationing. Sam remains the cheapest route to that answer, and sequences before Finance so the Finance conversation can be a specific scoping discussion rather than a generic discovery exercise.

Charter validation frame. Primary gate: G7 — Economic Truth. Sam is an operating owner and strong source on the current account book and information available to Sales; he is not the authority who can certify Finance's reported economics. G8 does not need further meeting time: the first conversation already established that the definition is tacit and unwritten; Mondelez is a language exception, while Kellogg's rationale remains a lower-priority, unconfirmed legacy/Malaysia-centred possibility. Do not ask which accounts Amir should own.

Fact / assumption / hypothesis split. - [FACT] (E2) Nestlé is the largest key-account network; most key accounts run on forward contracts, with spot used for urgent gaps. - [FACT] (Pricing workbook) Pricing holds line-level customer × product margin data. Customer!AE284 and Customer!AE290 show calculated margins of −53.505 and −153.505 MYR/MT for two Nestlé LMG/Olein lines. These are pricing-model calculations, not realised account P&L. - [HYP] Sales may not hold a reconciled account view across those pricing lines, service burden, terms and realised outcome. - [ASSUMPTION] Sam can explain how Sales accesses and uses Pricing's view, even if he is not the price-setting authority.

Question triage — what was cut and why. The pricing/economics questions lead because they carry the only remaining high-value uncertainty. The KA-definition question is cut: Sam already established that no definition is written, Mondelez is a language exception, and the unresolved Kellogg rationale is not worth re-litigating now. Detailed frame mechanics and capacity-prioritisation questions are also cut: Gabe is the process authority for pricing, while broad capacity scarcity is not the current operating premise. Share-of-wallet remains because it is an unanswered Primer check and grounds the demand-conversion question in the actual relationship.

Sequencing logic. Open on the practical commercial view and use the LMG/Olein lines as an invitation to explain, not an allegation. Then establish what the view excludes, ground it in share-of-wallet, and close on what actually stops profitable growth. Do not seek accountability for a line or negotiate future ownership.

Pressure test. Risk: Sam gives a confident "of course we know our margins" — ask which source he uses and establish what it contains and excludes. Risk: the two lines sound like an audit finding — call them a worked example from the pricing file and ask how the team thinks about the trade-off. Risk: growth constraints default to generic capacity language — ask for the actual blocker and distinguish a standing issue from a specific product/line exception.

Scenario branches. - Sales uses Pricing's view but no all-in view: strengthens the reconciliation-gap diagnosis and gives Finance a specific worked example. - A wider account view exists: capture its owner, inputs, cadence and trust level; narrow the charter claim accordingly. - The tight lines are deliberate: capture the authority, intended recovery mechanism and how this is checked over the account life. - The tight lines are not understood: treat that as a signal to validate with Pricing/Finance, not a conclusion about performance.

Judgment-call audit trail. Kept it to five questions to honour the "friendly, keep it warm" red line. The pricing data raises the quality of the G7 conversation but does not make Sam accountable for Pricing's inputs or realised P&L. Held the KA-definition question out because its current value is lower than the live economics/tender seam. Held the account-ownership line out entirely (routes to E12/Shashi).

Success tests. 5-min: pass. 30-sec: pass (Mission→Win→Hypothesis). Live: pass (Priority Questions are glanceable; Red Lines protect the warmth). Post-meeting: pass (fields provide the Finance-scoping and G7 checklist).