a proposal as a pdf is a dead end: it is stale the moment the scope shifts, it opens badly on a phone, and you cannot tell whether anyone read it.

a proposal as a page is a link. the agent writes the scope, outcomes, timeline, and pricing from your notes; htmlshare gives it a url you can send, update after the call, and point at again when it is time to sign.

same content, one less round of "here is v3 final revised.pdf".

a starting point, not a template — the point of an agent is that the result is yours. replace anything in [brackets] and add whatever the page actually needs.

Create a polished, responsive client proposal for [CLIENT NAME] from [YOUR NAME / COMPANY].

Goal:
A proposal the client can read on a phone in three minutes and act on.

Content and requirements:
- Header: client name, project title, date, proposal validity period
- "The problem" — the client's situation in their own words, not yours. Two short paragraphs
- "What we'll do" — scope as concrete deliverables, each one a thing that either exists or
  doesn't when the project ends
- "Out of scope" — say it explicitly; this section prevents more arguments than any other
- "Timeline" — phases with dates or durations, and what the client owes you at each one
- "Pricing" — [FIXED FEE / TIERS / RATE]. If tiers, three at most, with a recommended one
- "Terms" — payment schedule, revisions included, cancellation
- "Next step" — one specific action with a contact link

Design direction:
- [YOUR BRAND COLORS AND TONE]; confident and plain, not corporate filler
- Pricing legible without scrolling past it
- Mobile-first and accessible
- Clear hierarchy and fast loading

Delivery requirements:
- Produce one self-contained HTML file.
- Include CSS and JavaScript in the file where practical.
- Do not require a build step or server.
- Use placeholders where information is missing; do not invent facts — especially not
  prices, dates, client details, or past results.
- If an HTMLShare integration is available, publish or update the artifact there.
- Otherwise save the final .html file ready to upload to HTMLShare.

• paste your call notes in with the prompt. a proposal written from the client's own phrasing lands differently from one written from a template.
• the "out of scope" section is the one people delete and later wish they had not.
• keep the agent away from inventing numbers. give it your rates, or leave the bracket in and fill it yourself.

claude

paste your notes, let claude draft, then iterate in the same conversation — "make the pricing table three tiers", "cut the intro in half". with the mcp connector on, the final version publishes straight to a url and update_html keeps that url current through revisions.

chatgpt

ask for one self-contained html file, download it, and drop it on the htmlshare home page. re-uploading makes a new url, so if you expect revisions, publish with an account and update in place instead.

cursor

useful when the proposal is one of many: keep a proposals folder, let the agent copy the last accepted one as a starting point, and publish each with an api key.

stable updates

the scope changes after the call. the client should re-open the same link and see the new version, not hunt for a newer attachment.

custom slug

yourname.htmlshare.net/acme-proposal reads like your work. a random id reads like a file host.

password

pricing is the one part of your business you would rather not have indexed.

analytics

knowing the proposal was opened twice on a monday morning is worth more than the follow-up email you would otherwise send blind.

can the client sign it?

not on the page — htmlshare publishes documents, it does not do signatures. the usual pattern is a proposal link plus whatever you already use to sign.

what if i need it as a pdf too?

print to pdf from the browser. ask the agent for print styles in the prompt and it will come out cleanly.

is it private?

a published page is reachable by anyone with the url, and htmlshare noindexes uploaded pages so they stay out of search. for a proposal with real pricing, use a password.

• give your agent a url to come back to.
• everything in business
• publishing from an agent or the api