Website feedback
Feedback from clients who will not learn a new tool
Most client feedback arrives as a voice note, a forwarded email, or a screenshot with a red circle drawn on it. Writhink replaces that with one link: your client opens it, types a name, and comments on the page itself. There is no account for them to create and nothing for them to install. This page is about that side of the work, the relationship and the round; the mechanics of getting feedback in are on /website-feedback-tool.
No credit card. Your client doesn’t need an account.
01
Where client feedback actually arrives
A voice note at 8pm. Two emails, the second one a forward of the first with 'see below' on top. A screenshot with a red circle in it. Three messages in a group chat, one of which contradicts the other two. A phone call you took notes on somewhere.
None of this is your client being difficult. They are using whatever is closest to hand, which is what anyone does. The problem is downstream: none of it is a list, so none of it can be checked off, and the only person who knows the state of the round is you.
The fix is not persuading your client to adopt your project tracker. They will not. The fix is making the lowest-effort channel be the one that also produces a record.
02
Why the tracker you already pay for does not work on them
Every studio eventually tries the obvious thing and invites the client into the tool the team already uses. It fails the same way each time. An invitation email, a password, a project they cannot find two weeks later, one colleague who never got added, and then a text message saying 'quick one, the logo looks small'.
The asymmetry is the whole problem. For you the tracker is where work lives, so the cost of an account is spread over a thousand visits. For your client it is one visit to leave one sentence. Any step that costs more than the sentence itself loses to the phone already in their hand, every time.
So the channel has to cost less than a text message and still come out the other side as a list. That is the constraint the whole thing is designed around: a link, a name, a click, a sentence. No invitation to accept, no password to reset, no seat to license, no email address handed over to a vendor they have never heard of.
03
What the scatter costs, concretely
- An extra revision round, because 'the button' turned out to be the wrong button.
- Two items from the Thursday call that never made it into the build, discovered at sign-off.
- Two people at the client asking for opposite things, with no record of which one you followed.
- An hour a week turning messages into tasks, which is work nobody is paying for.
- A change you made in week two that gets questioned in week six, with the request that prompted it sitting in a chat nobody can search.
- A sign-off that means nothing, because there was never a list to sign off on.
04
How a round runs
| Stage | Your client | You |
|---|---|---|
| Round opens | Opens one link, no account | Share the link for the round, or leave the widget on the site so the channel is always there |
| Feedback comes in | Pins each change on the element it is about | An email digest tells you there is new feedback |
| You work | Nothing to do | Move each item through open, in progress, in review, resolved |
| Questions | Reads your reply in the thread under the item | Reply inside Writhink, no separate email |
| Disagreement | Sees which item the decision belongs to | Answer once, on the item, where it stays findable |
| Close | Confirms in the thread | Generate the AI prompt and implement |
05
Rounds, replies and a sign-off that holds
A round in Writhink is a list with states. Each comment sits in one of four: open, in progress, in review, resolved. That is enough structure to answer the only two questions that matter while a round is running, which are what is left and who is waiting on whom.
Because your replies are public to the client, the conversation about an item lives under the item. There is no separate email chain to reconcile afterwards, and no 'as discussed' with nothing behind it. When a client changes their mind, the change sits next to the original request instead of replacing it silently.
Sign-off is where that pays. Instead of an email asking whether everything looks good, you have a list both sides have been looking at all along: every item either resolved or explicitly still open, each with the request, the screenshot taken when it was left, and the thread underneath. Saying 'the twelve items from the 14th are resolved, these two we agreed to leave' reads as a summary rather than a defence, because the client can see the same thing you are seeing.
When the round closes the list leaves as one generated prompt — copy it, or download the .md — handed to whatever writes your code. Either way what was asked and what you did about it is one artifact instead of five channels, and it is still there in month six.
06
What changes on each side
For your client
- One link, no account, no password, and it works on the phone they are already holding
- They stop having to describe things: they click the thing
- Changed their mind? They edit their own comment, instead of sending 'ignore my last message'
- Your answer appears under their own request, not four replies down an email thread
- Nothing to keep, nothing to log back into, no seat anyone is paying for
For you
- One list instead of five channels, so the state of the round is visible without reconstructing it
- The weekly hour spent turning messages into tasks goes away
- A question and its answer stay attached to the item they belong to
- Email digests tell you when new comments land, so nobody babysits a tab
- At the end of the round there is something concrete to sign off on
07
What your client is agreeing to
Nothing that touches their inbox. A guest types a display name and that is the extent of it: no email address, no verification step, no account that outlives the project. You are not putting your client's contact details into another vendor's database in order to get a sentence out of them, which also means there is no conversation to have with their IT person about it.
Two trade-offs are worth knowing before you send the first link. Ownership of a guest's comments is held by a token in their browser, which is exactly what makes editing possible without a login, so a comment left on their laptop cannot be edited later from their phone. And if you go the always-on route, the embedded widget carries a Powered by Writhink badge on the page.
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
- Does my client really not need an account?
- No account, and the reason is not convenience for its own sake. Every account you ask a client to create becomes a support conversation you end up having: a password reset in week three, an invitation that went to the wrong person, a colleague who cannot see the project on the day the feedback is due. A guest types a display name, comments, and never sees an admin screen. How the link itself carries the authorization is explained on /website-feedback-tool.
- What if the link gets forwarded to someone I did not intend?
- Then that person can comment as well. Treat a review link the way you treat a shared document link: the link is the credential, so share it with the same care. For most client work that is the right trade, because the alternative is asking five people at the client to create accounts, and four of them will not.
- Two people at the client want opposite things. Does that get any easier?
- It gets recorded, which is most of it. Each guest picks their own display name and it is stored on every comment they leave, so the contradiction is visible as two items rather than as a feeling you had. You answer once, in the thread on the item, and the decision stays next to the request it settled instead of living in your sent folder.
- How do I close a round so it stays closed?
- Work every item to resolved, or leave it open on purpose with a reply saying why, then generate the prompt. What makes it stick is that the client has been looking at the same list the whole time: the request, the screenshot from the moment it was left, and the reply thread are all on the item, so 'we agreed to skip this' has something behind it in month six.
- Will I know when new feedback arrives?
- Yes. Email digests notify your team about new comments, so nobody has to keep the review open in a tab. What Writhink does not do is guarantee a delivery time or push alerts into Slack or SMS, because there are no chat integrations of any kind.
- My client is not technical at all. Is this genuinely lighter than email?
- Their side is: open a link, type a name, click a thing, type a sentence. The only habit worth teaching them is to click the element rather than describe it, and most people do that on their own within a few comments because it is faster than writing. Nothing about it needs explaining twice.
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.