LightSource vs. Procure Ai
Procure Ai, a London startup founded in 2020 and funded by one $13 million seed round, deploys more than 50 AI agents on top of an existing SAP, Ariba, or Coupa estate to automate intake, tactical sourcing, and tail-spend negotiation; in our assessment its automation reaches only as far as its connectors do, and its direct-materials agents are marketed without a direct-materials customer story behind them. LightSource is the AI-native Direct Materials Operating System, carrying every part from spec through scale, PLM through ERP, with revision-managed BOMs, drawings, and price history: live in days with implementation included, enterprise-ready with SSO, SCIM, access groups, and approval chains, and always free for suppliers.
| Attribute | LightSource | Procure Ai |
|---|---|---|
| The short version | LightSource: 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. | Procure Ai: Procure Ai, a London startup founded in 2020 and funded by one $13 million seed round, deploys more than 50 AI agents on top of an existing SAP, Ariba, or Coupa estate to automate intake, tactical sourcing, and tail-spend negotiation; in our assessment its automation reaches only as far as its connectors do, and its direct-materials agents are marketed without a direct-materials customer story behind them. |
| Built for | LightSource: Direct materials, spec through scale: parts, BOMs, NPI programs | Procure Ai: Automating intake, tactical sourcing, and tail-spend negotiation over an existing ERP/S2P estate; as of November 2026 also marketed for SAP S/4HANA direct materials |
| Core question | LightSource: Who should make this part, and at what price? | Procure Ai: How do we automate the procurement requests already flowing through the systems we own? |
| Architecture | LightSource: AI-native direct materials operating system, built around the part record | Procure Ai: 50+ AI agents layered on SAP, Ariba, Coupa, Ivalua, Jaggaer, WPS, Unite, Oracle, and Dynamics; not a system of record, so in our assessment its automation depends on the ERP and S2P data and connectors underneath it |
| Implementation | LightSource: Live in days on flat files; sourcing in about 30 days; implementation included | Procure Ai: Modular, no-rip-and-replace pitch with vendor forward-deployed engineers; no timeline published, and our estimate is one to three months for a first module; in our assessment, connecting it across an existing estate is an integration project, and G2 reviewers describe setup as time-consuming and some processes as not yet integrated |
| Pricing model | LightSource: All-in platform fee: configuration, integrations and implementation included; suppliers always free | Procure Ai: Enterprise subscription; AWS Marketplace lists $250,000/year for all modules, revenue-tier adjusted, with larger organizations paying more and AWS infrastructure costs possible on top; our estimate for a typical deployment is $325K to $500K a year |
| Supplier network | LightSource: 100,000+ suppliers live; free supplier workspace; AI discovery | Procure Ai: No quoting network documented; predictive supplier scouting is marketed, not evidenced |
| Target customer | LightSource: Manufacturers from growth stage to enterprise divisions | Procure Ai: European enterprises: DACH core, expanding to UK, Nordics, Benelux, and France; in our assessment a wide enterprise footprint for a seed-stage company |
| Public evidence | LightSource: 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 Sourcing | Procure Ai: Founded 2020; one $13M seed round (November 2025) and about 56 employees (Tracxn, October 2026); G2 4.4/5 on 27 reviews as of November 2026, 18 of them incentivized reviews posted in October 2026, and no Capterra, GetApp, or TrustRadius reviews; reviewers praise the unified data layer and fault integration gaps and setup effort; in major analyst coverage of sourcing but not on Hackett's 2025-26 recognition lists or in its 2026 guides; claims rest mostly on vendor materials and our evaluation. |
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.
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; Procure Ai rates Strong on 6, Moderate on 12, Limited on 20, Integrates on 1, Not offered on 12 and Not documented on 6.
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 | LightSource | Procure Ai |
|---|---|---|
| 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 | Procure Ai: Not documented. Not publicly documented; its direct page works from SAP info records, not part, drawing or revision records |
| BOMs: | LightSource: Strong. Multi-level BOMs with cost rollup from quotes or contracts, revision diffs and cost history charts | Procure Ai: Limited. Marketed: the direct page says it can source entire BOMs; no BOM import, costing or revision tracking shown |
| 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 | Procure Ai: Limited. Marketed: should-cost and cost-structure data cited for challenging price increases; no cost models shown |
| 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 | Procure Ai: Not documented. Not publicly documented; named connectors are ERP and eProcurement suites, with no PLM system listed |
| Category management and strategy: | LightSource: Moderate. Item categories with their own properties, category charts and Programs give category plans a live data spine | Procure Ai: Moderate. Native: spend taxonomy and opportunity detection; Category Strategy agents for value levers are marketed |
| Intake and orchestration: | LightSource: Not offered. By design, work starts at the item, BOM or Sourcing project; engineers raise needs in the Engineering role | Procure Ai: Strong. Native: dialog-based intake with policy checks over SAP, Ariba and Coupa; ~60% autonomous (vendor-reported) |
| 2 · Discover suppliers | ||
| Supplier engagement and early involvement: | LightSource: Strong. Early supplier involvement and design collaboration: data rooms, RFIs, threads, drawings shared by revision | Procure Ai: Not documented. Not publicly documented; suppliers enter at the tender or negotiation, with no DFM or design input |
| Supplier capability mapping: | LightSource: Strong. Supplier Discovery searches by process or material; profiles hold specialties, sites, tags and properties | Procure Ai: Not documented. Not publicly documented; supplier profiles hold certificates, risk and ESG scores, not equipment or capacity |
| 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 | Procure Ai: Not offered. Outside scope; an agent layer over SAP and S2P suites with no part record, costed BOM or readiness tracking |
| Supplier discovery: | LightSource: Strong. Supplier Discovery across 100,000+ suppliers by process or material; LightSource contacts the ones you pick | Procure Ai: Limited. Marketed: supplier scouting and discovery agents; no supplier network or capability database documented |
| GPOs and buying consortia: | LightSource: Not offered. Out of scope by design; competitive Sourcing projects across 100,000+ suppliers set your own pricing | Procure Ai: Not offered. Outside scope; 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 | Procure Ai: Limited. Native: RFQs over SAP material lines with AI-built bid sheets; no drawings or revisions attached to events |
| Quote breakdowns and normalization: | LightSource: Strong. Quote formats with flexible cost breakdowns; AI normalizes any quote; bids compared in one currency | Procure Ai: Limited. Native: AI proposal analysis and outlier flags; cost components in bid sheets are marketed, no category CBDs |
| Iterative pricing and re-quotes: | LightSource: Strong. RFQ versions and rounds, per-supplier updates and quote history compared across rounds; Item Cost Walk | Procure Ai: Limited. Native: autonomous negotiation rounds with counter-offers; no revision-linked 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+ | Procure Ai: Not offered. Outside scope; no parts or business marketplace and no catalog buying channel documented |
| Indirect RFx and e-auctions: | LightSource: Moderate. RFQs and RFIs for strategic indirect categories such as freight lanes and capex, with cost-breakdown bids | Procure Ai: Strong. Native: autonomous RFx and negotiation for tactical spend; RFI, RFP, RFQ and four eAuction formats listed |
| 4 · Contract and award | ||
| Award and nomination: | LightSource: Strong. Award scenarios with splits, suggested and AI-optimized plans, sequenced approvals; awards create contracts | Procure Ai: Limited. Native: tail award recommendations; Marketed: constraint-based scenarios with splits and capacity; no LTAs |
| Pricing formulas: | LightSource: Strong. Formula fields in quote formats price from item properties; per-period volumes and terms set at award | Procure Ai: Limited. Marketed: index-linked and tiered prices in bid sheets; no stored formulas, resets or caps documented |
| Third-party and internal benchmarking: | LightSource: Moderate. Target prices from contracts, should-costs and price history; cross-project quote comparison, bid distribution | Procure Ai: Limited. Marketed: price benchmarks from historical PO prices, indices and category data; practice undocumented |
| Contract management: | LightSource: Strong. Awarded contracts with price, volume, terms, expiry tracking and pricing history; authoring stays in your CLM | Procure Ai: Moderate. Configured: contract authoring, redlining and clause extraction agents, plus agreement expiry alerts |
| Tail-spend management: | LightSource: Not offered. No tail-spend desk or spot-buy channel; built for planned direct and strategic buys | Procure Ai: Strong. Native: autonomous tail-spend sourcing and negotiation is the core; 4.9% average savings (vendor-reported) |
| 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 | Procure Ai: Not offered. Outside scope; no APQP, PPAP, corrective-action or material-declaration workflow in any module |
| 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 | Procure Ai: Not offered. Outside scope; no tooling, prototype, pilot-build or material readiness tracking |
| Supplier onboarding and information: | LightSource: Strong. Suppliers join free by invitation; RFI qualification, certificates in data rooms, ERP vendor sync | Procure Ai: Moderate. Configured: automated onboarding workflows with certificate validation and expiry; tax and banking not shown |
| 6 · Ramp and launch | ||
| Production ramp and timelines: | LightSource: Moderate. Programs track awarded projects, open items and milestones per project; suppliers see the milestones | Procure Ai: Not offered. Outside scope; no launch timeline, ramp curve or SOP readiness 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 | Procure Ai: Not documented. Not publicly documented; risk sensing covers supplier profiles, with no sub-tier mapping or alternates |
| Supplier collaboration portals: | LightSource: Strong. Free for suppliers, onboarding in under 30 minutes: RFQs, Excel round-trip quotes, messages, data rooms | Procure Ai: Limited. Marketed: suppliers bid, negotiate and onboard through guided flows; no portal or supplier-side docs |
| 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 | Procure Ai: Limited. Marketed: analysis of supplier price-increase requests against indices; no formula-driven adjustments |
| Engineering changes and cost-downs: | LightSource: Strong. Item and BOM revision diffs reach live RFQs as pending changes; Re-source, Programs and Savings projects | Procure Ai: Not offered. Outside scope; no ECO intake or revision-driven re-quotes; value-lever ideas come from spend analytics |
| SRM and supplier performance: | LightSource: Strong. Weighted Scorecards, Book Of Business per supplier, data rooms with AI document analysis, contacts | Procure Ai: Moderate. Configured: SLA tracking, performance dashboard and relationship briefings; quality scorecards undocumented |
| Renewals and vendor consolidation: | LightSource: Not offered. Indirect renewal calendars are out of scope; direct contract expiry is tracked under Contracts | Procure Ai: Limited. Marketed: agreement expiry alerts trigger automatic re-sourcing; no renewal calendar or SaaS focus |
| 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 | Procure Ai: Limited. Configured: PO creation agents write orders into the ERP; no releases, EDI, ASNs or order collaboration |
| ERP and MRP (system of record): | LightSource: Integrates. ERP stays the transactional record; supplier master syncs both ways and awarded pricing flows into it | Procure Ai: Integrates. Configured: SAP ECC and S/4HANA, Oracle Fusion and Dynamics connectors; SAP info records written back |
| Invoice, AP automation and payments: | LightSource: Integrates. Invoicing and payment stay in your ERP or AP; Awarded contracts send agreed prices and payment terms | Procure Ai: Moderate. Configured: goods-receipt booking, invoice matching and payment agents atop the ERP; not the AP system |
| 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 | Procure Ai: Moderate. Configured: guided buying, PR triage and PO creation agents over the ERP; no catalogs or punchouts shown |
| 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 | Procure Ai: Not offered. Outside scope; no planning, TMS or WMS connectors; demand forecasting sits inside spend analytics |
| 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 | Procure Ai: Strong. Native: unified spend data store with taxonomy and savings tracking; G2 reviewers praise the single view |
| Risk monitoring and third-party risk: | LightSource: Moderate. AI Document Analysis flags expired certificates; supplier status and Scorecards; risk feeds connect by API | Procure Ai: Moderate. Configured: risk sensing on credit, cyber, ESG and news via D&B and Darkbeam feeds; no TPRM workflow shown |
| ESG, sustainability and supplier diversity: | LightSource: Not offered. ESG ratings and Scope 3 stay with specialist providers; RFIs and data rooms collect certificates | Procure Ai: Limited. Configured: EcoVadis ESG scores and CO2 figures on supplier profiles; no Scope 3 reporting or diversity |
| Master data management: | LightSource: Integrates. Items and suppliers mastered against PLM and ERP by external ID; AI duplicate detection and merge | Procure Ai: Moderate. Configured: supplier profile harmonization and dedupe with CDQ enrichment; item masters stay in the ERP |
| Tariff and HTS support: | LightSource: Moderate. Built-in HTS code property with AI suggestions; duty and freight as cost modifiers for landed-cost bids | Procure Ai: Not documented. Not publicly documented; tariff volatility framed its funding news, but no HTS or duty features appear |
| 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 | Procure Ai: Limited. Marketed: intake agents create SOWs and services can run through RFx; no VMS or contingent labor tools |
| SaaS and software spend: | LightSource: Not offered. Out of scope by design; LightSource is built for direct materials, not SaaS licenses | Procure Ai: Not offered. Outside scope; no software discovery, license or seat management |
| T&E, cards and expense: | LightSource: Not offered. Out of scope by design; LightSource is built for direct materials, not travel or expenses | Procure Ai: Not offered. Outside scope; no travel, card or expense tools; expense data only feeds spend classification |
| MRO: | LightSource: Moderate. MRO sourcing runs as Sourcing projects with awarded contracts; storeroom, min-max and CMMS stay out of scope | Procure Ai: Limited. Native: non-production material sourcing per its Kärcher testimonial; no storeroom, min/max or CMMS links |
| Strategic indirect: | LightSource: Strong. Freight lanes, rate cards and capex run as Sourcing projects; Ocean Freight and Capex quote templates | Procure Ai: Limited. Marketed: complex tenders with expressive bids and constraint-based scenarios; no lanes or rate compliance |
| Platform and AI | ||
| AI-native architecture: | LightSource: Strong. AI through the cycle: item extraction, RFX Setup Agent, custom views, award optimization, thread answers | Procure Ai: Strong. Native: built around AI since its 2020 founding; 50+ agents in autonomous, collaborative and ambient modes |
| Agentic and autonomous operation: | LightSource: Strong. Agents draft quote formats, bid views and award plans; autonomous sourcing; BYO agents (Claude, OpenAI) by API | Procure Ai: Strong, Tail and intake. Native agents run intake and tail negotiation; strategic and direct agents are marketed; no public API or MCP |
| 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 | Procure Ai: Limited, No API documented. No MCP server or public API documented; its own agents run on your chosen model, such as Claude or ChatGPT |
| Direct-materials focus: | LightSource: Strong. Built around parts: drawings, revisions, multi-level BOMs, tooling and ED&T costs, cost breakdowns | Procure Ai: Limited. A 2026 direct page covers SAP tail materials and award scenarios; no drawings, revisions or part records |
| NPI support: | LightSource: Strong. Revision-aware RFQs, target costs and should-costs for new parts, Engineering role, Programs for launches | Procure Ai: Not offered. Outside scope; no engineering collaboration, revision-driven resourcing or launch workflow |
| 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 | Procure Ai: Moderate, Vendor-led, IT-heavy. Vendor engineers set up agents and ERP links; reviewers report heavy IT coordination and unconnected steps |
| 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 | Procure Ai: Moderate, 1 to 3 months. No published timeline; our estimate: a first module in 1 to 3 months, a full estate longer with heavy IT work |
| 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 | Procure Ai: Moderate, Mid TCO, on top of S2P. AWS lists $250,000 a year for all modules; larger tiers pay more, on top of the ERP and S2P you keep. Our estimate: $325K to $500K a year all-in |
| SMB fit: | LightSource: Moderate, Medium. Self-serve start suits small teams; overpowered for organizations without two or more procurement heads | Procure Ai: Not offered, Not targeted. No small-team plan; the AWS list price is $250,000 a year and named customers are large firms such as EnBW |
| Mid-market fit: | LightSource: Strong, Core market. Lean teams run it self-serve; enterprise controls available, not required | Procure Ai: Limited, Stretch. A $250,000 a year list price is steep below $1B in revenue; its go-to-market centers on DACH enterprises |
| Enterprise readiness: | LightSource: Strong, Enterprise-ready. Used by global organizations such as Amazon, BRP and Yum! Brands; SSO, SCIM, access groups, approval chains | Procure Ai: Moderate, Young vendor. EnBW, Kärcher and DMG MORI are customers; SSO and SCIM not documented; about 56 staff on one seed round |
Where Procure Ai is strong: tail spend on connected systems
Procure Ai is at its best on high-volume, price-driven work inside an estate that is already connected: intake requests and tail-spend negotiations. It was founded in London in 2020 by co-CEOs Konstantin von Bueren and Yves Bauer and has been AI-native from the start; today the product is a set of more than 50 specialized AI agents, grouped into autonomous, collaborative, and ambient categories, running across the procurement lifecycle. The defining architectural choice, in Yves Bauer's words to tech.eu, is that the platform "sits on top of fragmented data landscapes and makes them intelligible, enriching what is there rather than replacing it." As of November 2026, its platform page names connectors for SAP ECC and S/4HANA, Oracle Fusion, and Microsoft Dynamics plus the Ariba, Coupa, Ivalua, Jaggaer, WPS, and Unite eProcurement suites, lists supplier-data enrichment partners including North Data, CDQ, EcoVadis, Dun & Bradstreet, and Darkbeam, and supports bring-your-own AI with Copilot, ChatGPT, Claude, Gemini, and Llama. It is also listed in SAP's Spend Management partner directory.
The evidenced results sit in intake and tail sourcing, and the figures are vendor-reported. Procure Ai reports that roughly 60 percent of quote-to-order intake requests are handled autonomously, average savings of 4.7 to 4.9 percent on tactical and tail-spend negotiations, and more than 50 billion euros in annual spend managed. Its November 2025 seed round ($13 million led by Headline, with C4 Ventures and Futury Capital) came with a reported 4x year-over-year revenue growth and an expansion plan from its DACH core into the UK, Nordics, Benelux, and France. It is still a young company: that seed is its only round on record, and Tracxn counted about 56 employees as of October 2026. The customer list includes real manufacturers: DMG MORI, Kärcher, and GMH Gruppe, alongside EnBW, Dr. Oetker, and Diebold Nixdorf. The flagship manufacturing testimonial, from Kärcher, comes from a sourcing specialist for non-production material, which is consistent with where the product is aimed.
Where LightSource wins: parts, drawings, revisions, and BOMs
LightSource is the Direct Materials Operating System, spec through scale, PLM through ERP, and it starts where Procure Ai's public materials stop: the part record, with its drawing and revision. AI ingestion turns Excel files, PDFs, and drawings into a revision-managed item master; BOMs nest, snapshot, diff, and roll up cost; RFQs go out at the part level with drawings attached. Cost breakdowns are the sharpest contrast: LightSource is the only sourcing solution with true flexible cost breakdowns, category-specific bid sheets configured per event, and its AI normalizes any quote format against them so line items like tooling, packaging, and logistics surface before award. AI-drafted award scenarios become tracked contracts, and every award adds to per-item, per-supplier price history that survives buyer turnover. The supplier side is live rather than marketed: 100,000+ suppliers on the network, free for suppliers, onboarding in under 30 minutes, quoting through Excel round-trips. Implementation runs in days on flat files, sourcing is typically underway in about 30 days, and implementation is included. It is enterprise-ready, with SSO, SCIM, access groups, and approval chains, and Claude, ChatGPT, Copilot, or a customer's own agents can operate it through an MCP server and a full GraphQL API. Manufacturers from Infinite Machine to BRP, Canada Goose, HelloFresh, Shure, Serta Simmons Bedding, Yum! Brands, and Arxada run direct-materials sourcing on it; LightSource reports 45 percent faster sourcing cycles at six months and 9 percent average savings per cycle, and Infinite Machine reports $10 million saved in nine months. LightSource was named a Gartner Cool Vendor in 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: an agent layer depends on its data
An agent layer is only as capable as the data and connectors underneath it, and Procure Ai describes itself in those terms: it enriches what is already there. Its agents read the data that flows through an ERP and S2P estate, meaning requisitions, catalog items, SAP info records and contracts, supplier records, tenders, invoices, and the spend cube built from them. That is why it is strongest on intake and tail sourcing: the purchases where several interchangeable suppliers compete mainly on price, and where an agent can run the event end to end because nothing outside the transaction data decides the award. In our assessment, that dependency is also where it strains as an organization grows: each additional ERP instance, eProcurement suite, or regional process is another connector to build and maintain, and G2 reviewers already report that processes outside its integrations run manually.
Direct materials awards work differently. The decision hinges on a drawing at a specific revision, tooling amortization, material and process cost structure, and supplier qualification, and none of that lives in a spend cube. It lives in PLM and in the sourcing record. As of November 2026, procure.ai's public materials do cover direct materials. Its strategic sourcing module lists direct materials alongside services and indirects, and a direct-procurement page for SAP S/4HANA describes agents that source entire Bills of Materials, negotiate call-off contracts and SAP info records from PO history and commodity indices, check price-increase requests against should-cost calculations, take tiered or index-linked prices in bids, and simulate award scenarios with supplier shares, dual-sourcing rules, and capacity limits. Engineering drawings, revisions, and part records still appear nowhere, and no PLM connector is named. In our evaluation that makes it a pricing and award layer for materials that already have ERP records, and the page's only testimonial, from DMG MORI's chief purchasing officer, is a general endorsement of the platform with no direct-materials detail. An agent layer over ERP data also has nothing to orchestrate for a new part that is not yet a record in it.
LightSource is built as the system of record those decisions need: item and BOM master data in from PLM, part-level RFQs and cost breakdowns in the middle, awarded pricing out to the ERP through a GraphQL API that mirrors the whole platform.
Agent layer versus operating system
These products are not a stack for direct materials. A professional procurement organization runs production spend on LightSource plus its ERP: LightSource holds the sourcing decision, from BOM ingestion through part-level RFQs, cost-breakdown analysis, and award scenarios, and the ERP stays the transactional backbone for purchase orders, receipts, and payables. Awarded terms and pricing flow into the ERP through the GraphQL API or flat files, and purchase orders go out through the ERP's normal channels with the approval chains finance already expects. Strategic indirect categories can run through LightSource's indirect RFx in the same system.
Procure Ai sits on a different layer, over the ERP and eProcurement suite, and its value depends on how much of that estate its connectors reach. Adding it means another subscription, listed at $250,000 a year for all modules on AWS Marketplace, and its own integration program across the same ERP. Its direct-procurement agents work from SAP price records and market indices, which overlaps the award and price-increase work LightSource does on the part record, so in our assessment running both on production materials would split one decision across two systems.
For a manufacturer whose critical spend is engineered parts, the direct-materials decision belongs in LightSource with the ERP underneath. An enterprise that also wants agents on high-volume indirect requests can evaluate Procure Ai separately for its indirect team, on its own budget and integration plan. Geography is a practical filter as well: Procure Ai's go-to-market is European, DACH-core and expanding into the UK, Nordics, Benelux, and France per its own funding announcement, while LightSource serves North American and global manufacturers.
What public reviewers say
As of November 2026, Procure Ai holds 4.4/5 across 27 reviews on G2, 17 of them five-star and 10 four-star, against 4.7/5 on 9 reviews in September. Its Capterra, GetApp, and TrustRadius listings carry no reviews, and a major analyst peer-review site lists the product with no reviews yet. LightSource holds 4.9/5 on G2, among the highest ratings in the procurement category. Procure Ai's G2 base grew in two distinct waves. The 9 reviews posted between February and September 2024 are marked organic, and 7 of them come from enterprise or mid-market companies. The other 18 arrived between October 9 and 21, 2026, all through G2's incentivized invite program. Procure Ai sells to large enterprises, while most of those 18 reviewers work at small businesses, so we give the organic, procurement-specific reviews more weight below.
The organic reviews praise what the product is built for: one data layer across fragmented systems, faster intake and tail-spend negotiation, and responsive support.
"Procure AI pulls data from everywhere, giving us a complete picture. It's the first time I feel that all of our procurement data is in one place."
-- G2 reviewer (Oil & Energy, Enterprise, May 2024)
An enterprise reviewer focused on tail spend (February 2024) wrote: "The negotiation features are so user-friendly, and our suppliers love it." The newer reviews repeat the point about time saved on repetitive requests and price comparisons.
The criticism concentrates in four places. The first and most consistent is that processes outside Procure Ai's integrations still need manual work. The oldest complaint on the page, from a utilities enterprise reviewer in September 2024, reads: "Some processes are not integrated yet so I have to do them manually." The same point recurs two years later:
"What I dislike about ProcureAI is the difficulty with integrating with certain applications/processes we have at the company I work with. This leads us to have manual processes along with the use of ProcureAI in our Procurement process."
-- G2 reviewer (Consulting, Enterprise, October 2026)
A mid-market analyst (October 2026, translated by G2) adds: "In certain processes, I have to load data or validate information, and that reduces automation."
Second, setup takes IT time. "The initial setup and integration with legacy ERP systems can feel a bit steep and time-consuming, requiring significant IT coordination to get right," wrote an associate account executive (Mid-Market, October 2026), and a team coordinator at a small business (October 2026) called setup and integration with their existing system "complex and time-consuming."
Third, several newer reviewers find the interface harder to navigate than the 2024 reviewers did. A marketing specialist (Enterprise, October 2026) wrote: "Sometimes the interface can be a bit confusing, and it takes time to find the right options. It could also be faster when processing requests, especially when there are multiple steps involved." A small-business reviewer (October 2026) found it "a little slow."
Fourth, the 2024 reviews describe a small support team that was slow to respond at first but resolved issues well. "It's still a small team and I had to wait a bit for my request to be addressed but then the team resolved it above expectations," wrote an enterprise reviewer (February 2024), and a mid-market retail reviewer (March 2024) mentioned "minor communication issues here and there due mostly to the current size of organization." Both reviews predate Procure Ai's 2025 funding round, so ask how support is staffed for your region today.
For an evaluation, this means the organic reviews support our read above of Procure Ai as a capable agent layer for intake and tail spend, and the recurring faults sit at the integration boundary: setup needs IT coordination, and any process or system not yet connected falls back to manual work. No reviewer in either group describes sourcing engineered parts from drawings, revisions, or BOMs. Because the base is small and two-thirds of it came from one incentivized campaign, ask Procure Ai for enterprise references running on your own ERP and eProcurement stack, and map which of your processes its connectors cover today. In our assessment, those integration-boundary faults are the ones that grow with an organization, since every new system, plant, or region adds another boundary to connect.
LightSource's review page is publicly archived, and the quotes below are verbatim, verified against that archive. The most specific reviews describe the direct-materials workflow this page is about:
"The platform allows for the seamless addition of RFP items/SKUs and BOM details through a simple drop/drag feature... The platform also has a robust set of analysis tools to quickly compare the different supplier responses, calculate forecasted savings and identify best of the best pricing for the RFP... We typically see a company deploy LightSource within a day or two."
-- G2 reviewer (Mid-Market, 2024)
"Having the cost and quoting information in a single location helps with rapid product launches and better visibility for our leadership group."
-- G2 reviewer (VP of Supply Chain, Mid-Market, 2024)
On the critical side, the recurring LightSource theme is supplier adoption rather than the product itself: "The biggest challenge of LightSource is just getting the suppliers to try it. Once they try it --- they're also hooked," per a G2 reviewer (Mid-Market, 2024).
When to choose what
Choose Procure Ai if
You run a European enterprise on SAP, Ariba, Coupa, or a similar estate, want intake, tactical sourcing, and tail-spend negotiation automated without replacing any of it, and have the IT capacity to connect it across that estate.
High-volume indirect requests are the pain: you want guided, dialog-based intake and a majority of quote-to-order requests handled without a buyer touching them.
You want one agent layer and a unified spend data store across fragmented S2P systems, with measurable savings on tail negotiations (Procure Ai reports 4.7 to 4.9 percent on average).
A private-cloud deployment option (noted by a G2 reviewer), European offices, and SAP partner alignment matter to your IT organization; its platform page documents two-factor login and IP restrictions, so confirm SSO and SCIM support directly.
Your sourcing events are price-competitive purchases with interchangeable suppliers, or renewals and price-increase negotiations on SAP S/4HANA tail materials, rather than spec packages with drawings.
Choose LightSource if
Your spend is engineered components: quoting means drawings, revisions, and spec packages, not description strings.
Award decisions need cost breakdowns, BOM roll-ups, and per-supplier price history behind them rather than a single unit price.
You are launching new products and need fast first quotes on parts with no purchase history, with engineering in the loop.
You want a quoting supplier network on day one: 100,000+ suppliers live, free for suppliers, onboarding in under 30 minutes.
You want sourcing live in days on flat files, with implementation and integrations included in one platform fee, without an enterprise-platform price floor (Procure Ai's AWS Marketplace list is $250,000 per year) or an integration program before value shows up.
You need enterprise controls and AI access from day one: SSO, SCIM, access groups, and approval chains, plus an MCP server and a full GraphQL API that Claude, ChatGPT, Copilot, or your own agents can operate.
RUNNING BOTH
Not as a stack for direct materials. A professional procurement organization runs LightSource for the part decision, from BOM ingestion through RFQs, cost breakdowns, and award scenarios, with its ERP as the transactional backbone and purchase orders going out through the ERP. Procure Ai is a separate agent layer over the ERP and eProcurement suite, with its own subscription and integration program. An enterprise that wants agents on high-volume indirect requests can evaluate it for the indirect team, while production materials and their price history stay in LightSource so one system holds each part decision.
Frequently asked questions
Is LightSource a replacement for Procure Ai?
For direct materials it can be: LightSource covers the BOM sourcing, should-cost comparison, and award scenarios that Procure Ai's direct-procurement page markets, on the part record that page does not describe, so a manufacturer does not need both for production spend. Procure Ai's core use is different: automating high-volume indirect intake and tail-spend negotiation inside an existing ERP or S2P estate. LightSource handles strategic indirect categories through its indirect RFx and leaves catalog buying and purchase orders to the ERP or P2P system.
Can LightSource and Procure Ai work together?
They are not a stack for direct materials. A professional procurement organization runs LightSource for part-level sourcing, with BOM ingestion, RFQs with drawings, cost-breakdown analysis, and award scenarios, and exports awarded pricing to its ERP through the GraphQL API, where purchase orders go out through normal channels. Procure Ai is a separate agent layer over the ERP and eProcurement suite with its own subscription and integration program; an enterprise that wants it for high-volume indirect requests can evaluate it on those terms and keep production materials in LightSource.
Does Procure Ai support BOMs, engineering drawings, or direct materials sourcing?
Procure Ai now markets part of this. As of November 2026, its direct-procurement page for SAP S/4HANA says its agents can source entire Bills of Materials, renew call-off contracts and scheduling agreements, negotiate SAP info records, check price increases against indices and should-cost calculations, take index-linked prices in bids, and simulate award scenarios with dual-sourcing and capacity rules. Engineering drawings, revisions, and part records appear nowhere in its public materials, no PLM connector is named, its flagship manufacturing testimonial still covers non-production material, and no G2 reviewer describes sourcing parts from drawings, revisions, or BOMs. In our evaluation that covers pricing and award decisions for materials already in the ERP; sourcing an engineered part from its drawing is the gap this comparison turns on.
Which is better for direct materials sourcing?
LightSource. It is built entirely around parts: a revision-managed item master, nested BOMs with cost roll-ups, part-level RFQs with drawings, flexible cost breakdowns, AI award scenarios, and per-supplier price history, plus 100,000+ suppliers live on a free supplier network, and it goes live in days with implementation included. Procure Ai's direct-procurement page markets BOM sourcing, should-cost checks, and award scenarios over SAP records, but publishes no part record, drawing handling, or revision control behind them.
How is each product priced?
Procure Ai does not publish pricing on its own site; its AWS Marketplace listing shows $250,000 per year for a 12-month contract covering all modules, with larger revenue tiers paying more, private offers available, no refunds, and AWS infrastructure costs possible on top. Our estimate for a typical enterprise deployment, including vendor-led onboarding and integration, is $325K to $500K a year. LightSource is priced as an all-in platform fee that includes implementation and integrations, and suppliers are always free.
How long does each take to implement?
LightSource customers go live in days on flat files and typically run their first sourcing in about 30 days, with implementation included. Procure Ai publishes no timeline; it pitches modular, no-rip-and-replace deployment with forward-deployed engineers and offers hosting in the customer's own infrastructure, which in our assessment brings an enterprise IT review. Our estimate is one to three months for a first module and longer for a full estate, and several G2 reviewers describe setup and ERP integration as time-consuming, with some processes not yet integrated.
Sources
Procure Ai homepage: positioning, customers, and reported savings
Procure Ai autonomous sourcing module: tactical and tail-spend focus
tech.eu: Procure Ai nets $13M to scale autonomous AI for procurement
Procure Ai reviews on G2: 4.4/5 on 27 reviews, including the dislike sections (November 2026)
CNBC: LightSource raises $33M co-led by Lightspeed and Bain Capital Ventures
LightSource: product, supplier network, and customer results
Tracxn: Procure AI company profile, one $13M funding round and 56 employees (October 2026)
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.

