AI and feedback
You shipped it in an afternoon. The review still takes a week.
Lovable, Bolt, v0 and Replit compressed the build. They did nothing at all to the part where a real client looks at the result and tells you what is wrong, which still arrives as a voice note, a screenshot with a red circle, or a call you have to transcribe. Writhink turns that into a prompt you paste straight back into the builder's chat.
No credit card. Your client doesn’t need an account.
01
The asymmetry nobody warns you about
Forty minutes to a working site. Four days to agree on the changes. The build step got fast and the feedback step did not move, so the feedback step is now most of the project timeline. It is also the part your client experiences directly, which means it is the part they judge you on.
There is a specific reason it does not compress: you cannot hand a voice note to a model. Everything the builder is good at needs text with an explicit target. Everything your client produces is untargeted. Somebody has to do that translation, and right now it is you, at 9pm, playing a 90-second recording twice to work out which card they meant.
02
What the review loop actually looks like today
Count how many of these happened on your last project.
- A voice note that says "the top part, you know, it's just not quite there"
- A screenshot pasted into an email with an arrow drawn on it and no page URL
- "the button" — and there are six buttons
- A call where you take notes, and the notes lose three items
- A complaint about a page on their phone that looks fine on your screen
- A second round that repeats four things from the first round, because nobody tracked what was already done
03
The same loop, with a review link in it
- Step 1
Send one link
Your client opens it in a browser. No account, no signup, no app to install, no password to reset. They type a display name and that is the entire onboarding.
- Step 2
They click the thing they mean
They pin the comment on the actual element. Writhink records the page, the element, where inside it the pin sits, their viewport size, whether they were on desktop, tablet or mobile, and a screenshot of that spot. Your client did nothing except click and type a sentence.
- Step 3
You generate the prompt
Every open comment, grouped by page and by element, exact duplicates merged, vague ones rewritten without inventing requests, and the genuinely ambiguous ones marked (unclear — ask the client) instead of guessed at.
- Step 4
Paste it into the builder
Lovable, Bolt, v0, Replit — into the chat box you already use. It is Markdown, and it reads as a numbered set of changes with a priority-ordered checklist at the end.
- Step 5
Answer the unclear ones and close them
The prompt ends with drafted replies for the ambiguous items. Post them in the review thread where the client left the comment, and mark items resolved as they land, so round two is not round one again.
04
Which route for which builder
There is no plugin and no connector for any of these tools. Writhink has zero native integrations with any third party. What changes between rows is only how you get a reviewable page in front of your client.
| Where the site lives | How you review it | Why |
|---|---|---|
| A published Lovable, Replit or Vercel URL | Paste the URL into a project and share the review link | It is a public URL, so it can be served through the proxy and pins can attach to real elements |
| The builder's preview or editor, behind your login | Chrome extension | A proxy cannot sign in as you; the extension runs in the tab you already have open |
| A Bolt or StackBlitz preview URL | Chrome extension | Ephemeral, session-bound previews are exactly what the extension exists for |
| localhost, while you are still iterating | Chrome extension | Nothing outside your machine can reach it |
| A live client site you want feedback on permanently | The embeddable widget script | Feedback stays available in place instead of only during a review round |
The extension is Chrome only. There is no Firefox, Safari or Edge build.
05
The hand-off is copy and paste, and it will stay that way
Lovable, Bolt, v0 and Replit are not MCP clients. They cannot reach into Writhink and read your feedback themselves, and anything claiming otherwise is describing software that does not exist. The route is: generate the prompt, copy it, paste it into the builder's chat. It takes a few seconds, and it is exactly why the prompt is built to be self-contained rather than to reference things only Writhink can see.
If you also work in Cursor or Claude Code, those are MCP clients. There an agent can query the feedback directly instead of waiting for you to paste it, which is covered on /client-feedback-for-ai-coding.
Two practical notes for builder chats. Feed the changes in batches: a prompt holding twenty changes across five pages produces a better result worked page by page, which is why the items are grouped that way and why the prompt tells the assistant to take one page at a time. And check the screenshot urls — some builder chats will not fetch an image from a url, in which case drop the image in by hand for the two or three items where the picture is the whole point.
06
When this is the wrong call
Cases where a review tool adds a step and returns nothing.
- You are the client. Building for yourself needs the browser you already have, not a review link.
- Your feedback comes from one technical co-founder who writes good tickets. A shared doc is fine.
- You need approvals with signatures, legal sign-off or an audit trail. Writhink tracks comment statuses, not approvals.
- You want the builder to apply changes automatically with nobody in between. That does not exist here — a person pastes the prompt and reviews the result.
- The project has three comments total. Paste them into your assistant yourself and skip the setup entirely.
Before you count on it
Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.
FAQ
Questions people actually ask
- My client is not technical. Will they manage this?
- The whole client-side experience is: open a link, type a name, click a spot on the page, write a sentence. No account, no password, no app. They can attach files up to 10 MB and reply in the thread the same way, still without signing up.
- The site only exists in the builder's preview, behind my login. Can they still review it?
- Not through the shared review link, because a proxy cannot log in as you. Use the Chrome extension on the tab you already have open, or publish to a preview URL your client can reach and share that. The extension is Chrome only.
- Does Writhink connect to Lovable, Bolt or v0 directly?
- No, and it will not pretend to. There is no plugin, no app-store listing and no API connector for any AI builder — or for any other third party. You copy the generated prompt into the builder's chat box, which is the only route that actually works today.
- What happens when the builder regenerates half the site?
- Nothing breaks on the Writhink side. Comments keep their page URLs, element anchors and screenshots, and stay meaningful as long as those elements still exist. If a page is rebuilt from scratch, share the review again and let the client pin against the new version.
- Can I collect feedback on the live site after launch, not just during a review round?
- Yes, with the embeddable widget: one script tag on the site, and anyone you allow can leave a pinned comment in place at any time. It feeds the same project, so a note left three weeks after launch lands in the same prompt as the rest.
Start
Send one link. Get feedback you can build from.
Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.