Case study · Client sign-off
Vexorx
A tool where an agency’s client comments on the website itself and approves a specific version with a signature both sides can return to in a dispute.



- 01Problem
- Website feedback arrives through Slack, email and calls, and the approval is impossible to find later. The agency can’t tell whether a project is waiting on them or on the client.
- 02Solution
- Each version goes through a review on a personal link, and the client never makes an account. Comments with screenshots are made on the page itself, and the approval is signed and pinned to that version.
- 03Result
- The product is live at vexorx.com and still being developed. The approval rules are enforced by the database, not the browser.
01 · Context
Why it exists.
I know this problem from my own client work. Building the site is rarely the hard part. The hard part is getting a clear yes from the client, on the right version, in a form both sides can point to later. Usually there is a staging link in Slack, a screenshot in an email, and an approval nobody can find.
In early 2026 Vexorx was a bug-reporting tool. Market research made me change direction: the product is now review and sign-off. The client is non-technical and never creates an account, and an approval has to belong to a specific version and person, because later it is the evidence in any conversation about scope.
02 · What I built
What is in it.
- A clear state for every version: in progress, with the client, changes requested or approved, always showing who it is waiting on.
- A review page on a personal link with no account, a checklist of criteria to confirm, and a requirement to check the site on phone, tablet or desktop.
- Comments made on the site itself: select an area, take a screenshot, add arrows or blur, suggest new copy.
- Approval with a signature: name, date and a fingerprint of the version, plus a printable receipt.
- Comment export to Trello, Linear, Asana and Slack, the agency’s own branding, and paid plans.
03 · Decisions
The decisions that mattered.
I turned a bug-reporting tool into a review and sign-off product.
WhyBug reporting means competing with Linear, Jira and Trello, where the work happens anyway. Vexorx exports comments into them and owns the one thing they lack: the approval state.
The script on the client’s site loads in full only for the reviewer.
WhyEvery visitor to the site downloads the script, not just the person reviewing. Everyone else gets a tiny piece of code and is not tracked in any way.
An approval takes a signature, not just a click.
WhyAn approval only matters once there is a dispute about scope, and a bare click does not say who approved or what they saw. The signature is pinned to the version, so any later change would show.
04 · Status
Where it stands now.
Vexorx is live and under active development, with a ClickUp integration on the way. The terms and privacy policy are drafts that have not yet been reviewed by a lawyer.