Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

BrightDrop chose SAP S/4HANA Cloud’s public cloud edition while it was still hiring staff and defining how its business would work. Rather than wait for a complete process map, its small IT team developed business capabilities and configured the ERP in parallel, prioritizing speed and standard product features. This is a case study of the approach reported in December 2022—not a claim about BrightDrop’s current ERP status.

Why BrightDrop needed an ERP early

General Motors launched BrightDrop in January 2021 as a business focused on electric first-to-last-mile delivery and logistics products, software, and services. ( GM’s launch announcement.) As the fledgling company began talking with suppliers and manufacturers, staff were handling initial procurement work with Excel and Word.

When Namo Tiwari became BrightDrop’s CIO in 2021, the company wanted a more durable system before improvised processes became more difficult to migrate. Its requirements extended beyond purchasing transactions: it wanted supplier onboarding, invoice processing, purchase orders, supply-chain demand planning, and financial forecasting.

Why the implementation ran alongside business development

The conventional sequence is to map business processes first and implement software afterward. BrightDrop could not rely on that order: the people who would ordinarily define established workflows were still being hired while the ERP project was underway. The company therefore had to develop its business processes and configure its system concurrently.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

That choice made agility and speed central selection criteria. Tiwari told CIO, “Agility and speed is most important for us.” He also described the aim of leaning on standard product capabilities: “We were looking for something where we could leverage 90% or maybe 100% of out-of-box capability because we were just building the business processes.” ( CIO’s December 6, 2022 case study.)

Using standard capabilities suited a company whose processes were still taking shape: it could configure around the product rather than first design a mature, highly customized operating model. The report describes this as the intended approach; it does not establish a particular implementation schedule, budget, return on investment, or operational result.

Why BrightDrop chose SAP S/4HANA Cloud public edition

BrightDrop selected SAP S/4HANA Cloud, specifically the public cloud edition, rather than simply adopting GM’s existing ERP setup. The choice aligned with two reported priorities: rely heavily on out-of-the-box capabilities and avoid managing server infrastructure with a small IT team. Tiwari summed up the infrastructure rationale this way: “I changed the whole dynamic here by going with the fully cloud solution.”

The intended scope spanned everyday purchasing needs and broader planning work. Supplier onboarding, invoices, and purchase orders addressed transactions with suppliers; demand planning and financial forecasting addressed the need to plan the emerging operation. The source does not provide a technical configuration map or describe which individual features were deployed.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What the case says about team capacity

CIO reported that, at the time of its December 2022 article, an IT team equivalent to 19 full-time staff served almost 300 BrightDrop employees. Those figures help explain the appeal of limiting infrastructure responsibilities, but they are dated case-study context, not current staffing numbers.

The account shows the trade-off in building an ERP while the business is forming: the team could not wait for every process owner and workflow to be settled, so it aimed to make implementation and business development inform each other. The available account does not establish how completely that approach succeeded or what the system’s later status became.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

BrightDrop’s later corporate and production timeline

BrightDrop’s organizational context changed after the ERP case study. On November 16, 2023, GM announced that BrightDrop had become part of GM: Zevo vans remained in GM Envolve’s commercial fleet offerings, while BrightDrop Core moved into GM’s software and services organization. ( GM’s integration announcement.)

On October 21, 2025, GM Canada said BrightDrop van production had ended and would not move to another site; production had been suspended since May 2025. ( GM Canada’s announcement.) These later developments clarify the company’s history, but do not establish the current status of its SAP deployment.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.