# Send Claude Cowork output to a client as a link · Stacktree Source: https://stacktr.ee/share-claude-cowork-output-with-client [Skip to content](#main) [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated September 20, 2026 use case # Cowork writes the proposal. Now send it. Proposal builder ends with a document, not a delivery. Turn it into a page the client opens in any browser: no download, no account, a passcode if the pricing is sensitive, and a read receipt so you know it landed. Change it after the call and the link you already sent shows the new version. [ Start from the proposal template ](https://app.stacktr.ee/new?template=client-proposal&join=1&from=seo_share_claude_cowork_output) No card. 3 free pages, each live for 7 days. What your client sees [ Brand & marketing audit open example Findings, perception map, score dial — one navigable page. Live page → ](https://example-brand-audit.stacktr.ee/)[ Performance report open example The monthly numbers, sent as a link that updates in place. Live page → ](https://example-performance-report.stacktr.ee/)[ Passcode-gated review passcode: demo Type what your client would type and see the styled gate. Live page → ](https://example-locked-review.stacktr.ee/) ## How do you send Claude Cowork output to a client? Publish it instead of attaching it. Save the Cowork output as HTML, publish it to Stacktree, and send the private link. The client opens it in any browser with no account and no download. Add a passcode, see when it was opened, and replace the page in place after the call. ## Where the workflow stops Claude for Small Business launched on 15 September 2026 as a Cowork plugin with 43 ready-to-run workflows. One of them, Proposal builder, turns a voice memo, a photo or an RFP into a branded proposal priced from your past jobs. It is a genuinely good piece of automation, and it ends exactly where every one of the 43 ends: with a document, and a deliberate pause. Nothing sends until you approve it. That pause is correct. What is not correct is what most people do next, which is attach the file to an email. The client downloads it, opens it from their file system, reads it in whatever application claims the extension, and you learn nothing about whether they got past page one. If the file is a large self-contained HTML page, it may not arrive at all: Gmail caps attachments at 25 MB, and mail filters treat HTML attachments with justified suspicion. A proposal is a document whose entire job is to be opened, read and acted on. Sending it in the one format that resists all three is a strange way to end a good workflow. ## The send step, in seven moves - Run the workflow. Proposal builder, or whichever one applies. Review what it drafted and approve it. This is the part Cowork already does well. - Save the output as a page. Ask for the deliverable as one self-contained HTML file, or export the document it produced to HTML. One file, styles and images inside it, nothing to unzip. - Publish it. Drag the file onto the Stacktree dashboard, or let Claude do it: Cowork speaks MCP, so the publish_html tool publishes the file it just wrote and hands back the URL in the same session. Either way you get an unguessable link that appears in no listing and no search index. - Add a passcode. One shared secret you tell the client, so a forwarded link alone opens nothing. If the proposal is going to several people at one company, restrict it to their email domain instead and let anyone at that domain in after a one-time magic link. - Send the link. Paste the URL into the email or the thread you were already writing. The client clicks and reads a page, on a phone in a taxi if that is where they are. - See when it is opened. Opens and last-read on Solo, plus the reactions and notes the client leaves on the page itself. Studio adds time on page, scroll depth and a dwell heatmap, so you can tell whether they reached the pricing section before they replied. - Update in place after the call. They asked for a different scope. Re-run the workflow, publish over the same site, and the link in their inbox now shows the revised proposal. No resend, no version two in the subject line, no risk of the wrong number being the one they sign. ## Why a link beats an attachment for a proposal - It opens. On any device, in any browser, with no application and no download prompt. - It is current. The version they see is the version you published most recently, so revisions do not fork. - It is private on purpose. Unguessable by default, passcode or company-domain gated when you want it, expiring on a date you choose. - It tells you something. Opened, when, how far read. A proposal opened three times the morning before a decision is useful information. - It looks like your work. Put it on your own domain, so the client reads it at proposals.yourfirm.com rather than at a vendor URL, and paid plans render no badge. ## Let Claude do the publishing If you would rather not touch a file at all, connect Stacktree as an MCP connector and stay inside Cowork. The plugin package is open at [github.com/stevysmith/stacktree-skill](https://github.com/stevysmith/stacktree-skill), carrying the publish skill, the job-shaped skills for client deliverables and reports, and the Stacktree MCP server. Cowork accepts a Git repository as a marketplace, so the repository URL goes straight into Customize, Plugins, Add marketplace. The plugin mechanics in full are on [Claude Cowork plugins and skills](/claude-cowork-plugins). Once it is connected, the end of a workflow becomes one more approved step: Claude publishes the proposal, sets the passcode, and gives you the link to paste. The same server works from [Claude Code](/claude-code) and any other MCP client, which matters if half your work comes out of a terminal and half out of Cowork. ## Also read If you are starting the proposal rather than finishing one, the [business proposal template](/templates/business-proposal) is the shape to hand Cowork: what a priced proposal needs on the page, in the order a client reads it. For the wider handoff, [sharing deliverables with clients](/share-with-clients) covers reports, dashboards and demos behind the same gates, and [sharing an HTML file with a client](/share-html-file-with-client) is the format-level version of this page. ## Which plan does this handoff need? Filing work under a client is free on every plan. What a paid plan buys is time on the clock and an address of your own. - Free $0 ### One handoff this week 3 pages, each live for 7 days, passcodes included. If one comes down before you meant it to, it is restorable from the dashboard for 48 hours. [ Start free ](https://app.stacktr.ee/?join=1&from=seo_share_claude_cowork_output) - Solo $19 a month ### A link the client keeps (paid-media dashboard, monthly report, proposal) 25 pages that never expire, your own domain, one client space, passcodes and company-email gates, and no Stacktree footer. [ Start with Solo ](https://app.stacktr.ee/billing?plan=solo&from=seo_share_claude_cowork_output&join=1) - Studio $79 a month ### Several clients, each with their own address Unlimited pages, 10 client spaces and 10 domains, so every client gets a permanent address, one passcode, and engagement detail on what they read. [ Start with Studio ](https://app.stacktr.ee/billing?plan=studio&from=seo_share_claude_cowork_output&join=1) FAQ ## Frequent questions How do I send a proposal from Claude Cowork to a client? + Publish it as a page and send the link. Run the workflow, ask Cowork for the deliverable as one self-contained HTML file, publish that file to Stacktree by dragging it onto the dashboard or by letting Claude call publish_html, and paste the URL into your email. The client opens a real page in their browser with nothing to download and no account to create, and you can put a passcode on it first. Can Claude Cowork send the proposal itself? + Only after you approve it. Anthropic is explicit that the Small Business skills draft, propose and stage, and that you approve before anything sends, posts or pays. That is the right default for a document with your pricing in it. What the workflow does not decide is what the client receives: an attachment they download, or a link they open. That choice is yours and it is the one that changes how the proposal reads. Does the client need a Claude account to open it? + No, and no Stacktree account either. The unguessable URL is the credential. If you add a passcode or restrict viewing to their company email domain, the client passes that gate in the browser: there is still nothing to install, nothing to sign up for, and no seat to pay for. Can I put a password on a proposal I send? + Yes. Set a passcode and tell the client, and forwarding the link alone opens nothing. Passcodes are on every plan, Free included. For a company-wide handoff, an email-domain gate lets anyone at yourclient.com in after a one-time magic link and keeps everyone else out. Gated pages also unfurl in Slack and Teams as a locked graphic, so the preview of a confidential proposal leaks no title and no numbers. How do I know if the client opened the proposal? + Every plan shows the reactions and notes viewers leave anchored to parts of the page. Solo adds the numbers: how many people opened it and when it was last read. Studio adds time on page, scroll depth, read-to-end rate and a dwell heatmap, all aggregate and anonymous. For a proposal, knowing it was opened twice on Thursday afternoon is worth more than a read receipt on an email. The client asked for changes. Do I send a new link? + No. Re-run the workflow, publish the revised page to the same site, and the URL stays identical. The client refreshes the link already in their inbox and sees the new version. That is the part an attachment can never do: once a file is sent, it is frozen, and every revision becomes another email and another chance for the wrong version to get signed. Can Cowork publish the page itself, without me exporting anything? + Yes. Stacktree is an MCP server and Cowork uses MCP connectors, so Claude can publish the file it just wrote and hand back the private link in the same session. The plugin package that carries the publish skill and the server is open at github.com/stevysmith/stacktree-skill, and because Cowork accepts a Git repository as a marketplace, the repository URL is installable from the Plugins page. What format should the deliverable be in? + A single self-contained HTML file is the format that travels best, because it renders as a page for the client instead of arriving as a download. A proposal that opens instantly on a phone, with the pricing laid out and nothing to install, gets read; a 4 MB attachment gets opened later. If Cowork produced a document, ask it for the HTML version of the same content. How long does a free page stay up? + 7 days. Every page published on the Free plan comes down 7 days after you publish it, and Free is 3 pages in total. A page that has come down is restorable from the dashboard for 48 hours. Starting a paid plan clears the expiry on every page already published, so a proposal your client is still deciding on stops counting down. Keep reading ## Related guides - [ What is Claude Cowork? Plans, platforms, use cases, and how it differs from Claude chat. ](/what-is-claude-cowork) - [ Claude Cowork plugins and skills The 43 Small Business workflows, and how to install a plugin. ](/claude-cowork-plugins) - [ Claude Cowork vs Claude Code Same agentic engine, two front doors. Which one your work belongs in. ](/claude-cowork-vs-claude-code) - [ Publish HTML from Claude Code One command, one OAuth sign-in, a private link in a tool call. ](/claude-code) - [ Share a Claude Design privately The export-then-publish move for design files. ](/share-claude-designs) - [ Business proposal template What a priced proposal needs on the page, in the order a client reads it. ](/templates/business-proposal) - [ Client feedback loop Comments on the live page, readable by you or by the agent that built it. ](/client-feedback-loop) - [ Pricing Passcodes on every plan; permanence, your domain and no badge from $19. ](/pricing) References ## Sources and further reading - [ Anthropic: Claude for Small Business ↗ The 15 September 2026 launch post, including Proposal builder and the approve-before-anything-sends rule. ](https://claude.com/blog/claude-for-small-business-launches-new-workflows-integrations-and-training-programs) - [ Claude Help Center: Get started with Claude Cowork ↗ What Cowork is, which plans have it, and how connectors and MCP servers reach outside services. ](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork) - [ Google: Gmail attachment limits ↗ The 25 MB cap that self-contained HTML deliverables run into. ](https://support.google.com/mail/answer/6584) - [ Microsoft Security: HTML smuggling ↗ Why mail filters and recipients treat an .html attachment with suspicion. ](https://www.microsoft.com/en-us/security/blog/2021/11/11/html-smuggling-surges-highly-evasive-loader-technique-increasingly-used-in-banking-malware-targeted-attacks/) ## Send the proposal as a page, not a file. Start from the proposal template, publish it private, add a passcode, and see when your client opens it. [ Start from the proposal template → ](https://app.stacktr.ee/new?template=client-proposal&join=1&from=seo_share_claude_cowork_output) stacktr.ee [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers) --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt