BriefGate vs Typeform: a form builder is not a client checklist
Introduction
Typeform is a conversational form builder: one question at a time, animated transitions, a design system good enough that people forward the link unprompted. It is built for surveys, lead capture, NPS, and quizzes — questions with a known, bounded shape, answered in one sitting by someone with no reason to stop halfway.
Client asset collection for a web, brand, or app project is a different shape of problem. The client doesn't have the logo, the copy, and the hosting password ready in one sitting — they have some of it now and the rest next week, if you chase them. BriefGate is built around that: your coding agent or you define the items with define_intake, the client gets a portal that shows what's still missing, a chase engine reminds them on a schedule, and get_intake_results returns typed data your agent can use directly.
If you're deciding between the two for collecting project materials from clients, here's where each one actually fits.
Side-by-side comparison
| Feature | Typeform | BriefGate |
|---|---|---|
| Built for | Conversational surveys, lead gen, quizzes, NPS | Client asset collection: files, text, decisions, credentials |
| File Upload question | Fixed 10 MB limit, every plan, no way to raise it | Per-plan storage; large files upload straight to object storage |
| Respondent account required | No | No — one magic link, no account |
| Credential / password field | No field type for this; a password typed into a question sits in plaintext in the response dashboard | Encrypted secrets vault (libsodium), one-time reveal |
| Reminders for incomplete responses | None — Typeform sends a follow-up after submission, but has no native way to nudge someone who hasn't submitted yet | Chase engine per intake: preset cadences, custom interval on paid plans, quiet hours, reminder cap |
| Ask for a re-upload / fix | No revision flow found | request_revision with a note; client sees exactly what to fix |
| Item-level progress | A typeform is answered or not; no per-question completion state | Each item is pending, submitted, needs revision, approved, or waived |
| Webhooks | Yes, on response submission | Yes — item.submitted, intake.completed, client.viewed, chase.bounced, intake.stalled, intake.overdue |
| MCP server | Official, OAuth-only: tools for forms, automations, contacts, and insights | Yes, first-party: npx @briefgate/mcp or hosted at https://mcp.briefgate.dev/mcp |
| API | Create API (REST) | REST API with an OpenAPI spec, plus llms.txt for agent autodiscovery |
| EU data residency | Not offered on Free through Business; hosted on AWS in the US per Typeform's own subprocessor list. Available only on custom Enterprise plans | Yes (netcup Germany + Cloudflare R2 EU) |
| Pricing | Free plan, then Basic from $25/mo (billed annually) for 100 responses/month, Plus from $50/mo for 1,000, Business from $83/mo for 10,000 | Free plan; Solo $29; Studio $50; Agency $79 per month |
Facts about Typeform were checked on 16 September 2026 against Typeform's own pricing page, help center, and community forum. Prices shown are Typeform's discounted annual-billing rates; monthly billing costs more per month at every paid tier. Links are at the end of this page.
Where the 10 MB limit actually bites
Typeform's File Upload question caps every upload at 10 MB, on every plan, with no setting to raise it. A print-ready logo file, a short walkthrough clip, or a batch of product photos routinely exceeds that. Typeform's own help center suggests working around it by asking respondents to paste a Dropbox or Google Drive link into a Website question instead — which reintroduces exactly the "now they need an account somewhere else" friction a client portal is supposed to remove.
Where reminders actually stop
Typeform can send a message after someone finishes a form — a thank-you, a follow-up sequence. What it doesn't do, by Typeform's own community forum, is notice that someone opened the form, answered three of ten questions, and never came back — and nudge them. For a one-sitting survey that's rarely a problem. For "send me the logo, the copy, and the WordPress login," it's the difference between a project that starts on schedule and one that stalls on an unread email.
When to choose Typeform
- You're building a survey, a lead-gen form, an NPS survey, or a quiz — bounded questions, answered in one sitting
- You want the most polished, animated form-filling experience for marketing or research
- You need embedded payment collection, logic branching across dozens of question types, or Typeform's design themes
- Files, if any, are small and incidental to the form, not the point of it
- You don't need reminders, because the person filling it out has no reason to leave and come back
When to choose BriefGate
- The client owes a mix of files, text, decisions, and credentials, delivered over days or weeks, not one sitting
- Files are the point — logos, brand photography, video, PDFs — and 10 MB is not enough
- You need a hosting login or API key collected somewhere safer than a plaintext response row
- Nobody has time to manually check who hasn't responded and nudge them
- Your coding agent needs
get_intake_resultsto return typed, structured data it can act on directly — not a response export to parse
Sources
- Typeform File Upload question, 10 MB limit on all plans, not changeable: https://help.typeform.com/hc/en-us/articles/360051567012-File-Upload-question
- Typeform has no native incomplete-response reminder: https://community.typeform.com/integrate-your-typeform-43/automated-email-reminder-to-responders-who-haven-t-completed-a-form-6240
- Typeform pricing, plans, and monthly response caps: https://www.typeform.com/pricing/
- Typeform Create API: https://www.typeform.com/developers/create/
- Typeform MCP server, OAuth-only, tool list: https://www.typeform.com/developers/mcp/
- Typeform hosting on AWS (US) and data-residency terms: https://www.typeform.com/dpa/ and https://trust.typeform.com/subprocessors