Use cases
Turn your next proposal into a private webpage instead of a PDF
3 September 2026 · 3 min read
Most proposals still go out as an attachment named something like final_v3_revised.pdf. It works, technically, but it's rarely a great first impression, and it definitely isn't the easiest thing to read on a phone. A small private webpage does the same job: the problem you understood, the scope, the timeline, the price, and what happens next, just without the attachment.
What goes on the page
Start with the problem as you understood it, so the client sees you actually listened before you start pitching. Then the scope, the timeline, the price, a couple of relevant examples if you have them, and what happens next if they say yes. Keep the order deliberate: understanding first, offer second.
End with a way to say yes
Add a WhatsApp or email button at the end so the client doesn't have to figure out how to reply. A floating WhatsApp button is a Growth tool on a Pro full site: set your number and a prefilled message, and it's there the moment the page goes live, no extra setup on the page itself.
If scope changes, edit the same page
A call happens, something in the scope shifts, and instead of a fourth PDF named final_v4, you update the same page and send the same link again. The client never has to figure out which version is current, because there's only ever one.
Keep it from being public
A proposal usually shouldn't be sitting somewhere a search engine can find it, or open to anyone who happens to guess the URL. Password protection on a Pro full site is the real access control here: nobody gets in without the password you set. A microsite is lighter, but weaker, it just isn't indexed by search engines, while the link itself still works for anyone who has it. That's fine if the link only ever goes to the client directly; password protection is the better call if the proposal is sensitive enough that you want that guarantee.
What actually makes this work
A fancy page won't save a weak offer, and it was never going to. What it does is remove the friction between a good offer and a client actually opening it, reading it properly on their phone, and replying without hunting for the right app to reply in.
Key takeaways
- ✓Lead with the problem you understood, then scope, timeline, price, examples, and what happens next.
- ✓A floating WhatsApp or email button at the end removes the last bit of friction between reading the proposal and replying to it.
- ✓If scope changes after a call, edit the same page instead of sending another PDF revision.
- ✓Password protection on a Pro full site actually restricts who can open it; an unlisted microsite just isn't indexed by search engines, anyone with the link can still view it.
Frequently asked questions
How do I add a WhatsApp button to a proposal page?
It's a Growth tool on a Pro full site. Enter your WhatsApp number and a prefilled message in the dashboard, and the button appears on the live page with no code to add.
Should a proposal page be public or private?
Password-protect it on a Pro full site if you want real access control, only someone with the password gets in. An unlisted microsite is lighter: it isn't indexed by search engines, but the link itself still works for anyone who has it, so only share it with the client it's meant for.
What if the scope changes after I send it?
Edit the same page and upload it again. The link doesn't change, so the client is always looking at the current version, not an old one still sitting in their inbox.
Is a webpage actually better than a PDF here?
It opens more reliably on a phone, it's easier to update without renaming a file, and it can end with a button the client can actually tap to reply. It won't fix a weak offer, but it removes friction around a good one.