Reviewing v0, Lovable and Bolt prototypes with stakeholders

By the HTMLAnnotate team14 November 20263 min read

AI app builders make a working prototype in an afternoon. Then you need a client, a manager or a co-founder to look at it and say what's wrong. Each tool shares differently, and some links only work for people with an account. Here is how to get a prototype in front of reviewers in v0, Lovable and Bolt, checked in each tool's own docs on 14 November 2026.

Why sharing a prototype is fiddly

AI builders give you two kinds of link. One opens the project in the builder, where the reviewer can see the chat and the code, and usually has to sign in. The other is the published site, which works like any website. Reviewers want the second one. Most also don't want to create an account to look at something for five minutes.

v0

Press Publish in the chat header. v0 deploys the prototype to a production address on vercel.app, or your own domain, and later changes go out with Publish Changes. Vercel's default protection covers preview deployments and leaves production addresses public, so the published link opens for anyone.

You can also share the chat itself from the Invite dialog, with "Anyone with the link" or "Anyone on the web". That shows the conversation and the generated app, which suits other builders more than clients. If your Vercel project uses Vercel Authentication or password protection, reviewers will hit a sign-in screen, so check the link in a private window first.

Lovable

Publishing puts the app on your-app.lovable.app. The audience setting decides who can open it. "Public" means anyone with the link, and every plan can limit it to invited people instead. Workspace and organisation-only options come with the Business and Enterprise plans.

Lovable also has preview links, which are view-only and open without a Lovable account. They expire after 7 days on the Free and Pro plans. Business and Enterprise can set longer expiry and add a password.

Bolt

Click Publish, then Publish again. The site goes to a bolt.host address with a random name you can edit, or to Netlify if you've connected it. Published sites are public by default, and on the Free plan they always are. Paid plans can make a site private to your team or invited emails.

Don't send the project link to reviewers. Bolt says people opening a project must have an account and be signed in.

Which link to send

From each tool's own documentation, checked on 14 November 2026.

Getting comments on the page

A link on its own gets you an email back: "the second card looks weird on my phone". To get comments pinned to the exact element, paste the published address into HTMLAnnotate and send the review link instead. Reviewers open it in any browser, click the card or button they mean, and type. They give a name and email once, and need no account with HTMLAnnotate or the builder.

Ask reviewers to check the phone view too. Prototypes are usually designed at desktop width, and desktop, tablet and phone comments stay separate, so you can see which layout each note is about.

If the prototype must stay private

A feedback tool has to open the page the way a visitor would. Invite-only sites, sign-in screens and password pages block that. For the length of the review, publish a public version with a name nobody would guess, then switch it back to private afterwards. If you can export the page as a single HTML file, you can upload that instead.

Feeding comments back to the builder

Once the comments are in, Copy for AI turns the open ones into a single brief, each with the element it refers to and what the reviewer asked for. Paste it into the v0, Lovable or Bolt chat and ask for the changes. If you build in Claude, ChatGPT or Cursor, an MCP connector lets the AI read the comments itself. See letting your AI tool fix client feedback with MCP.

Each builder has its own page with more detail: v0, Lovable and Bolt. Before showing a prototype to customers, run through the checklist for AI-built pages.

Questions