BriefGate vs collecting client files by email and a shared folder
Introduction
Most agencies don't start with a client-intake tool. They start with an email — "here's a link to a Google Drive/Dropbox folder, please drop your logo, photos, and copy in there" — and a mental note to follow up if nothing shows up by Friday. No subscription, no new login for the client, nothing to set up. For a one-off ask, it works.
The failure mode shows up on the second or third project, or the first client who isn't already comfortable with folders and permissions: files land in the wrong format, the password gets typed into the email body in plaintext, half the list never arrives, and "following up" becomes a recurring line item on your own to-do list instead of something that happens on its own. BriefGate replaces the folder-plus-email combination with a checklist your agent (or you) defines once, a portal the client can't get lost in, and reminders that go out without you writing them.
This page is for anyone still running client intake this way and deciding whether a dedicated tool is worth adding.
Side-by-side comparison
| Email + Google Drive/Dropbox | BriefGate | |
|---|---|---|
| Setup cost | None — a folder and an email | Define items once with define_intake; reusable as a template after |
| What it collects | Whatever the client puts in the folder, in whatever format | 12 typed items: files, images, text, URLs, choices, booleans, colour lists, structured JSON, encrypted secrets |
| Client needs an account | To upload into a Drive folder as Editor, yes — a Google account signed in; Dropbox's own file-request links avoid this (see our Dropbox comparison) | No — one magic link, no account |
| Attachment size, if emailed directly | Gmail caps a message at 25 MB total, then silently drops the attachment and inserts a Drive link instead | Per-plan storage; large files upload straight to object storage |
| Knowing what's still missing | You open the folder and compare against your own mental list, or a spreadsheet you maintain by hand | Portal and dashboard show each item's status: pending, submitted, needs revision, approved, waived |
| Reminders | You write and send them yourself, when you remember to | Chase engine per intake: preset cadences, custom interval on paid plans, quiet hours, reminder cap |
| Notification when a client uploads | None by default — Drive's own upload notifications are opt-in and go to the folder owner, not a per-item checklist | Webhooks: item.submitted, intake.completed, client.viewed, chase.bounced |
| Credential handling | Typed into the email body or a shared doc, in plaintext, indefinitely | Encrypted secrets vault (libsodium), one-time reveal |
| Asking for a fix | A reply-all email thread | request_revision with a note; the client sees exactly what to redo |
| Agent access | None — an agent would have to read your inbox and guess | get_intake_results returns typed JSON an agent can use directly; MCP server (npx @briefgate/mcp) or REST API |
| Cost | Free, if you already pay for Drive or Dropbox for other reasons | Free plan; Solo $29; Studio $50; Agency $79 per month |
Facts about Gmail and Google Drive were checked on 16 September 2026 against Google's own support pages. Links are at the end of this page.
Where the folder-and-email approach actually breaks
Uploading requires an account. Letting someone add files to a Drive folder you own requires Editor access and, per Google's own documentation, that they're signed into a Google account — a client without one, or who doesn't want to create one to send you a logo, is stuck before they start. A plain "anyone with the link" share is view-only; it doesn't grant upload rights.
Attachments have a hard ceiling. Gmail caps a message at 25 MB total attachments; past that, Gmail strips the attachment and inserts a Drive link automatically — which routes you straight back into the account-and-permissions problem above.
Nothing reminds anyone. Drive can notify you, the owner, when a file is added — an opt-in setting, not a default — but there is no first-party feature that reminds the client they haven't uploaded yet. That job stays on you, by hand, for every open item on every project.
Passwords end up in plaintext. A hosting login typed into an email or a shared doc sits there unencrypted, readable by anyone with access to that thread or drive, indefinitely, with no expiry.
When email + Drive/Dropbox is fine
- A one-off ask from a client you already work with regularly, who knows exactly what to send
- Files only, no credentials, no structured decisions to capture
- You don't mind manually tracking who has and hasn't sent their part
- You already pay for Drive or Dropbox and don't want another subscription for occasional use
When to switch to BriefGate
- You run more than the occasional project and are tired of writing the same follow-up email every week
- Clients need a checklist, not a folder — so they know exactly what's still missing without asking you
- You need to collect a password or API key somewhere safer than an email thread
- Your coding agent needs the results as typed data it can act on, not files it has to guess the meaning of
- You want reminders to happen automatically, on a schedule, without you remembering to send them
Sources
- Gmail attachment size limit (25 MB) and automatic fallback to a Drive link: https://support.google.com/mail/answer/6584
- Google Drive folder sharing, Editor role requires a signed-in Google account to add files: https://support.google.com/drive/answer/7166529
- Google Drive upload notifications are opt-in and notify the owner, not the uploader's counterpart: https://support.google.com/drive/answer/6318501