We built the review tool we kept wishing we had.
Revisio started as a question: why does a client's feedback have to be re-explained every single version? The rest followed from answering it properly.
The moment that started Revisio was small: a wall finish, approved as dark wood in version one, changed to light wood in version three, and reversed back to dark wood in version seven — by the same client, worded differently each time. Nobody had done anything wrong. The feedback was just scattered across seven rounds of screenshots, emails, and memory.
Every proofing tool we tried was good at the same job: collect a comment, attach it to a spot, mark it resolved. None of them remembered what a person had already asked for two versions ago. So the same corrections kept getting reopened, quietly, on someone's dime.
Revisio is built around that gap. Pins and sketches work the way you'd expect from any review tool. Underneath them, it reads across every version of a file — by wording and by where a note actually sits on the image — and says something a spreadsheet of comments never could: this has come up before, and here's what changed.
A short list of things we won't compromise on
Every note has a place
A comment that isn't attached to something specific is just an opinion floating in a thread. Everything in Revisio points at a pixel.
Memory is the product
Version one matters just as much on version nine. We build for the whole history of a file, not just the latest upload.
Studios ship, they don't administrate
Any minute spent re-explaining old feedback is a minute not spent making the work better. Revisio exists to give that minute back.
We're building this with the studios that use it.
Tell us what you're reviewing and what your feedback loop looks like today — it shapes what we build next.