Tony: Hello, I’m Tony Mangino from TC2, and this is Staying Connected—the podcast where we talk about what really matters to enterprise customers navigating today’s technology and sourcing decisions.

Comcast Business and Equinix announced something recently that I think points to a bigger shift in how enterprise connectivity may be procured.

Comcast Business is opening its last-mile network to partner platforms through standards-based APIs, starting with Equinix Fabric. In the initial phase, eligible customers will be able to check service availability, get pricing and order Comcast Business Ethernet connectivity through the Equinix environment. The stated goal is to reduce delivery time from weeks to days. Comcast says the model is designed to expand over time into additional services, including optical connectivity, cloud connectivity and cybersecurity.

That sounds like progress and most enterprise customers would welcome faster provisioning and less manual ordering.

I’m joined today by my colleague Keith Cook to discuss a strategic question prompted by Comcast’s announcement: if connectivity becomes easier to buy, does the enterprise need to rethink how it manages the buying decision?

Keith: Yes, Tony, I think it does.

Historically, network procurement has had a lot of friction. Some of it is unnecessary and should disappear.

But some steps exist for a reason. They force the enterprise to think about architecture, price, contract terms, diversity and lifecycle obligations before a circuit gets ordered.

If APIs compress the transaction, governance must move faster to keep pace.

Faster Ordering Is Not Better Sourcing by Itself

Tony: That distinction matters. Nobody wants to defend a six-week manual process just because it gives procurement more time to review a request.

 

Keith: Right. The objective is not to preserve bureaucracy, but to streamline it.

If the service is part of an approved architecture, the commercial terms are established and the pricing falls within agreed guardrails, digital ordering can be a major improvement.

The risk is when ease of purchase starts substituting for a solid sourcing decision.  A service can be technically available and easy to order without being the right option for that site.

The Architecture Has to Come Before the API

Tony:  Keith, suppose I have a branch that needs new connectivity. Equinix can provide an eligible Comcast Ethernet service and pricing digitally. What should already have been decided before somebody places the order?

Keith: The enterprise should know what site tier that location belongs to and what the connectivity standard is for that tier.

Does the site need one connection or two? Is Ethernet the preferred access type, or would DIA or broadband be more appropriate? Is there a diversity requirement? What bandwidth range is acceptable?

Those are network architecture decisions.

Once those rules exist, automation can accelerate execution.  Without them, the API simply lets the enterprise make inconsistent network decisions faster.

 

Tony: Yeah, that sounds great, we automate the transaction before we standardize the decision.

 

Keith: Right, and then you end up with a very efficiently purchased mess.

 

Digital Pricing Is Not a Benchmark

Tony: Comcast says qualified partners will be able to check availability and get pricing through the API.  That could improve visibility. But, what impact does that have on benchmarking and market assessments?

 

Keith: It helps, but a price returned through a platform should not automatically be assumed to be competitive.  And…you still need to know what that price includes. Is it based on the enterprise agreement? Does it reflect the negotiated discount? What service term is assumed? Do installation charges apply?

And most importantly, how does it compare with credible alternatives?

 

Tony: So the API can make the quote much easier to get. It doesn’t necessarily tell me whether it’s a good quote.

 

Guest: Right. It tells you what that provider will charge. You still need some market context to know whether the price is actually competitive.

What Contract Governs the Order?

Tony: This may be the most important sourcing question.  If I order a service inside a partner platform, what contract am I actually buying under?

 

Guest: That needs to be unambiguous.

Ideally, the digital transaction inherits the enterprise’s negotiated agreement: rates, service levels, billing protections, termination rights and the other commercial terms already established with the provider.

If the order introduces separate platform terms or different service conditions, the enterprise can create contract fragmentation and risk without realizing it.

 

Tony: And because the ordering experience is faster, the user may not even think of it as a contracting event.

 

Keith: Exactly why the controls need to sit inside the workflow. The platform should not only know which service can be ordered. It should know which commercial structure is authorized.

 

Availability Is Not Diversity

Tony: There’s another network-specific issue here.  An API can tell me that a provider serves the site. It still may not tell me whether the proposed services are physically diverse.

 

Keith: Correct.

Two services can come from different suppliers and still share a building entrance, conduit, local carrier or some other physical dependency.

If the site requires true diversity, that validation cannot disappear just because ordering is automated.

The enterprise needs to define what qualifies as an acceptable diverse solution and make sure the workflow supports that requirement.

 

Tony: Which is another example of governance moving into the rules instead of just sitting in an approval email afterward.

Standards Could Make the Model Much Bigger

 

Tony: Keith, Comcast says the integration uses standards-based APIs aligned with the Mplify Lifecycle Service Orchestration framework rather than a proprietary interface.

That seems, or at least sounds, important because it suggests the model could extend beyond one Comcast-Equinix relationship.

 

Keith: That’s where the strategic change becomes more interesting.

If multiple carriers expose standardized service discovery, pricing and ordering, connectivity could eventually be evaluated and procured much more programmatically.

A site requirement gets created. The system identifies available services, applies approved policies and moves the order forward with far less manual intervention.

That can remove a lot of friction.

But sourcing strategy increasingly has to be encoded into those policies.

Which suppliers are approved? What price variance is acceptable? Which terms are mandatory? When does a transaction require competitive review rather than automatic fulfillment?

 

Tony: So procurement doesn’t disappear. It becomes part of the operating model.

 

Guest: That’s how I see it.

The better outcome is not procurement manually approving every circuit. It is procurement helping establish commercial rules that let routine transactions move quickly without giving away leverage or introducing risk.

 

Convenience Can Create Stickiness

Tony: If Equinix becomes the place where I connect clouds, data centers and now last-mile services, the experience gets easier.  Could that convenience create another form of dependency?

 

Guest: Potentially.

Platforms become sticky when they accumulate workflow, data, integrations and operational habits.

That is not automatically bad. A platform may deserve that role because it makes the environment work better.

But the enterprise should understand whether services ordered through the platform remain portable. Are the underlying carrier relationships visible? Can the service be managed elsewhere later? What happens if the enterprise wants to change platforms?

Convenience has value. So does optionality.

Faster Provisioning Creates a Lifecycle Obligation

Tony: There’s one more issue I don’t want to miss.  If ordering becomes dramatically easier, you can create a lot more services.

 

Keith: And every fast order eventually becomes an inventory record, an invoice and, at some point, a disconnect.

Automation that accelerates ordering but doesn’t improve lifecycle control can create new waste.
Ideally, the same digital model that makes provisioning easier should support inventory, changes and disconnects just as well.

 

Tony: The easiest circuit to order can become the hardest one to remember three years later.

 

Keith: Which is why provisioning automation and lifecycle governance need to mature together.

 

What Should Enterprises Do Now?

Tony: This is still an initial integration, and Comcast says the companies will validate the model with enterprise customers before expanding it.  What should buyers take from it today?

 

Keith: Start preparing for a world where connectivity procurement becomes more programmable.

Define the architecture standards. Establish commercial guardrails. Decide which decisions can be automated and which still require review. Make sure digital orders inherit negotiated terms. And build lifecycle controls into the same process.

If you do that, API-driven procurement can remove friction without removing discipline.

Closing

Tony: And that’s the larger takeaway.

Comcast Business and Equinix are bringing last-mile connectivity into a digital platform where enterprises already manage interconnection, with a goal of moving provisioning from weeks toward days.

If that model scales, buying network services could become much easier.

The challenge is making sure easier ordering does not become easier overspending, weaker competition or fragmented contracts.  The future network procurement model may be faster, more automated and increasingly API-driven.  But the architecture, commercial rules and governance still have to come from the enterprise.

To our listeners, if you would like to discuss network strategy, digital procurement or how to structure sourcing and lifecycle controls for a more automated connectivity environment, or if you’d like to discuss other technology strategy, sourcing and cost reduction needs with Keith, me, or any of our TC2 and LB3 colleagues, please give us a call or shoot us an email.

You can also stay current by subscribing to Staying Connected, by checking out our websites, and by following us on LinkedIn.