Lead-to-Cash and Its Sub-Domain Processes

The L2C master process decomposed into L2O, O2A, and O2C — plus the companion Trouble-to-Resolve (T2R) process covering ITSM and service assurance.

What Is Lead-to-Cash?

Lead-to-Cash (L2C) is the end-to-end process that turns a sales opportunity into recurring revenue. It spans the entire BSS/OSS landscape — from the first customer interaction through to a working service and collected payment. L2C decomposes into three sub-domain processes: L2O (Lead-to-Order), O2A (Order-to-Activate), and O2C (Order-to-Cash).

Figure 1.8 — L2C as the top-level process, its three sub-processes (L2O, O2A, O2C), and T2R as the separate assurance process

L2O, O2A, O2C at a Glance

	L2O — Lead-to-Order	O2A — Order-to-Activate	O2C — Order-to-Cash
Domain	BSS (commercial)	BSS → OSS (crosses boundary)	BSS (revenue)
Goal	Capture a valid order	Deliver a working service	Collect payment
Key Systems	CRM, CPQ, Catalog, COM	SOM, ROM, Activation	Rating, Billing, Revenue Mgmt
Output	Validated commercial order	Service live on network	Cash collected

O2A Cannot Be Bolted On Later

The product catalog must be designed from day one with service and resource decomposition in mind. Building a modern L2O (digital sales) without a connected O2A creates a "digital front door on a manual factory" — orders arrive faster but still need human intervention to fulfil.

Trouble-to-Resolve (T2R) — The Assurance Companion

L2C covers fulfilment (sell → build → bill). Trouble-to-Resolve (T2R) covers assurance — everything after the service is live. T2R sits alongside L2C as a peer process with the strongest interaction with ITSM. Without it, a telco can deliver but cannot sustain — and sustaining is where most operational cost and customer experience impact sits.

T2R Capabilities at a Glance

Capability	Purpose	Key Systems
SLA Management	Track commitments vs real performance; trigger breach alerts and credits	Assurance Platform, SQM
ITIL Ticket & Case Mgmt	Incident, problem, and service request lifecycle	ITSM (ServiceNow, BMC)
Asset & Config Mgmt	Physical and logical asset state and configuration	Resource Inventory, CMDB
Field Services	Dispatch and track field engineering tasks	Workforce Mgmt (WFM)
Change Management	Controlled changes to live services via RFC/CAB	ITSM Change Module

Figure 1.9 — L2C populates SLM (Subscription Lifecycle Management), which T2R reads for fault correlation and impact analysis

T2R Is Not "Just ITSM"

T2R spans service assurance (monitoring, SLA management), ITSM operations (incident, problem, change), and field operations (workforce dispatch). Implementing ServiceNow alone does not deliver T2R — it delivers one component. The full capability requires integration with inventory, assurance platforms, network management, and workforce management.

Key Takeaways

L2C = sell it (L2O) → build it (O2A) → bill it (O2C)
T2R = detect it → correlate it → diagnose it → fix it → confirm it
The L2O → O2A handoff crosses the BSS/OSS boundary — this is the critical integration point
L2C populates SLM (product, service, resource records) — T2R depends on this data; modernise them together or assurance breaks
T2R feeds back into L2C via MACD triggers, SLA credits, and capacity signals
T2R spans service assurance, ITSM operations, and field services — it is not just ticketing