The technical capability is here — provision-to-revenue in under 60 seconds, demonstrated live. But what does that actually mean for the business teams who have to operate around it? CFOs, CROs, billing leaders, and SLA managers all have new operating models to figure out.
By Shawn Ennis • August 25, 2026 • 7 min read
At our TMF Catalyst this summer, the metric I was proudest of wasn’t any single number. It was the cumulative end-to-end demonstration: a drone surveillance mission could be provisioned, operated, monitored, completed, and billed in under 60 seconds total. The technical capability is real. The architecture works.
What I didn’t dwell on in the white paper — because it wasn’t the technical story — is what this actually means for the parts of the telecom business that aren’t in the network operations team. The CFO. The Chief Revenue Officer. The billing leadership. The SLA management team. The customer success organization. Every one of them now has new operating decisions to make in a world where services exist for 60 seconds.
This is the conversation I’m having with the COO and CFO at every operator I talk to. The technical capability is the easy part. The business operating model is where the real change happens.
The CFO problem: revenue recognition at the speed of slicing
Traditional telecom revenue recognition runs on a monthly cycle. Customer signs a contract, service gets provisioned, customer is billed every 30 days, revenue is recognized when invoiced. The finance team has built decades of process around this rhythm. Audit, tax, reporting, financial planning — all assume that the unit of analysis is a customer-month.
Ephemeral services blow this up. When a service exists for 18 minutes and produces a billing event the moment it ends, the unit of analysis becomes the service event, not the customer-month. A single enterprise customer might generate hundreds of service events per month, each with its own SLA, its own usage data, its own revenue recognition trigger. The finance team needs to roll this up to a customer-month view for traditional reporting while simultaneously operating at the service-event level for revenue capture.
The technology to do this isn’t hard. The business processes are. Specifically:
- Revenue recognition policy needs an addendum that handles per-event recognition
- Reconciliation needs to work between BSS events and finance ledger entries at scale
- Audit trails need to preserve service-event data for the duration required by tax authority
- Customer credit terms need to be re-thought when bills can fire mid-month
- Financial planning models need a new dimension: services consumed per customer per period
Most CFOs I talk to haven’t started this work yet. They will. The ones who start now will run smoother accounting cycles than the ones who wait.
The CRO problem: pricing services that exist for hours
The traditional CSP pricing model assumes that the customer is buying a tier of service for an extended period. Platinum SLA. Premium support. Reserved capacity. The price reflects the long commitment.
Ephemeral services need different pricing. The customer is buying a specific service event with specific guarantees for a specific duration. The pricing has to reflect what they actually consume — but the operator also needs to capture the value of the SLA guarantee, not just the bandwidth used.
I’ve seen three pricing models emerge in early discussions with CSPs:
Pricing model 1: Per-event pricing
Charge a flat fee per service event with size, duration, and SLA tier as inputs. Simple to understand. Easy to bill. Captures SLA value because the price isn’t just bandwidth — it’s the guarantee. Works well for predictable service categories like stadium events or scheduled broadcasts.
Pricing model 2: Subscription-with-event-overage
Customer pays a base monthly subscription that includes a certain number of service events. Additional events incur per-event charges. Familiar billing model. Predictable revenue floor. Works well for enterprise customers who use ephemeral services regularly but with variable frequency.
Pricing model 3: Usage-based with SLA premium
Charge by consumption (bandwidth, duration, edge compute) plus a premium for SLA guarantees. Closest to traditional metered pricing but with the SLA premium captured. Works well for customers who want maximum flexibility and are sophisticated enough to model their own costs.
Most operators will end up with a portfolio of pricing models, with different categories of customers and services on different ones. The CRO needs to be working on this now, before the first major sale, because changing pricing mid-customer-relationship is one of the most expensive things a CSP can do.
The SLA management problem: what does “guaranteed” mean for 18 minutes?
SLA management for permanent services is a known discipline. You have monthly thresholds, you measure against them, you credit the customer when you miss, you publish quarterly reports. The whole operation runs on a slow cycle.
SLA management for ephemeral services is a different operation. The SLA applies for the duration of the service. If the slice promised 5 Gbps and delivered 3 Gbps for the middle 6 minutes of an 18-minute mission, what’s the customer’s remedy? The math is harder. The audit is harder. The customer expectations are sharper.
Some practical questions every SLA team needs to answer:
- What’s the credit calculation for a partial-duration SLA miss?
- How quickly does the customer see SLA performance data after the service ends?
- Can the SLA be re-negotiated mid-service if conditions change?
- What’s the dispute resolution process for a service that doesn’t exist anymore?
- How does multi-slice SLA performance roll up to enterprise-level performance reports?
None of these questions have industry-standard answers yet. Every operator is going to have to develop their own framework, and the first operators to publish clear policies will have a competitive advantage in enterprise sales conversations.
The customer success problem: managing relationships that fire in real time
Customer success in traditional telecom is a quarterly business review function. The CSM meets with the customer once a quarter, reviews performance, plans the next quarter, manages the relationship. The cycle is slow and the touchpoints are infrequent.
Customer success for ephemeral services is a different job. The customer’s services are happening in real time. SLA events fire in real time. Renewal decisions are influenced by the experience of individual service events, not by aggregate quarterly metrics. The CSM needs near-real-time visibility into customer service health, the ability to proactively reach out when an SLA breach is imminent, and the operational support to mitigate problems before the customer files a credit request.
The skills are different too. Traditional CSMs are relationship managers. Ephemeral-services CSMs need to be technical enough to read a service dashboard, understand a correlation engine output, and engage with the customer about specific service incidents. The career path for this role doesn’t really exist yet at most operators.
The downstream organizational implications
Step back from the individual roles and look at the pattern. Every business function that touches the customer experience has to adapt to a faster operating tempo. The finance ledger updates more often. The pricing models accommodate more variation. The SLA management operates on shorter cycles. The customer success function gains real-time visibility and responsibility.
This is the part of the transition that takes longest. Technology can be deployed in six months. Process change takes 12-18 months. Cultural change takes 24-36 months. Operators that start the business-side work in parallel with the technical deployment finish the transition faster than operators that wait for the technology to mature before reorganizing.
The pattern that runs through all of this: the network getting faster forces the business to get faster. Not in the marketing sense. In the literal sense — financial cycles, pricing cycles, SLA cycles, customer engagement cycles all have to operate at the speed of the services they’re managing. The operators that align the business cadence to the network cadence win the next decade. The ones that don’t run a 2010-era business on a 2026 network.
Where to start
If you’re an operator preparing for slice-aware operations, my recommendation is to start the business-side conversation now, in parallel with the technical work. Specifically:
- Convene a working group with finance, sales, customer success, and operations leadership. The group’s job is to identify the business process changes needed before the first major ephemeral service launches.
- Pick a single pilot service category — live events is often the easiest — and design the end-to-end customer experience for it, from sales through delivery through billing through renewal. Use the pilot to surface process gaps.
- Don’t try to launch ephemeral services on top of unchanged business processes. The launch will look great in operations and fail in finance, billing, and customer success. The integration is where the real work lives.
The technical capability is here. The business capability is the next problem to solve. The operators that solve both win.
The technical depth behind the business change
How slice-aware operations connect the network layer to the business layer for ephemeral services.
About the author Shawn Ennis is the Founder & CEO of Rapax and Citus Technologies. With 25+ years in telecom operations, Shawn previously founded Assure1 (acquired by Oracle in 2021), holds 12 patents in telecom OSS/BSS, and hosts the Transformation Leaders Podcast. Connect on LinkedIn.