The Revolution Starts in the Storefront. It Doesn't Stay There.

The first article in this series told the story of how we rebuilt sees.com on Storefront Next with agents doing most of the typing. The second described what replaces the support retainer once the agents that built a site stay on to run it. This one is about the part of the story I think is least appreciated, and, for anyone running an IT organization inside a retailer, the most important.

Almost none of what we built is specific to storefront code.

What a skill actually is

Strip the commerce nouns out of our delivery infrastructure and look at what’s left. A skill, in our world, is a codified procedure with guardrails: what evidence to gather, what checks must pass, who approves, what gets escalated to a human. I walked through that loop in detail in the last article (the QA contract, the triage workflow, the human who signs every merge), so I won’t re-run it here. What matters for this piece is the shape underneath it.

The storefront was simply where we learned to run that pattern safely at production stakes. Six million sessions is a wonderful teacher. It forces you to build the things that make agents trustworthy rather than merely impressive: evidence-grounded outputs, mandatory verification, escalation paths, audit trails. Those disciplines are the hard part. The commerce content is just the first payload.

The same shape, everywhere you look

Now walk the pattern around the rest of the enterprise.

Legal approvals. A contract-review skill that checks an SOW against the master agreement, flags every delta, and routes the package for signature reads exactly like our QA contract with different nouns. Gather evidence: the two documents. Run the checks: clause by clause, against a rulebook the legal team owns. Prepare the decision: a redline and a summary of what changed. Let a human make it.

Procurement. An agent that assembles the vendor comparison, checks proposed terms against purchasing policy, chases the missing security questionnaire, and drafts the approval package is our triage workflow pointed at a different queue. HR onboarding, marketing operations, finance reconciliations, data enrichment, the same shape everywhere: gather evidence, run the checks, prepare the decision, let a human make it.

This is the real answer to the question CIOs keep asking: “We’re using AI, so why do the benefits only show up as a better day for staff instead of a better business for the enterprise?” Because AI arrived in most companies as personal tooling: a copilot here, a chat window there, individual people quietly getting faster. Personal tooling improves someone’s Tuesday. Operational infrastructure changes the P&L. The gap between those two things is not a product you can buy. It’s a set of skills (in both senses of the word), and somebody in the business has to build them.

Why buying a platform won't save you

Here is the uncomfortable part for anyone hoping to procure their way through this. Every vendor in your stack is currently rebranding as an AI platform, and much of what they're shipping is genuinely good. Buy it. Use it. But understand what it can't do: a platform cannot get interested in your problems.

The value we generated at See’s didn’t come from a platform feature. It came from noticing that parity checking was eating human weeks and building a pipeline for it. From noticing that demo reviews collected forty repetitive notes and turning those notes into measured gates. From noticing a cart being created at session start, invisibly, across six million sessions, and asking why. Every one of those is the same move: get interested in a problem, then reach first for an agentic, automated solution rather than a bigger backlog and a request for headcount.

That move is a habit, and habits live in teams, not in software. An enterprise that buys an agent platform without building the habit gets what most got from the last three platforms: shelfware with a dashboard.

Two kinds of IT department

Which brings me to the fork in the road. Over the next couple of years, I think retail IT departments will split into two recognizable species.

The first kind sucks air through its teeth. Everything is hard. Everything is a security review, a six-month estimate, a reason for the business to want less. This posture made a certain grim sense when IT capacity was genuinely scarce and every request was a threat to the roadmap. But it is lethal now, because the business can see, on their phones, in their own personal tooling, that the work has stopped being hard in the way IT keeps insisting it is. An IT team that positions itself as the department of no, at the exact moment the cost of yes is collapsing, is writing its own outsourcing memo.

The second kind I’d call IT entrepreneurs. They run toward problems, including problems that were never “IT problems”: the legal bottleneck, the procurement slog, the merchandising team’s promo setup misery. They prototype an agentic workflow in days, wrap it in the guardrails they learned running production systems, measure the savings, and take it to the CFO as money. Then they do it again. Each skill they ship makes the next one cheaper, because the infrastructure (the evidence patterns, the approval flows, the audit trails) is shared and improving.

For that second kind of team, this era is the best thing that has ever happened. IT stops being a cost center defending a backlog and becomes the place where the enterprise's operating leverage is manufactured. The CFO gets compounding efficiency they can actually book. And the CIO gets the only job security that matters now: being the executive who transformed the company, rather than the one who administered its tickets while somebody else did.

Why we’re really excited about Storefront Next

This is why I keep saying Storefront Next is not just another platform upgrade, however it may look on a slide.

Yes, it’s a faster, cleaner, more convention-driven storefront, and yes, it unlocks merchants: the people closest to revenue get a control surface they can actually use instead of a ticket queue they wait in. That alone justifies the move.

But the bigger prize is what the migration does to the IT team that runs it. A Storefront Next build done the way we did See’s is a working apprenticeship in agents-as-infrastructure: specs as the source of truth, agents writing code to the PR, automated QA, evidence-gated releases, humans concentrated on judgment. Come out the other side, and your team doesn’t just have a new storefront. It has the skills, the guardrails, and the confidence to point the same machinery at the next problem, and the one after that, all the way to the legal department.

The revolution starts in the storefront because the storefront is where the stakes are real and the payback is fast. It doesn’t stay there. The IT teams willing and experienced enough to take that chance won’t just survive the next few years; they’ll be the ones running the transformation everyone else is buying slideware about.

64labs is a Salesforce Commerce Cloud partner and Storefront Next launch partner. If you want your Storefront Next migration to leave your team transformed, not just your storefront, that’s the project we most like to run. Ask us. John will be at Dreamforce if you are going. Email John at jduncan@64labs.com.

‍