The situation
You run a small studio. Your agent drafted the redesign proposal for Harbor & Co in twenty minutes, and now it has to survive the client. The usual route is a PDF by email, a week of “see my comments in the attached”, and a final call where nobody is sure which version is current.
What you say
You, to your agent
Turn the proposal into a PTAL page for Dana at Harbor & Co. Add an approval form at the end and give me the link.
The agent publishes the proposal as a clean page and appends a short form: Approve, Approve with changes, Not yet, and a notes box. You paste the link into your email. Because it is a link and not a file, you can later say “publish version 2” and Dana’s bookmark just updates.
What the client sees
A page with your studio’s name on it and no PTAL account to make. Dana reads it on the train. She highlights “six weeks” and asks whether five is possible because the board meets then. She highlights “Copywriting is not included” and asks for it as an option. Then she picks Approve with changes and hits Send. Every one of those lands in your agent’s inbox with the exact words she pointed at.
What comes back
You, to your agent
Any word from Harbor?
- Dana on
six weeks
: “Board meets in five. Can we do five?” - Dana on
Copywriting is not included
: “Can you quote copy as an option?” - Dana: answered the form: Approve with changes.
You tell the agent five weeks is fine if copy arrives by week two, and to add copywriting as a priced option. It replies on each of Dana’s notes, publishes version 2 at the same link, and marks the threads resolved. Version 1 stays in the history, which is useful when someone asks what changed.
Why it works here
- The client needs nothing. No account, no seat on your tools, no PDF viewer arguing about comment support.
- Comments carry the quote. “Can we do five?” arrives attached to “six weeks”, so nothing is ambiguous and nothing is copied by hand.
- Approval is data. The form answer is a field, not a sentence buried in an email. Your agent can act on it, or a script can.
- One link, every version. Redlines go to the same URL. Your agent can restore any earlier version if the conversation goes backwards.
- Private enough. Unguessable link, no search indexing, an optional password, or limit the page to signed-in readers.
On Pro, an organization can require a password or a sign-in on every client page. See the sharing policy.