Updated
Share an AI-built prototype with a client and get feedback on it
By João Saraiva
A prototype built in Claude or ChatGPT is easy to make and awkward to review: screenshots lose what it does, and feedback scattered across email loses which version it was about. Here is how to send it as one link, collect comments pinned to the page, change it without breaking the link, and see whether it was opened.
How do you get client feedback on a prototype built with AI?
Send it as a working page at a link, not as a screenshot or a file, and collect comments on the page itself. On Solta, paste the HTML or React file Claude or ChatGPT wrote, or ask the chat to publish it through the connector, and turn on Comments for the site. Send the client the site's page in Solta, at solta.now/s/ and its name: they click a spot, write what they mean, and leave their email address, with no account. Each comment stays with the version it was about. When you change the prototype, the new version is a draft until you publish it, then the same link shows it, so the client never opens half-finished work. Its analytics show how many people opened it, and from where, without cookies. For sign-off, approval makes a new version wait until the client approves it.
Paste your prototype in the box below
Send it at a link the client can open
A site has two addresses. Its own, ending in solta.site, opens it on its own, full screen: that is the one for the finished thing. The site in Solta, at solta.now/s/ and its name, shows the same site with the Comments and Versions panels beside it: that is the one to send for feedback, because pinned comments show only there.
Your client needs no account to open either, and never pays. Keep it to the people it is for with a password, on every plan, or Invited, on Pro and Team, where only the addresses you add get in. Who can open what you send, and why Claude's own link asks for an account.
Collect comments pinned to the page
- Open the site in Solta and switch on Comments at the top of its Comments panel. They are off for a new site.
- Send the client the site's page in Solta.
- They choose Comment on the page, click the spot they mean and write. On a Public, Unlisted or Password site they leave their email address with it; on an Invited site, the people you invited to comment can.
- You get an email, gathered over a few minutes so a burst of comments is one message. Reply in the panel, and choose Mark as resolved on each one when it is dealt with.
A comment belongs to the version it was left on, and a new version starts with none, so what was said about version 2 never reads as if it were about version 3. With the connector added, you can also ask Claude or ChatGPT whether anyone has commented, and reply from the chat. How comments work.
Change it without changing the link
Paste or upload the new version, or ask the chat for the change. It is saved as a draft, and the link, its QR code and any page that embeds it keep showing the live version until you publish; then they all show the new one. Each published version keeps an address of its own under the site's, ending in /v/ and its number, so you can send the client a before and after. Free keeps the last 5 versions; Pro and Team keep every one, and an older one can be put live again. Drafts and versions.
Get sign-off before it goes live
On Pro and Team, turn on approval for the site and invite the client as an approver. A version you send for review waits until they approve it, the link keeps serving the old one meanwhile, and the history records who approved it and when. On Team, approval can be the default for every new site in a workspace. Approvers are free. Approval.
See whether it was opened
Each site's Analytics show views and visitors by day, with countries, devices, pages and the websites people came from. There is no cookie and no identifier, so they count visits; they don't name anybody. Free looks back 30 days.
To know who opened it, switch on Ask for an email first in Who can open this, on Pro and Team: each visitor gives an address before it opens, and you see every address, when it first and last opened the site and how often, with a CSV. Tick Verify the address with a code to check each one. Analytics.
Close it when the project ends
On every plan, give the link an end date. After it, the address says the link has expired, and a visitor who still needs it can ask you for it again. Nothing is deleted, and you still open it in Solta. Links that expire.
Questions
Does my client need an account to leave feedback?
No. On a Public, Unlisted or Password site, somebody without an account leaves their email address with the comment and needs nothing else. On an Invited site, the people you invited with comment access can comment, after verifying their address once.
How do I update a page I already sent without changing the link?
Upload or paste the new version, or ask Claude or ChatGPT to change it through the connector. It is saved as a draft, and the link keeps showing the old version until you publish; then the same link shows the new one. Free keeps the last 5 versions, and Pro and Team keep every one.
Can I see who opened the link?
Not by name from the link alone: a site's analytics count views and visitors, by day, country, device, page and referrer, with no cookie and nothing kept about any one person. To know who, switch on Ask for an email first, on Pro and Team: it lists each address a visitor gave, when it first and last opened the site, and how many times. To decide who, use Invited, on Pro and Team, where only the addresses you add get in.
Can the client approve a version before it goes live?
On Pro and Team. Turn on approval for the site and invite the client as an approver, who signs in with that address to approve: a new version waits until they do, and the version history records who approved it and when. Approvers are free and are not counted as publishers.
Can I stop the link working when the project ends?
Yes, on every plan. Set an end date under Who can open this, and after it the link says it has expired. Nothing is deleted, and moving the date opens the same link again.

