8 posts tagged with "strategy"

Abstract​

Autonomous software agents are increasingly executing commercial transactions on behalf of human principals — discovering suppliers, evaluating offers, and placing orders without human involvement at each decision point. This paper examines the human factors dimension of this transition: what changes when humans delegate purchasing authority to agents, how the cooperative structure of commerce changes when one or more parties to a transaction is a software system, and what oversight, accountability, and trust mechanisms are required for agent-mediated commerce to function within organizational contexts.

We analyze a three-party transaction scenario (human principal, procurement agent, manufacturer) to identify the moments of delegation, the accountability gaps that delegation creates, and the design requirements for capability surfaces — the architectural interface layer through which agents interact with merchants — that support rather than undermine human oversight. We argue that the technical architecture of agent-commerce systems encodes assumptions about human authority that deserve explicit examination, and that CSCW research has important contributions to make in designing systems where automation is a tool of human delegation rather than a replacement for human judgment.

Abstract​

Agent-mediated commerce — in which software agents autonomously discover suppliers, evaluate constraints, and execute transactions without human involvement at each step — is restructuring competitive dynamics in B2B markets. This paper analyzes the economic implications of this transition, identifying which traditional competitive advantages are durable in agent-evaluated markets and which erode, how the cost structure of supplier discovery changes, and what this means for the strategic positioning of manufacturers, distributors, and platform providers.

We argue that the transition to agent-mediated purchasing functions analogously to a market design change: it replaces attention-based competition (UX, SEO, merchandising) with operations-based competition (data completeness, interface reliability, fulfillment accuracy). This shift disproportionately favors organizations that have invested in operational excellence over those that have invested in human-attention capture. We further argue that capability surfaces — semantic contract layers enabling agent-to-merchant interaction without bespoke integrations — function as market infrastructure that reduces supplier discovery costs and changes the economics of direct manufacturer-to-buyer engagement.

Something happened recently in B2B procurement that most sellers don't know about yet.

A construction company's software placed an order for 200 precision industrial components — ISO certified, shipped to Denver, all-in for $38,000 — without a human making a single purchasing decision after the initial instruction was given. The software found the supplier, evaluated three alternatives, confirmed availability and certification, arranged freight, and submitted the order. The construction firm's project manager received a structured confirmation email with the purchase order, tracking number, and certification documents.

The supplier that won the business? They didn't win it with a great website. They didn't win it with SEO or a smooth checkout flow or a compelling product description. They won it because their product data was complete, their availability signal was machine-readable, and their API didn't return ambiguous strings when the software asked a yes-or-no question.

The supplier that lost? They had equivalent products. They lost because their availability field returned "usually ships in 1–2 weeks" instead of a structured value. The software couldn't parse that into a procurement decision and moved on.

This is the shift. And it's not coming — it's here.

Functional Programming Isn't Just for Academics — Part 11

Adopting functional programming isn't free. It requires training investment, a shift in team culture, and a willingness to tolerate an awkward middle period where the codebase is neither cleanly imperative nor fully functional. So the honest question — the one that belongs in a technology leadership conversation — is whether the benefits actually justify the cost.

This is my attempt at a direct answer, organized around the risk categories that tend to matter most in enterprise commerce organizations.

For three decades, commerce has centered on human buyers navigating browsers, apps, and IoT devices. Humans absorb ambiguity — tolerating unclear checkout processes, mysterious promotions, shifting shipping estimates, and surprise totals. If the brand is strong enough, they might still purchase despite friction.

Agentic commerce marks a fundamental shift: acknowledging that buyers aren't always human. Automated agents operate differently from people. They lack emotional attachment to brands and won't retry after failures. Instead, agents follow intent within constraints and systematically avoid unreliable paths.

In 1983 I asked my parents for an Atari for Christmas, instead I got a Commodore 64… Needless to say, I was very disappointed until I discovered how much cooler Wizard of Wor was than Combat. To their credit, my parents thought a computer was a better investment than a video game. I used that C64 through my sophomore year of college until I replaced it with a 486; my first real investment. So, like many in my generation, I cut my teeth on programming languages like BASIC and LOGO without really picking them for any reason. It was just kind of cool, as a kid, to be able to tell a computer what to do and watch it do it. I quickly understood that animating ASCII stick figures was a BASIC problem and digital Spirograph was a job for the LOGO turtle. In college I was using FORTran for math and science and C for everything else knowing that, depending on the task, one was more natural than the other.