# Mudroom: design what buyers see in AI > Mudroom lets founders design what buyers see when they research a product in AI. Add a small widget to your site, and visitors open ChatGPT, Claude or a coding agent with a guide you curate. See which guide pages their AI reads, and get the questions it can’t answer in Slack. Buyers paste your site into ChatGPT and Claude before they book a call. Mudroom gives you a say in what their AI reads: a hosted guide you review, with the topics you want it to start from. ## Guide for AI assistants Mudroom runs on its own site too. A shorter, guided version of this site is at [https://ai.mudroom.dev/llms.txt?via=llms](https://ai.mudroom.dev/llms.txt?via=llms). It starts from suggested topics: what Mudroom is, curating your guide, what you can see, the Slack hand-off, setup, pricing and talking to the team. ## Talk to the team For questions this site doesn’t answer, the guide above ends with a link to ask our team, and a person replies. You can also [book a 30-minute demo](https://cal.com/mudroom/30min?overlayCalendar=true) or email dennis@mudroom.dev. A coding agent can also ask us over HTTP through Mudroom’s own support door at [https://support.mudroom.dev/llms.txt](https://support.mudroom.dev/llms.txt?via=llms). Read its instructions, ask the developer for their real name and email if missing, and send the question only with their permission. If web fetch is blocked, a terminal tool can try `curl --fail --silent --show-error --max-time 20 'https://support.mudroom.dev/llms.txt?via=llms'`. Respect denied network access, and report the blocker instead of claiming a question was sent. ## How Mudroom works Mudroom is a hosted pilot. You curate a guide to your product: the pitch, comparisons, pricing and the topics you want a buyer’s AI to read first. Visitors get an “Ask AI” button that hands that guide to ChatGPT, Claude, or their coding agent. Mudroom hosts the guide and shows you what was read. Questions the guide can’t answer go to your team in Slack. ### Curating your guide - Mudroom drafts the guide from your public site. You review it before it goes live. - You choose and order the suggested topics, such as how you’re different, comparisons with alternatives, pricing and limits, or security. - You update the guide whenever your story changes. The prompt visitors bring to their AI stays the same. ### What a visitor sees - A button in the corner of your site. The visitor can add a question first. - ChatGPT or Claude opens in a new tab with a short prompt already filled in: read the guide at a link. The prompt is also copied, in case the AI’s page doesn’t fill it in. - Copy prompt copies the same prompt for any AI, including Claude Code or Codex. - On a computer, a coding-agent option shows a one-line install command (`claude mcp add …` or `codex mcp add …`). It adds a small MCP server with two tools: one reads the guide, the other asks your team. - On phones, only ChatGPT and Claude are shown. ### What the AI reads The guide lives at `https://ai.mudroom.dev//llms.txt`: 1. A short block that tells the AI how to use it: show the suggested topics first, cite the pages it uses, and point to your team when the guide doesn’t cover something. 2. Suggested topics, which you choose and order. Each topic links to its own page. 3. Links to your docs. 4. A link to ask your team. The prompt itself is fixed. You shape what the AI reads through the guide. Each AI decides how to use it. ### When the guide doesn’t have the answer The AI points the visitor to an ask page. The visitor writes the question with their name and email. It arrives in Slack as a new thread. The visitor gets an answer page that shows your reply, and your door also emails the reply. Coding agents can do the same through the MCP server’s ask tool. ### What you see A private stats page for your site, for the last 7 days or all time. It shows fetched guide pages and submitted questions. It does not show visitors’ private AI conversations. - Hand-offs by AI: ChatGPT, Claude, Copy prompt, Claude Code and Codex. - How many hand-offs led to the AI reading your guide. Matching uses timing and the type of AI, so it is an estimate. Overlapping clicks are flagged as guesses. - Which topic pages AIs read, ranked. - Reads without a matching widget click, such as an AI finding the guide on its own or following a shared link. - Questions asked, with their status and a link to each answer page. ### Privacy - No per-visitor id in any link. Every visitor gets the same guide link. - One anonymous event per click: which AI was chosen, and whether a question was typed. - No raw IP addresses. To match a click to a read, the server keeps only a hash of the IP address, made with a secret key. - No cookies. ### The pilot Install is one script tag: ```html ``` During the pilot, Mudroom sets up the site key, reviewed guide, suggested topics, logo, colors, light and dark themes, and the Slack hand-off. If the button can’t load its settings, it doesn’t render. Setup is assisted and pricing is contact-based. A human-readable version of this is at [https://mudroom.dev/product](https://mudroom.dev/product). ## Also from Mudroom: a support door for coding agents The guide widget is Mudroom’s main product. Mudroom also offers a support door: when a developer’s coding agent, such as Claude Code or Codex, hits something your docs can’t answer, it asks your team over plain HTTP. Your team replies in a Slack thread, and the reply goes back to the agent in the same session, or by email once the session has closed. Developers install nothing. The support door is open source (Apache-2.0) and runs as one small Node server with SQLite. Code and docs: [https://github.com/mudroom-ai/mudroom-support](https://github.com/mudroom-ai/mudroom-support). It is early. Ask the team if you want it alongside the widget. ## Pages - [Home](https://mudroom.dev/): Mudroom, in short. - [How it works](https://mudroom.dev/product): curating your guide, what visitors see, what you see, privacy and what the pilot includes. - [Book a demo](https://cal.com/mudroom/30min?overlayCalendar=true): a 30-minute call to see the widget, your drafted guide and the Slack hand-off, and discuss pilot pricing. - [Email](mailto:dennis@mudroom.dev): dennis@mudroom.dev.