How to build a client approval portal for creative work

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: A client approval portal is a private web page where a client sees your work, leaves comments on a specific version and signs it off, with a record of who approved what and when. It needs six things: versions that never get overwritten, comments tied to a version, one clear approve button, a locked approved version, a time-stamped log and easy access for the client. Ready-made proofing tools such as Ziflow (a proofing tool for marketing and creative teams), Filestage (a review and approval tool for files) and Frame.io (a video review tool owned by Adobe) cover this for most small agencies. A custom build only pays off when you have a volume, branding or integration need those tools cannot meet.

Ranjit Bhinge

Your client says "looks good" in an email, then three weeks later says they never approved the second version. A portal is meant to end that argument, and you have to decide whether to rent one or build one.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

I get asked this by agencies and in-house marketing teams that make creative work: videos, images, ads, web pages, documents. The work goes out for review, comments come back by email, chat and phone, and nobody is sure which version was signed off. A client approval portal fixes that one problem. In this page I explain what it must do, when to buy a ready-made tool, when to build your own, and what a good build looks like. Prices are vendor numbers as of November 2026 and they change, so check each vendor page before you decide.

What a client approval portal needs

Strip away the marketing and a portal has to do six jobs. If a tool or a build misses one of these, you will feel it within a month.

  • Versions. Every upload is a new numbered version (v1, v2, v3). Old versions stay visible and cannot be replaced. Without this, you cannot prove what the client saw.
  • Comments tied to a version. A comment says "v2, 0:14 in the video" or "v2, the logo on the top right". A comment on the wrong version is worse than no comment.
  • A decision. The reviewer presses one clear button: approve, or request changes. Free text such as "mostly fine" is not a decision.
  • A locked approved version. Once approved, that exact file is frozen. Any later change is a new version that needs a new approval.
  • A time-stamped log. An audit trail is a record, kept apart from ordinary users, of who did what and in which order. Here it should show who uploaded, who viewed, who commented and who approved, each with a date and time.
  • Easy access for the client. Clients will not create passwords for a tool they use twice a month. A private link, or a simple email sign-in, wins.

Nice extras are reminders when a review is late, deadlines, more than one reviewer, a branded address such as approvals.youragency.com (often called white-label), and a way to reach your project tool. Treat these as second priority.

Start with a ready-made tool

For most small agencies I would buy first. The tools are mature, and the rented price is lower than the cost of building and looking after your own. Here is what three well known ones list on their own pricing pages as of November 2026. Check the live pages, because plans move.

ToolWhat it isEntry planPaid plans as listedNotes
ZiflowOnline proofing for marketing and creative teamsFree: 2 users, 2 GB, 1 workflow stage, 60 days of historyStandard $199 a month (billed yearly, 15 users, 2 stages, 90 days of audit trail); Pro $329 a month (billed yearly, 20 users, 3 stages, 1 year of audit trail)Unlimited reviewers on every plan. Custom domain, white-label, e-signatures and detailed activity logs are listed under Enterprise only.
FilestageReview and approval for files, with reviewer groupsFree: 1 project, 5 new files a month, 10 team membersStarter 199 and Business 329 a month on the yearly toggle (shown in euros when I checked; currency may differ by country, and monthly billing costs more)Reviewers need no account, only an email address. Verified "approve and sign" and audit logs are listed under Enterprise.
Frame.ioVideo and image review, owned by AdobeFree: up to 2 members, 2 GB, 2 projectsPro $15 per member a month plus tax (up to 5 members); Team $25 per member a month plus tax (up to 15)Pro adds custom-branded and passphrase-protected shares. Check the live page for whether clients need an account and which tier has which approval controls.

Two things stand out. First, the free plans are real, but they are small: two users, or five new files a month. Second, the two tools that focus on approvals put the features that matter most to a legal-style record (signatures, white-label, full activity and audit logs) on the top, contact-sales plan. Ziflow does include a basic audit trail on its Standard plan. If you need a branded address and a signed approval, the cheap plan will not do it.

When a custom build is worth it

I use these decision rules. Pick a ready-made tool if two or more of these are true:

  • You review fewer than about 40 items a month.
  • Your clients are happy to use someone else's page.
  • You do not need the approval record to sit inside your own systems.
  • You need to start this week.

Pick a custom build if two or more of these are true:

  • You pay for several seats or higher plans and the bill is already a real line in your budget.
  • Clients expect your brand, your domain and your look, and the proofing tool shows its own.
  • Approval must feed your own system: your invoicing, your project board, your client records, a "ready to publish" flag.
  • You have unusual rules, such as a legal team that must approve before the client sees a draft, or three sign-offs in a fixed order.
  • You keep losing time because approvals live in one tool and everything else lives in another.

For cost ranges on custom portals, I wrote a separate page: what a custom client portal costs. For a wider look at portal tools, see agency client portal software and content approval software compared.

A worked example (made-up numbers)

These numbers are illustrative, not real client data. An agency has 12 clients and sends about 50 items a month for approval. It uses a ready-made tool at $329 a month, so about $3,950 a year. The tool shows its own look, and the agency pays a freelancer three hours a month to copy approved links into its project board, about 36 hours a year.

A small custom build that does only the six jobs above, with the agency's brand and a direct link into its board, might cost a single project fee plus a yearly care fee. I will not quote a figure here because it depends on your scope. The break-even test is simple: add the project fee to three years of care, divide by 36 months, and compare with the monthly tool price plus the value of the time you save. If the custom number is not clearly lower or clearly better in what it does, buy the tool.

Notice that this comparison includes care. A build that nobody looks after will break when a browser changes or a file type is added. Cost it as an ongoing service, not a one-off.

What a good build looks like: a plain spec

If you do build, give your builder this spec. It is short on purpose.

  1. Project and item. A client has projects. A project has items (a video, an ad, a page). An item has versions.
  2. Immutable versions. Uploading creates a new version. Nobody, including your own staff, can overwrite or delete one after a client has viewed it. Mistakes are fixed by a new version.
  3. Reviewer identity. Each reviewer is a named person with an email address. For a decision, send a one-time link or code to that email so the record shows a real person acted, not a shared link passed around.
  4. Comments. A comment belongs to a version and, where it makes sense, a point (a time in a video or a spot on an image). Comments can be marked resolved, with who resolved them.
  5. Decision. Two buttons: approve and request changes. Request changes requires at least one comment.
  6. Lock. Approving locks that version. The portal stores a fingerprint of the file, called a hash, so you can later show the approved file is the same file.
  7. Log. Every event writes a line: who, what, which version, when. Staff cannot edit it. Make it exportable as a PDF or spreadsheet for disputes.
  8. Reminders. If a review is open for 3 days, email the reviewer. After 7 days, email the account manager.
  9. Branding. Your logo, colours and domain. Keep client access simple.
  10. Handoff. When approved, mark the item "ready" in your own board and put a link to the locked file there.

Keep the first version this small. Add multi-step approvals, deadlines and integrations only when real use shows you need them.

Failure modes I would watch for

  • Silent overwrite. Someone uploads a "tiny fix" over v2. The client's approval now covers a file they never saw. The spec above prevents this.
  • The shared link. A client forwards the link, and a colleague approves. If your record says "client approved" but the person was not your contact, the record is weak. Use named reviewers.
  • Approval of the wrong thing. The client approves a mock-up, then the finished work looks different. Always attach the exact deliverable, or say in the item what the approval covers. See how to get approval on a real website version for the web case.
  • Nobody reads the email. Reminders that go to a generic inbox die. Send them to named people.
  • Comment sprawl. Feedback still arrives by email and chat, and nobody enters it. Tell clients that comments outside the portal do not count, and say so kindly at the start of each project.
  • A log nobody can export. A record you cannot produce in a dispute has no value.

Fix the process before you pick the tool

A portal does not repair a loose process. Agree three rules with each client before the first review: who the one approver is, how many revision rounds are included, and what counts as final. I describe these in a simple approval process for creative drafts and how to get clients to approve work in writing. If you use AI tools to make drafts, the same rules apply, and the cost of each revision round can be real, so count rounds.

A two-week test with pass and fail marks

Whether you rent or build, run a short test with one friendly client before you roll it out.

  1. Put 5 real items through the tool, with at least two revision rounds on one of them.
  2. Try to break the record: upload over an approved version, forward a link to a colleague, approve without a comment on a "request changes" item.
  3. Ask the client how long the first review took them and what confused them.
  4. Export the record for one item and read it as if you were in a dispute.

Pass marks: no approved file could be replaced; the record showed a named reviewer with a time for every approval; the client finished a review without help; the export was readable. Fail if any approved version could be changed, or if the client needed a call to find the button.

What to ask before you pay (tool or builder)

  • Can an approved version be changed or deleted? By whom?
  • Does the record show a named person and a time for each decision?
  • Do reviewers need an account? What happens if they forward the link?
  • Which plan includes branding, white-label, signatures and activity logs? Ask for the answer in writing.
  • How do I get all my files and records out if I leave?
  • Who looks after it when something breaks, and how fast?

Who should skip a custom portal

Skip a build if you send fewer than about 20 items a month, if the clients are casual and an emailed "approved" with a version number is enough, or if you have no one to look after the system. A free plan from a ready-made tool, plus a version sheet, is a fair start. Also skip it if your real trouble is unclear scope. A portal records approvals. It does not make a client decide.

How I'd approach this

I would start with the free plan of one ready-made tool and the version sheet from the process page, and run the two-week test. Keep a short list of every time the tool got in the way: a missing brand, a missing link to your board, a missing record. After two or three months, that list tells you whether a build is worth it. If it is, I would build the six jobs first and nothing else.

Blur Studio builds this kind of portal for agencies and small teams: the build, the finishing and testing, and the care after launch. If you want to talk it over, see how I work with business owners. A good result is a portal your clients use without being told twice.

Questions people ask

What is a client approval portal?

A private web page where a client reviews a specific version of your work, leaves comments and approves it, and where the approved version is locked and logged with a name and a time. It replaces approvals scattered across email and chat.

Do I need a custom portal or is a proofing tool enough?

For most small agencies a ready-made proofing tool is enough. Look at a build when the monthly bill is large, you need your own brand and domain, or approval has to feed your own systems. See the decision rules above and the cost page.

Do clients need an account to review?

Ziflow and Filestage list unlimited reviewers, and Filestage says reviewers need no account, only an email address. For Frame.io, check its page for how clients access shares. Vendor rules can change.

What is an audit trail and why does it matter?

It is a time-ordered record of who did what, kept apart from ordinary users. In an approval portal it shows who uploaded, commented and approved each version. It matters most when a client disputes what was signed off.

Is a client's click on an approve button legally binding?

It can be strong evidence of agreement, but it depends on your contract, your local law and how well the record shows who approved what. This is information, not legal advice. Check local law and ask a lawyer if the work is high value. Write the approval rules into your agreement.

Can I just use email and a shared folder?

Yes, for a small volume. Use a version sheet, one named approver and a rule that the last emailed approval must name the version. See the approval process page. Move to a tool when chasing and confusion cost you real time.

How long does a custom approval portal take to build?

It depends on your scope, so ask for a plan and a fixed first phase. A small version with the six core jobs is much quicker than one with multi-step approvals and integrations. A fair builder will not quote a number without knowing your needs.

More in this topic: Higgsfield and AI creative for agencies (19 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…