LightSource vs. Arkestro

Arkestro is a predictive procurement platform: it compresses multi-round sourcing events by generating AI-suggested prices before suppliers bid, and runs alongside suites like Coupa and SAP Ariba. LightSource is the Direct Materials Operating System: the system of record for parts, BOMs, RFQs, and awards, from spec through scale, PLM through ERP.

Last reviewed

· Based on public information ·

The short version
LightSourceLightSource is the AI-native Direct Materials Operating System, spec through scale, PLM through ERP: revision-managed parts and BOMs, part-level RFQs with flexible cost breakdowns, AI quote analysis, and awards that become tracked price history. Teams are live in days, and suppliers use it free.
ArkestroArkestro is a predictive procurement platform: it compresses multi-round sourcing events by generating AI-suggested prices before suppliers bid, and runs alongside suites like Coupa and SAP Ariba.
Architecture
LightSourceAI-native direct materials operating system, built around the part record
ArkestroPredictive pricing layer that runs alongside Coupa, SAP Ariba, and the ERP
Implementation
LightSourceLive in days on flat files; sourcing in about 30 days; implementation included
ArkestroEnterprise rollout; Arkestro cites results in as little as two months
Pricing model
LightSourcePlatform plus seats; implementation included; always free for suppliers
ArkestroNot published; Capterra's third-party listing shows a $500 per month starting point
Supplier network
LightSource20,000 suppliers live; free supplier workspace; AI discovery
ArkestroYour incumbent supplier list; suppliers respond to suggested prices inside events
Highlighted cells mark where the two differ most in practice, based on our evaluations and public documentation.

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.

System fitthe part lifecycle · PLM through ERPPLMspecs · CADrevisionsERPPOs · MRPpaymentsSpecSourceSupplyScaledirect materials operating systemcosted BOMRFQ · CBDawardssupply readinessthe procurement process · intake through payIntakeSource-to-contractPay (P2P)LightSource · S2C for direct materialsthe event window · opens and closesArkestrocollect bids · solve · exportsourcing optimization
System fitthe part lifecycle · PLM through ERPPLMspecs · CAD · revisionsdirect materials operating systemSpecSourceSupplyScalecosted BOMRFQ · CBDawardssupply readinessERPPOs · MRP · paymentsthe procurement process · intake through payIntakeS2CPayLightSource · S2C · direct materialsthe event windowcollect bids · solve · exportsourcing optimization
Arkestro operates inside source-to-contract: the event window opens at bid collection and closes at award. The part lifecycle before and after the event stays outside it; LightSource runs it end to end, PLM through ERP.
Footprints show each product's operating center of gravity, not every marketed feature.

At a glance

Built for
LightSourceDirect materials, spec through scale: parts, BOMs, NPI programs
ArkestroPredictive sourcing events across category spend
Core question
LightSourceWho should make this part, and at what price?
ArkestroWhat price should this event open at before suppliers bid?
Architecture
LightSourceAI-native direct materials operating system, built around the part record
ArkestroPredictive pricing layer that runs alongside Coupa, SAP Ariba, and the ERP
Implementation
LightSourceLive in days on flat files; sourcing in about 30 days; implementation included
ArkestroEnterprise rollout; Arkestro cites results in as little as two months
Pricing model
LightSourcePlatform plus seats; implementation included; always free for suppliers
ArkestroNot published; Capterra's third-party listing shows a $500 per month starting point
Supplier network
LightSource20,000 suppliers live; free supplier workspace; AI discovery
ArkestroYour incumbent supplier list; suppliers respond to suggested prices inside events
Target customer
LightSourceManufacturers from growth stage to enterprise divisions
ArkestroEnterprise procurement teams; most G2 reviewers are mid-market

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.

StrongModerateLimitedNot offeredNot documented
Product data
Parts & BOM ingestion
LightSourceStrong
AI ingestion from Excel, PDFs, and drawings into a revision-managed item master
ArkestroNot documented
Marketed: items enter events as line items with auto data sync; no public evidence of drawing, spec, or item-master ingestion
BOM & revision management
LightSourceStrong
Nested BOMs with revisions, snapshots, diffs, and cost roll-ups
ArkestroNot documented
Marketed: none; BOMs, revisions, and drawings do not appear anywhere in Arkestro's public materials
PLM/ERP integration
LightSourceStrong
PLM in, ERP out: GraphQL API mirrors the whole platform; flat-file start in days
ArkestroModerate
Configured: marketed coexistence with Coupa and SAP Ariba plus an Infor Marketplace listing; no PLM integration appears publicly
Sourcing
RFQ/RFX events
LightSourceStrong
Part-level RFQs with drawings, from 3-bids-and-a-buy to multi-round strategic events
ArkestroStrong
Native: multi-round events with AI-suggested prices and live ranking feedback; this is the core of the product
Quote analysis
LightSourceStrong
Flexible cost breakdowns (CBD): category-specific bid sheets; AI normalizes any quote
ArkestroModerate
Native: bid ranking, predicted anchors, and supplier error detection; no structured cost-breakdown quoting shown in public materials
Award scenarios & price history
LightSourceStrong
AI-drafted award scenarios, split awards, approvals; awards become tracked contracts
ArkestroModerate
Native: event-level awarding shown in case studies; award-modeling simulations are marketed; no per-part price history appears publicly
Should-cost
LightSourceModerate
Should-cost as first-class item data (third-party or your own); no native cleansheet studio
ArkestroModerate
Native: predicted anchor prices from historical quote and market data; statistical anchors rather than cost-structure models
Suppliers
Supplier network & discovery
LightSourceStrong
20,000 suppliers live; AI capability-based discovery
ArkestroLimited
Runs events with the customer's incumbent supplier list; supplier recommendations are marketed, no public supplier network
Supplier experience
LightSourceStrong
Free for suppliers; onboarding in under 30 minutes; Excel round-trip quoting
ArkestroModerate
Suppliers accept or counter suggested prices with live ranking feedback; a G2 reviewer noted the model took some getting used to for their suppliers
Supplier management (SRM)
LightSourceStrong
Scorecards, data rooms with AI document analysis, certification collection
ArkestroNot documented
No scorecards, data rooms, or supplier lifecycle tooling in public materials; supplier interaction centers on events
Intelligence
AI-native architecture
LightSourceStrong
AI embedded through the workflow: ingestion, event setup, bid analysis, awards
ArkestroStrong
ML-first since its 2017 Bid Ops origins; predictive pricing is the core mechanic, extended by Arkestro Labs and Intelligence
Tariff/HTS support
LightSourceModerate
AI-suggested HTS codes on the item master; no tariff scenario engine
ArkestroNot documented
No HTS classification or tariff capability appears in Arkestro's public materials
Spend analytics
LightSourceLimited
Sourcing-scoped analytics and savings tracking, not company-wide spend cubes
ArkestroLimited
Savings and cycle-time reporting around events; record-keeping and spend analytics stay in the surrounding suite
Process coverage
Procure-to-pay
LightSourceNot offered
No requisitions, POs, or invoicing; awarded pricing exports to your ERP/P2P
ArkestroNot offered
Native: none; Arkestro positions itself as a layer that works with Coupa and SAP Ariba rather than replacing them
Contract management
LightSourceLimited
Award and price record with expiry tracking; no authoring or redlining
ArkestroNot documented
Marketed: none; no contract authoring, repository, or lifecycle features appear in public materials
Intake & orchestration
LightSourceNot offered
No requester front door; work starts at the sourcing project
ArkestroNot documented
Marketed: no requester front door; the Opportunities co-pilot (in beta) recommends line-item sourcing actions
Fit & deployment
Direct-materials focus
LightSourceStrong
Built entirely around parts: revisions, drawings, BOMs, tooling costs
ArkestroModerate
Direct spend is in scope (Nissan Americas, A and B parts case studies), but parts are event line items, not managed objects
NPI support
LightSourceStrong
Engineering collaboration, revision-aware RFQs, fast first quotes
ArkestroNot documented
No engineering collaboration, revision, or NPI workflow appears publicly; new items get statistical baseline prices
Implementation & time-to-value
LightSourceStrong
Live in days on flat files; sourcing in about 30 days; implementation included
ArkestroModerate
Arkestro cites results in as little as two months; Capgemini and BDO partnerships support enterprise rollouts
Mid-market accessibility
LightSourceStrong
Lean teams run it self-serve; enterprise controls available, not required
ArkestroModerate
Most G2 reviewers are mid-market and call it straightforward after training; positioning and sales motion are enterprise
Notes use three words deliberately: "Native" works day one, "Configured" arrives through an implementation project, and "Marketed" appears on the vendor's site with day-one delivery undocumented. "Not documented" means the vendor does not publicly document this capability as of Sep 22, 2026; it may exist, and we note the gap rather than guess. Ratings reflect public documentation as of Sep 22, 2026.

Where Arkestro is strong

Arkestro, founded in 2017 as Bid Ops and rebranded in 2022, runs multi-round competitive sourcing events in which the buyer's side moves first: the platform generates a predicted price from historical quote and market data, and suppliers accept or counter it with live ranking feedback. That mechanic is differentiated, and it is well evidenced on high-volume, history-rich categories such as MRO, services, packaging, and commodity buys. Arkestro's own case studies document an automotive company capturing $1.4M in recognized savings across MRO and A and B parts, and a three-round, four-supplier tape event covering 15 line items.

The commercial base is real enterprise scale. Chevron, Nissan Americas, Valvoline, Koch Industries, JLL, and GAF appear as named customers, and Nissan uses the platform across both direct and indirect spend in North America. Arkestro raised a $36M strategic investment in May 2025 led by Altira Group and Aramco Ventures, reports that customer spend through the platform tripled year over year in 2026, and says it has quoted more than 400,000 items and processed $410B in spend. Its homepage claims 18.8% average savings and 60% faster cycle times; treat those as vendor figures rather than audited results, though the customer list itself is public.

Arkestro also positions itself carefully. It markets coexistence with Coupa and SAP Ariba rather than replacement, and it has Capgemini and BDO partnerships for enterprise rollout. If the goal is compressing negotiation cycles across a broad category estate without changing systems of record, this is Arkestro's home ground.

Where LightSource wins for direct materials

LightSource's object model is the part itself. AI ingestion builds a revision-managed item master from Excel files, PDFs, and drawings; BOMs nest with snapshots, diffs, and cost roll-ups; RFQs go out at the part level with drawings attached. Quotes come back as structured cost breakdowns rather than totals: as of September 2026, LightSource is the only sourcing solution with true flexible cost breakdowns, meaning category-specific bid sheets per event, and AI normalizes quotes in any format into comparable data. Awards become tracked contracts with per-part, per-supplier price history that survives buyer turnover.

The two pricing philosophies diverge exactly where history is thin. Arkestro's anchors are statistical, built from bid and market history, and they are strongest where that history is rich. An engineered component at new-product introduction has little or no history; its price forms from drawings, tolerances, tooling, and cost structure. LightSource treats should-cost as first-class item data, and engineering works inside the same system: item edits in active projects create revisions, and buyers re-issue the RFQ against the new revision with a full record of who quoted what on which revision.

The supplier side is a network rather than a list. 20,000 suppliers are live on LightSource, the platform is free for suppliers, onboarding takes under 30 minutes, and AI discovery searches by capability. The adoption math is also different: live in days on flat files, sourcing in about 30 days, implementation included. Customers include BRP, Canada Goose, HelloFresh, Shure, Serta Simmons Bedding, Yum! Brands, Infinite Machine, and Arxada. LightSource was named a Gartner Cool Vendor 2025 and carries venture backing co-led by Lightspeed and Bain Capital Ventures ($33M).

The structural difference: pricing events versus managing parts

Arkestro's own materials position it as working with systems such as Coupa and SAP Ariba rather than replacing them. Record-keeping stays in the suite and the ERP, and Arkestro adds a predictive pricing layer over the events that run through them. LightSource sits differently in the stack. It is the Direct Materials Operating System, the record itself: parts in from PLM or spreadsheets, awarded pricing out to the ERP, and everything about the part in between.

The claimed-versus-practice reading matters here. Arkestro's marketing names Smart Baselining, Supplier Recommendations, and Dynamic Award Modeling. We could not find an item master, BOM structures, revisions, drawings, spec packs, cost-breakdown quoting, or engineering collaboration anywhere in its public materials: the site, the product pages, the case-study PDFs, or the press releases. Arkestro can still run events on parts, and Nissan uses it across direct and indirect spend today. In the public record, though, parts live inside Arkestro as line items in an event, so the durable record of what the part is, which revision was quoted, and what it should cost has to live somewhere else. For engineered direct materials, maintaining that record is most of the work.

Running both: Arkestro on category events, LightSource on engineered parts

Arkestro is a sourcing-stage neighbor, so the coexistence story is narrower here than with intake or P2P tools, but it exists and it splits cleanly by spend type. A large manufacturer can run Arkestro as the negotiation-compression layer over indirect, MRO, and commodity categories inside its Coupa or SAP Ariba estate, exactly where Arkestro's predictive anchors and case-study evidence are strongest. LightSource is where the engineered parts live: items, BOMs, revisions, drawings, cost-breakdown quotes, awards, and per-part price history from NPI through production resourcing.

Both can feed the same downstream systems. LightSource exports awarded pricing to the ERP through its GraphQL API or flat files, so awards made in either tool end up in the same purchasing backbone. Where an Arkestro event would touch engineered direct materials, the evaluation question is depth: a line-item price event or a part-lifecycle record. Place your actual spend mix against that question and the split usually follows from it.

What public reviewers say

On G2, Arkestro holds 5.0 out of 5 across 11 reviews and LightSource holds 4.9 out of 5 across roughly 11 reviews. Both review bases are small and the same order of magnitude, so read individual reviews as anecdotes rather than statistics.

The positive Arkestro theme is consistent: the product is approachable once teams are trained. A G2 reviewer (Mid-Market, 2023) wrote: "The product is straightforward to use by our internal teams. Once trained, they can use the tool without support from Procurement." The thoughtful caveats concern category fit and the supplier side. The same reviewer noted: "Arkestro works very well for a lot of spend categories; however, in some areas, such as Marketing services, we haven't yet been able to demonstrate the value of the tool." And a G2 reviewer (Mid-Market, Electrical/Electronic Manufacturing, 2021) from the platform's Bid Ops era wrote: "Bid Ops was not a perfect fit at first with the way we do things, and it took some getting used to from our suppliers." That reviewer went on to credit the Bid Ops team for responsiveness in adjusting the tool to their needs. Worth knowing: Arkestro's G2 reviews date from 2021 to 2023, so they describe earlier versions of the product. Among verified reviewers on enterprise review platforms beyond G2, sentiment on Arkestro is more mixed than its perfect G2 score, with a wider spread of middling ratings in a small pool.

On the LightSource side, a G2 reviewer (Mid-Market, VP of Supply Chain, 2024) wrote: "Having the cost and quoting information in a single location helps with rapid product launches and better visibility for our leadership group." Another G2 reviewer (Mid-Market, 2024) was candid about the supplier-side start: "The biggest challenge of LightSource is just getting the suppliers to try it. Once they try it --- they're also hooked."

When to choose what

Choose Arkestro if

  • You need to compress high volumes of repetitive sourcing events across indirect, MRO, and commodity categories.

  • Your categories have rich bid history, which is where predictive price anchoring works best.

  • You have an installed Coupa or SAP Ariba estate and want a pricing layer that coexists with it rather than replacing it.

  • You are converting single-source and spot buys into competitive multi-round events at enterprise scale.

  • You are in energy or heavy process industries, where Arkestro's reference base (Chevron, Koch Industries) is deepest.

Choose LightSource if

  • Your spend is engineered direct materials: parts with drawings, revisions, and tooling, organized in BOMs.

  • You need quotes as structured cost breakdowns you can compare line by line, not predicted totals.

  • You launch products, so NPI resourcing, revision-aware RFQs, and per-part price history matter more than event throughput.

  • You want supplier discovery beyond your incumbent list; 20,000 suppliers are live and the platform is free for them.

  • You want to be live in days without a systems-integrator project, with implementation included.

RUNNING BOTH

Arkestro is a sourcing-stage neighbor, so the coexistence case is narrower than with intake or P2P tools, but it exists and it splits by spend type. Run Arkestro as the negotiation-compression layer over indirect, MRO, and commodity categories inside your Coupa or SAP Ariba estate, and run LightSource as the system where engineered parts live: items, BOMs, revisions, drawings, cost-breakdown quotes, awards, and per-part price history from NPI through production resourcing. Both can feed the same ERP, since LightSource exports awarded pricing through its GraphQL API or flat files. Where an Arkestro event would touch engineered parts, ask the depth question: a line-item price event or a part-lifecycle record.

Frequently asked questions

What is the difference between LightSource and Arkestro?

Arkestro is a predictive procurement platform that compresses multi-round sourcing events by suggesting prices from bid history, and it runs alongside suites like Coupa and SAP Ariba. LightSource is the Direct Materials Operating System: the system of record for engineered parts, with revision-managed items, BOMs, drawings, cost-breakdown quotes, award scenarios, and per-part price history from PLM through ERP. The practical difference is the unit of work: Arkestro works on events, LightSource works on parts.

Does Arkestro handle direct materials and BOMs?

Arkestro does run events on direct spend; Nissan Americas uses it across direct and indirect categories, and its case studies include A and B parts. However, its public materials show no item master, BOM, revision, or drawing constructs; parts appear as line items inside sourcing events. Buyers who need a revision-managed record of engineered parts keep that record elsewhere.

Does LightSource offer predictive pricing like Arkestro?

No, LightSource approaches price differently. It treats should-cost and target price as first-class item data, normalizes any supplier quote into structured cost breakdowns with AI, and tracks per-part price history across revisions and suppliers. Arkestro's mechanic is a statistically predicted anchor price generated from bid and market history before suppliers bid.

Can you use LightSource and Arkestro together?

Yes, and the split is by spend type. Arkestro can compress negotiation events across indirect, MRO, and commodity categories inside an existing Coupa or SAP Ariba estate, while LightSource serves as the system of record for engineered parts: items, BOMs, revisions, drawings, cost-breakdown quotes, and awards. Awarded pricing exports from LightSource to your ERP through its GraphQL API or flat files.

How much do LightSource and Arkestro cost?

LightSource prices as a platform fee plus seats, with implementation included; exact pricing depends on scope. Arkestro does not publish pricing; Capterra's third-party listing shows a starting point of $500 per month on a per-feature model. Ask each vendor directly how pricing scales with users, events, and spend.

Which is better for NPI sourcing, LightSource or Arkestro?

New-product introduction is where the two models differ most. Predictive anchors depend on bid history, which is thin for new engineered parts, while LightSource builds price from the part itself: drawings, revisions, should-cost data, and structured cost-breakdown quotes, with engineering collaborating in the same workflow. Arkestro's public materials do not document an NPI or engineering workflow.

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.