The Website Is About to Become an Implementation Detail

Website?

7:41

On the transition from published interfaces to generated ones — and what it means for everything built on top of the web.

A website, at its core, is a PDF with buttons. Sure, it's responsive. Sure, it has JavaScript. Maybe there's an AI chatbot in the corner. But fundamentally, every visitor gets roughly the same experience. Same layout. Same copy. Same navigation. Same calls to action. The same document, served to everyone. We've spent thirty years optimizing that model. That model is about to break.

The Negotiation That Doesn't Exist Yet

Imagine you arrive at richwashburn.com. The first thing that happens isn't HTML being served. It's a negotiation. Your browser — or more accurately, your personal AI agent — opens a conversation: "This user is technical. They've read twenty of Rich's articles. They care about AI infrastructure, not beginner tutorials. They have thirty minutes. They're likely evaluating consulting services."

The site's agent responds: "Understood. Instantiating an interface optimized for that."

Nothing has been rendered yet. The website hasn't been chosen.

It has been created. Now your spouse visits. The negotiation is completely different.

Beginner. Wants to understand AI. Doesn't know what an agent is. On mobile. Five minutes available.

She receives an entirely different experience. Different layout. Different copy. Different examples. Different products. Different calls to action. She may never see the consulting section at all. Now Jensen Huang visits. Or a fund manager's AI agent doing due diligence. No marketing fluff. No hero image. No animations. Just research, published thinking, case studies, technical architecture, and investment opportunities — organized around the visitor's objective rather than forcing everyone through the same funnel. Same domain. Three completely different interfaces. None of them pre-built. All of them generated.

The Part That Gets Really Interesting

Eventually, the interface may not even be visual. If my personal AI is browsing on my behalf, why would it need your website?

It simply queries your business agent directly: "Does Rich provide strategic consulting for autonomous media companies?"

Your agent responds with structured, machine-readable information. The negotiation lasts 200 milliseconds. No HTML is ever rendered. The transaction is complete.

Your "website" never existed in the traditional sense. It wasn't needed.

This changes what a domain represents in a fundamental way.

Today: Domain → Website → Information.

Tomorrow: Domain → Identity → Business Agent → Generated Experience.

The domain stops being the address of a document. It becomes something closer to an API endpoint for your organization's intelligence — a place where two systems find each other and negotiate what they each need.

What Happens to Design

We spend enormous effort debating whether a button should be blue or green. Whether the hero image should be abstract or literal. Whether the headline should lead with the benefit or the problem. That entire discipline starts to dissolve. Design shifts from arranging pixels to defining intent and constraints. The system decides the presentation. If research suggests this visitor prefers dense technical documentation, generate that. If another responds better to video, generate that. If someone needs accessibility accommodations, the interface creates itself around those needs automatically.

Designers stop making choices for an imaginary average user. They start defining the parameters within which an intelligent system makes choices for each specific user. That's a different job. It requires different skills. The people who understand this early will build something the people optimizing button colors can't compete with.

The Relationship Model Becomes the Product

Here's the implication that I think most people are missing. The website stops being the product. The relationship model becomes the product.

Your business doesn't expose pages. It exposes capabilities. Every interaction becomes a negotiation between two intelligent systems. Your AI knows everything about your company — your services, your expertise, your policies, your pricing, your history. Their AI knows everything about them — their goals, their context, their constraints, their preferences.

The interface is simply whatever those two systems decide is the most effective way to communicate.

That's not personalization in the sense we talk about it today — showing you a product recommendation based on browsing history. That's something categorically different. Two agents collaborating to find the most efficient path to mutual value. The companies that understand this are going to build for that model now — not by waiting for the interfaces to exist, but by building the underlying intelligence that will drive them. The knowledge model. The business policy. The agent that can represent them faithfully to any system that comes asking.

A Return to Protocol

There's a historical parallel worth understanding here. The early internet was protocol-driven. Clients negotiated with servers through standardized exchanges before presenting information to users. HTTP, MIME types, content negotiation — the web was built on systems talking to systems first, humans seeing the result second.

The graphical web layered documents on top of those protocols. The document became the thing. The protocol became invisible plumbing.

What's coming is almost a return to protocol-first interaction — but instead of negotiating MIME types and HTML versions, the negotiation is about goals, context, permissions, expertise, and preferred modes of communication.

The page becomes a temporary artifact of that conversation. A rendering. One possible output among many. Not the canonical thing itself.

The Prediction

Within the next decade, most organizations won't maintain a single canonical website. They'll maintain a canonical knowledge model, brand identity, business policy, and agent. The website will be one of many possible renderings of that underlying intelligence — generated on demand for humans, for AI agents, for mobile devices, for augmented reality, for interfaces we haven't invented yet. Asking "what does your homepage look like?" will sound a bit like asking today: "what does your fax cover sheet look like?" Not because websites disappeared. Because static interfaces became an implementation detail rather than the business itself.

The organizations building for that future now — not the website they're publishing today, but the intelligence underneath it — are the ones that will be easy to find, easy to transact with, and easy to trust, regardless of what interface layer the next decade invents.

The web isn't dying. The document is.

What comes after is something closer to a conversation between agents — and the businesses that show up to that conversation with the most coherent, capable, well-structured intelligence are going to have an advantage that no amount of homepage A/B testing can replicate.

---

Rich Washburn is a technologist and strategist working at the intersection of AI, infrastructure, and capital. He is Managing Partner and Chief AI Officer at Eliakim Capital and CIO of Data Power Supply.