Ivalua

1.1 Identity and platform

Ivalua was founded in 2000 by David Khuat-Duy, and an August 2026 independent vendor profile places its headquarters in Redwood City, California (CO001, CO002). The product is positioned as an enterprise source-to-pay suite: sourcing, contracting, procurement, supplier management, payments and related processes share a unified data model (CO003). JAGGAER, a direct competitor, describes Ivalua as configurable and oriented toward complex procurement; that comparison is useful as attributed positioning, not as an independent benchmark (CO003). The operational implication is a wide workflow footprint, while the evidence does not establish implementation outcomes or customer economics.[CO001, CO002, CO003]

1.2 Financing, ownership and milestones

Public transaction histories indicate two earlier growth-equity rounds: KKR's reported $70 million investment in April 2017 and a $60 million round in May 2019, when the company announced a valuation above $1 billion (CO005-CO009). Ivalua's release described 2019 annual revenue as on pace to exceed $100 million; this is a company forecast, not a verified result, ARR, or current run rate (CO010). Multiples.vc reports an Hg acquisition on December 1, 2024 for an undisclosed price, while a later profile still lists earlier investors without clarifying the post-transaction ownership structure (CO004). The timeline therefore records reported events rather than implying current valuation or financing capacity. The stakeholder table is deliberately partial.[CO004, CO005, CO006, CO007, CO008, CO009, CO010, CO011]

1.3 Leadership and governance

Available sources identify founder David Khuat-Duy and name Franck Lheureux as CEO in an Ivalua-issued release; that release also identifies Khuat-Duy as Founder and Chief AI Officer (CO001, CO012). Its publication date is not visible in the fetched text, so it does not establish that these titles remain current on the report date. No assigned source supplies a complete executive or board roster, appointment history, control rights, or succession arrangements. The two named leaders give only a partial view of functional coverage; key-person dependence cannot be assessed from titles alone. The leadership table distinguishes attributed roles from diligence questions rather than treating an incomplete list as exhaustive.[CO001, CO012]

1.4 Scale, product claims and diligence limits

Ivalua's release says it is trusted by over 500 admired brands, but that company-reported brand reach is not an independently verified customer count (CO013). The same release describes IVA Studio and platform-level permissions and logging; those are product claims, not independently tested controls, and the fetched text does not establish the product's current availability (CO012). UpGuard's public page describes continuous security monitoring but does not expose a rating or check-level findings in the retrieved text (CO014). ERP Research reports lengthy implementations and a steep learning curve, while Lemon Learning, which sells in-application learning services, also characterizes adoption as a challenge (CO016). Current revenue, ARR, valuation, headcount, exact customer count, debt, and adverse-event status remain unverified in this assigned evidence set.[CO012, CO013, CO014, CO016]

1.5 Exhibits

2.1 Define the category before sizing it

Procurement software is a workflow category, not a synonym for all corporate spend or supply-chain technology. Mordor Intelligence describes procurement software as covering online ordering, purchase orders, invoice matching and payment, alongside electronic sourcing requests; Gartner's product description places Ivalua across sourcing, supplier management, contracts, procurement, and invoice processing. Those descriptions show material overlap, but do not establish that every procurement-software dollar is addressable by Ivalua. The more defensible company-relevant boundary is enterprise source-to-pay workflows spanning source-to-contract and procure-to-pay. Adjacent ERP, corporate-card, expense, and broader supply-chain budgets are not separately valued by the evidence available here and should not be added to the market total.[CM001, CM002]

2.2 Category growth is not an Ivalua TAM

Mordor Intelligence estimates the global procurement-software market at USD 9.81 billion in 2025 and USD 10.74 billion in 2026, and forecasts USD 17.11 billion by 2031, a 9.76% CAGR for 2026–2031. Its application, organization-size, and regional cuts indicate where spending is concentrated, but they are different denominators and not additive addressable-market layers. The chart therefore separates the category time series from selected 2025 shares; it does not imply that those shares sum to 100% or form a nested TAM/SAM/SOM. The report's proprietary estimation framework is not detailed in the fetched text. No public Ivalua-specific market share, module-level spend base, or qualifying customer count is established, so SAM and SOM remain open diligence questions rather than estimates.[CM003, CM004, CM005, CM006, CM007, CM008, CM015]

2.3 Buyers and budget paths vary by workflow

The available evidence indicates that large enterprises remain the largest spending cohort, while SME procurement-software spending is forecast to grow quickly; neither statistic identifies Ivalua's own customer mix. The likely buyer group for a complex suite is procurement leadership working with finance, IT, legal, and operational stakeholders, but the actual budget owner and approval path are not disclosed. Forrester Consulting's Ivalua-commissioned TEI combines interviews with four decision-makers into a hypothetical composite organization; its assumptions illustrate the scale of one modeled buyer, not a representative customer or market average. A competitor's comparison describes Ivalua implementations as requiring upfront design and an internal configuration owner; that is a commercially interested view, not an independent benchmark.[CM005, CM006, CM009, CM010, CM016]

2.4 Adoption drivers face data and execution constraints

Workflow consolidation and procurement automation are the market's stated value proposition, but adoption depends on the buyer's ability to integrate systems, govern data, and absorb implementation and change costs. A Capgemini-Ivalua solution page advertises sizable cycle-time and savings outcomes without disclosing the underlying sample or calculation on that page; these are partner claims, not independently verified benchmarks. Separately, an Ardent Partners-Ivalua study as reported by The SCXchange describes substantial AI ambition alongside fragmented data, integration concerns, and governance gaps. The respondent base and sampling method are not in the fetched excerpt, so these percentages are directional survey evidence rather than a market-wide adoption rate. Diligence should test a target buyer's source-system landscape, data quality, process ownership, implementation capacity, and realized savings before applying category growth to Ivalua's sales opportunity.[CM011, CM012, CM013, CM014, CM016]

3.1 The competitive set spans suites, adjacent tools, and orchestration

Gartner Peer Insights places Ivalua in Strategic Sourcing Application Suites and names Coupa, Zycus, JAGGAER, GEP, IBM, Synertrade, SAP, and Corcentric in its all-time alternatives list (CP001). Its separate overview says reviewers also considered Coupa, Zycus, and JAGGAER before buying Ivalua (CP003). These are buyer-consideration signals, not market shares or proof that every product is interchangeable. JAGGAER's own comparison presents Ramp as a card-led finance and spend-management platform with procurement layered in, making it adjacent rather than a full source-to-pay peer on the evidence reviewed (CP013). ProcurementMag describes Zip and ORO Labs as orchestration challengers, but its promotional tone and unsupported claims make that an early signal rather than a measured share shift (CP016). Manual processes, spreadsheets, and fragmented legacy tools remain a documented status-quo alternative in the four-interview Forrester study, not a vendor competitor (CP006).[CP001, CP003, CP013, CP016]

3.2 Breadth and configuration capacity are the key trade-off

Forrester describes Ivalua as covering sourcing, contracts, suppliers, and procurement operations, while JAGGAER's comparison describes a unified source-to-pay suite and attributes low-code configuration and a unified data model to Ivalua (CP012). The latter is a competitor's characterization, not an independent feature benchmark. JAGGAER also says Ivalua's model requires an internal configuration owner and upfront design work, whereas its own modular model can be activated in phases; the source has an incentive to favor JAGGAER (CP012). In a separate comparison, JAGGAER characterizes Ramp as oriented around cards, expenses, and accounts payable, and says it lacks direct-materials sourcing; treat those statements as competitor-authored positioning, not verified product tests (CP013). The matrix therefore marks unsupported vendor-by-vendor cells as unknown. In particular, this source pool does not substantiate comparable security, integration, channel reach, or switching-cost advantages across the named suites.[CP006, CP012, CP013]

3.3 Published pricing and modeled returns are not comparable quotes

The only captured directory price for Ivalua is Software Advice's displayed starting price of $150,000 per year, alongside a 3.8 rating from six reviews (CP004, CP005). Software Advice discloses that providers pay for sponsored profiles, so neither the price nor rating should be mistaken for an audited quote or broad customer benchmark. Forrester's commissioned Total Economic Impact study uses four decision-maker interviews and a modeled composite organization; its three-year benefit, cost, NPV, and ROI figures are scenario outputs, not Ivalua revenue, a customer guarantee, or a competing-vendor comparison (CP006-CP010). It estimates eight months of implementation and $845,000 in implementation costs for that composite (CP011). JAGGAER says both its own platform and Ivalua are custom-priced, while its Ramp comparison quotes a Ramp Plus starting price; these vendor-comparison statements still do not normalize modules, users, term, discounts, or implementation scope (CP014).[CP004, CP005, CP006, CP007, CP008, CP009, CP010, CP011, CP014]

3.4 Durability depends on implementation proof that public data does not settle

A unified platform may reduce fragmentation, but the available sources do not quantify the switching cost, customer multi-homing, renewal behavior, channel exclusivity, or module-level retention needed to establish durable lock-in. Gartner's captured profile shows 3.0 from 35 ratings and includes both favorable and critical reviewer excerpts; Gartner explicitly cautions that reviews are individual opinions, not statements of fact (CP001, CP002). The third-party RFP.wiki snapshot provides its own score and feature-score fields, but the captured text gives no scoring methodology, so those values should not be treated as a validated benchmark (CP015). Its plotted values are shown only as that publisher's display, not as validated comparative product performance. ProcurementMag's modular-ecosystem thesis raises a plausible displacement question, but its claims about vendor growth and outcomes lack substantiation in the fetched article (CP016). Before underwriting moat durability, diligence should obtain comparable customer references, full implementation plans and costs, realized discount schedules, renewal and churn cohorts, and proof of which workflows customers actually consolidate.[CP001, CP002, CP015, CP016]

3.5 Exhibits

4.1 Revenue model and disclosure quality

The available evidence describes Ivalua as a subscription software business whose enterprise pricing is negotiated rather than published. Reported pricing varies with modules, users, organization size, and implementation scope; the sources do not disclose realized contract values, recurring-revenue mix, implementation revenue, or revenue-recognition terms. A Forrester study describes license fees tied to modules and user counts, while a JAGGAER-authored comparison also says both vendors use custom quotes. These are pricing mechanisms, not proof of Ivalua's realized price or gross margin (CI001, CI002). Historical revenue evidence is dated and ambiguous. Multiples.vc lists $100 million of revenue for May 2019 but explicitly says figures may be revenue or ARR and may be run-rate or trailing-twelve-month revenue. Gartner Peer Insights lists an annual-revenue band of $50 million–$250 million without a measurement date or method. Neither can establish current revenue, ARR, growth, or recognition quality; the source values should not be combined or treated as current (CI005, CI006).[CI001, CI002, CI005, CI006]

4.2 Buyer economics and delivery costs

Ivalua's customer value case is directionally plausible but not independently established as realized economics. Forrester Consulting says Ivalua commissioned its TEI study; the study interviews four decision-makers and models their experience as one composite retailer. Its reported $24.2 million in three-year, risk-adjusted present-value procurement-efficiency savings uses a composite with $500 million of annual procurement spend, not a representative audited customer result. The same model assumes $500,000 in annual fees for 300 users and full platform functionality, with license costs flat for three years (CI007, CI008, CI009). Separately, Capgemini and Ivalua market potential productivity and operating-cost outcomes, including up to 50% higher productivity and 70% operational cost savings. These are partner-published outcome claims without customer-level baselines or calculation detail in the reviewed page, so they should not be compared directly with Forrester's modeled savings. A competitor-authored comparison says Ivalua requires more upfront design work and a dedicated internal configuration owner; that is a plausible implementation and service-delivery burden, but it is not a measured cost estimate. A Gartner user review also reports slow issue resolution, including a reviewer-reported average of up to three months for major issues (CI010, CI012, CI013).[CI007, CI008, CI009, CI010, CI011, CI012, CI013, CI014]

4.3 Capital needs and underwriting verdict

Tracxn reports $134 million raised across three rounds and identifies a $60 million May 2019 round; Multiples.vc reports a $130 million total across two rounds. The different historical totals appear to reflect different round coverage, and neither figure represents cash currently available. Multiples.vc says Hg acquired Ivalua in December 2024 for an undisclosed price, leaving transaction valuation, financing structure, and any acquisition debt unquantified in this evidence set (CI003, CI004). There is no current public evidence here for audited revenue or ARR, gross margin, cash, debt, operating cash flow, burn, runway, customer concentration, churn, or sales payback. Consequently, capital adequacy and a valuation-linked financial verdict cannot be underwritten from disclosed figures. Request current audited statements and a recurring-revenue bridge, then reconcile cash and debt, cash conversion, implementation economics, retention, and the sponsor's financing structure before setting a growth or valuation case. The specific data-room requests and their underwriting relevance are summarized in the unit-economics table.[CI003, CI004, CI005, CI006]

5.1 Product surface and workflow coverage

Sources describe Ivalua as an enterprise source-to-pay suite, not a narrow purchasing tool: the named surface spans sourcing, contracts, supplier management, intake, eProcurement, invoice processing, payments and spend analysis (CE001, CE002). A competitor-authored comparison characterizes its architecture as a unified data model with low-code workflow changes (CE003); this is a useful product-positioning clue, not an independent benchmark or technical architecture review. BriefGlance reports that Ivalua introduced IVA Studio on June 11, 2026 and describes IVA as able to execute end-to-end S2P processes autonomously (CE004). That is a current product claim, not proof of production autonomy, model safeguards, or performance. The module matrix and product-surface stack therefore map publicly described capabilities while marking maturity and validation gaps explicitly.[CE001, CE002, CE003, CE004]

5.2 Implementation evidence and outcome attribution

Ivalua’s implementation case should be underwritten as a complex enterprise deployment rather than an assumed self-serve SaaS rollout. A Forrester Consulting Total Economic Impact study commissioned by Ivalua interviewed four users and modeled their experiences as a composite retail organization (CE007, CE008). For that composite, the study estimates procurement-efficiency savings of $24.2 million in three-year risk-adjusted present value, based in part on annual savings of 2.25%–2.35% of $500 million in procurement spend (CE009); it also reports an 80% reduction from a 336-hour average supplier-onboarding process (CE010). These are study-specific estimates, not Ivalua-wide realized outcomes. The same study assigns eight months and $845,000 of internal resource, planning, and deployment costs to its composite implementation (CE016). Capgemini’s partner page separately advertises “up to” gains without disclosing a sample denominator (CE011), while Lemon Learning frames in-application guidance as an adoption aid (CE012). Test these claims against named references, scope, services costs, and post-go-live ownership before treating them as repeatable economics.[CE007, CE008, CE009, CE010, CE011, CE012, CE016]

5.3 Configuration, integration, and operating dependencies

Public descriptions point to configurability and breadth as the core differentiation, but the evidence is not a component-level architecture specification. JAGGAER’s comparison says Ivalua uses a low-code framework and unified data model, while also warning that rollout needs upfront design and an internal configuration owner (CE003); because JAGGAER is a competitor, neither side of that comparison is an independent implementation benchmark. Fincons describes its own Ivalua competence center as providing implementation, configuration, integration, and management services (CE005). The Forrester study says the platform supports integrations and adaptation to complex organizational needs, but its commissioned, interview-based design limits generalization (CE006, CE007). Buyers should validate ERP and master-data interfaces, customization governance, upgrade behavior, supplier onboarding responsibility, and the effort needed to maintain workflows across entities. The architecture table separates what the sources name from what remains to be demonstrated.[CE003, CE005, CE006, CE007]

5.4 Trust, assurance, and evidence gaps

The assigned pool does not establish Ivalua’s service-level performance, security certifications, data-residency controls, AI permission boundaries, incident record, or independent penetration-test results. UpGuard’s page says its vendor risk report uses continuous monitoring across several risk categories, but the fetched public page does not disclose Ivalua’s score or individual findings (CE014). A SoftwareConnect testimonial describes a regulated-company deployment with little customization and a desire for compliance and control, but it is an unattributed individual account rather than assurance evidence (CE013). RFP Wiki recommends testing exception handling across intake, approvals, supplier data, policy, and ERP synchronization rather than relying on a happy-path demo (CE015). The pool also has no credible developer or practitioner-community activity signal; nor does it provide independently validated architecture or reliability evidence. These are diligence gaps, not proof of weak controls or an incident, and should be closed with current documentation, assurance reports, customer references, and scenario-based testing.[CE013, CE014, CE015]

6.1 Visible customer segments are enterprise-weighted, not a customer census

The available material points to large and operationally complex procurement environments, but it does not establish Ivalua's customer-base mix. G2 displays reviews from both enterprise users (more than 1,000 employees) and mid-market users (51–1,000 employees); those are reviewer profile labels, not account counts or revenue segments (CU001). Forrester's Ivalua-commissioned study describes CACI as a $7.7 billion government contractor with 40,000 suppliers, while its separate composite organization is explicitly a model, not a named customer (CU009, CU010). A Procurement Magazine profile repeats Ivalua's statement that it manages more than US$500 billion in direct and indirect spend; this is spend processed/managed, not company revenue or customer count (CU012). The evidence therefore supports enterprise fit examples, but not geographic, vertical, payer, or account-size distributions. The table separates observed user profiles and named examples from modeled or company-issued scale claims, and records what each leaves unresolved.[CU001, CU009, CU010, CU012]

6.2 Adoption proof mixes user reviews with a commissioned modeled study

Public adoption signals are not a consistent time series. G2's captured page lists a 4.3 rating from 114 reviews and a nine-month average implementation time, but the page does not define the underlying sample, period, or implementation measure (CU001, CU002). G2 reviewers praise flexibility while also describing setup, partner-guidance, and supplier-onboarding obstacles (CU003). A SoftwareConnect testimonial from an unnamed regulated business describes replacing Excel, Word, and Access for contract work with an end-to-end Ivalua implementation and little customization; it supplies no customer name or quantified outcome (CU004). Forrester says Ivalua commissioned its TEI study, which interviewed four decision-makers and modeled a composite organization (CU005). Within those different bases, the G2 page's nine-month figure and Forrester's composite six-month implementation assumption both describe multi-month work, not a comparable benchmark (CU006). The CACI account in that study reports a 1.5-year selection and a phased full-scope rollout over two years, alongside supplier-onboarding outcomes (CU007, CU008). These examples support diligence on implementation planning, but not a promise of typical time-to-value or recurring adoption.[CU001, CU002, CU003, CU004, CU005, CU006, CU007, CU008]

6.3 Named cases exist, but retention and expansion evidence is not disclosed

The strongest named proof in this pool is CACI: the commissioned Forrester study describes the government contractor's deployment and reports supplier onboarding moving from an average of 21 days to one day, with 98% of suppliers enabled (CU007, CU008). These are study-reported customer outcomes, not audited or independently sampled results. FeaturedCustomers' captured page lists customer-case-study titles for Maxim Healthcare Services, Cengage, Covea, Arval, and Technip, but the fetched text does not provide deployment status, dates, outcomes, or reference contacts for those entries (CU011). Capgemini's co-branded Ivalua page promotes performance figures for its combined solution without naming a customer or supplying the denominators and study design in the captured text (CU013). Across the retained materials, no customer retention, churn, renewal, cohort, expansion, or top-account concentration metric is reported (CU015, CU016). Competitor and alternatives pages discuss configuration, training, and implementation trade-offs but do not quantify customers switching from Ivalua (CU017). The named-proof table is consequently partial; logos and case-study headings cannot establish production status, outcomes, retention, or concentration.[CU007, CU008, CU011, CU013, CU015, CU016, CU017]

7.1 Implementation, adoption, and value capture

The clearest evidenced execution risk is not a documented outage or failure rate; it is the organizational burden of configuring and adopting a broad source-to-pay suite. Softwr says that Ivalua configuration requires a systems integrator and an internal product owner, and JAGGAER's competitor comparison independently describes upfront design work and a dedicated owner. Lemon Learning, which sells in-app guidance for Ivalua, calls user adoption a genuine challenge. These sources differ in incentives and provide no comparable implementation cohort, so they establish a credible diligence issue, not a measured probability of failure (CR001, CR002, CR003). The cost envelope is also uncertain. Softwr says pricing is unpublished and implementation is priced separately; it gives no customer-specific invoice. Capgemini's partner page promotes productivity and operating-cost outcomes without a named sample or methodology in the fetched text. Do not capitalize those promoted savings or infer payback from managed spend: procurement throughput is not Ivalua revenue or cash generation (CR004, CR009, CR010). Before underwriting a rollout, require a named executive owner, scoped implementation statement of work, customer references at comparable complexity, adoption measures, and acceptance milestones. Missing ownership, a material schedule/cost deviation, or adoption below contractually agreed thresholds should pause expansion pending a recovery plan (CR016). [CR001, CR002, CR003, CR004, CR009, CR010, CR016]

7.2 Security, legal, and reliability assurance

The assigned security material is a diligence lead, not a security verdict. UpGuard describes continuous monitoring using 330+ external checks but the fetched Ivalua page does not disclose a score or check-level results. Nudge Security describes categories a vendor profile may cover and asks about breach history, yet its fetched page supplies no Ivalua-specific incident or control finding. Neither page establishes a clean incident history; absence of a disclosed event in these pages is not proof of absence (CR011, CR012, CR013). The retained evidence likewise does not establish Ivalua's current licenses or approvals, litigation or enforcement status, IP disputes, privacy terms, or AI-data controls. These remain open verification items rather than asserted adverse findings. For a product that may process enterprise supplier, contract, invoice, and spend data, request current independent assurance reports, certification scope and expiry, penetration-test remediation, incident history, data-flow and subprocessor inventories, contractual notification terms, and counsel's jurisdiction-by-jurisdiction legal review before treating the risk as controlled (CR014). The three-row register is intentionally partial: it identifies unresolved exposures, not a complete census of legal matters. [CR011, CR012, CR013, CR014]

7.3 Sponsor, financial disclosure, and partner dependencies

The available ownership record supports a transaction, not an assessment of current leverage or governance. Multiples.vc reports that Hg acquired Ivalua for an undisclosed price on 1 December 2024; MC Capital's January 2025 investment item identifies Hg's Genesis 10 fund but also gives no transaction terms. Multiples.vc's latest recorded revenue and valuation figures are both dated May 2019. Those historical revenue and valuation figures cannot substitute for current ARR, recognized revenue, cash, debt, burn, margin, or working-capital data (CR005, CR006, CR015). Deloitte announced a strategic alliance with Ivalua in August 2026, and Capgemini publishes an Ivalua solution page. This shows named ecosystem relationships, not exclusivity, a concentrated delivery channel, or realized commercial outcomes. Treat partner claims as commercially interested evidence and verify delivery capacity, alternative integrators, customer references, and the actual division of implementation responsibility (CR007, CR008, CR009). The financing and partner registers therefore rank disclosure and concentration as unquantified exposures; they do not assert that Ivalua has excessive leverage, a specific partner dependency, or weak governance. [CR005, CR006, CR007, CR008, CR009, CR015]

7.4 Decision gates and thesis-break conditions

Current evidence supports process gates rather than invented numeric risk thresholds. Before a deployment is treated as an underwritable expansion case, diligence should require a named accountable owner, an implementation baseline with scope and cost, customer-validated adoption and outcome measures, and independent evidence for security and regulatory controls. Set numeric tolerances in the contract and investment case using the buyer's own baseline; the assigned sources do not support a universal implementation duration, failure rate, or savings threshold (CR001, CR003, CR009, CR016). Pause or reprice the thesis if the company cannot provide current financial statements and transaction/governance terms, if a required certification or legal authorization is absent or out of scope, if an incident review reveals unresolved material exposure, or if a rollout misses buyer-agreed acceptance and adoption milestones without a credible remediation plan. These are diligence triggers, not claims that any such event has occurred. The main residual risk is therefore evidence asymmetry: public partner and vendor pages describe capabilities, while the information needed to quantify downside remains private or unverified (CR013, CR014, CR015, CR016). [CR001, CR003, CR009, CR013, CR014, CR015, CR016]

7.5 Exhibits

8.1 Investment thesis and anti-thesis

The positive case is a broad source-to-pay platform with a long operating history and reported use across large enterprises. Hg's fetched portfolio page describes Ivalua as trusted by hundreds of brands, while a Supply Chain Digital article carrying company-issued material says dozens of leading financial institutions use the platform; neither statement is audited customer evidence. Procurement Magazine's profile describes a suite spanning supplier risk, sourcing, contracts, eProcurement, invoicing, payments, and spend analysis, but product breadth does not demonstrate current monetization. The counter-case is valuation opacity: the only concrete valuation/revenue reference in this pool is from 2019, and the Hg and Agila materials do not disclose consideration. A competitor- authored comparison describes implementation/configuration effort, while an archived Capterra review contains an individual complaint about slowness and errors; both are diligence signals, not prevalence estimates. UpGuard's current public page describes continuous monitoring but exposes no rating or findings, so it is neither evidence of a security incident nor proof of clean controls.[CV011, CV012, CV013, CV014, CV016, CV010, CV009]

8.2 Entry price and valuation evidence

The best-supported historical anchor is not a current mark: Ardian's May 2019 release reported a $60 million growth-equity round valuing Ivalua at more than $1 billion and said the company was on pace to exceed $100 million in annual revenue that year. Multiples.vc records the same round as $1 billion on $100 million of revenue and displays a 10.0x revenue multiple, but that is a secondary database calculation, not an audited financial statement or a current comparable. Hg's portfolio page associates Ivalua's partnership with Hg with 2024; AgilaCapital describes a minority investment alongside Hg and explicitly says the transaction terms were not disclosed. A VendorBenchmark page advertises 2026 pricing figures across 38+ commitments, but the fetched text discloses no transparent sample or methodology, so it is not a verified price or valuation input. Thus the assigned public evidence cannot establish the present enterprise value, equity value, dilution, preference stack, or sponsor return hurdle. JAGGAER's competitor-authored comparison describes quote-based, scope-dependent arrangements rather than a published list price; it is not an independent benchmark. Do not translate historical revenue, funding raised, or product breadth into cash available or a present valuation.[CV001, CV002, CV003, CV005, CV006, CV014, CV015, CV007, CV017]

8.3 Scenarios, comparables, and diligence

Bull, base, and bear cases are decision frameworks rather than numerical forecasts. A credible bull case requires time-matched evidence of recurring revenue growth, retention, gross margin, and efficient implementation, plus a verified entry price and deal rights; none can be inferred from the 2019 revenue figure. The base case gives no credit for unverified growth or margins and treats the undisclosed Hg and Agila transaction terms as an unresolved entry-risk premium. The bear case is triggered if diligence finds slowing growth, weaker renewals, concentrated customers, margin pressure, implementation friction, or material security-control deficiencies; UpGuard's fetched page exposes no findings, so it is not evidence of either a breach or clean controls. Old individual reviews are prompts to test, not proof of current incidence. The available Multiples.vc screen is insufficient as a current comparable set: it is anchored to 2019 and does not provide a time-matched, verified peer cohort with consistent revenue definitions and operating metrics. VendorBenchmark's 2026 pricing figures also lack a transparent sample and methodology, so they are not a verified valuation reference. Obtain the current cap table and transaction documents, audited financials, cohort retention and customer concentration, debt/cash details, and a screened peer/transaction set before setting a price, return target, or exit window.[CV003, CV010, CV014, CV015, CV016, CV009, CV017]