
Guest: Lars Bettermann, Chief Procurement Officer at Bridgestone
Listen on Spotify | Listen on Apple Podcasts | Listen on Amazon Music
Lars Bettermann opens with an admission that might surprise anyone who now runs procurement for a tire maker: “I never imagined procurement to be such an interesting space when I was at college.” He studied economics, and procurement barely registered in the curriculum, which he calls “a big mistake” given the value and influence the function carries inside a company. Roughly three decades later, as Chief Procurement Officer at Bridgestone, he keeps returning to one test throughout this conversation with Spencer: are you relevant in the field you work in? Relevance means understanding the latest trends in your category, recognizing when a new technology makes you better at your job, and refusing to assume that the way things have always worked is the way they should keep working. “The moment you don’t innovate or the moment you don’t further develop you are dead,” he says. “So standing still is not an option.”
Bettermann is the Chief Procurement Officer at Bridgestone, where he owns the procurement teams in both North America and Europe. His career began about 30 years ago at Ford Motor Company through a trainee program, and he later spent more than a decade as a consultant at Accenture before moving to Bridgestone. In this episode, he and Spencer cover a lot of ground: what the path to CPO actually looks like, how tech-savvy a procurement leader needs to be, whether the ERP is on its way out, why Bridgestone would not build its own software, and how a tire maker measures the value procurement creates.
How a Ford Trainee Program Led to a Career in Procurement
Bettermann did not plan on procurement. He studied economics, liked the automotive industry, and wanted to see how vehicles get built, so he landed at Ford after college. The trainee program the company offered for people like him happened to be in procurement. “That’s how I ended up in procurement about 30 years ago,” he says, and he found it to be “the spot you want to be.”
Spencer’s opening question is a practical one: how does someone become a CPO, through excellent category management or through executive leadership experience? Bettermann’s answer has two layers. Early in a career, he says, it matters “to indeed get famous for something,” and that something is usually a category. His were a handful of categories at Ford, including fuel tanks and the fuel system. Consulting at Accenture then added a second skill on top of that depth: bringing people together, running projects, and moderating between different opinions. That, in his view, is the main ability a future CPO needs, because procurement puts suppliers, internal customers, and people like cost estimators at one table, and the leader is the moderator in the middle of that ecosystem.
Why Relevance Matters More Than Any Single Skill
Spencer asks how deep into the weeds a CPO needs to be on technology at a moment when AI is forcing teams to re-evaluate their processes and assumptions. Bettermann’s answer starts with the obvious: hardly any job in procurement today is not technology supported or technology enabled, so being tech-savvy “is not a choice anymore but a must.” Then he widens the frame. Success in procurement, he says, comes from being relevant in what you do. A marketing category manager cannot be relevant without understanding the latest trends in marketing and what is possible when sourcing agencies and merchandising material. “What I ask from my people is to be relevant in the field they are operating in.” Technology follows from that: once you know your field well enough to see that a tool is state of the art in it, adopting the tool and staying relevant go hand in hand.
Where Technology Should Go First
Spencer recalls a comment Bettermann made in an earlier podcast interview at DPW: a young person entering procurement today may not need to know how to turn a purchase requisition into a purchase order, because that process could be automated. Bettermann clarifies what he sees in younger colleagues. Someone who says they want to be in procurement, he imagines, is picturing negotiation, contracting, and sitting at a table with suppliers, not processing requisitions. The requisition-to-PO process is not more or less important, he says, but it does not draw the same interest, and it is not where you can add the most value as a person. That is why it is easier to become famous as a category manager. The same logic tells him where to apply technology: the areas that get less attention and offer the most room to be automated are where he would target a pilot.
He adds a compliment for Spencer’s company, noting that LightSource is one of the few tackling the front office, working with category managers, while the back end of the process already has many competitors. Spencer says part of that was circumstance, since he focused on what he understood when he started the company, but the hypothesis held up. He never expected to compete with ERP, and nearly every customer, he notes, is in some stage of a perennial ERP transformation.
Why Procurement Is Where the Value Shows Up
Spencer explains why he built a company around procurement’s earliest stages. At Tesla, where the team built its own ERP, he came to feel that “all of that battle is won or lost by the time you create a purchase order.” He points to a 50-cent negotiation on a single component in the Model 3 as the kind of small win that moves a business’s financial results, and says it felt like putting on glasses: procurement was the most important team in the business, yet it ran on spreadsheets and emails until the transaction. That pulled him toward the upstream relationship between suppliers, engineering, and procurement, the “three-legged stool,” rather than tail spend.
Bettermann agrees that the beauty of procurement is that you can immediately see the impact of what you do. A saving on a large spend line lands directly on the P&L, something HR, Spencer’s comparison, does not get in the same way. Then the question becomes what you do with that power, and there, he says, technology should help build better cases, better value, and better numbers.
Is the ERP Really Dead?
Bettermann does not hide his view: he thinks ERP systems are “kind of dead.” His reasoning is that an ERP is a mainframe trying to serve every side of a company’s operations, whereas he sees the field moving toward targeted, off-the-shelf solutions for different processes.
Spencer pushes back with how most companies see it. For many, the ERP is the bedrock system of record, the digital twin of the business, and when it conflicts with anything else, even the people, the ERP wins. Bettermann’s answer is that there should still be a source of truth, whether you call it the ERP or a base system, holding things like material codes and supplier master data. He pictures “an island somewhere where you can then connect different boats going to the island”: procurement sails over, collects the data it needs, and works in a lighter system. Spencer presses on the risk. One medical device customer, he says, has its platforms integrate with a data lake instead of with each other, and without built-in business logic you could end up with “an island full of people with huts that are all built differently.”
Bettermann says he would like to hear how that company fares, then returns to the question he always asks himself: “what problem are we trying to solve?” An ERP, he says, is also inflexible, upgrades take real time and effort, and he wonders how much of it is legacy carried for compliance. What procurement actually needs is a proper reflection of the source-to-contract process, category managers supported by the data they need, and a highly efficient back end for turning requisitions into purchase orders. “I would love a world where I don’t need to carry all that complicated backpack,” he says, before conceding it may be an illusion that never becomes real.
Start With the Problem, Not the Technology
Spencer says he loves starting with the problem and working backward, and uses the Segway to make the point. Everyone, venture capitalists included, thought it was the coolest technology around, until it arrived at $6,000 and the obvious question was what problem it solved. Start from the technology and you end up with the Segway; start from the problem, he says, and you might think of a scooter.
Bettermann has his own example, from his Ford heritage. Ford succeeded through mass production, he says, and nearly went bankrupt when Henry Ford insisted a customer could have any car as long as it was black, until competitors started offering colors. It is the same pattern, he argues, as the Segway giving way to someone else’s e-scooter, and as the ERP, and as what LightSource does: you probably needed an ERP in order to see where its gaps are and where to find your niche.
Why Bridgestone Won’t Build Its Own Software
Spencer raises a third option beyond monolith and best-of-breed: building in house. Companies like GM have built end-to-end internal systems with large IT teams, and now AI coding tools can produce a convincing prototype in about 15 minutes, though the last 20 percent, making it reliable and deployable, is the hard part. The bar, he notes, is getting lower.
Bettermann is not convinced. He grants there are good examples, but as a procurement person he believes in the ecosystem around him, partners and suppliers who specialize in the problem they solve. “My problem as Bridgestone is that I want to produce the best tire in the world and I want to offer that at the best value at the best price for my customer.” So why would he step away from “my core competency which is building a tire” and invest his knowledge in something outside his core responsibility? He would, he says, never put his stakes on it.
Why Standing Still Is Not an Option
The tug-of-war between legacy process and new technology comes next. Spencer notes that large customers often ask for configuration to match what they already do, rather than asking how a new approach could redraw the lines. Bettermann says he would always adjust processes when there is a need, and that need can come from a malfunction in the process, a customer demand, a change in the environment, or a change in technology. It is worth adjusting a process to apply technology that solves a problem better, he says, and it is a mistake to close the door on whatever is innovative today that was not two years ago.
He is candid about the constraint. Silicon Valley companies have more room to move at speed than big companies with a heritage, he says, and he sometimes looks “jealously” at companies like Spencer’s, “not that you are better or worse,” just without the heritage he proudly carries. Spencer, who offers “speed wins” as one of his company’s taglines, agrees that the more storied a company is, the more there is to lose, and asks how you reward people for bets with a 90 percent chance of failure and a 10 percent chance of becoming the lifeblood of the business. Bettermann is not sure he buys the founder-versus-executive framing. For him it is about taking responsibility: he wants people to act as if they were the CEO of their area, to deliver regular business and also keep thinking about innovation and process change, rather than only doing the job from 8 to 5. His shorthand: “Don’t stick to the black cars.”
How Bridgestone Measures the Value Procurement Creates
On incentives, Spencer asks why a salesperson earns a share of every sale while procurement does not earn a share of the savings it creates, and notes that value is not only cost out: it can also be cost containment, reliability in a market, speed to market, and early supplier involvement. That is why Bridgestone uses a value scorecard rather than a single KPI, Bettermann says. Cost reduction is the most famous measure and cost avoidance the second, joined by how many suppliers a person introduced to drive innovation, how well they reduce risk, and whether they secure the right payment terms with suppliers. People are incentivized on how they do against that set of KPIs, he explains, though not one to one as in sales, and the work is in setting the right frame for them.
Spencer then asks how you quantify something like risk reduction, where the point is an event you prevented. Bettermann’s answer is to foresee as much as possible of the risk that could hit your area of responsibility. Energy is his example: a very famous category these days, where a category manager who hears what is happening in the market might secure energy capacity for the following year. He says plainly that he is making the scenario up to illustrate the point. It ties back to his relevance test: an energy category manager has to understand what it means when the world goes crazy securing energy at a reasonable price for the company.
The Question Behind Every Answer
Whether the topic is career advice, ERP systems, or incentives, Bettermann’s answers come back to the same two questions: am I relevant in what I do, and what problem are we trying to solve? Relevance, in his telling, is not about owning the newest tool. It means knowing your category well enough to recognize when a technology or a process change makes you better, and building a team of people who feel responsible for acting on that. It also means not chasing a technology because it is impressive, and not staying with a process or system only because it is the one you inherited.
Spencer closes by saying he loves that Bettermann calls category managers famous, an elevation of the function that the industry should embrace, and that the conversation left him energized. Bettermann says it seems they could continue for another hour at least. Season 2 of Source Code opens with a conversation about what it takes for procurement to earn that status.

Guest: Lars Bettermann, Chief Procurement Officer at Bridgestone
Listen on Spotify | Listen on Apple Podcasts | Listen on Amazon Music
Lars Bettermann opens with an admission that might surprise anyone who now runs procurement for a tire maker: “I never imagined procurement to be such an interesting space when I was at college.” He studied economics, and procurement barely registered in the curriculum, which he calls “a big mistake” given the value and influence the function carries inside a company. Roughly three decades later, as Chief Procurement Officer at Bridgestone, he keeps returning to one test throughout this conversation with Spencer: are you relevant in the field you work in? Relevance means understanding the latest trends in your category, recognizing when a new technology makes you better at your job, and refusing to assume that the way things have always worked is the way they should keep working. “The moment you don’t innovate or the moment you don’t further develop you are dead,” he says. “So standing still is not an option.”
Bettermann is the Chief Procurement Officer at Bridgestone, where he owns the procurement teams in both North America and Europe. His career began about 30 years ago at Ford Motor Company through a trainee program, and he later spent more than a decade as a consultant at Accenture before moving to Bridgestone. In this episode, he and Spencer cover a lot of ground: what the path to CPO actually looks like, how tech-savvy a procurement leader needs to be, whether the ERP is on its way out, why Bridgestone would not build its own software, and how a tire maker measures the value procurement creates.
How a Ford Trainee Program Led to a Career in Procurement
Bettermann did not plan on procurement. He studied economics, liked the automotive industry, and wanted to see how vehicles get built, so he landed at Ford after college. The trainee program the company offered for people like him happened to be in procurement. “That’s how I ended up in procurement about 30 years ago,” he says, and he found it to be “the spot you want to be.”
Spencer’s opening question is a practical one: how does someone become a CPO, through excellent category management or through executive leadership experience? Bettermann’s answer has two layers. Early in a career, he says, it matters “to indeed get famous for something,” and that something is usually a category. His were a handful of categories at Ford, including fuel tanks and the fuel system. Consulting at Accenture then added a second skill on top of that depth: bringing people together, running projects, and moderating between different opinions. That, in his view, is the main ability a future CPO needs, because procurement puts suppliers, internal customers, and people like cost estimators at one table, and the leader is the moderator in the middle of that ecosystem.
Why Relevance Matters More Than Any Single Skill
Spencer asks how deep into the weeds a CPO needs to be on technology at a moment when AI is forcing teams to re-evaluate their processes and assumptions. Bettermann’s answer starts with the obvious: hardly any job in procurement today is not technology supported or technology enabled, so being tech-savvy “is not a choice anymore but a must.” Then he widens the frame. Success in procurement, he says, comes from being relevant in what you do. A marketing category manager cannot be relevant without understanding the latest trends in marketing and what is possible when sourcing agencies and merchandising material. “What I ask from my people is to be relevant in the field they are operating in.” Technology follows from that: once you know your field well enough to see that a tool is state of the art in it, adopting the tool and staying relevant go hand in hand.
Where Technology Should Go First
Spencer recalls a comment Bettermann made in an earlier podcast interview at DPW: a young person entering procurement today may not need to know how to turn a purchase requisition into a purchase order, because that process could be automated. Bettermann clarifies what he sees in younger colleagues. Someone who says they want to be in procurement, he imagines, is picturing negotiation, contracting, and sitting at a table with suppliers, not processing requisitions. The requisition-to-PO process is not more or less important, he says, but it does not draw the same interest, and it is not where you can add the most value as a person. That is why it is easier to become famous as a category manager. The same logic tells him where to apply technology: the areas that get less attention and offer the most room to be automated are where he would target a pilot.
He adds a compliment for Spencer’s company, noting that LightSource is one of the few tackling the front office, working with category managers, while the back end of the process already has many competitors. Spencer says part of that was circumstance, since he focused on what he understood when he started the company, but the hypothesis held up. He never expected to compete with ERP, and nearly every customer, he notes, is in some stage of a perennial ERP transformation.
Why Procurement Is Where the Value Shows Up
Spencer explains why he built a company around procurement’s earliest stages. At Tesla, where the team built its own ERP, he came to feel that “all of that battle is won or lost by the time you create a purchase order.” He points to a 50-cent negotiation on a single component in the Model 3 as the kind of small win that moves a business’s financial results, and says it felt like putting on glasses: procurement was the most important team in the business, yet it ran on spreadsheets and emails until the transaction. That pulled him toward the upstream relationship between suppliers, engineering, and procurement, the “three-legged stool,” rather than tail spend.
Bettermann agrees that the beauty of procurement is that you can immediately see the impact of what you do. A saving on a large spend line lands directly on the P&L, something HR, Spencer’s comparison, does not get in the same way. Then the question becomes what you do with that power, and there, he says, technology should help build better cases, better value, and better numbers.
Is the ERP Really Dead?
Bettermann does not hide his view: he thinks ERP systems are “kind of dead.” His reasoning is that an ERP is a mainframe trying to serve every side of a company’s operations, whereas he sees the field moving toward targeted, off-the-shelf solutions for different processes.
Spencer pushes back with how most companies see it. For many, the ERP is the bedrock system of record, the digital twin of the business, and when it conflicts with anything else, even the people, the ERP wins. Bettermann’s answer is that there should still be a source of truth, whether you call it the ERP or a base system, holding things like material codes and supplier master data. He pictures “an island somewhere where you can then connect different boats going to the island”: procurement sails over, collects the data it needs, and works in a lighter system. Spencer presses on the risk. One medical device customer, he says, has its platforms integrate with a data lake instead of with each other, and without built-in business logic you could end up with “an island full of people with huts that are all built differently.”
Bettermann says he would like to hear how that company fares, then returns to the question he always asks himself: “what problem are we trying to solve?” An ERP, he says, is also inflexible, upgrades take real time and effort, and he wonders how much of it is legacy carried for compliance. What procurement actually needs is a proper reflection of the source-to-contract process, category managers supported by the data they need, and a highly efficient back end for turning requisitions into purchase orders. “I would love a world where I don’t need to carry all that complicated backpack,” he says, before conceding it may be an illusion that never becomes real.
Start With the Problem, Not the Technology
Spencer says he loves starting with the problem and working backward, and uses the Segway to make the point. Everyone, venture capitalists included, thought it was the coolest technology around, until it arrived at $6,000 and the obvious question was what problem it solved. Start from the technology and you end up with the Segway; start from the problem, he says, and you might think of a scooter.
Bettermann has his own example, from his Ford heritage. Ford succeeded through mass production, he says, and nearly went bankrupt when Henry Ford insisted a customer could have any car as long as it was black, until competitors started offering colors. It is the same pattern, he argues, as the Segway giving way to someone else’s e-scooter, and as the ERP, and as what LightSource does: you probably needed an ERP in order to see where its gaps are and where to find your niche.
Why Bridgestone Won’t Build Its Own Software
Spencer raises a third option beyond monolith and best-of-breed: building in house. Companies like GM have built end-to-end internal systems with large IT teams, and now AI coding tools can produce a convincing prototype in about 15 minutes, though the last 20 percent, making it reliable and deployable, is the hard part. The bar, he notes, is getting lower.
Bettermann is not convinced. He grants there are good examples, but as a procurement person he believes in the ecosystem around him, partners and suppliers who specialize in the problem they solve. “My problem as Bridgestone is that I want to produce the best tire in the world and I want to offer that at the best value at the best price for my customer.” So why would he step away from “my core competency which is building a tire” and invest his knowledge in something outside his core responsibility? He would, he says, never put his stakes on it.
Why Standing Still Is Not an Option
The tug-of-war between legacy process and new technology comes next. Spencer notes that large customers often ask for configuration to match what they already do, rather than asking how a new approach could redraw the lines. Bettermann says he would always adjust processes when there is a need, and that need can come from a malfunction in the process, a customer demand, a change in the environment, or a change in technology. It is worth adjusting a process to apply technology that solves a problem better, he says, and it is a mistake to close the door on whatever is innovative today that was not two years ago.
He is candid about the constraint. Silicon Valley companies have more room to move at speed than big companies with a heritage, he says, and he sometimes looks “jealously” at companies like Spencer’s, “not that you are better or worse,” just without the heritage he proudly carries. Spencer, who offers “speed wins” as one of his company’s taglines, agrees that the more storied a company is, the more there is to lose, and asks how you reward people for bets with a 90 percent chance of failure and a 10 percent chance of becoming the lifeblood of the business. Bettermann is not sure he buys the founder-versus-executive framing. For him it is about taking responsibility: he wants people to act as if they were the CEO of their area, to deliver regular business and also keep thinking about innovation and process change, rather than only doing the job from 8 to 5. His shorthand: “Don’t stick to the black cars.”
How Bridgestone Measures the Value Procurement Creates
On incentives, Spencer asks why a salesperson earns a share of every sale while procurement does not earn a share of the savings it creates, and notes that value is not only cost out: it can also be cost containment, reliability in a market, speed to market, and early supplier involvement. That is why Bridgestone uses a value scorecard rather than a single KPI, Bettermann says. Cost reduction is the most famous measure and cost avoidance the second, joined by how many suppliers a person introduced to drive innovation, how well they reduce risk, and whether they secure the right payment terms with suppliers. People are incentivized on how they do against that set of KPIs, he explains, though not one to one as in sales, and the work is in setting the right frame for them.
Spencer then asks how you quantify something like risk reduction, where the point is an event you prevented. Bettermann’s answer is to foresee as much as possible of the risk that could hit your area of responsibility. Energy is his example: a very famous category these days, where a category manager who hears what is happening in the market might secure energy capacity for the following year. He says plainly that he is making the scenario up to illustrate the point. It ties back to his relevance test: an energy category manager has to understand what it means when the world goes crazy securing energy at a reasonable price for the company.
The Question Behind Every Answer
Whether the topic is career advice, ERP systems, or incentives, Bettermann’s answers come back to the same two questions: am I relevant in what I do, and what problem are we trying to solve? Relevance, in his telling, is not about owning the newest tool. It means knowing your category well enough to recognize when a technology or a process change makes you better, and building a team of people who feel responsible for acting on that. It also means not chasing a technology because it is impressive, and not staying with a process or system only because it is the one you inherited.
Spencer closes by saying he loves that Bettermann calls category managers famous, an elevation of the function that the industry should embrace, and that the conversation left him energized. Bettermann says it seems they could continue for another hour at least. Season 2 of Source Code opens with a conversation about what it takes for procurement to earn that status.

Guest: Lars Bettermann, Chief Procurement Officer at Bridgestone
Listen on Spotify | Listen on Apple Podcasts | Listen on Amazon Music
Lars Bettermann opens with an admission that might surprise anyone who now runs procurement for a tire maker: “I never imagined procurement to be such an interesting space when I was at college.” He studied economics, and procurement barely registered in the curriculum, which he calls “a big mistake” given the value and influence the function carries inside a company. Roughly three decades later, as Chief Procurement Officer at Bridgestone, he keeps returning to one test throughout this conversation with Spencer: are you relevant in the field you work in? Relevance means understanding the latest trends in your category, recognizing when a new technology makes you better at your job, and refusing to assume that the way things have always worked is the way they should keep working. “The moment you don’t innovate or the moment you don’t further develop you are dead,” he says. “So standing still is not an option.”
Bettermann is the Chief Procurement Officer at Bridgestone, where he owns the procurement teams in both North America and Europe. His career began about 30 years ago at Ford Motor Company through a trainee program, and he later spent more than a decade as a consultant at Accenture before moving to Bridgestone. In this episode, he and Spencer cover a lot of ground: what the path to CPO actually looks like, how tech-savvy a procurement leader needs to be, whether the ERP is on its way out, why Bridgestone would not build its own software, and how a tire maker measures the value procurement creates.
How a Ford Trainee Program Led to a Career in Procurement
Bettermann did not plan on procurement. He studied economics, liked the automotive industry, and wanted to see how vehicles get built, so he landed at Ford after college. The trainee program the company offered for people like him happened to be in procurement. “That’s how I ended up in procurement about 30 years ago,” he says, and he found it to be “the spot you want to be.”
Spencer’s opening question is a practical one: how does someone become a CPO, through excellent category management or through executive leadership experience? Bettermann’s answer has two layers. Early in a career, he says, it matters “to indeed get famous for something,” and that something is usually a category. His were a handful of categories at Ford, including fuel tanks and the fuel system. Consulting at Accenture then added a second skill on top of that depth: bringing people together, running projects, and moderating between different opinions. That, in his view, is the main ability a future CPO needs, because procurement puts suppliers, internal customers, and people like cost estimators at one table, and the leader is the moderator in the middle of that ecosystem.
Why Relevance Matters More Than Any Single Skill
Spencer asks how deep into the weeds a CPO needs to be on technology at a moment when AI is forcing teams to re-evaluate their processes and assumptions. Bettermann’s answer starts with the obvious: hardly any job in procurement today is not technology supported or technology enabled, so being tech-savvy “is not a choice anymore but a must.” Then he widens the frame. Success in procurement, he says, comes from being relevant in what you do. A marketing category manager cannot be relevant without understanding the latest trends in marketing and what is possible when sourcing agencies and merchandising material. “What I ask from my people is to be relevant in the field they are operating in.” Technology follows from that: once you know your field well enough to see that a tool is state of the art in it, adopting the tool and staying relevant go hand in hand.
Where Technology Should Go First
Spencer recalls a comment Bettermann made in an earlier podcast interview at DPW: a young person entering procurement today may not need to know how to turn a purchase requisition into a purchase order, because that process could be automated. Bettermann clarifies what he sees in younger colleagues. Someone who says they want to be in procurement, he imagines, is picturing negotiation, contracting, and sitting at a table with suppliers, not processing requisitions. The requisition-to-PO process is not more or less important, he says, but it does not draw the same interest, and it is not where you can add the most value as a person. That is why it is easier to become famous as a category manager. The same logic tells him where to apply technology: the areas that get less attention and offer the most room to be automated are where he would target a pilot.
He adds a compliment for Spencer’s company, noting that LightSource is one of the few tackling the front office, working with category managers, while the back end of the process already has many competitors. Spencer says part of that was circumstance, since he focused on what he understood when he started the company, but the hypothesis held up. He never expected to compete with ERP, and nearly every customer, he notes, is in some stage of a perennial ERP transformation.
Why Procurement Is Where the Value Shows Up
Spencer explains why he built a company around procurement’s earliest stages. At Tesla, where the team built its own ERP, he came to feel that “all of that battle is won or lost by the time you create a purchase order.” He points to a 50-cent negotiation on a single component in the Model 3 as the kind of small win that moves a business’s financial results, and says it felt like putting on glasses: procurement was the most important team in the business, yet it ran on spreadsheets and emails until the transaction. That pulled him toward the upstream relationship between suppliers, engineering, and procurement, the “three-legged stool,” rather than tail spend.
Bettermann agrees that the beauty of procurement is that you can immediately see the impact of what you do. A saving on a large spend line lands directly on the P&L, something HR, Spencer’s comparison, does not get in the same way. Then the question becomes what you do with that power, and there, he says, technology should help build better cases, better value, and better numbers.
Is the ERP Really Dead?
Bettermann does not hide his view: he thinks ERP systems are “kind of dead.” His reasoning is that an ERP is a mainframe trying to serve every side of a company’s operations, whereas he sees the field moving toward targeted, off-the-shelf solutions for different processes.
Spencer pushes back with how most companies see it. For many, the ERP is the bedrock system of record, the digital twin of the business, and when it conflicts with anything else, even the people, the ERP wins. Bettermann’s answer is that there should still be a source of truth, whether you call it the ERP or a base system, holding things like material codes and supplier master data. He pictures “an island somewhere where you can then connect different boats going to the island”: procurement sails over, collects the data it needs, and works in a lighter system. Spencer presses on the risk. One medical device customer, he says, has its platforms integrate with a data lake instead of with each other, and without built-in business logic you could end up with “an island full of people with huts that are all built differently.”
Bettermann says he would like to hear how that company fares, then returns to the question he always asks himself: “what problem are we trying to solve?” An ERP, he says, is also inflexible, upgrades take real time and effort, and he wonders how much of it is legacy carried for compliance. What procurement actually needs is a proper reflection of the source-to-contract process, category managers supported by the data they need, and a highly efficient back end for turning requisitions into purchase orders. “I would love a world where I don’t need to carry all that complicated backpack,” he says, before conceding it may be an illusion that never becomes real.
Start With the Problem, Not the Technology
Spencer says he loves starting with the problem and working backward, and uses the Segway to make the point. Everyone, venture capitalists included, thought it was the coolest technology around, until it arrived at $6,000 and the obvious question was what problem it solved. Start from the technology and you end up with the Segway; start from the problem, he says, and you might think of a scooter.
Bettermann has his own example, from his Ford heritage. Ford succeeded through mass production, he says, and nearly went bankrupt when Henry Ford insisted a customer could have any car as long as it was black, until competitors started offering colors. It is the same pattern, he argues, as the Segway giving way to someone else’s e-scooter, and as the ERP, and as what LightSource does: you probably needed an ERP in order to see where its gaps are and where to find your niche.
Why Bridgestone Won’t Build Its Own Software
Spencer raises a third option beyond monolith and best-of-breed: building in house. Companies like GM have built end-to-end internal systems with large IT teams, and now AI coding tools can produce a convincing prototype in about 15 minutes, though the last 20 percent, making it reliable and deployable, is the hard part. The bar, he notes, is getting lower.
Bettermann is not convinced. He grants there are good examples, but as a procurement person he believes in the ecosystem around him, partners and suppliers who specialize in the problem they solve. “My problem as Bridgestone is that I want to produce the best tire in the world and I want to offer that at the best value at the best price for my customer.” So why would he step away from “my core competency which is building a tire” and invest his knowledge in something outside his core responsibility? He would, he says, never put his stakes on it.
Why Standing Still Is Not an Option
The tug-of-war between legacy process and new technology comes next. Spencer notes that large customers often ask for configuration to match what they already do, rather than asking how a new approach could redraw the lines. Bettermann says he would always adjust processes when there is a need, and that need can come from a malfunction in the process, a customer demand, a change in the environment, or a change in technology. It is worth adjusting a process to apply technology that solves a problem better, he says, and it is a mistake to close the door on whatever is innovative today that was not two years ago.
He is candid about the constraint. Silicon Valley companies have more room to move at speed than big companies with a heritage, he says, and he sometimes looks “jealously” at companies like Spencer’s, “not that you are better or worse,” just without the heritage he proudly carries. Spencer, who offers “speed wins” as one of his company’s taglines, agrees that the more storied a company is, the more there is to lose, and asks how you reward people for bets with a 90 percent chance of failure and a 10 percent chance of becoming the lifeblood of the business. Bettermann is not sure he buys the founder-versus-executive framing. For him it is about taking responsibility: he wants people to act as if they were the CEO of their area, to deliver regular business and also keep thinking about innovation and process change, rather than only doing the job from 8 to 5. His shorthand: “Don’t stick to the black cars.”
How Bridgestone Measures the Value Procurement Creates
On incentives, Spencer asks why a salesperson earns a share of every sale while procurement does not earn a share of the savings it creates, and notes that value is not only cost out: it can also be cost containment, reliability in a market, speed to market, and early supplier involvement. That is why Bridgestone uses a value scorecard rather than a single KPI, Bettermann says. Cost reduction is the most famous measure and cost avoidance the second, joined by how many suppliers a person introduced to drive innovation, how well they reduce risk, and whether they secure the right payment terms with suppliers. People are incentivized on how they do against that set of KPIs, he explains, though not one to one as in sales, and the work is in setting the right frame for them.
Spencer then asks how you quantify something like risk reduction, where the point is an event you prevented. Bettermann’s answer is to foresee as much as possible of the risk that could hit your area of responsibility. Energy is his example: a very famous category these days, where a category manager who hears what is happening in the market might secure energy capacity for the following year. He says plainly that he is making the scenario up to illustrate the point. It ties back to his relevance test: an energy category manager has to understand what it means when the world goes crazy securing energy at a reasonable price for the company.
The Question Behind Every Answer
Whether the topic is career advice, ERP systems, or incentives, Bettermann’s answers come back to the same two questions: am I relevant in what I do, and what problem are we trying to solve? Relevance, in his telling, is not about owning the newest tool. It means knowing your category well enough to recognize when a technology or a process change makes you better, and building a team of people who feel responsible for acting on that. It also means not chasing a technology because it is impressive, and not staying with a process or system only because it is the one you inherited.
Spencer closes by saying he loves that Bettermann calls category managers famous, an elevation of the function that the industry should embrace, and that the conversation left him energized. Bettermann says it seems they could continue for another hour at least. Season 2 of Source Code opens with a conversation about what it takes for procurement to earn that status.
Faster sourcing,
lower cost, less chaos.
See how LightSource connects engineering, procurement, and suppliers in one operating system to help you launch faster at lower cost.
DPW Award Winner
SOC 2
Hackett Group 2026 Validated
Kearney #1
Gartner Cool Vendor
Procuretech 100
G2 Top Rated
Faster sourcing,
lower cost, less chaos.
See how LightSource connects engineering, procurement, and suppliers in one operating system to help you launch faster at lower cost.
DPW Award Winner
SOC 2
Hackett Group 2026 Validated
Kearney #1
Gartner Cool Vendor
Procuretech 100
G2 Top Rated
Faster sourcing,
lower cost, less chaos.
See how LightSource connects engineering, procurement, and suppliers in one operating system to help you launch faster at lower cost.
DPW Award Winner
SOC 2
Hackett Group 2026 Validated
Kearney #1
Gartner Cool Vendor
Procuretech 100
G2 Top Rated
Trusted by:
Trusted by:
Trusted by:




