Claude can write a proposal, build a clickable mockup or turn a spreadsheet into a report in minutes. Getting it to a client is the awkward part: attachments get lost, HTML files get blocked, and once you hit send you have no idea whether anyone looked. This guide shows how to send what Claude built as a proper link — and see the moment your client opens it.
What you need
- A free ArtifactDeploy account.
- ArtifactDeploy connected to Claude once: in Claude, open Settings → Connectors → Add custom connector and paste
https://mcp.artifactdeploy.com/mcp. (Claude Code and other apps: see the setup guide.)
Step 1 — Build it and deploy it
Ask Claude for the deliverable, then ask it to publish:
“Build a one-page proposal for Rahul’s café website: scope, timeline, three pricing options and next steps. Then deploy it as ‘Café website proposal’.”
Claude replies with a live link a few seconds later. Open it on your phone — it’s a real web page, not a file, so it reads well anywhere.
Step 2 — Make it look good when you share it
When you paste a link into WhatsApp, LinkedIn, Slack or email, the app shows a preview card. Every ArtifactDeploy link gets one automatically, and you can set your own title, description and image:
“Set the share title to ‘Café website — proposal for Rahul’ and the description to ‘Scope, timeline and pricing, ready to review.’”
A clear card makes the link look like something worth opening — and it’s the first thing your client sees.
Step 3 — Create a personal link for each person
This is the part that changes how you follow up. Instead of sending everyone the same URL, give each person their own:
“Make personal links for Rahul and Meera.”
Each personal link is the same page with ?to=Name on the end. Send Rahul his link and Meera hers. You can also create them in the dashboard under Deployments → Share → People. Personal links work on every plan, including Free.
Step 4 — See who opened it
Ask Claude, or open the People tab:
“Who opened the café proposal?”
You’ll see whether each person opened it, when, and how many times. Link-preview bots (WhatsApp, Slack and so on) are filtered out, so a preview card loading doesn’t count as an open. If someone forwards their link, those views still count under their name — useful to know when a proposal is being passed around internally.
How to use this to follow up
- Opened within an hour: they’re interested. A short “Any questions on the proposal?” lands while it’s fresh.
- Opened three times: they’re probably discussing it. Offer a 15-minute call.
- Not opened after two days: the email may have been missed. Re-send with a one-line summary rather than “just following up”.
When the client asks for changes
Ask Claude to make them: “Change the timeline to six weeks and add a maintenance option.” Claude updates the same deployment, so the links you already sent show the new version. No “proposal-final-v3.pdf”.
Keep drafts and pricing private
On Pro, add a password (“Protect the proposal with the password café-2026”) or make a deployment private while you work on it. You can also put client work on your own domain, such as proposals.yourstudio.com.
It works for more than proposals
The same steps work for mockups, monthly reports, pitch decks, audits and dashboards. If you send work to clients regularly, see ArtifactDeploy for freelancers or for consultants, or start from a ready-made design in the template gallery.