p2predict 0.9.1__tar.gz → 0.9.4__tar.gz

{p2predict-0.9.1/src/p2predict.egg-info → p2predict-0.9.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: p2predict
-Version: 0.9.1
+Version: 0.9.4
 Summary: Parametric price benchmarking for engineering and procurement trade-offs. Agentic first, runs on your data, stays on your machine.
 Author: Ahmed Khalil Hafsi
 License-Expression: PolyForm-Noncommercial-1.0.0
@@ -26,7 +26,7 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.1
 Requires-Dist: joblib>=1.2
-Requires-Dist: matplotlib>=3.7
+Requires-Dist: matplotlib>=3.9
 Requires-Dist: mpld3>=0.5
 Requires-Dist: numpy>=1.24
 Requires-Dist: pandas<3.0,>=2.0
@@ -46,7 +46,7 @@ Dynamic: license-file
 
 <div align="center">
 
-# P2Predict
+<img src="./documentation/logo.svg" alt="P2Predict" width="240" />
 
 ### The right price is already in your data.
 
@@ -59,6 +59,14 @@ Dynamic: license-file
 
 ![P2Predict MCP Demo](./documentation/p2predict_mcp_demo.gif)
 
+**Set up in one command:**
+
+```bash
+pip install p2predict[mcp]
+```
+
+Built for procurement and engineering teams in automotive, semiconductors, electronics, industrials, pharma, and chemicals.
+
 </div>
 
 ## The problem
@@ -151,7 +159,7 @@ Drop the whole RFQ on the agent. Every line gets a target and a range. The eight
 
 Most tools hand you a number and walk away. P2Predict hands you the number **and tells you how confident to be in it**, per part, in dollars. That honesty is the whole point: a confident-but-wrong benchmark loses you credibility the moment a supplier checks it.
 
-![Honest confidence ranges, per part](./case-studies/battery-management-ics/assets/intervals_comparison.png)
+![Honest confidence ranges, per part](./documentation/charts/confidence-range.svg)
 
 Three real parts, three different confidence ranges. The model is tight on the part it knows well and openly uncertain on the ones it doesn't. A narrow range means negotiate hard. A wide one means get a quote first. Your category manager always knows which.
 
@@ -165,7 +173,7 @@ Point P2Predict at a category and it shows you the levers. These charts come str
 
 **Supplier choice is the biggest lever on the board.** Same single-cell chip, identical spec, sorted by who makes it:
 
-![Supplier premium on an identical part](./case-studies/battery-management-ics/assets/manufacturer_premium.png)
+![Supplier premium on an identical part](./documentation/charts/supplier-premium.svg)
 
 The premium supplier is priced at roughly four times the value option for the same part. That is a number you take into a negotiation, backed by your own data.
 
@@ -175,10 +183,18 @@ The premium supplier is priced at roughly four times the value option for the sa
 
 Package size, supplier premium, multi-cell architecture: each one in dollars, each one adding up exactly to the predicted price. This is what lets your category manager say *"I know what I'm paying for, and here's the line I want to cut."*
 
+**Complexity is priced, not assumed.** Every package pin on this same chip adds cost, monotonically, from $2.31 at 8 pins to $4.88 at 48 pins:
+
+![Package complexity priced by pin count](./documentation/charts/pin-count-curve.svg)
+
+And on the 30 parts held back from training, entirely unseen by the model, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work on parts it never saw, not asking you to trust it blind.
+
 ## How it fits your stack
 
 **You don't use P2Predict; your agent does.** It speaks to **any AI agent** through a standard connector — Claude, GPT, or a local model — so your category managers never learn a new tool. They ask the assistant they already use, and it runs the analysis for them. This is agentic-first: there is no dashboard and no app, the interface is the agent you already have.
 
+Under the hood, P2Predict is two layers. A **math layer** trains on your spend, predicts the price, attributes it spec by spec, and puts a calibrated range on every estimate — the defensible statistics. A **judgment layer** sits on top and steers the conversation: which analysis to run, when to stop and ask you for more data, and whether a result is solid enough to quote or needs a real RFQ first. It's what keeps a weaker agent from overstating a number it shouldn't.
+
 Everything runs **on your own machine**. Your purchasing data is your most sensitive commercial asset, so P2Predict never uploads it and no third party trains on it. Pair it with a local model to keep the whole loop offline, or with a cloud agent if you prefer; either way your raw spend stays put, with no data-residency conversation to have with legal.
 
 It complements should-cost tools, it does not replace them. Bottom-up should-costing builds a part up from material, labor, and machine time to estimate what it *should cost to make*. P2Predict does not do that and is not trying to. It answers the other question every category manager actually asks: *what has the market charged us for parts like this, and what should we expect to pay for the next one?*
@@ -193,11 +209,48 @@ Three worked case studies, each reproducible end to end on data anyone can downl
 
 Each one leads with results, shows where to trust them, and points to exactly where every number comes from.
 
+## FAQ
+
+**Is it really free?**
+Yes, for internal use. P2Predict is source-available under the PolyForm Noncommercial License. No seats, no trial period, no sales call. A commercial license is only needed if you deploy it for clients or embed it in a paid product.
+
+**How reliable are the numbers?**
+Every estimate comes with a range, not just a number, and the range is honest about how thin your data is: wide where history is sparse, tight where it's deep. On the public case studies, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work, not asking you to trust it blind.
+
+**Does my data ever leave my machine?**
+No. P2Predict trains and predicts entirely on your own machine. The only thing that leaves is whatever your AI agent normally sends to its own model. Pair it with a local model to keep that offline too.
+
+**Which AI agents does it work with?**
+Any agent that speaks MCP: Claude, GPT-based agents, or a model running locally. That's the core idea behind P2Predict: it's a capability for your agent to use, not a new tool for you to learn. No dashboard, no separate login. It just shows up wherever you already do your work with your agent.
+
+**Is this a should-cost tool?**
+No. Should-costing builds a part up from material, labor, and machine time. P2Predict benchmarks against what the market has actually charged for comparable parts.
+
+**Why is this open source?**
+Because a closed tool only ever does what its vendor decided to ship. Source-available means you, or your agent, can read every line, tune the code or the interfaces to your company's ecosystem, or wire it into your own stack and other tools without waiting on anyone's roadmap. That kind of ownership doesn't exist behind a closed API.
+
+**Who built P2Predict?**
+It started in 2023 as a project in my free time, weekends and sporadic evenings. See below for the background it draws on.
+
+**Who do I talk to about rolling this out for my team?**
+Nobody, really: it installs with one pip command and runs on your own data in a few minutes. Start with [INSTALL.md](INSTALL.md) and [TECHNICAL.md](TECHNICAL.md). If you'd still like a hand, want a commercial license, or want to share a dataset for a future case study, reach out at [ahmedhafsi.com/contact](https://ahmedhafsi.com/contact). Happy to help.
+
 ## Who built it
 
-P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**, Senior Manager of Negotiation Excellence at Infineon, where he leads negotiation strategy across automotive, semiconductor, consumer, and chemicals categories in Asia-Pacific. He built and led Dyson's global Negotiation Excellence capability and advised on negotiation and applied game theory at TWS Partners in Munich and London. He trained as an engineer at the Karlsruhe Institute of Technology and works across three continents in four languages.
+P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**.
+
+**Experience**
+
+- **Senior Manager, Negotiation Excellence** — Infineon Technologies (2023–present). High-stakes deals across Asia, including foundry, OSAT, and strategic suppliers.
+- **Senior Manager, Negotiation Excellence** — Dyson (2020–2023). Architected and led the global Negotiation Excellence capability: governance, KPIs, tooling, and renegotiation campaigns.
+- **Senior Management Consultant, Negotiation & Game Theory** — TWS Partners, Munich & London (2014–2019). Advised industrial clients on negotiation strategy and applied game theory.
+
+**Education & training**
+
+- Karlsruhe Institute of Technology (KIT), Electrical Engineering & Information Technology (2008–2014).
+- Harvard Law School, Program on Negotiation (2021). Negotiation Master Class: Advanced Strategies for Experienced Negotiators.
 
-P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More on his approach to negotiation, pricing, and game theory at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
+P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
 
 ## Try it / set it up
 

{p2predict-0.9.1 → p2predict-0.9.4}/README.md

@@ -1,6 +1,6 @@
 <div align="center">
 
-# P2Predict
+<img src="./documentation/logo.svg" alt="P2Predict" width="240" />
 
 ### The right price is already in your data.
 
@@ -13,6 +13,14 @@
 
 ![P2Predict MCP Demo](./documentation/p2predict_mcp_demo.gif)
 
+**Set up in one command:**
+
+```bash
+pip install p2predict[mcp]
+```
+
+Built for procurement and engineering teams in automotive, semiconductors, electronics, industrials, pharma, and chemicals.
+
 </div>
 
 ## The problem
@@ -105,7 +113,7 @@ Drop the whole RFQ on the agent. Every line gets a target and a range. The eight
 
 Most tools hand you a number and walk away. P2Predict hands you the number **and tells you how confident to be in it**, per part, in dollars. That honesty is the whole point: a confident-but-wrong benchmark loses you credibility the moment a supplier checks it.
 
-![Honest confidence ranges, per part](./case-studies/battery-management-ics/assets/intervals_comparison.png)
+![Honest confidence ranges, per part](./documentation/charts/confidence-range.svg)
 
 Three real parts, three different confidence ranges. The model is tight on the part it knows well and openly uncertain on the ones it doesn't. A narrow range means negotiate hard. A wide one means get a quote first. Your category manager always knows which.
 
@@ -119,7 +127,7 @@ Point P2Predict at a category and it shows you the levers. These charts come str
 
 **Supplier choice is the biggest lever on the board.** Same single-cell chip, identical spec, sorted by who makes it:
 
-![Supplier premium on an identical part](./case-studies/battery-management-ics/assets/manufacturer_premium.png)
+![Supplier premium on an identical part](./documentation/charts/supplier-premium.svg)
 
 The premium supplier is priced at roughly four times the value option for the same part. That is a number you take into a negotiation, backed by your own data.
 
@@ -129,10 +137,18 @@ The premium supplier is priced at roughly four times the value option for the sa
 
 Package size, supplier premium, multi-cell architecture: each one in dollars, each one adding up exactly to the predicted price. This is what lets your category manager say *"I know what I'm paying for, and here's the line I want to cut."*
 
+**Complexity is priced, not assumed.** Every package pin on this same chip adds cost, monotonically, from $2.31 at 8 pins to $4.88 at 48 pins:
+
+![Package complexity priced by pin count](./documentation/charts/pin-count-curve.svg)
+
+And on the 30 parts held back from training, entirely unseen by the model, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work on parts it never saw, not asking you to trust it blind.
+
 ## How it fits your stack
 
 **You don't use P2Predict; your agent does.** It speaks to **any AI agent** through a standard connector — Claude, GPT, or a local model — so your category managers never learn a new tool. They ask the assistant they already use, and it runs the analysis for them. This is agentic-first: there is no dashboard and no app, the interface is the agent you already have.
 
+Under the hood, P2Predict is two layers. A **math layer** trains on your spend, predicts the price, attributes it spec by spec, and puts a calibrated range on every estimate — the defensible statistics. A **judgment layer** sits on top and steers the conversation: which analysis to run, when to stop and ask you for more data, and whether a result is solid enough to quote or needs a real RFQ first. It's what keeps a weaker agent from overstating a number it shouldn't.
+
 Everything runs **on your own machine**. Your purchasing data is your most sensitive commercial asset, so P2Predict never uploads it and no third party trains on it. Pair it with a local model to keep the whole loop offline, or with a cloud agent if you prefer; either way your raw spend stays put, with no data-residency conversation to have with legal.
 
 It complements should-cost tools, it does not replace them. Bottom-up should-costing builds a part up from material, labor, and machine time to estimate what it *should cost to make*. P2Predict does not do that and is not trying to. It answers the other question every category manager actually asks: *what has the market charged us for parts like this, and what should we expect to pay for the next one?*
@@ -147,11 +163,48 @@ Three worked case studies, each reproducible end to end on data anyone can downl
 
 Each one leads with results, shows where to trust them, and points to exactly where every number comes from.
 
+## FAQ
+
+**Is it really free?**
+Yes, for internal use. P2Predict is source-available under the PolyForm Noncommercial License. No seats, no trial period, no sales call. A commercial license is only needed if you deploy it for clients or embed it in a paid product.
+
+**How reliable are the numbers?**
+Every estimate comes with a range, not just a number, and the range is honest about how thin your data is: wide where history is sparse, tight where it's deep. On the public case studies, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work, not asking you to trust it blind.
+
+**Does my data ever leave my machine?**
+No. P2Predict trains and predicts entirely on your own machine. The only thing that leaves is whatever your AI agent normally sends to its own model. Pair it with a local model to keep that offline too.
+
+**Which AI agents does it work with?**
+Any agent that speaks MCP: Claude, GPT-based agents, or a model running locally. That's the core idea behind P2Predict: it's a capability for your agent to use, not a new tool for you to learn. No dashboard, no separate login. It just shows up wherever you already do your work with your agent.
+
+**Is this a should-cost tool?**
+No. Should-costing builds a part up from material, labor, and machine time. P2Predict benchmarks against what the market has actually charged for comparable parts.
+
+**Why is this open source?**
+Because a closed tool only ever does what its vendor decided to ship. Source-available means you, or your agent, can read every line, tune the code or the interfaces to your company's ecosystem, or wire it into your own stack and other tools without waiting on anyone's roadmap. That kind of ownership doesn't exist behind a closed API.
+
+**Who built P2Predict?**
+It started in 2023 as a project in my free time, weekends and sporadic evenings. See below for the background it draws on.
+
+**Who do I talk to about rolling this out for my team?**
+Nobody, really: it installs with one pip command and runs on your own data in a few minutes. Start with [INSTALL.md](INSTALL.md) and [TECHNICAL.md](TECHNICAL.md). If you'd still like a hand, want a commercial license, or want to share a dataset for a future case study, reach out at [ahmedhafsi.com/contact](https://ahmedhafsi.com/contact). Happy to help.
+
 ## Who built it
 
-P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**, Senior Manager of Negotiation Excellence at Infineon, where he leads negotiation strategy across automotive, semiconductor, consumer, and chemicals categories in Asia-Pacific. He built and led Dyson's global Negotiation Excellence capability and advised on negotiation and applied game theory at TWS Partners in Munich and London. He trained as an engineer at the Karlsruhe Institute of Technology and works across three continents in four languages.
+P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**.
+
+**Experience**
+
+- **Senior Manager, Negotiation Excellence** — Infineon Technologies (2023–present). High-stakes deals across Asia, including foundry, OSAT, and strategic suppliers.
+- **Senior Manager, Negotiation Excellence** — Dyson (2020–2023). Architected and led the global Negotiation Excellence capability: governance, KPIs, tooling, and renegotiation campaigns.
+- **Senior Management Consultant, Negotiation & Game Theory** — TWS Partners, Munich & London (2014–2019). Advised industrial clients on negotiation strategy and applied game theory.
+
+**Education & training**
+
+- Karlsruhe Institute of Technology (KIT), Electrical Engineering & Information Technology (2008–2014).
+- Harvard Law School, Program on Negotiation (2021). Negotiation Master Class: Advanced Strategies for Experienced Negotiators.
 
-P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More on his approach to negotiation, pricing, and game theory at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
+P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
 
 ## Try it / set it up
 

{p2predict-0.9.1 → p2predict-0.9.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "p2predict"
-version = "0.9.1"
+version = "0.9.4"
 description = "Parametric price benchmarking for engineering and procurement trade-offs. Agentic first, runs on your data, stays on your machine."
 readme = "README.md"
 license = "PolyForm-Noncommercial-1.0.0"
@@ -39,7 +39,7 @@ classifiers = [
 dependencies = [
     "click>=8.1",
     "joblib>=1.2",
-    "matplotlib>=3.7",
+    "matplotlib>=3.9",
     "mpld3>=0.5",
     "numpy>=1.24",
     "pandas>=2.0,<3.0",

{p2predict-0.9.1 → p2predict-0.9.4/src/p2predict.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: p2predict
-Version: 0.9.1
+Version: 0.9.4
 Summary: Parametric price benchmarking for engineering and procurement trade-offs. Agentic first, runs on your data, stays on your machine.
 Author: Ahmed Khalil Hafsi
 License-Expression: PolyForm-Noncommercial-1.0.0
@@ -26,7 +26,7 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.1
 Requires-Dist: joblib>=1.2
-Requires-Dist: matplotlib>=3.7
+Requires-Dist: matplotlib>=3.9
 Requires-Dist: mpld3>=0.5
 Requires-Dist: numpy>=1.24
 Requires-Dist: pandas<3.0,>=2.0
@@ -46,7 +46,7 @@ Dynamic: license-file
 
 <div align="center">
 
-# P2Predict
+<img src="./documentation/logo.svg" alt="P2Predict" width="240" />
 
 ### The right price is already in your data.
 
@@ -59,6 +59,14 @@ Dynamic: license-file
 
 ![P2Predict MCP Demo](./documentation/p2predict_mcp_demo.gif)
 
+**Set up in one command:**
+
+```bash
+pip install p2predict[mcp]
+```
+
+Built for procurement and engineering teams in automotive, semiconductors, electronics, industrials, pharma, and chemicals.
+
 </div>
 
 ## The problem
@@ -151,7 +159,7 @@ Drop the whole RFQ on the agent. Every line gets a target and a range. The eight
 
 Most tools hand you a number and walk away. P2Predict hands you the number **and tells you how confident to be in it**, per part, in dollars. That honesty is the whole point: a confident-but-wrong benchmark loses you credibility the moment a supplier checks it.
 
-![Honest confidence ranges, per part](./case-studies/battery-management-ics/assets/intervals_comparison.png)
+![Honest confidence ranges, per part](./documentation/charts/confidence-range.svg)
 
 Three real parts, three different confidence ranges. The model is tight on the part it knows well and openly uncertain on the ones it doesn't. A narrow range means negotiate hard. A wide one means get a quote first. Your category manager always knows which.
 
@@ -165,7 +173,7 @@ Point P2Predict at a category and it shows you the levers. These charts come str
 
 **Supplier choice is the biggest lever on the board.** Same single-cell chip, identical spec, sorted by who makes it:
 
-![Supplier premium on an identical part](./case-studies/battery-management-ics/assets/manufacturer_premium.png)
+![Supplier premium on an identical part](./documentation/charts/supplier-premium.svg)
 
 The premium supplier is priced at roughly four times the value option for the same part. That is a number you take into a negotiation, backed by your own data.
 
@@ -175,10 +183,18 @@ The premium supplier is priced at roughly four times the value option for the sa
 
 Package size, supplier premium, multi-cell architecture: each one in dollars, each one adding up exactly to the predicted price. This is what lets your category manager say *"I know what I'm paying for, and here's the line I want to cut."*
 
+**Complexity is priced, not assumed.** Every package pin on this same chip adds cost, monotonically, from $2.31 at 8 pins to $4.88 at 48 pins:
+
+![Package complexity priced by pin count](./documentation/charts/pin-count-curve.svg)
+
+And on the 30 parts held back from training, entirely unseen by the model, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work on parts it never saw, not asking you to trust it blind.
+
 ## How it fits your stack
 
 **You don't use P2Predict; your agent does.** It speaks to **any AI agent** through a standard connector — Claude, GPT, or a local model — so your category managers never learn a new tool. They ask the assistant they already use, and it runs the analysis for them. This is agentic-first: there is no dashboard and no app, the interface is the agent you already have.
 
+Under the hood, P2Predict is two layers. A **math layer** trains on your spend, predicts the price, attributes it spec by spec, and puts a calibrated range on every estimate — the defensible statistics. A **judgment layer** sits on top and steers the conversation: which analysis to run, when to stop and ask you for more data, and whether a result is solid enough to quote or needs a real RFQ first. It's what keeps a weaker agent from overstating a number it shouldn't.
+
 Everything runs **on your own machine**. Your purchasing data is your most sensitive commercial asset, so P2Predict never uploads it and no third party trains on it. Pair it with a local model to keep the whole loop offline, or with a cloud agent if you prefer; either way your raw spend stays put, with no data-residency conversation to have with legal.
 
 It complements should-cost tools, it does not replace them. Bottom-up should-costing builds a part up from material, labor, and machine time to estimate what it *should cost to make*. P2Predict does not do that and is not trying to. It answers the other question every category manager actually asks: *what has the market charged us for parts like this, and what should we expect to pay for the next one?*
@@ -193,11 +209,48 @@ Three worked case studies, each reproducible end to end on data anyone can downl
 
 Each one leads with results, shows where to trust them, and points to exactly where every number comes from.
 
+## FAQ
+
+**Is it really free?**
+Yes, for internal use. P2Predict is source-available under the PolyForm Noncommercial License. No seats, no trial period, no sales call. A commercial license is only needed if you deploy it for clients or embed it in a paid product.
+
+**How reliable are the numbers?**
+Every estimate comes with a range, not just a number, and the range is honest about how thin your data is: wide where history is sparse, tight where it's deep. On the public case studies, predictions land within roughly 16% of the actual price half the time, and within 73% nine times in ten. That's the model showing its work, not asking you to trust it blind.
+
+**Does my data ever leave my machine?**
+No. P2Predict trains and predicts entirely on your own machine. The only thing that leaves is whatever your AI agent normally sends to its own model. Pair it with a local model to keep that offline too.
+
+**Which AI agents does it work with?**
+Any agent that speaks MCP: Claude, GPT-based agents, or a model running locally. That's the core idea behind P2Predict: it's a capability for your agent to use, not a new tool for you to learn. No dashboard, no separate login. It just shows up wherever you already do your work with your agent.
+
+**Is this a should-cost tool?**
+No. Should-costing builds a part up from material, labor, and machine time. P2Predict benchmarks against what the market has actually charged for comparable parts.
+
+**Why is this open source?**
+Because a closed tool only ever does what its vendor decided to ship. Source-available means you, or your agent, can read every line, tune the code or the interfaces to your company's ecosystem, or wire it into your own stack and other tools without waiting on anyone's roadmap. That kind of ownership doesn't exist behind a closed API.
+
+**Who built P2Predict?**
+It started in 2023 as a project in my free time, weekends and sporadic evenings. See below for the background it draws on.
+
+**Who do I talk to about rolling this out for my team?**
+Nobody, really: it installs with one pip command and runs on your own data in a few minutes. Start with [INSTALL.md](INSTALL.md) and [TECHNICAL.md](TECHNICAL.md). If you'd still like a hand, want a commercial license, or want to share a dataset for a future case study, reach out at [ahmedhafsi.com/contact](https://ahmedhafsi.com/contact). Happy to help.
+
 ## Who built it
 
-P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**, Senior Manager of Negotiation Excellence at Infineon, where he leads negotiation strategy across automotive, semiconductor, consumer, and chemicals categories in Asia-Pacific. He built and led Dyson's global Negotiation Excellence capability and advised on negotiation and applied game theory at TWS Partners in Munich and London. He trained as an engineer at the Karlsruhe Institute of Technology and works across three continents in four languages.
+P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**.
+
+**Experience**
+
+- **Senior Manager, Negotiation Excellence** — Infineon Technologies (2023–present). High-stakes deals across Asia, including foundry, OSAT, and strategic suppliers.
+- **Senior Manager, Negotiation Excellence** — Dyson (2020–2023). Architected and led the global Negotiation Excellence capability: governance, KPIs, tooling, and renegotiation campaigns.
+- **Senior Management Consultant, Negotiation & Game Theory** — TWS Partners, Munich & London (2014–2019). Advised industrial clients on negotiation strategy and applied game theory.
+
+**Education & training**
+
+- Karlsruhe Institute of Technology (KIT), Electrical Engineering & Information Technology (2008–2014).
+- Harvard Law School, Program on Negotiation (2021). Negotiation Master Class: Advanced Strategies for Experienced Negotiators.
 
-P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More on his approach to negotiation, pricing, and game theory at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
+P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
 
 ## Try it / set it up
 

{p2predict-0.9.1 → p2predict-0.9.4}/src/p2predict.egg-info/requires.txt

@@ -1,6 +1,6 @@
 click>=8.1
 joblib>=1.2
-matplotlib>=3.7
+matplotlib>=3.9
 mpld3>=0.5
 numpy>=1.24
 pandas<3.0,>=2.0