Send a client report as a link, not a PDF attachment
Every month you build the same deliverable — the ads report, the SEO round-up, the performance summary — and every month it leaves the building the same bad way: exported to PDF, attached to an email, opened on a phone as a wall of unreadable eight-point tables, and then quietly ignored. A hosted report fixes all three problems at once. You publish the page, you send one line and a link, and your client opens something that was actually designed for a screen. This page is about making that the default for the work you send out on a cadence.
Build the report as one HTML file
Pull the numbers the way you already do, then have your model lay them out as a single self-contained page — headline metrics with the change against last period, your commentary, what you did, what is next. The starter prompt below is the one our own client-report users copy; paste your figures into its placeholders and you get a file, not a project.
Drop it on host-html and check the preview
Paste the code or drag the .html file onto the drop zone. The preview renders exactly what will ship, so you catch a broken table before the client does. Publish and you have a link — no git, no build, no deploy pipeline waiting on you at 6pm on the last day of the month.
Send one line and the link
The email becomes a sentence instead of a 3MB attachment. Afterwards the page's own stats tell you whether it was opened and where the visit came from, which is the question you have never been able to answer about a PDF.
Why the report should be a page, not a file
An attachment fails in ways a link simply cannot. It bounces off a mailbox size limit, it gets stripped by a corporate filter, it renders badly on the phone your client is actually holding, and the moment one figure changes you have to send a second file and hope they open the right one. A link has none of those failure modes: one URL, always the current version, laid out for whatever screen it lands on.
It also lets the report do things paper cannot. Charts that respond to a hover, a table the client can sort, a section that expands when they want the detail and stays collapsed when they don't. A PDF flattens all of that into an image of a report. And you no longer need a design team to produce one — ask Claude or ChatGPT for a self-contained HTML report with your numbers and your section order and it will hand you a single file, which is exactly the input host-html takes.
Then there is the part nobody talks about: you find out whether it landed. Per-page analytics on a paid plan tell you the report was opened, when, from where and on what kind of device. That is a far better opening for the next call than "did you get a chance to look at it?"
Running the monthly cadence properly
The pattern for a recurring deliverable is one page per client per month. Publish August's report as its own page, send the link, and leave it alone. On a paid plan you choose the slug, so the URL can read like the report it is rather than a random string of characters — which matters when the client forwards it to their own boss.
Collections gather the whole run behind a single link at host-html.com/c/your-name, so a client who wants to compare March with August is one click away from both instead of digging through eleven emails. That one link is also the thing you hand over at a quarterly review.
And when you spot a wrong figure ten minutes after sending — everyone has — in-place editing on a paid plan rewrites the page behind the same URL. The link already sitting in their inbox shows the corrected number. No apology email, no "please ignore my previous message", no second version circulating with your name on it.
What the client sees, and what it costs you
Your client needs no account, no app and no login. They tap the link and read the report, on a laptop or on a train. If the numbers are commercially sensitive you can put the page behind a password on a paid plan, and on Pro you can remove the small host-html badge so the deliverable carries nobody else's branding — which is usually the first thing a consultant asks about.
Publishing is free: a free account takes about five seconds and no card. Free pages carry an expiry date, which host-html puts in front of you at publish time rather than burying it — 5 days, fine for a one-off, and wrong for a report a client may pull up next quarter. Pro is $12 a month, or $120 a year, and keeps every page live forever. Permanence is the specific reason most people on a reporting cadence pay: the link in last March's email still resolves.
The attachment against the link
| Emailed PDF | Hosted page | |
|---|---|---|
| Opened on a phone | Eight-point tables, pinch and zoom, half of it off the edge | Reflows to whatever screen it is opened on |
| A number turns out wrong | Re-export, re-attach, and an email that starts “ignore the last one” | Fix the page in place on Pro — the link you already sent shows the corrected version |
| Did they read it | No idea unless they reply | Page views, referrers and countries on the page's own stats — page-level, not per-recipient |
| Getting there at all | Attachment size limits, spam filters, a Drive link nobody has access to | One URL that travels through email, Slack and WhatsApp the same way |
| Finding it next quarter | Buried somewhere in an inbox thread | Still at the same address — permanently on Pro; a free page comes down after 5 days |
What this needs from host-html
- Per-page analytics — Views, unique visitors, referrers and countries per report. It tells you the page was opened, not which recipient opened it.
- Pages that outlive the engagement — A free report page expires after 5 days. Pro keeps every month's report at its original URL for good.
- Collections — Group the whole year of reports behind one link the client bookmarks once.
- The prompt library — Fourteen starter prompts for the artefacts operators actually ship — reports, portals, proposals, audits, invoices.
Frequently asked questions
How do I send a client report as a link instead of an attachment?
Save or copy your report as a single self-contained HTML file, paste it into host-html or drop the file on the upload zone, and publish. You get a live URL you can put in one line of email, and the client opens it in their browser with nothing to download.
Can the client open the report without an account or a login?
Yes. A published page is an ordinary web page, so the recipient needs no host-html account, no app and no signup. If you would rather restrict it, password protection on a paid plan gates the page behind a passphrase you share separately.
What happens if a number changes after I have sent the report?
On a paid plan you edit the HTML in place and the URL stays identical, so the link you already sent now shows the corrected figure. Version history keeps the previous snapshot, so you can still see exactly what the client saw before the fix.
Can I tell whether the client actually opened the report?
Yes, at the page level. Every plan records views, and detailed analytics on a paid plan add referrers, countries and device types. You will see that the report was opened and roughly from where — not which individual person opened it.
Where do last month's reports live?
Each report is its own page in your dashboard, and collections let you group a client's whole run behind one link. That gives the client a single archive URL instead of a folder of attachments scattered across a year of email threads.
How long does a client report page stay online?
A free page expires automatically after 5 days, with the exact date shown before you publish. On Pro, $12 a month, every page lives forever, which is what you want for a deliverable a client may re-open months after you sent it.