LightSource vs. Arkestro

Arkestro, founded in 2017 as Bid Ops, markets itself as a predictive procurement platform: a pricing layer that opens multi-round sourcing events with AI-suggested target prices that suppliers accept or counter, running on top of suites like Coupa and SAP Ariba that hold the record. In our assessment the predicted price is a statistic of the bids already received; as of November 2026 its MCP connector for outside AI agents is listed as coming soon, and its public G2 and Capterra reviews date from 2018 to 2023. LightSource is the Direct Materials Operating System, spec through scale, PLM through ERP: the enterprise-ready system of record for parts, BOMs, RFQs, and awards, live in days with implementation included and suppliers always free.

Last reviewed

· Based on public information ·

Side-by-side comparison: LightSource vs Arkestro, a short summary plus 8 attributes
Attribute
LightSource
Arkestro
The short versionLightSource: LightSource 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.Arkestro: Arkestro, founded in 2017 as Bid Ops, markets itself as a predictive procurement platform: a pricing layer that opens multi-round sourcing events with AI-suggested target prices that suppliers accept or counter, running on top of suites like Coupa and SAP Ariba that hold the record. In our assessment the predicted price is a statistic of the bids already received; as of November 2026 its MCP connector for outside AI agents is listed as coming soon, and its public G2 and Capterra reviews date from 2018 to 2023.
Built forLightSource: Direct materials, spec through scale: parts, BOMs, NPI programsArkestro: Predictive sourcing events across category spend
Core questionLightSource: Who should make this part, and at what price?Arkestro: What price should this event open at before suppliers bid?
ArchitectureLightSource: AI-native direct materials operating system, built around the part recordArkestro: Predictive pricing layer over the buyer's suite, which stays the record; offers and awards sync to SAP, Oracle, Coupa, or SAP Ariba; MCP for outside agents listed as coming soon (November 2026)
ImplementationLightSource: Live in days on flat files; sourcing in about 30 days; implementation includedArkestro: Arkestro says live in 5 days on a spend file and ROI in 45 days; ERP and S2P connectors are confirmed in technical scoping, Capgemini and BDO support enterprise rollouts, and G2 reviewers note that suppliers need training too
Pricing modelLightSource: All-in platform fee: configuration, integrations and implementation included; suppliers always freeArkestro: Not published; Capterra's third-party listing shows a $500 per month starting point, per feature; our estimate for an enterprise deployment is $225K to $325K a year all-in
Supplier networkLightSource: 100,000+ suppliers live; free supplier workspace; AI discoveryArkestro: Your incumbent supplier list; suppliers respond to suggested prices inside events
Target customerLightSource: Manufacturers from growth stage to enterprise divisionsArkestro: Enterprise procurement teams with a suite underneath; most G2 reviewers are mid-market; in our assessment strongest on categories that draw many comparable bids per line
Public evidenceLightSource: Named customers on record; G2 4.9/5, among the highest ratings in the procurement category; Gartner Cool Vendor 2025; Hackett 50 to Watch 2025-26, evaluated in SolutionMap Sourcing and Direct SourcingArkestro: Founded 2017; venture-funded through a $26M Series A (2022) and a $36M strategic round (2025), with 51 to 200 employees on LinkedIn; G2 5.0/5 on 11 reviews (newest February 2023) and Capterra 5.0/5 on 4 reviews (2018 to 2019), as of November 2026; recent reviews on a major analyst peer-review site are more mixed; Hackett 50 to Watch 2025-26 and in its 2026 sourcing and spend analytics guides; named enterprise customers and public case studies.
Highlighted cells mark where the two differ most in practice, based on our evaluations and public documentation.

Where each system actually works

The procurement landscape reduced to what matters for this comparison: three rows across the nine lifecycle stages, one lane per product. Orange bars are where LightSource operates, outlined bars are where this vendor does; solid means native in practice, dashed partial, dotted claimed but not evidenced.

Direct materials · Spec-to-Scale (S2S)ERP and supply chain systemsLifecycle stageDefine and intakeDiscover suppliersSourceContract and awardIndustrializeRamp and launchScale and sustainOrder and payPlan and fulfillDirect materialsLightSourceSpec-to-Scale system of record · Parts & drawings · BOMs · Supplier engagement +1ArkestroShould-costSpec-aware RFQs +4PricecomplianceBoth direct and indirectLightSourceCategorymanagementSupplierdiscoveryContracts · Supplier onboarding +2ArkestroSpendanalyticsSupplierdiscoverySupplierportalsIndirectLightSourceIndirect RFx · MROStrategicindirectArkestroIndirect RFx +1StrategicindirectLightSource · nativepartialArkestro · nativepartialclaimed, not evidenced
Concentrated in Source and Contract and award (stages 3 and 4): predictive multi-round RFQs, tail and spot buys, and quote benchmarking. LightSource runs direct materials from Define and intake through Scale and sustain on a part record; Arkestro prices the event and syncs awards to the suite.
Bars merge the areas each product covers along the lifecycle; labels name the main ones. Solid is native in practice, dashed is partial, dotted is claimed but not evidenced. Explore all 45 areas on the interactive map.

Capability comparison, in detail

Fifty-seven capabilities in thirteen groups, aligned to the areas on our interactive procurement technology map. The LightSource column is identical on every comparison page, including the ones we don’t win.

Across 57 capabilities, LightSource rates Strong on 28, Moderate on 13, Integrates on 6 and Not offered on 10; Arkestro rates Strong on 2, Moderate on 12, Limited on 11, Integrates on 8, Not offered on 11 and Not documented on 13.

StrongModerateLimitedIntegratesNot offeredNot documented

Strong: native, documented and usable day one. Moderate: native but partial, assistive or in early access. Limited: narrow, marketed only, or delivered through a configuration project. Integrates: the step runs in the connected system of record (PLM, ERP, AP) and the product connects to it. Not offered: outside the product's scope. Not documented: no public evidence as of Nov 18, 2026.

Capability comparison: LightSource vs Arkestro, 57 capabilities in 13 groups
Capability
LightSource
Arkestro
1 · Define and intake
Parts, drawings and metadata: LightSource: Strong.
Item master with drawings, custom properties and frozen revisions; AI extracts items from PDFs and sheets
Arkestro: Not documented.
Not publicly documented; parts enter events as line items, with no drawing, spec or item record
BOMs: LightSource: Strong.
Multi-level BOMs with cost rollup from quotes or contracts, revision diffs and cost history charts
Arkestro: Not documented.
Not publicly documented; BOMs, revisions and cost roll-ups appear nowhere in its public materials
Should-cost, VAVE and design-to-cost: LightSource: Moderate.
Should-cost and target cost on every item set bid baselines and flag awards above target
Arkestro: Limited.
Native: baseline prices derived from quote statistics for new items; no bottom-up cost models or VAVE
PLM (system of record): LightSource: Integrates.
PLM stays the engineering record; items, BOMs and files sync in by external ID via the API or spreadsheets
Arkestro: Not documented.
Not publicly documented; the integrations page names ERP, S2P and CLM systems but no PLM
Category management and strategy: LightSource: Moderate.
Item categories with their own properties, category charts and Programs give category plans a live data spine
Arkestro: Limited.
Marketed: Opportunities co-pilot (beta, Oct 2025) suggests line-item sourcing actions; no category plans
Intake and orchestration: LightSource: Not offered.
By design, work starts at the item, BOM or Sourcing project; engineers raise needs in the Engineering role
Arkestro: Integrates.
Configured: Zip and ServiceNow listed as API and webhook connectors; no native requester front door
2 · Discover suppliers
Supplier engagement and early involvement: LightSource: Strong.
Early supplier involvement and design collaboration: data rooms, RFIs, threads, drawings shared by revision
Arkestro: Not documented.
Not publicly documented; suppliers enter at the event with suggested prices, no DFM or design input
Supplier capability mapping: LightSource: Strong.
Supplier Discovery searches by process or material; profiles hold specialties, sites, tags and properties
Arkestro: Not documented.
Not publicly documented; supplier recommendations are marketed, with no equipment or process record
Spec-to-Scale system of record: LightSource: Strong.
One record from item and BOM through RFQ, quote, award and Awarded contract, between PLM and ERP
Arkestro: Not offered.
Outside scope; a predictive pricing layer over events, with no part, BOM or cost-breakdown record
Supplier discovery: LightSource: Strong.
Supplier Discovery across 100,000+ suppliers by process or material; LightSource contacts the ones you pick
Arkestro: Limited.
Marketed: recommends suppliers from procurement history; events run on the buyer's own suppliers
GPOs and buying consortia: LightSource: Not offered.
Out of scope by design; competitive Sourcing projects across 100,000+ suppliers set your own pricing
Arkestro: Not offered.
Outside scope; Arkestro is a sourcing tool with no GPO or buying-consortium contract features
3 · Source
Spec-aware sourcing (RFQs with drawings): LightSource: Strong.
Sourcing projects built from items with drawings; per-item quote formats drafted by the RFX Setup Agent
Arkestro: Limited.
Native: line-item events cover A and B parts; no BOM-driven events, revision-tied drawings or bid templates
Quote breakdowns and normalization: LightSource: Strong.
Quote formats with flexible cost breakdowns; AI normalizes any quote; bids compared in one currency
Arkestro: Limited.
Native: offers broken into cost elements on its own bid sheet; no category cost-breakdown templates
Iterative pricing and re-quotes: LightSource: Strong.
RFQ versions and rounds, per-supplier updates and quote history compared across rounds; Item Cost Walk
Arkestro: Moderate.
Native: targeted round-two counteroffers with live rank feedback; no revision re-quotes or cost walks
Marketplaces: LightSource: Not offered.
Not a marketplace: suppliers join your Sourcing projects free; Supplier Discovery finds them across 100,000+
Arkestro: Not offered.
Outside scope; Arkestro runs buyer-led events and is not a parts or business marketplace
Indirect RFx and e-auctions: LightSource: Moderate.
RFQs and RFIs for strategic indirect categories such as freight lanes and capex, with cost-breakdown bids
Arkestro: Strong.
Native: multi-round RFQ events where buyers open with predicted offers and suppliers accept or counter
4 · Contract and award
Award and nomination: LightSource: Strong.
Award scenarios with splits, suggested and AI-optimized plans, sequenced approvals; awards create contracts
Arkestro: Moderate.
Native: award scenarios and event-level awards in case studies; no nominations or long-term agreements
Pricing formulas: LightSource: Strong.
Formula fields in quote formats price from item properties; per-period volumes and terms set at award
Arkestro: Not documented.
Not publicly documented; events price line items against predicted offers, with no index-linked formulas
Third-party and internal benchmarking: LightSource: Moderate.
Target prices from contracts, should-costs and price history; cross-project quote comparison, bid distribution
Arkestro: Moderate.
Target prices are a statistic of the bids received, about half a standard deviation below the mean; reactive
Contract management: LightSource: Strong.
Awarded contracts with price, volume, terms, expiry tracking and pricing history; authoring stays in your CLM
Arkestro: Integrates.
Configured: Icertis and Agiloft listed as API and webhook connectors; no native contract lifecycle tools
Tail-spend management: LightSource: Not offered.
No tail-spend desk or spot-buy channel; built for planned direct and strategic buys
Arkestro: Strong.
Native: tail and spot buys run as predictive multi-line events at volume; no catalogs, cards or spot desk
5 · Industrialize
APQP, PPAP and supplier quality: LightSource: Moderate.
Certifications and quality documents via RFIs and data rooms; AI flags expiring certificates; PPAP in your QMS
Arkestro: Not offered.
Outside scope; sourcing ends at award, with no APQP, PPAP or corrective-action workflow
Tooling, prototypes and pilot builds: LightSource: Moderate.
Tooling and ED&T costs in quotes and bid totals; tooling items record cavity count, tool life, ownership
Arkestro: Not offered.
Outside scope; no tooling, prototype or pilot-build tracking in public materials
Supplier onboarding and information: LightSource: Strong.
Suppliers join free by invitation; RFI qualification, certificates in data rooms, ERP vendor sync
Arkestro: Not documented.
Not publicly documented; suppliers are invited to events, with no registration, certificate or banking flow
6 · Ramp and launch
Production ramp and timelines: LightSource: Moderate.
Programs track awarded projects, open items and milestones per project; suppliers see the milestones
Arkestro: Not offered.
Outside scope; no launch timeline, ramp curve or supplier milestone tracking
Alternate sourcing and tier-N visibility: LightSource: Moderate.
Dual-source awards with supplier caps and Supplier Discovery for alternates; tier-N mapping in your risk tools
Arkestro: Not documented.
Not publicly documented; award modeling is marketed as weighing risk, with no tier-N map or alternates
Supplier collaboration portals: LightSource: Strong.
Free for suppliers, onboarding in under 30 minutes: RFQs, Excel round-trip quotes, messages, data rooms
Arkestro: Moderate.
Native: suppliers accept or counter predicted offers with live rank feedback; quotes only, no POs
7 · Scale and sustain
Price compliance and index adjustments: LightSource: Strong.
Awarded contract prices, Pricing History and Item Cost Walk set the reference price for each item
Arkestro: Limited.
Marketed: Continuous Procurement promises always-on benchmarking; no invoice, PO or index checks
Engineering changes and cost-downs: LightSource: Strong.
Item and BOM revision diffs reach live RFQs as pending changes; Re-source, Programs and Savings projects
Arkestro: Not documented.
Not publicly documented; no ECO intake or revision-driven re-quote workflow in public materials
SRM and supplier performance: LightSource: Strong.
Weighted Scorecards, Book Of Business per supplier, data rooms with AI document analysis, contacts
Arkestro: Not documented.
Not publicly documented; no scorecards or performance reviews, supplier activity centers on events
Renewals and vendor consolidation: LightSource: Not offered.
Indirect renewal calendars are out of scope; direct contract expiry is tracked under Contracts
Arkestro: Not documented.
Not publicly documented; no renewal calendar, auto-renew controls or vendor consolidation tools
8 · Order and pay
LightSource stops at the award on purpose. Purchase orders, receipts and invoices run in your ERP or procure-to-pay system, and LightSource writes awarded pricing and supplier records into it.
PO, release and order collaboration: LightSource: Integrates.
POs and releases run in your ERP; awarded prices and terms flow there via the GraphQL API or files
Arkestro: Integrates.
Configured: awards sync back to SAP, Oracle or Coupa by API and webhook; no releases or ASNs
ERP and MRP (system of record): LightSource: Integrates.
ERP stays the transactional record; supplier master syncs both ways and awarded pricing flows into it
Arkestro: Integrates.
Configured: REST API and webhooks for SAP, Oracle and Coupa; offers and awards sync to the record
Invoice, AP automation and payments: LightSource: Integrates.
Invoicing and payment stay in your ERP or AP; Awarded contracts send agreed prices and payment terms
Arkestro: Not offered.
Outside scope; no invoicing, AP or payment touchpoint, Arkestro sits upstream of the P2P suite
Requisition to PO, catalogs and punchouts: LightSource: Integrates.
No requisitions, catalogs or punchouts; awarded prices export to your ERP or P2P, where POs are issued
Arkestro: Integrates.
Configured: awards sync to Coupa, SAP Ariba or ServiceNow for the PO; no requisitions or catalogs
9 · Plan and fulfill
Downstream planning and logistics stay in the supply chain systems that own them; LightSource is upstream of the forecast.
Planning and logistics systems: LightSource: Not offered.
Planning, S&OP, TMS and WMS sit downstream of LightSource and are out of scope
Arkestro: Not offered.
Outside scope; no demand planning, TMS or WMS features or connectors
Cross-cutting: analytics, risk and governance
Spend analytics and savings tracking: LightSource: Moderate.
BOM-level spend and cost analytics, Savings projects, My Supply Chain dashboards; BI cubes fed by the API
Arkestro: Limited.
Native: savings and cycle-time reporting on events; Sievo connector listed; no spend cube
Risk monitoring and third-party risk: LightSource: Moderate.
AI Document Analysis flags expired certificates; supplier status and Scorecards; risk feeds connect by API
Arkestro: Integrates.
Configured: Exiger listed as an API and webhook connector; no native risk monitoring or TPRM
ESG, sustainability and supplier diversity: LightSource: Not offered.
ESG ratings and Scope 3 stay with specialist providers; RFIs and data rooms collect certificates
Arkestro: Integrates.
Configured: EcoVadis listed as an API and webhook connector; no native ESG or diversity tools
Master data management: LightSource: Integrates.
Items and suppliers mastered against PLM and ERP by external ID; AI duplicate detection and merge
Arkestro: Integrates.
Configured: supplier data syncs by REST API with the ERP or suite as the record; no MDM tools
Tariff and HTS support: LightSource: Moderate.
Built-in HTS code property with AI suggestions; duty and freight as cost modifiers for landed-cost bids
Arkestro: Not documented.
Not publicly documented; tariffs appear as webinar topics, not as an HTS or landed-cost feature
Indirect category systems
Category-specific indirect systems. LightSource runs strategic indirect categories that behave like direct, such as packaging, logistics lanes and facilities.
Services and contingent workforce: LightSource: Not offered.
Out of scope by design; LightSource is built for direct materials, not contingent labor or statements of work
Arkestro: Not offered.
Outside scope; services can run as sourcing events, with no VMS or SOW management
SaaS and software spend: LightSource: Not offered.
Out of scope by design; LightSource is built for direct materials, not SaaS licenses
Arkestro: Not offered.
Outside scope; no software discovery, license or renewal management
T&E, cards and expense: LightSource: Not offered.
Out of scope by design; LightSource is built for direct materials, not travel or expenses
Arkestro: Not offered.
Outside scope; no travel, card or expense features
MRO: LightSource: Moderate.
MRO sourcing runs as Sourcing projects with awarded contracts; storeroom, min-max and CMMS stay out of scope
Arkestro: Limited.
Native: MRO is a lead case-study category for events; no storeroom, catalog or CMMS buying
Strategic indirect: LightSource: Strong.
Freight lanes, rate cards and capex run as Sourcing projects; Ocean Freight and Capex quote templates
Arkestro: Moderate.
Native: predictive multi-round events for packaging and other indirect categories; no lane books
Platform and AI
AI-native architecture: LightSource: Strong.
AI through the cycle: item extraction, RFX Setup Agent, custom views, award optimization, thread answers
Arkestro: Moderate.
Marketed as predictive; in our assessment the core is bid statistics and automated counteroffers
Agentic and autonomous operation: LightSource: Strong.
Agents draft quote formats, bid views and award plans; autonomous sourcing; BYO agents (Claude, OpenAI) by API
Arkestro: Limited, Rule-based automation.
Counteroffers automated from bid statistics; Opportunities co-pilot in beta since Oct 2025; MCP coming soon
AI compatibility (agents, MCP, API): LightSource: Strong, MCP + full API.
Claude, OpenAI, Copilot and your own agent harness connect via LightSource's MCP server and full GraphQL API
Arkestro: Limited, API only.
REST API and webhooks today; MCP for outside agents still listed as coming soon, with no public API docs
Direct-materials focus: LightSource: Strong.
Built around parts: drawings, revisions, multi-level BOMs, tooling and ED&T costs, cost breakdowns
Arkestro: Moderate.
Direct spend in scope (Nissan, A and B parts cases), but parts are event line items, not managed records
NPI support: LightSource: Strong.
Revision-aware RFQs, target costs and should-costs for new parts, Engineering role, Programs for launches
Arkestro: Not documented.
Not publicly documented; no engineering collaboration or revision workflow; new items get predicted prices
Fit, setup and cost
Cost rows carry our estimates: subscription plus implementation and integration fees, stated with their inputs. "High TCO" means suite-scale spend with integrator fees on top.
Setup model (self-serve vs. integrator): LightSource: Strong, Self-serve, vendor-led.
No third-party systems integrators: LightSource configures and integrates the platform as part of the license
Arkestro: Moderate, Vendor-led, partners.
Vendor scopes connectors; Capgemini or BDO back enterprise rollouts; reviewers say suppliers need training
Time to launch: LightSource: Strong, Days to weeks.
Live in days on spreadsheet syncs; sourcing running in about 30 days; API connectors follow without a project
Arkestro: Moderate, Weeks to months.
Vendor says live in 5 days on a spend file; ERP connectors follow technical scoping; suppliers need training
Pricing and total cost (estimate): LightSource: Strong, All-in platform fee.
Platform fee covers configuration, integrations and implementation; suppliers always free; no SI fees or per-seat add-ons
Arkestro: Moderate, Low entry, mid TCO.
Not published; Capterra lists a $500 a month entry price. Our estimate for an enterprise deployment: $225K to $325K a year all-in
SMB fit: LightSource: Moderate, Medium.
Self-serve start suits small teams; overpowered for organizations without two or more procurement heads
Arkestro: Limited, Stretch.
A stretch: quote-based enterprise sales, and its bid statistic needs high-volume categories with many bidders
Mid-market fit: LightSource: Strong, Core market.
Lean teams run it self-serve; enterprise controls available, not required
Arkestro: Moderate, Stretch on cost.
Most G2 reviews (2021 to 2023) are from mid-market users; our $225K+ all-in estimate strains lean teams
Enterprise readiness: LightSource: Strong, Enterprise-ready.
Used by global organizations such as Amazon, BRP and Yum! Brands; SSO, SCIM, access groups, approval chains
Arkestro: Moderate, Layer on the suite.
Chevron, Nissan and Koch run it as a layer over their suites; SSO named, SCIM and multi-entity not documented
Notes use a few 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. "Integrates" means the step runs in the system of record that owns it (PLM, ERP, AP) and the product connects to it. "Not documented" means the vendor does not publicly document this capability as of Nov 18, 2026; it may exist, and we note the gap rather than guess. Ratings reflect public documentation as of Nov 18, 2026.

Where Arkestro is strong

Arkestro, founded in 2017 as Bid Ops and rebranded in 2022, is a venture-backed company whose strength is one event mechanic: multi-round competitive sourcing events in which the buyer's side moves first, with the platform generating what it calls a predicted price that suppliers accept or counter with live ranking feedback. The mechanic is well evidenced on high-volume, history-rich categories such as MRO, packaging, and commodity parts. 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 on all spend and a 13-day average cycle time at one materials company; treat those as vendor figures rather than audited results, though the customer list itself is public.

Arkestro also positions itself carefully, as a layer that connects to the existing suite rather than replacing it, 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, with the corollary that the item record, contracts, and purchase orders all stay in those other systems.

The Hackett Group's 2026 sourcing guide describes Arkestro as a predictive procurement orchestration platform built on data, behavioral science, game theory and machine learning, and placed it on its 2025-2026 '50 to Watch' list.

Where LightSource wins for direct materials

LightSource runs direct materials on one enterprise-ready record, spec through scale and PLM through ERP, and it is used by global organizations. 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 November 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 on where price comes from. Arkestro's anchors are statistical, computed from the bids suppliers submit, so they show where the bids cluster rather than what the part should cost. An engineered component at new-product introduction needs the second answer; 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. 100,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. Enterprise controls are standard, with SSO, SCIM, access groups, and approval chains, and an MCP server and full GraphQL API let Claude, OpenAI, Copilot, or a customer's own agents operate the platform. 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 Hackett Group placed LightSource on its 2025-2026 '50 to Watch' list and lists it in its September 2026 Sourcing (for direct) solutions guide as AI-native and purpose-built for direct materials procurement.

The structural difference: pricing events versus managing parts

Arkestro needs a suite underneath it to be useful: its own materials position it as a layer over the existing suite rather than a replacement. Its integrations page lists connectors for SAP, Oracle, Coupa, SAP Ariba, Icertis, Agiloft, Zip, and ServiceNow, and every offer, counter, and award syncs back to the buyer's system of record, with approvals, award handoffs, and audit events routed to those systems as well. Record-keeping, contracts, and requester intake stay in those connected systems, and Arkestro adds a pricing layer, marketed as predictive, 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. As of November 2026, Arkestro's Predictive Sourcing page describes AI-suggested prices on every line item, automatic counteroffers, supplier recommendations, and line-item award scenarios that weigh value, risk, and supplier diversification, and its Continuous Procurement page adds scheduled price-update events with every price versioned across SKUs and suppliers. In our assessment, the AI-suggested price is a statistic of the bids already in the event, set roughly half a standard deviation below their mean once about five bids arrive, a reactive target rather than a prediction, so the predictive marketing should not be taken at face value. The method also depends on bid volume: in our assessment it says something useful about a commodity line with many bidders and little about an engineered part with only a few qualified suppliers. 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 and SKUs with price history, 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.

Several capabilities a growing enterprise would rely on are early or undocumented. The Opportunities category co-pilot launched in beta at two customers in October 2025, MCP connectivity for outside agents is listed as coming soon as of November 2026, and Arkestro's trust center lists SOC 2 Type 2 and ISO/IEC 27001 and names access control and single sign-on as enterprise features, but does not document SCIM provisioning or multi-entity controls.

Pricing layer versus operating system

For direct materials these two are not a stack. Arkestro is a pricing layer that needs a suite under it: the item record, contracts, approvals, and purchase orders live in Coupa, SAP Ariba, or the ERP, and Arkestro adds the event on top. Professional procurement organizations buying engineered parts run a simpler architecture: LightSource for the sourcing decision, spec through award, and the ERP as the transactional backbone for purchase orders, receipts, and payables. Awarded pricing flows from LightSource into the ERP through the GraphQL API or flat files, and the PO goes out through the ERP's normal channels with the approval chains finance already expects. LightSource also runs RFx for strategic indirect categories such as freight lanes and capex, so the manufacturer avoids a second event tool, a second supplier login, and a second integration to keep in sync.

In our assessment an event layer fits while sourcing is a series of independent price events on comparable items, and it is outgrown for direct materials as the organization adds programs, plants, and product revisions. At that point sourcing becomes the management of the parts themselves: which revision was quoted, what the part should cost, and who supplies it across every BOM it sits in. That record has to live somewhere, and in an Arkestro deployment it lives outside Arkestro.

The one overlap is an enterprise that already runs Arkestro on tail and spot buys inside its Coupa or SAP Ariba estate; those buys can stay there while engineered parts move to LightSource and the ERP. As of November 2026, Arkestro lists MCP connectivity for agents as coming soon, with its REST API and webhooks available today; LightSource's MCP server and GraphQL API, which mirrors the whole app, let Claude, OpenAI, and other agents operate LightSource directly.

What public reviewers say

As of November 2026, Arkestro holds 5.0 out of 5 across 11 reviews on G2 and 5.0 out of 5 across 4 reviews on Capterra, and LightSource holds 4.9 out of 5 on G2, among the highest ratings in the procurement category. The Arkestro scores need context. The newest of its G2 reviews is from February 2023 and its Capterra reviews date from 2018 and 2019, most of them written in the Bid Ops era before the 2022 rebrand, so they describe earlier versions of the product. Every review base here is small, so read individual reviews as anecdotes rather than statistics.

The positive theme is consistent across both sites: the tool is easy to use and the team is responsive. A G2 reviewer (Mid-Market, February 2023) wrote: "The product is straightforward to use by our internal teams. Once trained, they can use the tool without support from Procurement." A G2 reviewer in pharmaceuticals (Mid-Market, August 2021) said the AI negotiation "works exceptionally well on new items where you don't have a pricing history," which fits our reading that the suggested price is computed from the bids in the current event. On Capterra, a Senior Account Manager who bid through the platform (October 2018) wrote that they "found Bid Ops to be easy to use."

The critical comments sit inside those perfect scores and cluster around bid structure and the supplier side. One G2 reviewer (Mid-Market, February 2023) wrote: "We haven't figured out how to get delivery dates as must have on bids." A Director of Chemical Purchasing (G2, Mid-Market, February 2021) wrote: "Program needs to have an awarding option to notify suppliers." Supplier adoption comes up repeatedly: "Vendors need to be trained to use it as well" (G2, Vice President, August 2021), and "it took some getting used to from our suppliers" (G2, Mid-Market, Electrical/Electronic Manufacturing, 2021), though that reviewer credited the team for adjusting quickly. An enterprise reviewer (G2, Senior Digital Innovation Manager, August 2021) noted that it "does require organizational buy-in," and category fit has limits: "in some areas, such as Marketing services, we haven't yet been able to demonstrate the value of the tool" (G2, Mid-Market, February 2023). On Capterra, the same Senior Account Manager asked for "a live bid session," and an early user noted that Total Cost of Ownership assumptions had to be entered manually while those features were still being prototyped.

The newer reviews are more mixed. On a major analyst peer-review site, the handful of verified reviews posted in 2026 range more widely than the G2 and Capterra pools. Reviewers there credit price analytics, the AI-suggested anchor price, and instant competitive feedback after each round. The critical reviews, several written from the bidding supplier's side, describe bid forms that leave out payment terms and Incoterms, submitted bids that cannot be revised while the window is still open, a confusing product list and messaging area in the quote window, and little explanation of who won or lost an award and why. In our assessment these are the frictions that grow as an event tool spreads to more suppliers and more categories.

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, and a suite or ERP already holds the item, contract, and supplier record.

  • Your categories draw many comparable bids per event, which is where bid-based price anchoring works best; in our assessment, engineered parts with only a few qualified suppliers give it little to work with.

  • You have an installed Coupa or SAP Ariba estate, want a pricing layer that coexists with it, and are prepared to run and maintain one more integration.

  • 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 has flagship references (Chevron, Koch Industries) and strategic investors (Aramco Ventures, Altira Group).

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, with category-specific bid sheets per event.

  • 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; 100,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.

  • You want enterprise controls and agent access from day one: SSO, SCIM, access groups, approval chains, an MCP server, and a full GraphQL API that Claude, OpenAI, or your own agents can operate.

RUNNING BOTH

Not as a stack for direct materials. Arkestro is a pricing layer that needs a suite under it; a professional organization buying engineered parts runs LightSource for the sourcing decision, spec through award, with its ERP as the transactional backbone, and purchase orders go out through the ERP. LightSource also runs RFx for strategic indirect categories, so a second event tool is rarely needed. The one overlap is an enterprise that already runs Arkestro on tail and spot buys inside Coupa or SAP Ariba; those buys can stay there while engineered parts move to LightSource and the ERP.

Frequently asked questions

What is the difference between LightSource and Arkestro?

Arkestro is a procurement tool, marketed as predictive, that compresses multi-round sourcing events by suggesting target prices from bids; it is a layer that needs a suite such as Coupa or SAP Ariba underneath to hold the record. LightSource is the Direct Materials Operating System: the enterprise-ready 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 in another system, which LightSource provides from spec through scale.

Does LightSource offer predictive pricing like Arkestro?

LightSource sets target prices from the part itself. It treats should-cost and target price as first-class item data, compares every quote against contracts, should-costs, and price history, captures quotes as structured cost breakdowns, and tracks per-part price history across revisions and suppliers. Arkestro markets its mechanic as a predicted anchor price; in our assessment it is a simple statistic of the bids received, set about half a standard deviation below their mean.

Can you use LightSource and Arkestro together?

For direct materials, most organizations do not need both. Arkestro is a pricing layer over a suite such as Coupa or SAP Ariba, while a professional organization buying engineered parts runs LightSource for the sourcing decision and its ERP for purchase orders, with awarded pricing exported through the GraphQL API or flat files. LightSource also runs RFx for strategic indirect categories. An enterprise that already runs Arkestro on tail and spot buys inside its suite can keep it there while engineered parts move to LightSource.

How much do LightSource and Arkestro cost?

LightSource prices as an all-in platform fee that covers implementation, configuration, and integrations, and suppliers always use it free; 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, and our estimate for a typical enterprise deployment, including implementation and integration, is $225K to $325K a year. 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. Arkestro's suggested targets are computed from the bids suppliers submit, so they reflect the opening offers rather than what a new engineered part should cost, and a new part with only a few qualified suppliers gives that statistic little to work with. 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.

Sources

  1. Arkestro: Integrations (REST API and webhooks; SAP, Oracle, Coupa, SAP Ariba, Icertis, Agiloft, Exiger, EcoVadis, Sievo, ServiceNow, Zip; MCP coming soon)

  2. Arkestro: Predictive Sourcing (suggested pricing, counteroffers, supplier recommendations, award scenarios)

  3. Arkestro: Continuous Procurement (scheduled price update events, versioned price history)

  4. Arkestro homepage (savings and cycle-time claims, named customers, as of November 2026)

  5. Arkestro press release: $36M strategic investment (May 2025)

  6. TechCrunch: Arkestro Series A and Bid Ops rebrand (June 2022)

  7. Arkestro press release: Nissan Americas collaboration (February 2026)

  8. PR Newswire: Arkestro 2026 momentum release (400,000+ items, $410B spend; Capgemini and BDO partnerships)

  9. Arkestro press release: leadership appointments and platform spend growth (August 2026)

  10. Arkestro Use Case Booklet Vol. 2 (A and B parts, tape sourcing event)

  11. G2: Arkestro reviews (5.0 out of 5 on 11 reviews, newest February 2023, as of November 2026)

  12. Capterra: Arkestro reviews (5.0 out of 5 on 4 reviews, 2018 to 2019, as of November 2026)

  13. G2: LightSource reviews

  14. Capterra: Arkestro listing (starting price)

  15. CNBC: LightSource raises $33M co-led by Lightspeed and Bain Capital Ventures

  16. BusinessWire: LightSource emerges from stealth with $33M

  17. The Hackett Group: Procurement Technology 2025-2026 Recognition Lists (Hall of Fame, 50 to Know, 50 to Watch, Future 5)

  18. The Hackett Group: Sourcing (for direct) Solutions guide, vendor landscape and top-5 capabilities (Sep 2026)

  19. The Hackett Group: Sourcing Solutions guide, vendor landscape (Sep 2026)

  20. The Hackett Group: Spend Analytics Solutions guide (Sep 2026)

  21. G2: Arkestro pricing (no pricing provided by vendor)

  22. PR Newswire: Arkestro Labs and Arkestro Intelligence launch; Opportunities co-pilot in beta (October 2025)

  23. Arkestro Trust Center (SOC 2 Type 2, ISO/IEC 27001:2022; access control and single sign-on named; SCIM not documented, as of November 2026)

  24. LinkedIn: Arkestro company page (51 to 200 employees)

This comparison is based on publicly available information as of November 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.