LightSource vs. Pactum

Pactum, founded in 2019, runs AI agents that negotiate indirect purchase requests and supplier terms such as payment days, discounts, and rebates. In our assessment it is a narrow negotiation layer that depends on the systems around it: its widest agent coverage runs only inside Coupa, and the direct-materials pages it published in 2025 and 2026 have been withdrawn. LightSource is the Direct Materials Operating System, spec through scale, PLM through ERP: the enterprise-ready system of record where manufacturers decide who should make each part and at what price, live in days with implementation included and suppliers always free.

Last reviewed

· Based on public information ·

Side-by-side comparison: LightSource vs Pactum, a short summary plus 8 attributes
Attribute
LightSource
Pactum
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.Pactum: Pactum, founded in 2019, runs AI agents that negotiate indirect purchase requests and supplier terms such as payment days, discounts, and rebates. In our assessment it is a narrow negotiation layer that depends on the systems around it: its widest agent coverage runs only inside Coupa, and the direct-materials pages it published in 2025 and 2026 have been withdrawn.
Built forLightSource: Direct materials, spec through scale: parts, BOMs, NPI programsPactum: Autonomous indirect procurement from intake to negotiated PO, plus supplier-wide terms campaigns
Core questionLightSource: Who should make this part, and at what price?Pactum: How do we negotiate the thousands of requests and supplier agreements no buying team has time to touch?
ArchitectureLightSource: AI-native direct materials operating system, built around the part recordPactum: Six AI agents (intake, policy alignment, single-source negotiation, tactical sourcing, advanced sourcing, post-sourcing negotiation) plus Campaigns; runs in Coupa, SAP Ariba, the Pactum API, or standalone, but coverage narrows away from Coupa: three agents run in SAP Ariba and only single-source negotiation runs through the Pactum API, as of November 2026
ImplementationLightSource: Live in days on flat files; sourcing in about 30 days; implementation includedPactum: Pilot live in 2-4 weeks, per Pactum; implemented by Pactum, with no system-of-record migration. Full rollout takes longer: its direct-materials showcase customer had only begun the infosec approval for full system integration in year two, and custom integrations beyond Coupa and SAP Ariba are scoped before signing
Pricing modelLightSource: All-in platform fee: configuration, integrations and implementation included; suppliers always freePactum: Annual subscription sized by company revenue band and the agents chosen, with a 12-month minimum; list prices not published. Vendor states no savings share, per-user or per-negotiation fees. Our estimate for a typical deployment: $250K to $400K a year, scaled up from Fortune's 2021 figure of $120,000 a year plus gain share to reflect the larger agent lineup and custom integration work
Supplier networkLightSource: 100,000+ suppliers live; free supplier workspace; AI discoveryPactum: No supplier network; works your existing suppliers, and its Tactical Sourcing agent finds and invites alternatives for RFQs
Target customerLightSource: Manufacturers from growth stage to enterprise divisionsPactum: Enterprises, typically above $250M in revenue per its pricing page, which also lists a band for companies under $1B; named customers are Global 2000 (Walmart, Honeywell, SUEZ). In our assessment it pays off only where a large indirect tail supplies the negotiation volume
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 SourcingPactum: Founded 2019; G2 4.5/5 on 1 vendor-invited review, no Capterra or GetApp reviews, and 3 on a major analyst peer-review site, as of November 2026; reviewers praise ease of use and note setup needs defined rules and good data; Hackett 50 to Watch 2025-26, covered in its 2026 contract management guide; about 20 named customers, and most public evidence of results comes from Pactum's own releases and press accounts of the Walmart pilot.
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 +1PactumShould-costSpec-aware RFQs +4PricecomplianceBoth direct and indirectLightSourceCategorymanagementSupplierdiscoveryContracts · Supplier onboarding +2PactumSpendanalyticsSupplierdiscoveryContractsSupplier portals · SRM · Invoices & APIndirectLightSourceIndirect RFx · MROStrategicindirectPactumIntakeSaaS spendIndirectRFxTail spendStrategicindirectRenewals +1LightSource · nativepartialPactum · nativepartialclaimed, not evidenced
Concentrated on the Indirect row, stages 1 to 4: intake and policy checks, RFQs and RFPs, single-source and tail negotiation, plus supplier terms campaigns. LightSource runs direct materials from Define and intake through Scale and sustain on part records; Pactum negotiates requisitions and terms, mostly indirect.
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; Pactum rates Strong on 5, Moderate on 7, Limited on 20, Integrates on 2, Not offered on 16 and Not documented on 7.

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 Pactum, 57 capabilities in 13 groups
Capability
LightSource
Pactum
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
Pactum: Not offered.
Outside scope; no item master or part record, as agents start from requisitions, bids or supplier lists
BOMs: LightSource: Strong.
Multi-level BOMs with cost rollup from quotes or contracts, revision diffs and cost history charts
Pactum: Not offered.
Outside scope; no BOM, revision or drawing model anywhere in its public documentation
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
Pactum: Limited.
Material Intelligence (Jul 2026) mapped materials to price indices; no cleansheets, VAVE or design-to-cost
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
Pactum: Not offered.
Outside scope; integrations cover Coupa, SAP Ariba and the Pactum API, with no PLM connector
Category management and strategy: LightSource: Moderate.
Item categories with their own properties, category charts and Programs give category plans a live data spine
Pactum: Not documented.
Not publicly documented; Alignment turns existing category strategies into rules, with no spend segmentation
Intake and orchestration: LightSource: Not offered.
By design, work starts at the item, BOM or Sourcing project; engineers raise needs in the Engineering role
Pactum: Moderate.
Native: Intake Agent in Teams or P2P, plus Alignment policy checks (1M+ run); approvals stay in the P2P
2 · Discover suppliers
Supplier engagement and early involvement: LightSource: Strong.
Early supplier involvement and design collaboration: data rooms, RFIs, threads, drawings shared by revision
Pactum: Not offered.
Outside scope; agents engage suppliers at the requisition or RFx, with no DFM or early involvement
Supplier capability mapping: LightSource: Strong.
Supplier Discovery searches by process or material; profiles hold specialties, sites, tags and properties
Pactum: Not documented.
Not publicly documented; the Tactical agent finds alternative suppliers, with no capability 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
Pactum: Not offered.
Outside scope; negotiation agents over P2P requisitions, with no part, BOM, award or contract record
Supplier discovery: LightSource: Strong.
Supplier Discovery across 100,000+ suppliers by process or material; LightSource contacts the ones you pick
Pactum: Limited.
Marketed: Tactical Sourcing agent finds and invites alternative suppliers; no supplier network or database
GPOs and buying consortia: LightSource: Not offered.
Out of scope by design; competitive Sourcing projects across 100,000+ suppliers set your own pricing
Pactum: Not offered.
Outside scope; no GPO or buying-consortium 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
Pactum: Limited.
Native: RFQs built from requisitions or an uploaded spec or scope; no BOM lines, drawings or revisions
Quote breakdowns and normalization: LightSource: Strong.
Quote formats with flexible cost breakdowns; AI normalizes any quote; bids compared in one currency
Pactum: Limited.
Native: lines up bid-sheet items and compares final offers on value; no cost breakdowns or outlier flags
Iterative pricing and re-quotes: LightSource: Strong.
RFQ versions and rounds, per-supplier updates and quote history compared across rounds; Item Cost Walk
Pactum: Limited.
Native: Post-Sourcing agent negotiates every bid over several rounds; 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+
Pactum: Not offered.
Outside scope; Pactum negotiates with suppliers 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
Pactum: Moderate.
Native: Tactical RFQs, buyer-led Advanced Sourcing RFPs and post-RFx rounds; e-auctions not documented
4 · Contract and award
Award and nomination: LightSource: Strong.
Award scenarios with splits, suggested and AI-optimized plans, sequenced approvals; awards create contracts
Pactum: Limited.
Native: ranked final offers compared on value and the buyer awards; no award scenarios or nominations
Pricing formulas: LightSource: Strong.
Formula fields in quote formats price from item properties; per-period volumes and terms set at award
Pactum: Not documented.
Not publicly documented; agents trade price, payment terms and lead time, not 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
Pactum: Limited.
Price List agents (2025) argued from ERP price history and commodity indices; no benchmark library
Contract management: LightSource: Strong.
Awarded contracts with price, volume, terms, expiry tracking and pricing history; authoring stays in your CLM
Pactum: Limited.
Negotiated terms post back to the P2P; Hackett notes it is not a CLM; no authoring or redlining
Tail-spend management: LightSource: Not offered.
No tail-spend desk or spot-buy channel; built for planned direct and strategic buys
Pactum: Strong.
Native: tail and messy-middle buys competed or negotiated at scale; Walmart in production since 2021
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
Pactum: Not offered.
Outside scope; no APQP, PPAP, FAI 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
Pactum: Not offered.
Outside scope; no tooling, prototype or pilot-build tracking
Supplier onboarding and information: LightSource: Strong.
Suppliers join free by invitation; RFI qualification, certificates in data rooms, ERP vendor sync
Pactum: Not documented.
Not publicly documented; Campaigns validate supplier contacts, with no registration or certificate capture
6 · Ramp and launch
Production ramp and timelines: LightSource: Moderate.
Programs track awarded projects, open items and milestones per project; suppliers see the milestones
Pactum: Not offered.
Outside scope; a lead-time negotiation module exists, with no launch timeline or ramp 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
Pactum: Not offered.
Outside scope; no sub-tier mapping or pre-qualified alternates for parts
Supplier collaboration portals: LightSource: Strong.
Free for suppliers, onboarding in under 30 minutes: RFQs, Excel round-trip quotes, messages, data rooms
Pactum: Moderate.
Native: suppliers negotiate in chat or bid by link; 83% of Walmart suppliers called the bot easy to use
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
Pactum: Limited.
Native: Alignment checks requests against contracts before the PO; no index cycles or invoice match
Engineering changes and cost-downs: LightSource: Strong.
Item and BOM revision diffs reach live RFQs as pending changes; Re-source, Programs and Savings projects
Pactum: Limited.
Native: requisition negotiation on engineered parts at one energy customer; no ECO intake or re-quotes
SRM and supplier performance: LightSource: Strong.
Weighted Scorecards, Book Of Business per supplier, data rooms with AI document analysis, contacts
Pactum: Limited.
Native: Campaigns renegotiate terms across the supplier base; no scorecards or performance reviews
Renewals and vendor consolidation: LightSource: Not offered.
Indirect renewal calendars are out of scope; direct contract expiry is tracked under Contracts
Pactum: Limited.
Native: SaaS renewals via Advanced Sourcing and post-M&A terms harmonization; no renewal calendar
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
Pactum: Not offered.
Outside scope; no scheduling agreements, releases, EDI or ASNs; negotiated prices write back for the PO
ERP and MRP (system of record): LightSource: Integrates.
ERP stays the transactional record; supplier master syncs both ways and awarded pricing flows into it
Pactum: Integrates.
Configured: Coupa and SAP Ariba APIs or the Pactum API; outcomes post back to the requisition or event
Invoice, AP automation and payments: LightSource: Integrates.
Invoicing and payment stay in your ERP or AP; Awarded contracts send agreed prices and payment terms
Pactum: Limited.
Native: Campaigns win early-pay discounts and enroll suppliers in SCF (early access); no invoices or AP
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
Pactum: Limited.
Native: Intake Agent drafts coded requisitions and steers to Coupa catalogs; POs issue in the P2P
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
Pactum: Not offered.
Outside scope; negotiates delivery and lead time but is not a planning, TMS or WMS system
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
Pactum: Limited.
Native: reports savings on negotiations its agents run; no spend cube or classification documented
Risk monitoring and third-party risk: LightSource: Moderate.
AI Document Analysis flags expired certificates; supplier status and Scorecards; risk feeds connect by API
Pactum: Not documented.
Not publicly documented; agents negotiate commercial terms, with no supplier risk feeds 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
Pactum: Not documented.
Not publicly documented; no sustainability ratings, Scope 3 or diversity features found
Master data management: LightSource: Integrates.
Items and suppliers mastered against PLM and ERP by external ID; AI duplicate detection and merge
Pactum: Integrates.
Configured: supplier records read live from Coupa or Ariba, mapped per tenant; no golden-record 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
Pactum: Not documented.
Not publicly documented; no HTS codes, tariff classification or duty features on its site
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
Pactum: Limited.
Marketed: Advanced Sourcing agent targets professional services and contract labor RFPs; no VMS or SOWs
SaaS and software spend: LightSource: Not offered.
Out of scope by design; LightSource is built for direct materials, not SaaS licenses
Pactum: Limited.
Marketed: Advanced Sourcing agent names SaaS renewals; no app discovery, license or seat tools
T&E, cards and expense: LightSource: Not offered.
Out of scope by design; LightSource is built for direct materials, not travel or expenses
Pactum: Not offered.
Outside scope; no travel or expense tools; Campaigns can enroll suppliers in your card program (early access)
MRO: LightSource: Moderate.
MRO sourcing runs as Sourcing projects with awarded contracts; storeroom, min-max and CMMS stay out of scope
Pactum: Limited.
Native: Campaigns name MRO and industrial supplies as best fit for terms negotiation; no storeroom tools
Strategic indirect: LightSource: Strong.
Freight lanes, rate cards and capex run as Sourcing projects; Ocean Freight and Capex quote templates
Pactum: Moderate.
Native: Maersk spot trucking lane negotiations since 2021; no lane bid scenarios 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
Pactum: Strong.
Native: negotiation agents are the product; largest AI-closed deal $140.5M, about 13 minutes per negotiation
Agentic and autonomous operation: LightSource: Strong.
Agents draft quote formats, bid views and award plans; autonomous sourcing; BYO agents (Claude, OpenAI) by API
Pactum: Strong, Negotiation agents.
Native autonomous negotiation since 2021, advisory to fully autonomous; closed to outside agents, no 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
Pactum: Limited, Narrow API, no MCP.
No MCP or outside-agent access documented; the Pactum API carries only single-source negotiation requisitions
Direct-materials focus: LightSource: Strong.
Built around parts: drawings, revisions, multi-level BOMs, tooling and ED&T costs, cost breakdowns
Pactum: Limited.
Site now leads with indirect; direct use is part-buy negotiation, e.g. turbine parts at one energy customer
NPI support: LightSource: Strong.
Revision-aware RFQs, target costs and should-costs for new parts, Engineering role, Programs for launches
Pactum: Not offered.
Outside scope; no engineering collaboration or new-part sourcing; agents start from a requisition
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
Pactum: Strong, Vendor-led.
Pactum implements Coupa and SAP Ariba links in the subscription; other stacks need a scoped custom build
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
Pactum: Moderate, Pilot in weeks.
Pilots live in 2 to 4 weeks per Pactum; its energy customer still lacked full system integration in year two
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
Pactum: Moderate, Quote-only, mid TCO.
Quote-only by revenue band, 12-month minimum; Fortune put the 2021 fee at $120K plus gain share; our estimate: $250K to $400K a year all-in
SMB fit: LightSource: Moderate, Medium.
Self-serve start suits small teams; overpowered for organizations without two or more procurement heads
Pactum: Not offered, Not a fit.
Typically works with companies above $250M in revenue, per Pactum; no self-serve plan, trial or sub-year term
Mid-market fit: LightSource: Strong, Core market.
Lean teams run it self-serve; enterprise controls available, not required
Pactum: Moderate, Stretch.
Growth band for under $1B, typically from $250M; in our assessment value needs a large negotiation tail
Enterprise readiness: LightSource: Strong, Enterprise-ready.
Used by global organizations such as Amazon, BRP and Yum! Brands; SSO, SCIM, access groups, approval chains
Pactum: Strong, Core, Coupa-first.
Walmart, Honeywell and Novartis run it; SSO, SOC 2 Type 2; widest agent set only in Coupa; no SCIM 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 Pactum is genuinely strong

Pactum's strength is narrow and real: it pioneered autonomous supplier negotiation on buys someone has already defined, and has run it in production at serious scale since 2021. As of November 2026 it describes itself as autonomous procurement for indirect and supplier engagement: six AI agents take a request from intake through policy checks, RFQs, and negotiation to the purchase order, and its Campaigns agents negotiate payment terms, discounts, and rebates with thousands of suppliers in parallel, inside Coupa or SAP Ariba, through the Pactum API, or on their own. The public results are real. Walmart's pilot reached agreement with 64 percent of participating suppliers against a 20 percent target, with average savings of 1.5 percent and payment terms extended to 35 days, and by January 2023 Pactum reported deals with 68 percent of the suppliers approached at average savings of 3 percent. Maersk began using it for spot trucking rates in 2021, with Pactum reporting 96 percent lane conversion at prices 22 percent below human test groups. The company says its largest single autonomously negotiated deal was $140.5 million and its fastest took 87 seconds.

Two things stand out beyond the numbers. Suppliers appear to like the experience: Pactum reported in January 2023 that 83 percent of Walmart's suppliers found the bot easy to use, a figure HBR's November 2022 account of the pilot also carries, and Bloomberg reported in April 2023 that nearly three in four suppliers preferred negotiating with the bot; Pactum's customer page now puts that preference at 82 percent for a Walmart payment-terms campaign. And it creates value where competitive sourcing is not an option: sole-source renewals, single-source requisitions, and working-capital campaigns across a long tail no buying team has hours to touch. It is venture-backed, with a $54 million Series C led by Insight Partners in June 2025 and more than $100 million raised in total, and by Pactum's November 2026 count more than 50 global enterprises run $55 billion of spend through it, including Honeywell, SUEZ, and Ahold Delhaize USA.

The Hackett Group's 2026 contract management guide notes that Pactum is not a CLM provider but is often evaluated against one, describing an autonomous negotiation solution for large ($5B+ revenue) organizations, and placed Pactum on its 2025-2026 '50 to Watch' list.

Where LightSource is the system of record

LightSource owns the decision Pactum does not attempt: who should make a part, and at what cost structure. It runs that decision on an enterprise-ready platform that goes live in days. That work starts from the part itself. Items arrive by AI ingestion from Excel, PDFs, and drawings into a revision-managed item master. Nested BOMs carry snapshots, diffs, and cost roll-ups. RFQs go out at part level with drawings attached, from three-bids-and-a-buy to multi-round strategic events, against a network of 100,000+ live suppliers where onboarding is free and takes under 30 minutes. 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.

Quotes come back in any format and AI normalizes them into comparable line items. LightSource is the only sourcing solution with true flexible cost breakdowns: category-specific bid sheets per event, so a casting quote and a PCB quote each get compared on the cost structure that matters for that category. AI drafts award scenarios, including split awards, a buyer approves the decision, and awards become tracked contracts with per-part, per-supplier price history that survives buyer turnover. Manufacturers from Infinite Machine to BRP, Canada Goose, Shure, and Yum! Brands run this loop today, live in days on flat files and sourcing in about 30 days, with implementation included. Enterprise controls come standard, with SAML single sign-on, SCIM provisioning, access groups, and approval chains, and reviewers rate it 4.9/5 on G2, among the highest ratings in the procurement category.

None of this exists in Pactum, and that is by design. Its public documentation has no item master, BOM, revision, drawing, or award-scenario concept; its agents start from a purchase request in the P2P or Teams, the bids from a closed RFx, or an uploaded list of supplier contacts and current terms. When the question is a new part or a design revision, there is no part record for an agent to start from.

Different units: agreement versus part

The structural difference is what each product models, and Pactum's model stops at the request and the agreement: what was asked for, which policy and contract apply, what the current terms are, and how far an agent may move in a negotiation. As of November 2026 its site leads with indirect procurement, and the Price Lists and Material Intelligence pages that described its direct-materials work in 2025 and 2026 are no longer published. Its current direct-materials evidence is a customer story: a global energy technology company that has used requisition negotiation since mid-2025 on engineered components such as gas turbine parts, instrumentation, and flow components, and co-developed a module that negotiates lead time alongside price. By Pactum's own account that work is still early: about $9 million of spend went through it in the first year, and in year two the customer had only begun the infosec approval that would allow full system integration. That work negotiates the price and delivery of a part someone has already specified; it does not build a cleansheet from part geometry or process steps.

LightSource models the part. A revision-managed item with drawings sits at the center, BOMs aggregate items into products, RFQs carry the engineering context to suppliers, and cost breakdowns decompose what comes back. That model is what lets a buyer answer questions Pactum does not pose: which of five capable suppliers should make this bracket, what happens to landed cost if the award splits two ways, what revision C did to assembly cost.

The overlap is narrow: tactical RFQs on simple buys, where Pactum's Tactical Sourcing agent now finds and invites alternative suppliers; indirect RFx, where Pactum's Advanced Sourcing agent runs multi-round RFPs and LightSource runs RFQs for strategic indirect categories such as freight lanes and capex; and negotiation on parts that are already specified, as at the energy customer. Pactum has genuine manufacturing customers, including Honeywell and that energy technology company, so it does touch direct-material spend. It works on the price, terms, and lead time of a requested buy, while the part definition, the BOM, and the cost-structure comparison stay upstream.

Pactum as an optional indirect add-on

For direct materials, a professional organization runs LightSource as its sourcing system with its ERP as the transactional backbone, and purchase orders go out through the ERP. LightSource runs the sourcing decision: ingest the BOM, send part-level RFQs against the network, analyze cost breakdowns, model award scenarios, and record the award as a tracked contract with price history. Pactum has no role in that loop. In our assessment it earns a place only in a large enterprise that already runs Coupa or SAP Ariba for indirect spend and carries a long tail of incumbent agreements nobody revisits; there its agents campaign payment terms, discounts, and rebates and negotiate single-source requisitions between sourcing cycles.

In our assessment the boundary is clean because each system stops where the other starts. Pactum does not create parts, BOMs, or award scenarios, and it has no supplier network of its own. LightSource's agents draft quote formats, bid views, and award plans, and it runs autonomous sourcing; supplier-wide terms campaigns sit outside it, and its MCP server and GraphQL API, which mirrors the whole platform, let Claude, OpenAI, and other agents operate it and pass item, quote, and award data to whatever negotiation or P2P agents an enterprise runs downstream.

What public reviewers say

As of November 2026, Pactum's G2 profile carries a single review, rated 4.5 out of 5 and collected through a vendor invitation, as G2 labels it. Its listings on Capterra and GetApp show no user reviews, and a major analyst peer-review site shows three. On G2, LightSource holds 4.9 out of 5 on G2, among the highest ratings in the procurement category. Pactum sells large enterprise programs to a base of more than 50 global enterprises, a segment that rarely writes public reviews, so the low count is not by itself a sign of weak results. It does leave a buyer with little independent customer feedback: most of the public evidence for Pactum's results comes from its own releases and customer stories and from press accounts of the Walmart pilot.

Reviewers praise ease of use, a responsive vendor team, and less manual negotiation work. The one G2 reviewer, at an enterprise manufacturer, uses Pactum for "automated negotiations with tail end suppliers & running simple basic sourcing events" and wrote:

"Easy to use and navigate, AI assistant in new Advanced sourcing is useful, Pactum team is helpful and ready to receive feedback and improvement suggestions"

-- G2 reviewer (Verified User in Manufacturing, Enterprise, October 2026)

The strongest public endorsement may come from the other side of the table: Pactum's own January 2023 release reported that 83 percent of Walmart suppliers described the bot as easy to use and liked being able to make counteroffers, HBR's November 2022 account of the pilot carries the same ease-of-use figure, and Bloomberg reported in April 2023 that nearly three in four suppliers preferred negotiating with the bot.

The criticism is mild and falls under two headings. The first is setup. On a major analyst peer-review site, none of the three reviews is critical, and the two we could read come from IT and software companies with under $250 million in revenue, smaller than the Global 2000 enterprises Pactum names as customers. Those reviewers credit Pactum with a simple interface, less manual negotiation work, and value found in long-tail contracts, and add that it runs smoothly only once workflows and rules are configured, works best on standardized procurement processes, and needs clear process design and good data to deliver results.

The second is product polish. The G2 reviewer, who uses the new Advanced Sourcing agent, lists one dislike: "Still some small bugs in some functionalities" (Verified User in Manufacturing, Enterprise, October 2026). It is one review, and it is the only fault a customer has posted about Pactum on G2 or Capterra. In our assessment both themes fit a young product that runs best on standardized, well-configured buys and asks more of the buyer as the work gets more complex.

For an evaluation, this means Pactum's public record is consistent with its claims for tail spend and supplier campaigns but too small to show patterns across many customers. The reviewers who explain their use cases mention tail-end negotiations, simple sourcing events, and standardized workflows, which fits the boundary drawn above. Ask for reference calls with customers in your industry, plan time to define negotiation rules and clean supplier and spend data before the first campaign, and ask which agents are generally available and which are still in early access.

LightSource's reviews are specific about why teams adopt it. A vice president of supply chain wrote: "Having the cost and quoting information in a single location helps with rapid product launches and better visibility for our leadership group. It's got its quirks, but the constant updates are promising." G2 reviewer (Mid-Market, 2024). Another reviewer's caveat doubles as a read on the supplier network: "The biggest challenge of LightSource is just getting the suppliers to try it. Once they try it --- they're also hooked." G2 reviewer (Mid-Market, 2024).

When to choose what

Choose Pactum if

  • You have thousands of incumbent supplier agreements (payment terms, rebates, discounts) that nobody has time to renegotiate, and you want AI agents working them in parallel.

  • Working capital is the goal: Pactum reports a median gain of 30 payment days where suppliers improved their terms, and more than $21 million in discounts and early-payment discounts won by its Campaigns agents.

  • You negotiate sole-source renewals, single-source requisitions, or spot logistics rates, situations where a competitive sourcing event is not an option.

  • You want indirect requests taken from intake through policy checks, RFQs, and negotiation to a purchase order without migrating any system of record, and you run Coupa, where its widest agent coverage sits; SAP Ariba carries three of its agents, and other P2P systems connect through the Pactum API, built on your side.

Choose LightSource if

  • Your spend is engineered parts with drawings and revisions, and the question is who should make each part and at what cost structure.

  • You need a system of record for items, BOMs, quotes, and awards that survives buyer turnover, from PLM through ERP.

  • You want competitive part-level RFQs against a network of 100,000+ suppliers, with AI quote analysis, flexible cost breakdowns, and award scenarios a human approves.

  • You source new parts in NPI, where there is no incumbent agreement to negotiate and speed to first quote decides the launch date.

  • You want enterprise controls and an open platform from day one: SAML single sign-on, SCIM provisioning, access groups, approval chains, and an MCP server and full GraphQL API that Claude, ChatGPT, or your own agents can operate, on an all-in platform fee with suppliers always free.

  • You are a lean or mid-market team that needs to be live in days with implementation included; Pactum lists a band for companies under $1B in revenue but says it typically works with companies above $250M.

RUNNING BOTH

Not as a stack for direct materials. A professional manufacturing organization runs LightSource for sourcing with its ERP as the transactional backbone, and purchase orders go out through the ERP; LightSource holds the item master, BOMs, cost breakdowns, and award record. Pactum is a separate, optional purchase for a large enterprise that already runs Coupa or SAP Ariba for indirect spend and has a long tail of incumbent agreements nobody revisits, where its agents campaign payment terms, discounts, and rebates. If you buy it for that, LightSource's GraphQL API can feed it item, quote, and award data.

Frequently asked questions

Is Pactum a competitor to LightSource?

Not directly. Pactum's AI agents negotiate purchase requests and supplier terms, mostly in indirect spend and mostly inside Coupa or SAP Ariba, while LightSource is the Direct Materials Operating System where manufacturers run competitive part-level sourcing and keep the record of items, BOMs, quotes, and awards. Their capabilities overlap only on tactical buys and indirect RFQs, and a manufacturer's direct-materials loop runs on LightSource and its ERP without Pactum.

What is the main difference between LightSource and Pactum?

The unit of work. Pactum's unit is a negotiation: an AI agent closing price, payment terms, or lead time on a purchase request, or payment terms, discounts, and rebates across a supplier base, thousands of times in parallel. LightSource's unit is a sourcing decision: a part-level RFQ with drawings, AI quote analysis with cost breakdowns, and an award a human approves, on a platform that goes live in days with implementation included.

Does Pactum support direct materials sourcing?

At a narrow and early layer. As of November 2026 Pactum's site leads with indirect procurement, and its 2025 Price Lists pages for direct materials are no longer published. Its current direct-materials example is a global energy technology company that has used requisition negotiation since mid-2025 on engineered components such as gas turbine parts, negotiating lead time alongside price on parts already specified; Pactum reports about $9 million of spend through it in the first year, with full system integration still awaiting infosec approval. It has no BOM, drawing, revision, or item-master model, so competitive sourcing of engineered parts sits outside its scope.

Can LightSource negotiate with suppliers automatically like Pactum does?

LightSource negotiates through competition: multi-round part-level RFQs in which its agents draft quote formats, bid views, and award plans, plus autonomous sourcing, and Claude, OpenAI, and other agents can operate it through its MCP server and GraphQL API. Supplier-wide campaigns on payment terms, discounts, and rebates across an incumbent base are Pactum's specialty, and LightSource's award data can feed a tool built for that work.

Can you use LightSource and Pactum together?

For direct materials you do not need to. A professional organization runs LightSource with its ERP, and purchase orders go out through the ERP. An enterprise that also runs Coupa or SAP Ariba for indirect spend can add Pactum to campaign terms across its incumbent supplier base, and LightSource's GraphQL API exposes item, quote, and award data for that downstream work.

How do LightSource and Pactum pricing models differ?

LightSource is priced as an all-in platform fee, with implementation included, suppliers always free, and go-live in days on flat files. Pactum does not publish list prices; its pricing page describes one annual subscription with a 12-month minimum, sized by company revenue band, from under $1B to $20B+, and by the agents chosen, with implementation included and no value share, success fee, or per-user or per-negotiation charge, while custom integrations beyond Coupa and SAP Ariba are scoped before signing. Our estimate for a typical deployment is $250K to $400K a year, scaled up from the $120,000 a year plus gain share that Fortune reported in 2021.

Sources

  1. Pactum homepage: indirect procurement positioning, six-agent lineup, 50+ enterprises and $55B of spend under management (November 2026)

  2. Pactum: Indirect Procurement agent lineup (November 2026)

  3. Pactum: Intake Agent (Teams and P2P requisition intake)

  4. Pactum: Single-Source Negotiation Agent

  5. Pactum: Tactical Sourcing Agent (RFQs, finds and invites alternative suppliers)

  6. Pactum: Advanced Sourcing Agent (buyer-led multi-round RFPs)

  7. Pactum: Post-Sourcing Negotiation Agent (negotiation after a closed RFx)

  8. Pactum: Integrations, what runs where (widest agent coverage in Coupa; three agents in SAP Ariba; single-source negotiation via the Pactum API; fetched Nov 19, 2026)

  9. Pactum customer page: 50+ enterprises, named customers, 82% Walmart supplier preference (November 2026)

  10. Pactum customer story: global energy technology leader, requisition negotiation on gas turbine parts; about $9M of first-year spend; infosec approval for full system integration begun in year two

  11. Pactum Campaigns: payment terms, discounts, rebates, M&A harmonization, SCF and card enrollment (early access)

  12. Pactum Alignment Agent: policy and contract checks inside existing P2P flows

  13. Pactum: $54M Series C led by Insight Partners (June 2025)

  14. Bloomberg: Walmart uses Pactum AI to handle vendor negotiations (2023)

  15. Grocery Dive: 2021 interview on Pactum's Walmart pilot

  16. Talk Business & Politics, June 2023: Walmart pilot (64% vs 20% target, 1.5% savings, 35-day terms) and 68% / 3% rollout figures

  17. Pactum via BusinessWire, January 2023: Walmart results, 83% of suppliers found the chatbot easy to use

  18. Harvard Business Review, November 2022: How Walmart Automated Supplier Negotiations

  19. Procurement Magazine: Pactum and Maersk autonomous freight negotiations

  20. G2: Pactum reviews (1 review, 4.5/5, as of November 2026)

  21. G2: Pactum review by an enterprise manufacturing user (October 2026)

  22. Capterra: Pactum listing, no user reviews (November 2026)

  23. GetApp: Pactum listing, no user reviews (November 2026)

  24. G2: LightSource reviews

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

  26. LightSource homepage: platform, customers, and supplier network

  27. Pactum pricing page (fetched Nov 19, 2026): annual subscription by revenue band, 12-month minimum, no savings share; custom integrations beyond Coupa and SAP Ariba scoped before signing

  28. Fortune, April 2021: Pactum's earlier license plus gain-share model

  29. G2: Pactum pricing not listed

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

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

  32. The Hackett Group: Contract Management Solutions guide (Sep 2026)

  33. LightSource integrations: SAML single sign-on and SCIM provisioning (Okta, Azure AD); connects to Claude, ChatGPT, Microsoft Copilot and Grok (fetched Nov 19, 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.