Guides

Client intake guides and checklists

What to ask a client before you start a website, e-commerce, branding, or app project — checklists, email templates, and a client intake checklist you can reuse on every job.

Checklists
Templates
How-to & guides
Collecting documents from clients

The fastest way to collect files or documents from clients is one list, sent once, with a deadline and a fixed reminder schedule.

Website copy from clients

What text a website needs, who should write each piece, how to ask a client for it with a word count and a deadline, and what to do when it doesn't arrive.

Getting client logins securely

Sending logins by email or WhatsApp leaves a permanent password in a chat log. Here are safer options, ranked worst to best, plus what to do after.

Why clients don't send materials

Clients rarely withhold a logo or photos on purpose — they stall from being overwhelmed, an unclear ask, no deadline, or no one owning it on their end.

Client intake for Cursor agents

BriefGate MCP lets a Cursor agent collect a client's logo, copy, and credentials through a tracked portal instead of stalling mid-build.

Async human input for coding agents

MCP elicitation asks whoever is running the agent, in the same session. An answer from a client who isn't there needs an asynchronous channel instead.

Get client assets into your coding agent

Every coding agent hits the same wall: the code is ready to go, and the client's logo, copy, or login isn't — and there's no good way to hand it over.

Client intake for OpenAI Codex

Connect BriefGate's MCP server to OpenAI Codex so it can request a client's files, text, and logins — BriefGate emails them and follows up automatically.

BriefGate with AI assistants

BriefGate is one MCP server that works the same way across every MCP-capable AI assistant — see the setup guide and confirmed status for each client.

ChatGPT as an MCP client

How to use ChatGPT as an MCP client for BriefGate, so a chat that's scaffolding client work can ask the client for a file or a login directly.

Client intake for Gemini CLI

Gemini CLI reads MCP servers from settings.json — point it at BriefGate's hosted endpoint to collect client assets straight from the terminal.

Client intake for Windsurf

Windsurf's Cascade agent reads MCP servers from mcp_config.json — connect it to BriefGate's hosted endpoint to collect client assets with an API key.

Client intake for VS Code (Copilot)

Add BriefGate's MCP server to VS Code so Copilot's agent mode can request a client's logo, copy, and logins — and get them back without leaving the editor.

Client intake for Claude Desktop

Connect Claude Desktop to BriefGate as a remote connector or a local MCP server — both give you the same 13 tools for client intake from a chat.

Client intake for claude.ai (web)

claude.ai connects to BriefGate as a custom connector — no install, no API key to copy, sign in once from your browser.

Client onboarding automation

A tool-agnostic guide to automating the four steps between a signed deal and a full project folder — dashboard, Zapier, n8n, or your own code against the API.

Intake events in your own code

The moment a client finishes an intake, the files, copy, and credentials you asked for already exist — typed, validated, ready to read.

Route files to Drive, Dropbox, Slack

BriefGate does not route files into Drive, Dropbox or Slack itself — it gives Zapier, n8n or your own script everything needed to do that routing for you.

A client portal with no account

Your client gets an email, taps a link on their phone, and is looking at a page asking for their logo files.

How client credentials are stored

Almost every project needs a password at some point — here's exactly how BriefGate encrypts and stores client credentials like logins and API keys.

When a crawler finds a shared link

On 17 September 2026 a Bing Webmaster Tools site scan of briefgate.dev flagged two pages for a missing H1.

Reminders that arrive at a sensible hour

The point of a reminder is that materials show up without you having to remember to ask again.

Client API keys without the chat history

How to get a client's API key to your coding agent without pasting it into chat: a BriefGate secret item, one-time reveal, and where to store it next.

When a client uploads the wrong file

What happens when a client uploads the wrong file in BriefGate: how request_revision flags the item in the portal, and how to prevent it with constraints.

Where a human still steps in

An agent can run a BriefGate intake end to end, yet a few moments still need a person: what an API key can never do, and where using it well is a judgment call.

Case studies