Get stakeholder sign-off before work moves forward.
Send it once. yeses follows up with reviewers and records exactly who approved what.
- Free plan, no card, no time limit
- 20 seats, never per user
- Reviewers don't need an account
Priced on projects
20 seats on every paid plan. The price moves with work in review, not headcount.
Every 2 business days
Reviewers are automatically reminded up to 3 times.
One decision each
Approve or request changes recorded against a name and a time.
Version aware
See when an approval was given on a version that has since changed.
The problem
“Looks good” isn’t approval.
Feedback gets scattered across Figma, Slack, email, meetings, and documents.
Then the work moves forward, and someone says:
“Wait, I never approved this.”
yeses turns informal feedback into a clear, recorded decision.
Why it matters
Catch objections before they become expensive.
Get the right feedback while changes are still easy to make, before development, publishing, production, or launch.
Reduce rework, delays, and last-minute surprises.
How it works
Four steps, and you stop chasing.
- 01
Send it for review
Add the design, PDF, content, or product decision that needs approval.
- 02
Choose the approval flow
Pick a flow you have already set up, or name the stages and who signs off on each.
- 03
Let yeses follow up
Reviewers are reminded automatically until they respond.
- 04
Get a clear decision
Every reviewer either approves or requests changes.
What you get
Send it once. yeses handles the rest.
Approval flows
The process stops living in your head.
Set the order once: brand, then legal, then the client. From then on yeses opens each stage as the one before it approves, asks the right people, and holds that stage's own deadline. You are not the one remembering who is next, or working out whether stage two can start yet.
Automatic follow-ups
Stop chasing people for reviews.
Send the request once. Reviewers are reminded every two business days, up to three times; then yeses stops, so nobody is nagged forever.
Clear decisions
Know that everyone actually approved.
No more guessing whether a comment, an emoji, or a meeting conversation counted as approval. See who approved, what they approved, which version they reviewed, when they approved it, and who is still pending.
Version history
Know exactly what was approved.
Keep versions, feedback, and decisions together. When something changes, an approval given on an earlier version is marked as such, so a stale yes never passes for a current one.
Who it's for
One approval process. Different kinds of work.
Product teams
Get stakeholder sign-off before engineering starts.
Design teams
Get clear approval on designs and revisions.
Marketing teams
Approve campaigns and creative before launch.
Content teams
Review and approve content before publishing.
Agencies
Get clear client approval and keep a record of every decision.
No migration
Keep working in the tools you already use.
yeses becomes the approval layer between work being reviewed and work moving forward.
- Figma for design
- Notion for documentation
- Slack for conversations
- Linear or Jira for development
Use yeses for approval.
Questions
The things people ask first.
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.
What can I send for review?
Images up to 25 MB and PDFs up to 50 MB. Comments pin to a point on either, page by page in a PDF. Anything you would otherwise paste into a thread and hope someone responds to.
How often are reviewers reminded?
Every two business days, up to three times. Then yeses stops. Nobody gets nagged forever, and you are not the one sending the reminders.
What if a client just doesn't respond to a review?
Give it a deadline, and say plainly that silence counts as approval. It's a short clause to add to a contract or proposal, and it closes a stalled round without anyone having to chase it forever. Generate the clause.
What can a reviewer actually do?
Approve, or request changes. Both are recorded against their name and the time they decided. There is no vague third option to argue about later.
How do I know if my own review process has these gaps?
Six quick questions, and it names which mechanisms are missing rather than guessing — in the order they cost you. It scores your own answers, not a comparison against anyone else's. Take the approval health check.
Does yeses post to Slack?
Yes. Connect a workspace and yeses posts to a channel you pick when a review has been waiting too long, and messages reviewers who are already in your Slack. Anyone who is not, which is most outside clients, keeps getting email. How to connect Slack.
Can I import designs straight from Figma?
Yes. Paste a link to a Figma file, pick the frames you want, and they come in as images. Nothing is ever written back to Figma, and reviewers never see a Figma link. See how Figma import works.
What if the work changes after someone approved it?
Their approval is marked stale. You can see it was given on an earlier version, so a yes on v2 never quietly passes for a yes on v3.
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 approval before work moves forward.
Stop chasing reviewers, catch objections earlier, and always know exactly who approved what.