The document is a link, not a file

Stop us if this has happened to you. You finish a deck, attach it, hit send. Twenty minutes later your client replies: "Slide 4 looks broken on my end." You open the file. It looks fine. You ask what version of PowerPoint they're on. They don't know. They send a screenshot. The font is missing. The chart is now an image. The table got squashed into one cell.

You spend the next thirty minutes troubleshooting a tool that's meant to save you time.

The file format was a 1995 compromise

Office files made sense when networks were slow, disks were small, and "sharing" meant attaching to email. Every property of the format — binary, self-contained, version-pinned to whichever software produced it — solved a real problem of that era.

Those problems don't exist anymore. Browsers are everywhere. Bandwidth is cheap. Files have become the bottleneck they once solved.

Three things break when you deliver files

1. Your client can't always open it

Maybe their corporate IT blocks the attachment. Maybe their version of PowerPoint hasn't been updated in three years. Maybe they're on a phone and don't want to download a 12 MB binary just to see what you wrote. Maybe the font you used isn't installed and now your Helvetica deck looks like Comic Sans.

A link has none of these problems. A link opens in any browser, on any device, in any version. If your client can read your email, they can read your link.

2. AI can't read it cleanly

You want AI to help you revise paragraph two on slide three. But what AI receives is a binary blob it has to parse. Sometimes it succeeds. Often the formatting gets mangled on the way back. So you end up copy-pasting plain text in, copy-pasting plain text out, and manually rebuilding the slide.

Text is what AI reads natively. If your source is text, AI can revise any sentence without breaking the layout.

3. Every change requires re-sending

Find a typo? Hit send again. New number from finance? Hit send again. The client opens the latest one, but the rest of the team is reading final_v3.pptx. Everyone is looking at different versions of "the truth."

A link doesn't have this problem. There is only one URL. When you edit, the link reflects the change. Everyone you sent it to sees the latest version automatically.

So what about Office files?

We don't pretend the world has moved on. Your client's compliance team might require a .pptx for the records. Your manager might want to print a .pdf. Some recipients still live entirely in Office.

That's why every deck, doc, and dashboard in Plain has a clean fallback to .pptx, .docx, and .xlsx. The export is a safety net, not the default. You send a link. If the link doesn't fit the workflow on the other end, you click "export" and attach the file.

The mental model flips: delivery is a link by default; files are a backup plan. That single inversion is the difference between fighting your tools and using them.

This is what Plain is

Plain is a workspace where AI generates decks, docs, and dashboards, you edit them through chat or inspect mode, and you deliver them as a single URL. The deck case study isn't on slide 14 of an attachment — it's at inplain.app/s/abc123. The doc isn't a .docx — it's a page your client opens on their phone. The dashboard isn't a screenshot pasted in a deck — it's live data that updates when you do.

And when somebody really does need a file? It's one click away.