Client portal vs shared Drive: when custom software is worth it
Auth, roles, and workflows that turn scattered files into a product your clients trust
Shared drives are fine until permissions get messy, clients email the wrong folder, and nobody knows which PDF is current. A client portal is not “Drive with a logo.” It is authenticated access, roles, and workflows—typically in web-app territory from €8000+, not a marketing-page add-on.
Drive vs portal, honestly
Compare the operating model, not the file icons. Portals win when the relationship needs status, permissions, and repeatable jobs—not just storage.
Shared Drive vs client portal
| Need | Shared Drive | Client portal |
|---|---|---|
| File sharing | Excellent | Good (with deliberate UX) |
| Who sees what | Folder ACLs; easy to drift | Roles designed per job |
| Status of work | Comments and filenames | States, tasks, timelines |
| Client self-serve | Limited and confusing | Built for the client job |
| Audit trail | Weak for business process | Actions can be logged |
| Integrations | Manual exports | APIs, webhooks, automations |
| Cost shape | Low tooling cost | From €8000+ to build right |
When a custom portal is worth it
Build when Drive rituals are costing trust or labor every week: wrong versions, repeated status emails, permission theater, or compliance needs you cannot meet with shared links.
Portal worth-it signals
- Clients need their own login and only their data
- Statuses, approvals, or uploads are part of the service
- Staff re-key the same updates into email every week
- Roles matter (viewer vs uploader vs approver)
- You need automations with human-in-the-loop checks
When Drive (or similar) still wins
If you exchange a few files with trusted clients and status lives in meetings, do not invent software. Improve naming, folders, and a simple checklist first. Portals fail when the workflow was never defined.
How to scope without boiling the ocean
Ship the smallest portal that removes the weekly pain: auth, one role model, one primary workflow, and clear empty states. Fancy dashboards can wait until the core loop works.
- 1
Map the weekly pain
List the emails and Drive mistakes that burn time. Those become launch requirements.
- 2
Define roles first
Viewer, client, staff, admin—verbs before screens.
- 3
Pick one workflow
Upload → review → approve is enough for v1 if that is the pain.
- 4
Price as a web app
Budget from €8000+ with care after launch. Treat it like product, not a theme.
Portal scoping steps
Final thoughts
Shared Drive is a tool. A client portal is a product. Build the portal when roles, status, and trust demand it—and budget accordingly. Otherwise, discipline the folder and keep the money for work that compounds.
Related Articles
Website SEO that actually moves leads (not just rankings)
Structure, speed, intent pages, and tracking—SEO as a growth system, not a checklist theater
Automations inside custom portals: auth, roles, human-in-the-loop
Who can trigger what, what runs alone, and where a person must still approve
Ready to build something this considered?