Lead-to-Cash
Lead-to-Cash is the end-to-end process that takes a customer from first interest to paying for a working service. At its core it is one order, followed all the way through: qualify the lead, quote it, capture the order, break it down into the services and resources it needs, activate them, and bill for what was delivered. It is the runtime phase that faces the customer, and it runs once per order.
- Clock
- Runtime
- Unit of work
- Per order
- Cadence
- Minutes to days
- Produces
- An installed base
The whole phase, in one order
One order, followed through every system it touches. This is what the Academy means by Lead-to-Cash: not only the order-management chain, but the CRM where the lead is captured, the ERP that answers for stock, logistics and the finance ledger, and the billing that closes the loop — even where those systems have no module of their own.
L2C consumes what Concept-to-Market published and produces the installed base: the inventory records that say what each customer actually has. Everything downstream — billing, assurance, renewals — reads from that record, so the phase is judged on whether the record is right.
The step that decides that is decomposition. A product order has to become service orders, and those have to become resource orders, and each step down is driven by the catalog relationships defined at design time. Where a relationship is missing, someone closes the gap by hand or hard-codes it in the orchestrator, and the service that results has no traceable link back to the specification it was meant to come from.
L2C is also where commercial truth and technical truth first drift apart. Billing works from the product order; the network only knows what was actually activated. If nobody reconciles the two, the gap opens on the day the order completes and widens quietly from there.
Foundations reference
The L2C master process decomposed into Lead-to-Order, Order-to-Activate and Order-to-Cash, with the companion Trouble-to-Resolve process. Read it before the modules below if the sub-domain boundaries are new to you.
Modules in this phase
CRM & Lead to Order
Customer, Lead, Qualification and Order Capture
What a telco CRM owns and what it only engages with, from the first sign of interest to the order handed to COM: the party, customer and account model, leads, qualification, credit and KYC, order capture and the customer in life. Consumer (B2C) focus.
CPQ, Pricing & CLM
Commercial Configuration Engine
The vendor-neutral engine room of commercial configuration: how a product catalog becomes a priced, approvable, margin-aware, contractable quote — catalog and bundling mechanics, matrix pricing, discounting and multi-currency, margin modeling, and contract lifecycle.
Billing & Revenue Management
From Usage to Cash
Mediation, rating and charging, subscription and convergent billing, interconnect and roaming, revenue assurance, fraud management and collections — one chain from product and order to cash, with a simulation lab that runs it.
ERP & Finance Integration
The Ledger, Stock and Network Assets
What an ERP owns in a telco and what it does not: the ledger, payables, fixed assets, procurement, stock and warehouse, and where they meet Lead-to-Cash. Who owns receivables, why IFRS 15 makes the ledger differ from the invoice, how network build becomes a fixed asset, the integration boundary and the vendor landscape.
Order Management (COM/SOM/ROM)
The Order Orchestration Chain
How commercial orders decompose into service orders and resource orders, with orchestration at every layer. The module spans the BSS/OSS line: COM is BSS, SOM and ROM are OSS; it sits with BSS so the order journey is taught in one place.
The Network
Access, Transport & Core Domains
The network technologies and domains that orchestration and fulfilment act on: access, aggregation, transport and core, then IP/MPLS and transport, the mobile core and fixed access, each as an orchestration domain with its own elements, service models and controllers.
Network Activation & Provisioning
From Service Order to an Active Service Across Network Domains
How a service order becomes an active service across network domains: how the network is recorded in inventory, the EMS/NMS and controllers that manage each domain, how ROM reaches them, how resources are configured and activated, and how orchestration coordinates several domains for one order.
Domain Examples
End-to-End Service Walkthroughs
How the systems in the modules before this one work together to deliver real services: FTTH, mobile, SD-WAN, 5G slicing, IoT and more. Each example has an architecture overview, a step-by-step workflow mapped to eTOM, a BPMN view and the product model.
Foundations and the reference modules — TMF Open APIs, frameworks, architecture patterns and the vendor landscape — apply across all three phases, so they are not listed under any one of them.
Hands downstream
L2C hands Trouble-to-Resolve an installed base: product, service and resource inventory records that a fault can be correlated against.
Next: T2R — Trouble-to-Resolve