LightSource vs. Excel and email
Excel and email are the default sourcing stack: a grid everyone knows, an inbox every supplier answers, and shared folders holding the drawings. LightSource is the Direct Materials Operating System, spec through scale, PLM through ERP, built to be the system of record those tools were never designed to be.

Where each system actually works
Keep PLM for product definition and ERP for transactions. LightSource connects the direct-material decisions between them, from spec through scale.
At a glance

Capability comparison, in detail
Twenty capabilities in six groups. The LightSource column is identical on all six comparison pages, including the ones we don’t win.

Where Excel and email are genuinely the right tool
Nobody chose Excel and email for sourcing; the stack was already there. Roughly 750 million people use Excel, per Microsoft CEO Satya Nadella in 2017, and third-party estimates run above a billion. Every PLM and ERP exports to it, every cost engineer models in it, and every supplier on earth can open a bid sheet with no account and no training. Trade-press surveys put spreadsheet reliance among supply chain professionals at 65 to 80%, and two-thirds of companies say they consider Excel a supply chain system.
The strengths are real. A blank grid offers total modeling freedom: any bid sheet, any cost breakdown, any should-cost structure, with no vendor roadmap in the way. The marginal software cost is near zero, since Excel ships inside the Microsoft 365 subscription most manufacturers already own. Implementation is zero; it is already on every laptop, and it works offline in a plant with no Wi-Fi. The grid also keeps improving: Copilot Agent Mode, generally available on Excel for the web in December 2025 and on Windows desktop in January 2026, builds formulas, tables, and PivotTables from natural language, though it requires a paid Copilot license and it operates on cells rather than on parts, quotes, or suppliers.
When The Wall Street Journal reported in 2017 that finance chiefs were telling their teams to stop using Excel, the backlash was loud enough to earn its own follow-up coverage. That attachment is earned. For a team sourcing a small number of parts a year, Excel and email is arguably the correct tool.
Where LightSource wins
The wins are structural, and they compound with part count, supplier count, and time.
Parts instead of rows. LightSource keeps a revision-managed item master: nested BOMs, snapshots, diffs, and cost roll-ups. AI ingestion builds it from the Excel files, PDFs, and drawings a team already has, so parts stop being rows retyped into each new bid sheet.
RFQs that carry revision integrity. Drawings attach to the part, not to a ZIP on an email, so suppliers quote against the current revision and the record shows who quoted what, on which revision, and when.
Flexible cost breakdowns without hand-merging. In our evaluations, LightSource is the only sourcing solution with true flexible cost breakdowns: category-specific bid sheets per event, with a drag-and-drop editor and a formula editor that keep the modeling freedom buyers built in Excel. AI then normalizes every returned quote into one comparable structure, so nobody hand-merges eight differently mangled attachments.
Price history that belongs to the company. Awards become tracked contracts with per-part, per-supplier price history and cost walks. US median employee tenure is 3.9 years per the Bureau of Labor Statistics; when a buyer leaves, the record stays.
A network instead of an address book. 20,000 suppliers are live on the network, with AI capability-based discovery, and suppliers use it free.
A small implementation gap. The status quo's one structural advantage is zero rollout, and against LightSource that advantage is narrower than against any suite: live in days on flat files, sourcing in about 30 days, implementation included. Manufacturers including BRP, Canada Goose, HelloFresh, and Shure run direct materials sourcing on LightSource today; Gartner named it a Cool Vendor in 2025, and it carries venture backing co-led by Lightspeed and Bain Capital Ventures ($33M).
The structural case: why files, inboxes, and memory fail at scale
The status quo has four components: the grid, the inbox, the shared drive, and the buyer's memory. The fourth is the actual system of record for supplier history and past pricing, and it is the component that walks out the door.
Spreadsheet error rates are a documented research field. Raymond Panko of the University of Hawaii, surveying 85 intensive inspection studies of operational spreadsheets, found that 94% contained errors, with cell error rates of 1 to 5% on nontrivial work and average error-detection rates in inspection experiments of only about 60%. His framing is careful: "spreadsheet programs are not error-prone. People are error prone." Panko's point is about process, not software: a chain of hand-copied files gives human error nowhere to get caught, which is exactly why shared records and audit trails exist.
Most famous spreadsheet failures come from finance, academia, and public health rather than sourcing departments, and they should be read as general spreadsheet-risk evidence. One, though, is squarely a sourcing story: in 2003, TransAlta lost $24 million, about 10% of annual profit, when a cut-and-paste misalignment in a bid-submission spreadsheet attached bids to the wrong contracts. And Public Health England's 2020 loss of 15,841 COVID case records, silently truncated by a legacy .xls row limit, shows the failure mode at scale: the pipeline produced no error message, just missing rows.
Email adds its own measured cost. McKinsey Global Institute found interaction workers spend 28% of the workweek managing email and roughly 19% more hunting for internal information, and email is the medium that carries the entire quote cycle. McKinsey separately reports that companies expect digital procurement to cut time spent on transactional sourcing by 30 to 50%, and The Hackett Group's 2023 study put e-sourcing adoption at about 74% of organizations, which means roughly a quarter of large enterprises still run sourcing with no tool at all.
Running both: keep Excel, move the system of record
This is not a dual-run architecture; Excel is the starting point, not a companion system. What actually happens is migration without abandonment.
LightSource ingests the spreadsheets a team already has: drop an Excel file, PDF, or drawing and items are created or updated automatically, with flat-BOM templates for bulk loads, so clean data is not a precondition for starting. Suppliers keep quoting exactly the way they do today through Excel round-trip: download the bid sheet, fill it offline, upload it back. Every grid, bid sheet, and analysis exports back to Excel for whatever modeling comes next.
Excel does not disappear. Cost engineers will keep building cleansheets and one-off models in it, and they should. It goes back to being what it is great at, ad hoc analysis and scratchpad modeling, and it stops being the system of record for parts, quotes, and supplier history.
What public reviewers say
LightSource holds 4.9/5 on G2 across roughly 11 reviews; there is no G2 category for the status quo, so the closest proxy is Microsoft Excel itself, at 4.7/5 across more than 3,100 reviews. The caveat cuts both ways: the review bases differ by two orders of magnitude, and Excel's reviewers are rating a spreadsheet, not a sourcing system.
Excel's reviews are admiring. A G2 reviewer, a CTO (Mid-Market, 2026), writes: "What I like best about Microsoft Excel is its power and flexibility for complex data analysis. It offers advanced formulas, pivot tables, and strong performance when working with large datasets." The same review lists the cost of that flexibility: "Collaboration in Microsoft Excel can be limited and often leads to version conflicts when multiple people edit files ... Managing large shared files can also become messy and hard to track." Another G2 reviewer, an IT recruiter (Mid-Market, 2026), names the risk the error research documents, calling the grid "prone to human error," where "a small mistake in a formula, wrong cell reference, or accidental overwrite can impact the entire sheet."
On the LightSource side, a G2 reviewer, a VP of Supply Chain (Mid-Market, 2024), writes: "Having the cost and quoting information in a single location helps with rapid product launches and better visibility for our leadership group. It's got its quirks, but the constant updates are promising." And a G2 reviewer (Mid-Market, 2024) who deployed it across multiple portfolio companies makes the turnover point directly: "All the RFPs are centrally located, so no loss of data when a SM leaves the organization."
In verified enterprise reviews of sourcing tools generally, spreadsheets appear most often as the before state: the manual bid comparisons and scattered quote files reviewers describe being glad to leave behind.
When to choose what
Choose Excel and email if
You source a small number of parts a year and buys are one-off; the overhead of any system would exceed the payoff.
Budget is zero and there is no appetite for a software purchase; Excel ships with the Microsoft 365 you already own.
You need total modeling freedom for ad hoc analysis: any bid sheet, any cleansheet, no vendor roadmap in the way.
Universal supplier acceptance matters more than structure; every supplier can quote by Excel and email today, with no account and no training.
You need something with nothing to implement, ever, that works offline, on a plane, or in a plant with no Wi-Fi.
Choose LightSource if
Your part count, supplier count, or event cadence has outgrown hand-merged bid sheets and version-numbered filenames.
You need to prove which drawing revision a supplier quoted, with an audit trail of who changed what and when.
Quote and price history should belong to the company, not to a buyer's inbox; US median employee tenure is 3.9 years per BLS.
You want to keep Excel-grade bid-sheet flexibility but have AI normalize every returned quote into one comparable structure.
You want supplier discovery beyond the address book: 20,000 suppliers live on the network, free for suppliers to join.
RUNNING BOTH
Every LightSource customer starts exactly where you are, so the realistic plan is both, with the roles redrawn. LightSource ingests your existing spreadsheets, PDFs, and drawings into a revision-managed item master, suppliers keep quoting through familiar Excel round-trip files, and every analysis exports back to Excel. The spreadsheet stays for what it is great at, ad hoc modeling and cleansheet scratch work, while the parts, quotes, awards, and supplier history move into a system of record that survives turnover. The switch structures your spreadsheets; it does not abandon them.
Frequently asked questions
Is Excel good enough for direct materials sourcing?
At small scale, yes. For a team sourcing a handful of parts a year with one-off buys, Excel plus email is arguably the correct tool: effectively free, universally known, and accepted by every supplier. The limits are structural and compound with part count, supplier count, and time: no item master, no shared quote history, and no revision control.
What is the difference between LightSource and Excel for sourcing?
The unit of work. Excel treats sourcing as files: bid sheets, email threads, and folders that restart from zero each event. LightSource is the Direct Materials Operating System, where the unit of work is a revision-managed part carrying its drawings, quotes, price history, and awards, so history compounds instead of disappearing into inboxes.
Do suppliers have to stop using Excel if we adopt LightSource?
No. LightSource is free for suppliers, onboarding takes under 30 minutes, and quoting supports Excel round-trip: suppliers download a bid sheet, fill it offline, and upload it back. Returned quotes land in one comparable structure instead of eight differently formatted attachments.
How error-prone are spreadsheets really?
In research compiled by Raymond Panko, 94% of 85 intensively audited operational spreadsheets contained errors, with cell error rates of 1 to 5% on nontrivial work; his framing is that people, not spreadsheet programs, are error prone. No software eliminates human error. A system of record adds the shared structure, single quote format, and audit trail that make errors easier to catch.
How long does it take to move from Excel and email to LightSource?
Teams go live in days on flat files and run sourcing in about 30 days, with implementation included. AI ingestion structures the spreadsheets, PDFs, and drawings you already have, so clean data is not a precondition for starting.
What does running sourcing on Excel and email actually cost?
The software is effectively free, since Excel ships with Microsoft 365 subscriptions most manufacturers already own; Copilot's agent features require a paid per-user license. The real costs are labor and error exposure: McKinsey Global Institute found interaction workers spend 28% of the workweek on email, and without shared price history every sourcing event restarts from zero.
Sources
Panko, What We Don't Know About Spreadsheet Errors Today (EuSpRIG 2015)
The Register: TransAlta's $24M bid-submission spreadsheet error (2003)
The Register: Public Health England's .xls row-limit data loss (2020)
McKinsey Global Institute: The social economy (28% of the workweek on email)
McKinsey: Driving superior value through digital procurement
The Hackett Group: procurement technology adoption (2023 Key Issues)
Supply Chain Dive: two-thirds of companies consider Excel a supply chain system
Microsoft: Agent Mode in Excel generally available (Dec 2025)
WSJ: Stop Using Excel, Finance Chiefs Tell Staffs (Nov 2017, summary)
CNBC: LightSource raises $33M co-led by Lightspeed and Bain Capital Ventures
This comparison is based on publicly available information as of September 2026 and our understanding of both products. Products evolve; if you spot something out of date, tell us and we will fix it.
All product names and trademarks are the property of their respective owners and are used for identification only.
See your cost model in LightSource
Bring a representative bid sheet. See how an event-specific breakdown is structured, then walk through the PLM-to-ERP handoff.