Voti for digital agencies and studios
Many clients, one archive
Every brand with its own rules, every person with only their own opened. Potens, the intelligence inside Voti, answers with the client’s brand book in front of it and cites which one and which page.
What the studio has already written down
The brand book, the contract and the style guide go up exactly as they are. They are indexed in seconds, and from that moment their contents can be asked about.
- Client brand book· p.7
- Campaign brief· p.2
- Services agreement· p.4
- Tone and style guide· p.11
- Handover checklist· p.1
- Licence terms· p.3
- Standard quote· p.2
- Project close-out· p.6
Nothing is rewritten or summarised: it is indexed and cited. And deleting a document deletes what was indexed from it.
Three questions that land mid-project
The answers come from the client’s document, not from the model. When no document supports one, Potens says so, and the question is logged without an author on the list of what still needs writing down.
Can we use this typeface on this client’s work?
The scope of the licence that was bought, with its expiry date.
Licence terms· p.3What exactly does the retainer we sold include?
The signed scope, with what falls outside written next to it.
Services agreement· p.4How do we hand this over, and who signs it off?
The steps of the handover and who signs each one.
Handover checklist· p.1
What runs out in a studio
A deadline is not an appointment. It is an entity with a type, a due date, an owner and a severity, and the severity is computed on the server: seven days out it becomes a warning, two days out it becomes critical. Each morning it goes to whoever owns it, in the app and by email, in their language.
- A contract ending or renewingWith an owner and a severity, in the morning notice.
- A phase falling dueLogged as a deadline, not as a card someone has to remember to check.
- A licence expiringType expiry, with its date and its assigned owner.
A contractor never sees the folder next door
Voti has five roles, from owner to guest, and the role sets the starting point. The detail does not come from it: it comes from per-document, per-person permissions, granted and withdrawn one at a time. Denial always wins, and they protect against Potens too — a document outside someone’s reach never enters their answer, whole or in fragments.
- A freelancer for three weeks
- The brand book and the brief for the client they came in on.
- Whoever runs the account
- The contracts and the terms for their clients.
- Someone who joined this week
- Whatever is opened to them, document by document.
- Admin
- The whole archive, and the record of every access and every denial.
What adapts to your studio, and what does not
There is no agency edition of Voti. There is a description of the studio — written at sign-up, changed whenever it needs to be — that Potens carries into every answer.
- It does not integrate with Figma, Slack or any studio tool: Voti neither reads from nor writes to them.
- It is not a project tracker or a timesheet. It holds the documentation and the deadlines around the work.
- It ships with no agency templates or corpus. The archive is the studio’s own, and suggested questions come from its own documents.
The client’s brand book is already written. It just does not answer yet.
Upload one client’s brand book and their contract, ask what your account team gets asked, and see in seven days whether it fits.