10+ Things You Should Build With AI Instead of Sending Files

What It Covers

OpenAI's Codex "Sites" feature launch prompts an examination of 18 specific knowledge work artifacts—slide decks, strategy memos, competitive analyses, board materials, and more—that knowledge workers should rebuild as websites rather than continuing to distribute as static files, PDFs, or spreadsheets.

Key Questions Answered

• •Version Control via URL: Static files create versioning chaos—the familiar "final_v2_FINAL_actual" naming problem. Publishing work as a website gives any artifact a single canonical URL that always reflects the current version, eliminating distribution lag, conflicting copies, and the cognitive overhead of tracking which file is authoritative across an organization.
• •Slide Deck Replacement: The default artifact for presenting ideas—the slide deck—should be reconsidered as a narrative website. Tools like Gamma already collapse this distinction. Native websites break the 16:9 constraint, support live links, enable interactive elements, and allow post-send updates, making them a structurally superior format for most presentation use cases.
• •Proposal Microsites for Sales: Static sales proposals become interactive microsites where prospects can toggle variables to recalculate pricing or projected ROI without the sender present. Critically, microsites generate behavioral data—what sections were read, clicked, or abandoned—giving sales teams signal that a PDF dropped into email cannot provide.
• •Living Competitive Intelligence: A competitive analysis built as a website transforms from a one-time snapshot into a continuously updated intelligence hub. As AI agents mature, this structure enables automated research agents to monitor competitors and push updates directly to the hub at regular intervals, replacing manual quarterly refresh cycles entirely.
• •Agent-Ready Formatting: Cloudflare data shows bot and agent browsing now exceeds human browsing volume. Knowledge work artifacts built as HTML websites are structurally compatible with agent consumption, while the existing ecosystem of PDFs, CSVs, and PowerPoint files is comparatively brittle and poorly suited for the emerging agentic workflow paradigm.