For agencies and sales teams

Twenty proposals a month.
One live link per client, all of them measured.

Pitches, proposals, monthly reports, creative approvals: your team already generates them with AI. Hostus gives each client a folder, each deliverable a gated link, and you a view of who opened what, across every account.

Free plan · no card · 30 seconds
Monday pipeline review

Which proposals were opened? Which ones died at the price?

1 · Last week

Eight proposals went out

Acme, Bolt Retail, Cardo, Delta Clinics, Ember, Fjord, Grove, Helix.
Each on its own gated link, in its own client folder.
8 docs · gate by domain
2 · This morning

The reading data

5 opened. Acme and Grove re-read Pricing. Delta never got past Scope. Bolt, Cardo, Helix: not opened yet.
per reader · per section
3 · 10:00

The team acts

Call Acme and Grove today about ROI. Re-send Bolt, Cardo, Helix with a new preview title. Ask Claude to shorten Scope on Delta's link.
same links · new versions
Four workflows, at your volume

What an agency does with Hostus

proposal · pitch · quote

Proposals at volume, each one identified

Twenty PDFs a month and no idea which ones were opened, forwarded to procurement, or abandoned at the price.

Gate each proposal to the client's domain. Every reader at the company is identified; you see who opened, when, and which section held them. Time the follow-up call on the day they read Pricing.

Email gateWho openedReading by section
client folder · data room

A data room per client, without the contract

Proposal, reports, creative rounds and notes scattered across email threads and three drives.

One folder per client, shared with one invite link. Everyone you add sees every doc inside, read-only, including the ones you add next month. Subfolders up to three levels for accounts with many workstreams.

Folder sharingPrivate linkVersion history
brief · approval · sign-off

Briefs and approvals that store themselves

Campaign briefs come by WhatsApp, approvals by "ok" in an email thread. Nothing is where you need it when the client disputes a change.

Put the brief form or the approval checkbox inside the branded page. Every submission lands in an inbox on the doc and in your email with Reply-To set to the client, exportable as CSV, with the date.

Forms that workReply-ToCSV export
monthly report · dashboard

Reports Claude updates by intent

Twelve monthly reports, twelve new PDFs, twelve emails, every month.

One link per client. Connect Claude and say "update the Acme report with October's numbers". It edits the live page on the same link; the previous edition stays in history. The client bookmarks one URL forever.

Same linkClaude connectorVersion history
Reading by section

Every proposal reports back, per reader

Time per section anchored to your headings. Per reader on gated docs. Cookieless, no IPs stored, nothing to disclose in the client's security questionnaire beyond an email gate.

The same card exists for every proposal, report and case study you send. Compare them and you learn which structure closes.

Responses

Briefs, approvals and sign-ups in one inbox

Any form with named fields in a hosted page stores its responses. Unread state, reviewable spam folder, CSV, close after N, your own tests tagged.

Replying to a client's brief is a plain reply: the email has Reply-To set to them.

Pages agencies host on Hostus

Every client-facing artifact your team makes with AI

Proposal

Scope, timeline, pricing options, gated to the client's domain.

Email gateReading by section

Pitch deck as a page

The deck Claude wrote as HTML: scrolls on a phone, embeds video, changes after the meeting.

Edit in placeLink preview

Monthly performance report

One link per client, updated by Claude with the new numbers each month.

Same linkClaude connector

Creative approval page

Three options, an approval form per option, the client's pick in your inbox with a timestamp.

Forms that workCSV export

Campaign brief form

Your branded intake form instead of a generic one; answers with Reply-To set to the client.

Forms that workReply-To

Case study for prospects

Results behind an email gate, so you know which prospect read it and how far.

Email gateWho opened
Why HTML instead of PDF decks and proposal software

Brand fidelity, interactivity and control, at agency volume

Pixel-perfect on brand

The page is whatever your designers or your AI write in HTML. No proposal tool's template, no watermark.

Interactive proposals

Pricing toggles, option tabs, embedded reels and video, calculators. Clients explore instead of skimming a PDF.

Control after sending

Fix a number across a live link, revoke access when a deal dies, keep every version for the dispute you hope never comes.

Signal across accounts

Who opened, who re-read Pricing, who never got past Scope. Compare proposals and learn which structure closes.

Speed from Claude

Generate, publish and update by intent from the chat. "Update the Acme proposal with the new scope" is a sentence, not a task.

Nothing to install for the client

A link in the email. Gate means typing an email; private means a magic link. No portal, no password.

With Claude connected

Pipeline review in one question

You
Which of last week's proposals were opened, and where did people stop?
Claude
Five of eight opened. Acme and Grove re-read Pricing; Delta stopped at Scope; Bolt, Cardo and Helix have not opened yet. Want me to shorten Delta's Scope section, and draft a re-send note for the three unopened ones with a new preview title?

Twelve tools over MCP: publish and update by intent, semantic search across every client doc, reading data (hostus_attention), form responses (hostus_responses), saved context. One OAuth login in the Claude app.

How it works

Three steps per client, then it runs itself

01

Create the client folder

One folder per account, subfolders per workstream if you need them. Share it once with the client's team; every doc you add later is covered.

02

Publish each deliverable

Drop the HTML or let Claude publish it. Gate proposals to the client's domain, keep internal docs private, set the link preview.

03

Read the signal, update in place

Who opened, what held them, which brief came in. Fix on the same link or ask Claude to. Call on the right day.

Good to know before you switch

Accounts are individual today: one owner publishes, and folders are shared read-only with clients and colleagues. There are no team seats or co-editing yet, and no custom domain: links are acme-proposal.v.hostus.io. Hostus hosts HTML, not PDFs, and does not do e-signatures. The free plan covers 20 docs, 2 MB of HTML and 100 form responses a month; at agency volume you will likely move to the paid plan ($9.99 a month or $49.99 a year) for unlimited docs and responses and 200 MB. The inline editor is desktop-only.

Questions people ask

Can several people on my team publish?

Today one account owns the docs; colleagues can be given read access through folder sharing. Team seats and co-editing are not built yet. If you need them, write to team@hostus.io.

Can the client's whole team open a proposal?

Yes. Gate by their domain and anyone at the company opens it with an email, each one identified. Or restrict to a list of names.

How do approvals work without e-signature?

Put an approval form on the page: name, checkbox, comment. The submission is stored with a timestamp, emailed to you with Reply-To set to the client, and exportable as CSV. For a legally binding contract keep your e-signature tool.

What happens when a deal dies?

Switch the doc to private or remove the domain from the gate. Access ends on the next request, media included. The doc and its versions stay in your account.

Does the free plan cover an agency?

It covers your first twenty live docs with every feature, no card. Past that, the paid plan is $9.99 a month or $49.99 a year for unlimited docs and responses and 200 MB.

Give every client one live link

Free plan, no card. Publish this week's proposals as gated links and run Monday's pipeline review on real reading data.