Content approval software that clears a whole campaign.
yeses is content approval software that sends a set of finished files out in one round. Comments land on the file they belong to and a single approval covers the set, so a campaign goes live with every yes recorded against a name.
- Free plan, no time limit
- No credit card
- Reviewers don't need an account
“Has everyone seen the final set?”
yeses is content approval software for the assets a campaign actually ships: social sizes, ad creative, email headers, the one-pager that goes to the client. It reviews finished files rather than drafts, so if the thing waiting on sign-off lives in a CMS as unpublished copy, this is the wrong tool. If it is the set of files that comes out at the end, the sign-off is what yeses is for.
How it works
A content round, start to finish.
- 01
Put the drop in one project
Every size, every cut, every PDF. Images up to 25 MB and PDFs up to 50 MB, with no export step in between.
- 02
Send the set for review
One round covers the whole set. Reviewers get their own link, and outside agencies need no account to use it.
- 03
Feedback lands on the file it is about
A comment about the story crop is pinned to the story crop, not buried in a thread covering six files at once.
- 04
One decision closes the round
Each reviewer approves or requests changes on the set, recorded against their name and the version they saw.
Features
Online content proofing, and the sign-off that ends it.
Marking up an asset is the part every tool does. What decides whether a campaign goes out on time is whether the round closes with a named decision.
Proofing
A comment about the story crop is on the story crop.
Feedback is pinned to a point on the file it concerns. Six assets in one round means six threads, each attached to the asset it belongs to, so nobody reads “the logo is too small” and has to ask which of the six.
Versions
Change one file and the round starts again.
A new version is numbered and freezes the set it covered. Approvals given on the version before are marked stale rather than erased, so you can see that legal signed off on v2 and has not seen the crop you changed since.
Follow-ups
Nobody on the campaign is chasing legal.
Reviewers who have not responded are reminded every two business days, up to three times. Then yeses stops and flags the round as stuck. The reminders leave whoever owns the campaign without turning into an inbox nobody can escape.
One round, one decision
A drop is approved as a drop.
Content does not arrive one file at a time, and approving it one file at a time is where the calendar goes wrong.
A version in yeses holds the whole set, and a reviewer's decision covers that version. Four social sizes, an email header and a one-pager go out together, and brand, legal and the campaign lead each answer once. There is no state where five files are approved, one is not, and nobody can say whether the campaign is cleared.
The granular half is the comments, which is where granularity is actually useful. Anyone can pin a note to a specific asset and hold a thread on it, and requesting changes requires a comment, so a blocked round always arrives with the reason attached to the file that caused it. If the wording needs signing off as well as the artwork, it goes in the same thread: copy approval software that keeps the words and the picture apart leaves somebody to reconcile them afterwards.
Questions
Content approval, answered.
Can yeses approve blog posts or copy in our CMS?
No. yeses reviews finished files, which means images up to 25 MB and PDFs up to 50 MB. If the thing being approved is a draft living in a CMS or a doc, this is the wrong tool. If it is the asset that comes out at the end, it is the right one.
Do reviewers approve each file separately?
No, and that is deliberate. A round covers the whole set, so one approval signs off every file in it. Comments are the granular half: each one is pinned to the file it is about, so specific feedback never costs you six separate sign-offs.
What counts as content here?
The assets a campaign ships. Social sizes, ad creative, email headers, one-pagers, the PDF that goes to a client. Anything you would otherwise attach to an email and ask four people to look at.
What happens if we change one file after someone approved?
Send a new version and the round starts again from the first stage. Approvals given on the earlier version are marked stale rather than deleted, so a yes on v2 never quietly passes for a yes on v3.
Is this online content proofing or content approval?
Both, and the difference matters. Proofing here means checking a finished asset and marking what is wrong with it, which is the comment half. Approval is the recorded sign-off that ends the round. Tools that do the first without the second are where content sits waiting while everyone assumes someone else said yes.
Do reviewers need a yeses account?
No. Each reviewer gets their own link and approves straight from it. No sign-up, no password. The link is what identifies them, so the decision is still recorded against a specific person. What that means for security.
How long do our review rounds actually spend waiting?
Longer than most teams guess, and the waiting is the part nobody plans for — the days between sending the work out and the last person replying. Put your own numbers in and see it per project. Try the revision cost calculator.
What does it cost?
There is a free plan, and it runs a whole review from start to finish: one project at a time, unlimited reviewers, the full decision record. Paid plans start at $63 a month billed annually, or $79 monthly, and buy volume rather than the basics. Every account opens with a 30-day trial of Business, takes no card, and never turns into a payment by itself. See the plans.
Get the whole set signed off at once.
Send a campaign's files for review, let yeses chase the people who have not answered, and publish knowing exactly who approved what.