Delivered · published
A SaaS platform that turns AI chat content into web pages
A SaaS application that lets web agents turn conversation context into shareable Markdown, HTML or JSX pages while users control publication, updates and reuse.
- Client
- saved.md
- Industry
- Reports, proposals and presentations
- What we built
- Agent connection + versioned page publishing + reusable templates
- Status
- Delivered · published
The challenge
What was getting in the way
Professionals draft useful work with AI, then copy it into another tool to format and share. Sending the whole chat exposes the working conversation instead of giving a client or colleague the finished result.
Professionals already use AI conversations to prepare reports, proposals, briefs, dashboards and presentations. The useful context often stays inside the chat while the final deliverable still has to be copied into a document, redesigned and shared as another file attachment.
An AI conversation is a productive workspace, but it is a poor final format for client or internal delivery. Copying the result into another tool loses time, structure and interactive behaviour. Sharing the chat exposes too much context and makes the reader work through the drafting process instead of seeing the finished outcome.
- A professional asks an AI tool to turn the current conversation into a defined page or document.
- The web agent shapes the relevant context into Markdown, HTML or JSX and prepares a saved.md publication action.
- The user reviews and approves the action before the page is published.
- The finished deliverable receives a clean web link and can be updated, versioned, remixed or exported when the work changes.
Approach
How the system works
We built a publishing platform that turns selected chat content into web pages, reports and interactive presentations. Users approve publication and updates, with version history and reusable templates.
- 01
Agent publishing interface
An MCP connection lets supported AI tools create, retrieve and update saved.md pages from the conversation where the work begins.
- 02
Multi-format page renderer
The publishing layer turns Markdown, HTML or JSX into a hosted web page, including light interaction and presentation controls where the format supports them.
- 03
Page lifecycle
Ownership, approval, version history, reusable templates, remixing and export keep each deliverable useful after its first publication.
Turn a conversation into a shareable deliverable
- 01Web page
- 02Report
- 03Presentation
Rules handle
- Validate the requested page format and required publication fields.
- Create a stable page record and a public link with an opaque identifier.
- Render Markdown, HTML and JSX through the correct page runtime.
- Retain the current page version and reject updates based on stale state.
- Preserve page ownership and collaborator editing permissions.
- Generate a PDF export when the user needs a file version of the published page.
AI handles
- Select the relevant context from the conversation and leave unrelated drafting history out of the deliverable.
- Choose a suitable page type or template for the requested professional outcome.
- Structure the source content and produce the Markdown, HTML or JSX needed by the page.
- Prepare revisions while keeping the existing page structure and the user's requested changes intact.
People decide
- Decide which conversation details, evidence and claims belong in the public page.
- Approve the saved.md publishing action before the agent creates or updates a page.
- Review the rendered deliverable before sharing it with a client, colleague or public audience.
- Choose whether to update the live page, create a remix or export a fixed file.
The website
The published web experience
Explore selected screens from the project. The complete site opens separately for current content and full interaction.
Stack
Built with
Every tool the system connects, and the job it does.
AI workspaces
ChatGPT, Claude, Gemini, Codex, VS Code, Claude Code, Cursor and other clients that can use the saved.md MCP connection.
Page formats
Markdown for direct documents, HTML for composed web pages and JSX for interactive deliverables and presentations.
Template library
Reusable starting points for reports, proposals, dashboards, briefs, presentations and other professional page types.
Web and file delivery
Public links for live reading and PDF export when the recipient or workflow requires a file.
Limits
Limits of this case
- Pages are public to anyone who has the link, so users must remove information that should remain private before publication.
- The quality of the finished page depends on the conversation context, source material and instructions available to the agent.
- Interactive JSX pages support light application behaviour, but they do not replace a full custom application when the workflow needs a dedicated backend or complex permissions.
- Connected AI tools still control how approval prompts and MCP actions appear inside their own interfaces.
- The case-study frames are official product captures from a specific release. The live website remains the source for current behaviour.
Possible next phase
Expand reusable deliverable patterns and collaborative editing while keeping publication approval and version safety visible in every agent workflow.
Next case study
