Freelancers and small studios love a shared Drive because it is free, familiar, and "good enough." Then a client comments on v3 in email, another comments on v2 in the folder, and you ship the wrong file. A client portal is not a prettier Drive. It is a place where the latest version, the decision, and the people are the same object.
This is what you actually need if you ship work with clients, not what looks organized in a screenshot.
What Drive is good at
Drive (or Dropbox, or a Notion wiki) is excellent at storing files. It is a bad product for:
- Proving which file is the approved one
- Letting a guest review without a Google account maze
- Showing project status without a separate board
- Keeping chat next to the asset
- Knowing who saw the link
If your "portal" is a folder named Client Name, you still own the chase. You paste links. You re-attach PDFs. You hope the last comment won.
What a portal has to do
A freelancer-sized portal can be small. It does not need a 40-page intranet. It needs:
1. One login the client remembers (or a guest review link with email OTP when they should not need an account). 2. The current status of the work, not a dump of every file you ever made. 3. Approvals that stick to a version, so "make it pop" has a home. 4. Files nested in folders when the engagement is more than one PDF.
Felagar's client portal is the client-facing side of the same workspace the studio uses. Deliverable review is the guest path: branded link, OTP, comment, approve. That is the piece Drive never grew.
Freelancer vs agency: the same failure mode
A freelancer with three clients feels Drive pain as inbox chaos. An agency with thirty clients feels it as "where is the latest brand kit." The failure is the same: files without a workflow.
Account pulse (waiting reviews, quiet clients, burn) only works if review is a first-class state. A Drive star is not a state. A Felagar review waiting on a guest is.
If you cobrand the portal per company, the client still sees one place that looks like you, not like your software vendor. That is white-label, not a custom Drive theme.
When Drive is still fine
Keep Drive (or your DAM) when:
- The client is the system of record for assets you did not create
- You are exchanging raw footage that does not need approval in your process
- Legal wants a tape backup outside the workspace
Then link from the project. Do not pretend the folder is the project. Felagar files can sit in nested folders and still show up from deliverable uploads. The portal is the front door. Storage can be mixed. Status cannot.
Permissions without a Google maze
Freelancers waste hours on "can you request access" emails. A portal with invited roles (admin, viewer, designer, brand manager in Felagar's model) is slower to set up once and faster forever. A guest review link is faster still when the person only needs to approve a file.
Do not make the CFO create a workspace account to say yes on a PDF. Do not make the designer share a personal Drive. Those are the two failure modes. OTP review and a proper invite cover them.
What you do not need
You do not need a 40-page intranet, a second Slack the client will ignore, or a knowledge base you will not maintain. You need a door with a lock you control, a current version, and a yes/no that sticks. If a tool gives you those three and still uses Drive for raw dumps, you have a portal. If it only gives you a folder, you have storage.
Freelancers skip this because setup feels like "agency software." It is not. One client, one review link, one board they can see is enough to test whether Drive was the bottleneck. If they still email PDFs after that, the problem is habit. Keep the portal anyway so your record is the one that is true.
Clients also need a place to upload a brief without email attachments that vanish. Portal uploads that land on the project (and in Files) close that loop. Drive can still hold the raw dump. The brief that starts the work should be in the workspace.
White-label matters here more than agencies admit. If the URL and the email look like your studio, clients treat it as your process. If it looks like a vendor, they treat it as optional homework.
A simple swap
This week:
1. Pick one active client. 2. Put the live deliverable on a review link instead of a Drive comment. 3. Put status on a board the client can see (read-only is enough). 4. Stop emailing "latest_FINAL_v7.pdf."
If they need to talk, use client communication on the thread, not a parallel Slack DM you will lose.
Hosted Felagar is in invite-only beta. Request access if you want portal, reviews, and chat without standing up your own stack. Compare the habit to Drive honestly: Drive stores. A portal decides.