What a design or creative agency needs from a client portal
A client portal for a design agency needs three things a generic project tool lacks: feedback pinned to the artwork itself, a queue that limits how many requests are active at once, and billing that matches a flat monthly design subscription. The same list applies to a client portal for a creative agency doing video or motion work, with timestamped video comments added.
ManyRequests lists all three on its lowest plan. The details below come from its pricing page and help center, read on 3 October 2026, not from hands-on use.
We may earn a commission if you buy through our links, at no extra cost to you.
See current ManyRequests plans →Design feedback and annotation in ManyRequests
The help center describes an annotation module. A client opens a file shared in the request discussion, clicks the exact spot and types a comment. On video, the comment is pinned to both the area and the timestamp. Clients can also record a Loom video on the file.
| File type | Annotation |
|---|---|
| PNG, JPG, GIF | Comments pinned to a point on the image |
| Comments pinned to a point on the page | |
| MP4, MOV | Comments pinned to an area and a timestamp |
| Live websites | Not supported yet; the pricing page marks website proofing as coming soon |
One detail to tell clients on day one: files must be shared in the discussion panel of a request. Files attached to the request form itself cannot be annotated. The design subscription page also lists version control and brand profiles, where a client stores logos, fonts and colors once and references them on each request.
Running an unlimited-design subscription with revision queues
Unlimited design only works commercially if the number of active requests is limited. ManyRequests has two service settings for this: the maximum number of current requests, and the maximum number of requests per month. Set the first to 1 and a client can submit as many briefs as they like, but only one is worked on at a time. The rest wait in a queue.
- Create a recurring service under Services, All Services, and set its monthly price.
- On the details step, set the maximum number of current requests, for example 1 for a standard plan and 2 for a premium plan.
- Turn on the request queue under Settings, Modules and Extensions, Requests.
- Clients then see Active and Queued sections and drag cards to change priority.
Revision rounds are handled as comments and annotations on the same request until the client marks it complete. For studios that prefer to meter work, the credit model is an alternative: the help center example prices a landing page at 5 credits, a social ad at 2 and a quick edit at 1. The billing page says clients can pause, cancel, renew or upgrade their own subscription. See credits versus hours for how to choose.
Which plan fits a design studio and what four seats cost
Core is enough for most design studios, because design and video proofing, the queue view, subscriptions and a custom domain are included in both plans. Pro adds Slack, webhooks, workload management and removal of the vendor badge.
| Plan and billing | Base | Three extra seats | Monthly total |
|---|---|---|---|
| Core, paid monthly | $59 | 3 x $20 | $119 |
| Core, paid annually | $39 | 3 x $15 | $84 |
| Pro, paid monthly | $99 | 3 x $30 | $189 |
Storage matters for design files. The pricing page's comparison table shows 1TB on Core and 2TB on Pro, while the FAQ on the same page says 500GB and 1TB, so ask support which applies. Extra storage is $25 a month per 500GB, and the vendor states a 10GB limit per file. A studio keeping layered source files and video masters for many clients should estimate storage before picking a plan. The Core versus Pro comparison goes through the remaining differences.
The limit to know about, and when Queue or Kitchen.co fits better
The limitation that matters most to design teams is file coverage. The annotation list has no native Figma or website entry, so web and UI work has to be reviewed as exported images or PDFs, or in Figma itself. The documentation read for this page also describes no setting that caps the number of revision rounds per request.
If most of your work is websites, Queue is the better pick. Its pricing page says it supports review on over 30 file types and live websites, and its Growth plan is $49 a month with two seats, with a free plan until you add a client. If you only need simple file feedback and approvals with projects and invoices, Kitchen.co charges $29 per internal user a month. The ManyRequests versus Queue comparison covers the first choice in depth.
We may earn a commission if you buy through our links, at no extra cost to you.
Visit ManyRequests →Sources used for this page
The facts above come from the pages below, read on 3 October 2026. We have not used these products hands-on. Prices and terms change, so confirm them on the vendor's site before you buy.
- Pricing Plans | ManyRequests — Vendor pricing page · manyrequests.com · checked 2026-10-03
- Agency Billing and Invoicing Software | ManyRequests — Vendor product page · manyrequests.com · checked 2026-10-03
- Design Subscription Services use case | ManyRequests — Vendor product page · manyrequests.com · checked 2026-10-03
- How To Write Annotations On Attachments | ManyRequests Help Center — Vendor documentation · help.manyrequests.com · checked 2026-10-03
- How To Manage Max Number of Active Tasks | ManyRequests Help Center — Vendor documentation · help.manyrequests.com · checked 2026-10-03
- How To Use Queue | ManyRequests Help Center — Vendor documentation · help.manyrequests.com · checked 2026-10-03
- How To Create Credit Based Services | ManyRequests Help Center — Vendor documentation · help.manyrequests.com · checked 2026-10-03
- How To Setup and Use Brands | ManyRequests Help Center — Vendor documentation · help.manyrequests.com · checked 2026-10-03
- Pricing plans | Queue — Vendor pricing page · usequeue.com · checked 2026-10-03
- Kitchen.co Pricing — Vendor pricing page · kitchen.co · checked 2026-10-03