Service van at 2am with digital data streams in the sky — UCP as infrastructure for service industries

I Don’t Think UCP Is About Shopping

Will’s Take is editorial perspective — opinion, future-casting, and industry observation from Will Tygart. Not analysis. Not client work. Just how I see it.

Everyone covering UCP is writing about Nike sneakers and Gemini checkouts. I get it — that’s the demo Google ran. That’s the image that stuck.

But I’ve been sitting with this thing for a few months now, and I keep coming back to the same thought: retail is just the proof of concept. The actual disruption is somewhere nobody’s writing about yet.

I work in service businesses. Restoration contracting. Luxury asset lending. Cold storage logistics. B2B verticals that have nothing to do with a shopping cart. And when I look at what UCP actually does — strips out the custom integration overhead between any agent and any business backend — I see something that was built for retail but belongs to every transaction-based industry that ever existed.

Let me explain what I mean.

The real problem UCP solves isn’t checkout. It’s discovery-to-transaction in any complex service.

When a homeowner has water damage at 2am, what actually happens? They Google something in a panic. They call a number. They wait. Someone answers or doesn’t. If someone answers, there’s a verbal intake, a promised callback, a dispatch, an estimate, a signed authorization. Every step is manual. Every step is a potential drop-off.

That entire sequence is a commerce transaction. It has the same DNA as buying a carry-on luggage through Gemini — intent, discovery, selection, commitment, fulfillment, post-purchase. The only difference is nobody built the protocol layer for it.

UCP is that protocol layer. Not just for retail. For any business that has a backend, a service offering, and a customer trying to get something done.

The industries that are about to get blindsided aren’t selling products.

Think about what it means to standardize the capability layer across service verticals. An AI agent that knows what a restoration contractor can do — their service area, their response time commitment, their pricing structure, their licensing — can initiate a job dispatch the same way Google initiates a checkout. The contractor doesn’t have to be on the phone. The homeowner doesn’t have to wait until morning. The insurance carrier gets the FNOL data automatically because it was captured in the transaction layer.

Same logic applies to asset lending. A borrower with a Patek Philippe wants to know what they can get against it. Right now that’s a phone call, an appraisal appointment, a back-and-forth on terms. What if their agent could query a lender’s UCP capability profile, get a preliminary offer based on market comps, and initiate the intake — before a human ever picks up the phone?

Cold storage. B2B freight. Facility services. Specialty trades. Every one of these has a transaction at its core that currently lives inside a phone call or an email thread or a PDF.

I’m not saying any of this is built yet. I’m saying the protocol exists to build it.

That’s the part people are missing when they talk about UCP. They see it as Google’s checkout infrastructure. It’s actually a universal commerce primitive — and the word “universal” is doing more work than anyone is giving it credit for.

The industries that figure this out first — the ones that build their capability profiles, define their service primitives, make themselves queryable by agents — those are the ones that win the next decade of customer acquisition. Not because they have the best website. Because they’re reachable when an agent is making a decision on a customer’s behalf at 2am.

Retail moves fast. But it’s also the most obvious target. Every VC, every product team, every Google partner is already thinking about checkout.

Nobody is thinking about the plumber.

That’s where I want to be.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *