1. Define the valuation question
Separate enterprise value, equity value, transaction price, strategic value and accounting measurement.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a valuation scope memorandum.
The principal failure occurs when one headline multiple is treated as a complete valuation conclusion. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for define the valuation question should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
2. Map the revenue architecture
Trace subscription, usage, licence, implementation, customisation, support, data and pass-through revenue.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue architecture map.
The principal failure occurs when all reported revenue is assumed to carry software economics. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for map the revenue architecture should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
3. Reconcile contracts to reported revenue
Tie order forms, statements of work, invoices, deferred revenue and recognition policy to the ledger.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contract-to-ledger reconciliation.
The principal failure occurs when management labels substitute for contract-level evidence. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for reconcile contracts to reported revenue should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
4. Identify performance obligations
Assess distinct promises, integration, modification and stand-ready services under the applicable accounting framework.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a performance-obligation matrix.
The principal failure occurs when bundled delivery obscures the timing and nature of revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for identify performance obligations should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
5. Test principal-versus-agent presentation
Determine control, fulfilment responsibility, inventory risk and pricing discretion for third-party models, cloud and data.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a gross-to-net assessment.
The principal failure occurs when gross billings inflate scale where the company arranges rather than controls supply. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for test principal-versus-agent presentation should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
6. Build a revenue quality bridge
Reconcile reported revenue to recurring product revenue, consumption revenue, professional services and non-recurring items.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue quality bridge.
The principal failure occurs when annualised revenue overstates repeatable economics. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for build a revenue quality bridge should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
7. Measure contracted recurring value
Test term, cancellation, minimum commitments, renewal rights, price protection and service dependencies.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contracted-revenue evidence pack.
The principal failure occurs when contract value is counted before enforceability and delivery readiness are established. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for measure contracted recurring value should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
8. Separate product from services effort
Allocate engineering, solution architecture, data preparation, integration, change management and support hours.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a delivery-effort allocation.
The principal failure occurs when labour-intensive delivery is embedded inside product gross margin. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for separate product from services effort should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
Table 1. Revenue architecture
| Stream | Evidence | Valuation treatment |
|---|---|---|
| subscription | contract and cohort | recurring base |
| usage | consumption history | scenario revenue |
| implementation | hours and acceptance | services economics |
| pass-through | control assessment | gross or net |
Illustrative analytical design; company-specific evidence and professional advice govern.

Values are illustrative evidence indices and require company-specific support.
9. Reconstruct contribution margin
Attribute model inference, cloud, data, human review, implementation labour and customer success costs.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contribution-margin model.
The principal failure occurs when headline gross margin excludes costs required to produce reliable customer outcomes. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for reconstruct contribution margin should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
10. Measure implementation intensity
Track time to deploy, customer effort, third-party dependency, custom code and rework.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an implementation-intensity scorecard.
The principal failure occurs when slow bespoke onboarding is described as scalable software delivery. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for measure implementation intensity should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
11. Test repeatability
Compare configuration, reusable connectors, workflows and models across customers.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a repeatability evidence matrix.
The principal failure occurs when revenue growth depends on rebuilding the solution for each account. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for test repeatability should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
12. Assess productisation maturity
Evaluate standard features, release cadence, documentation, self-service, APIs and partner enablement.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a productisation maturity model.
The principal failure occurs when a consulting workflow is presented as a software product. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for assess productisation maturity should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
13. Map human-in-the-loop economics
Quantify review, escalation, exception handling, annotation and quality assurance by use case.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a human-effort unit model.
The principal failure occurs when hidden labour grows with transaction volume. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for map human-in-the-loop economics should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
14. Model inference and infrastructure cost
Measure tokens, compute, storage, retrieval, observability, vendor pricing and utilisation.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an AI cost-to-serve model.
The principal failure occurs when unit economics assume static model and cloud costs. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for model inference and infrastructure cost should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
15. Test model-vendor dependency
Review switching cost, rate limits, pricing rights, availability, indemnities and portability.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a model dependency register.
The principal failure occurs when margin and continuity depend on one external model provider. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for test model-vendor dependency should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
16. Assess data rights and provenance
Verify collection, licences, consent, retention, cross-border transfer and output rights.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a data-rights evidence file.
The principal failure occurs when commercial value rests on data the company cannot lawfully reuse. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for assess data rights and provenance should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
Table 2. Productisation evidence
| Dimension | Evidence | Value implication |
|---|---|---|
| deployment | time and labour | scalability |
| reuse | common code and connectors | incremental margin |
| support | tickets and expert hours | cost to serve |
| customisation | customer-specific assets | concentration risk |
Illustrative analytical design; company-specific evidence and professional advice govern.

Values are illustrative evidence indices and require company-specific support.
17. Evaluate intellectual-property control
Map proprietary code, models, prompts, workflows, patents, trade secrets and contractor assignments.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an IP control schedule.
The principal failure occurs when claimed technology ownership is fragmented or non-exclusive. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for evaluate intellectual-property control should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
18. Measure model performance
Define accuracy, calibration, hallucination, latency, drift, robustness and business outcome metrics.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a model performance dossier.
The principal failure occurs when demo performance substitutes for production evidence. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for measure model performance should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
19. Quantify reliability cost
Price monitoring, evaluation, fallback, incident response, red teaming and remediation.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a reliability cost model.
The principal failure occurs when trust and compliance work is treated as optional overhead. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for quantify reliability cost should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
20. Map regulatory exposure
Classify use cases, provider roles, deployer duties, documentation and prohibited or high-risk activity.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a regulatory exposure matrix.
The principal failure occurs when revenue forecasts ignore compliance limits and implementation cost. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for map regulatory exposure should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
21. Test customer concentration
Measure revenue, gross profit, renewal and implementation resources by account.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a customer concentration analysis.
The principal failure occurs when one complex customer creates both reported scale and material fragility. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for test customer concentration should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
22. Normalise retention metrics
Reconcile logo, gross revenue and net revenue retention for price, usage, services and acquisitions.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a cohort retention bridge.
The principal failure occurs when expansion services disguise weak product retention. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for normalise retention metrics should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
23. Separate price from consumption
Decompose growth into customers, seats, transactions, tokens, price and service work.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a growth-driver waterfall.
The principal failure occurs when usage volatility is presented as contracted recurring revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for separate price from consumption should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
24. Test sales efficiency
Measure fully loaded acquisition cost, sales cycle, proof-of-concept conversion and payback by segment.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a sales efficiency cohort model.
The principal failure occurs when capitalised pilots and founder selling hide acquisition cost. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for test sales efficiency should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
Table 3. AI unit economics
| Driver | Measure | Control |
|---|---|---|
| compute | cost per outcome | routing |
| human review | minutes per case | thresholds |
| reliability | evaluation and incidents | monitoring |
| retention | cohort recurring margin | renewal discipline |
Illustrative analytical design; company-specific evidence and professional advice govern.

Values are illustrative evidence indices and require company-specific support.
25. Assess channel economics
Review reseller, cloud marketplace, systems integrator and referral arrangements.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a channel economics schedule.
The principal failure occurs when channel revenue carries undisclosed commissions, control and dependency. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for assess channel economics should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
26. Measure backlog quality
Test signed commitments, termination, acceptance, funding, delivery capacity and revenue timing.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a backlog conversion model.
The principal failure occurs when pipeline and bookings are capitalised as if they were earned revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for measure backlog quality should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
27. Build a product-services scenario model
Forecast revenue, margins, cash flow and capital needs under distinct productisation paths.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a three-case operating model.
The principal failure occurs when one blended forecast conceals radically different operating models. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for build a product-services scenario model should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
28. Select valuation approaches
Triangulate income, market and cost approaches under a documented basis of value.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a valuation approach memorandum.
The principal failure occurs when a single revenue multiple dominates contrary evidence. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for select valuation approaches should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
29. Normalise comparable-company metrics
Adjust peers for revenue mix, growth, margins, retention, size, geography, risk and accounting.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a comparable-company normalisation.
The principal failure occurs when nominal AI labels create false comparability. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for normalise comparable-company metrics should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
30. Analyse precedent transactions
Review control, synergies, cycle, consideration, earnouts and target revenue quality.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a precedent-transaction evidence table.
The principal failure occurs when headline transaction multiples are imported without context. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for analyse precedent transactions should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
31. Value intangible assets
Assess technology, data, customer relationships, trade names and assembled workforce under applicable standards.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an intangible-asset value map.
The principal failure occurs when enterprise value is attributed wholly to an undifferentiated AI premium. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for value intangible assets should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
32. Model obsolescence and useful life
Test model replacement, architecture change, open-source substitution and customer switching.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an obsolescence curve.
The principal failure occurs when technology is assigned a perpetual advantage despite rapid decay. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for model obsolescence and useful life should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
Table 4. Valuation triangulation
| Approach | Primary evidence | Key risk |
|---|---|---|
| income | cash-flow scenarios | forecast bias |
| market | normalised peers | false comparability |
| transactions | adjusted precedents | cycle and synergy |
| cost | reproduction and obsolescence | economic utility |
Illustrative analytical design; company-specific evidence and professional advice govern.

Values are illustrative evidence indices and require company-specific support.
33. Assess technical debt
Quantify remediation, security, scalability, documentation, testing and architecture constraints.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a technical-debt value adjustment.
The principal failure occurs when future engineering spend required to sustain revenue is ignored. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for assess technical debt should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
34. Price regulatory and litigation risk
Scenario-weight fines, remediation, claims, contract termination and market restriction.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a risk-adjusted cash-flow schedule.
The principal failure occurs when legal exposure appears only as generic discount-rate uplift. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for price regulatory and litigation risk should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
35. Analyse strategic buyer synergies
Separate revenue, cost, data, distribution and capability synergies from standalone value.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a standalone-to-strategic value bridge.
The principal failure occurs when seller forecasts include value available only to a particular buyer. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for analyse strategic buyer synergies should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
36. Design earnout metrics
Choose auditable revenue, gross profit, retention, deployment and product milestones with control protections.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an earnout architecture.
The principal failure occurs when deferred price rewards gross revenue that destroys contribution value. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for design earnout metrics should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
37. Run reverse stress tests
Identify the churn, margin, inference-cost, implementation and regulatory thresholds that break value.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a reverse-stress dashboard.
The principal failure occurs when downside analysis stops before the investment case fails. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for run reverse stress tests should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
38. Translate diligence into adjustments
Map evidence gaps to forecast changes, multiple selection, escrow, indemnity and contingent consideration.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a diligence-to-value matrix.
The principal failure occurs when risks are listed without economic consequence. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for translate diligence into adjustments should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
39. Build the valuation committee record
Document sources, assumptions, sensitivities, conflicts, specialists and unresolved matters.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a valuation decision file.
The principal failure occurs when the conclusion cannot be reproduced or governed. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for build the valuation committee record should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
40. Close through evidence gates
Require reconciled revenue, cost attribution, rights, performance, compliance, scenarios and approved valuation ranges.
The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an AI-native valuation close certificate.
The principal failure occurs when the transaction proceeds on narrative momentum. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.
The decision pack for close through evidence gates should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.
Table 5. Valuation close
| Outcome | Measure | Evidence |
|---|---|---|
| revenue quality | product-services bridge | contract reconciliation |
| economics | contribution margin | cost allocation |
| risk | scenario-weighted exposure | diligence record |
| value | approved range | committee file |
Illustrative analytical design; company-specific evidence and professional advice govern.

Values are illustrative evidence indices and require company-specific support.
References
- IFRS Foundation, IFRS 15 Revenue from Contracts with Customers, https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/
- IFRS Foundation, Post-implementation Review of IFRS 15, https://www.ifrs.org/content/dam/ifrs/project/pir-ifrs-15/rfi-iasb-2023-4-pir-ifrs-15.pdf
- IFRS Interpretations Committee, Principal versus Agent: Software Reseller, https://www.ifrs.org/content/dam/ifrs/supporting-implementation/agenda-decisions/2022/principal-versus-agent-software-reseller-may-2022.pdf
- IFRS Foundation, IFRS 3 Business Combinations, https://www.ifrs.org/issued-standards/list-of-standards/ifrs-3-business-combinations/
- IFRS Foundation, IAS 38 Intangible Assets, https://www.ifrs.org/issued-standards/list-of-standards/ias-38-intangible-assets/
- IFRS Foundation, Intangible Assets project, https://www.ifrs.org/projects/work-plan/intangible-assets/
- International Valuation Standards Council, International Valuation Standards, https://ivsc.org/standards/
- International Valuation Standards Council, Deciphering Technology, https://ivsc.org/perspectives-paper-deciphering-technology/
- International Valuation Standards Council, 2026 IVS Exposure Draft, https://ivsc.org/consultations/ivs-exposure-draft-for-consultation-2026/
- NIST, Artificial Intelligence Risk Management Framework, https://www.nist.gov/itl/ai-risk-management-framework
- NIST, Generative Artificial Intelligence Profile, https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf
- NIST, AI RMF Playbook, https://www.nist.gov/itl/ai-risk-management-framework/nist-ai-rmf-playbook
- European Commission, AI Act regulatory framework, https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
- European Commission, Guidelines on obligations for general-purpose AI providers, https://digital-strategy.ec.europa.eu/en/faqs/guidelines-obligations-general-purpose-ai-providers
- European Commission, AI Act Service Desk, https://ai-act-service-desk.ec.europa.eu/en/ai-act
- ISO, ISO/IEC 42001 Artificial intelligence management system, https://www.iso.org/standard/81230.html
- OECD, OECD AI Principles, https://oecd.ai/en/ai-principles
- WIPO, Artificial Intelligence and Intellectual Property, https://www.wipo.int/about-ip/en/frontier_technologies/ai_and_ip.html
- UK Intellectual Property Office, Artificial intelligence and intellectual property, https://www.gov.uk/government/collections/artificial-intelligence-and-intellectual-property
- UK Competition and Markets Authority, AI Foundation Models, https://www.gov.uk/cma-cases/ai-foundation-models-initial-review
- US Federal Trade Commission, AI and business guidance, https://www.ftc.gov/business-guidance/blog/2023/02/keep-your-ai-claims-check
- US Securities and Exchange Commission, EDGAR company filings, https://www.sec.gov/edgar/search/
- US Department of Justice and Federal Trade Commission, Merger Guidelines, https://www.justice.gov/atr/merger-guidelines
- European Commission, Merger control, https://competition-policy.ec.europa.eu/mergers/overview_en
- UK Competition and Markets Authority, Merger assessment guidelines, https://www.gov.uk/government/publications/merger-assessment-guidelines
- PCAOB, Auditing Accounting Estimates, Including Fair Value Measurements, https://pcaobus.org/oversight/standards/auditing-standards/details/AS2501

