@tjrobertson52

OpenAI just announced ChatGPT sites. Are we gonna talk about why every business should be looking at this right now, but also why this can't be the future of websites?

If you're familiar with Claude artifacts or dashboards, Sites looks like the two combined with authentication added on. It's one of those products that solves an issue you didn't know you had until you see it.

The main use case seems to be when teams of people need to make an important decision. Instead of putting a document together and then calling a team meeting to explain that document to everyone, you just give all that information to Codex and it creates a web application for you. You can then share that web app with everyone on their team, and they just authenticate with their ChatGPT account.

I've been doing this for a while now with Claude artifacts, and you only have to do it once to see it's just far superior to creating a document. It's essentially bespoke software spun up for one specific purpose.

But even though I think every business should be utilizing this technology right now, I think looking back, we're going to see this as an awkward transition phase. It just doesn't fit within the model I think we're heading towards.

For AI to effectively work in your business and ultimately run your business, there needs to be a single knowledge base. Each piece of information needs to live in a single canonical document written for AI. Otherwise, if important information is scattered, isolated, or duplicated across multiple sources, you'll never truly be able to turn that data over to AI.

I believe in the next two years, we're gonna see businesses starting to adopt AI operating systems that fully own and maintain all information about the company. Sites is a really cool tool that's useful right now, but this can't be what knowledge work looks like two years from now.

These web applications are completely isolated from the rest of your work. They're incredibly useful for collecting information, coordinating across your team, and making important decisions. But that information and those decisions need to be reflected in your knowledge base.

Personally, I'm hoping the major platforms will stop making prototypes and toys and actually start building the operating system that's gonna run future businesses.

In the meantime, we'll continue building our own operating system at our agency. And if you haven't already started doing it for your business, start building that knowledge base. It's gonna be mandatory no matter who builds the platform.