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 documents from clients is one list, sent once, with a deadline and a fixed reminder schedule instead of scattered emails.

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 onboarding questionnaire

A web design onboarding questionnaire covers goals, audience, brand, content, and technical needs — asked before design starts, not discovered midway.

Ways to request files from clients

There is no single best way to collect files from clients. Compare email, transfer links, cloud requests, forms, and dedicated portals to find the right fit.

Get website content from clients

What to ask a client for on a WordPress build — copy, images, and access — in what order, and how to handle the credentials safely.

Sending logins to your developer safely

Sending a website login by email or WhatsApp leaves a permanent password sitting in a chat log. Here's how to hand access to your developer safely instead.

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 — https://mcp.briefgate.dev/mcp, plus the local npx -y @briefgate/mcp package — that works the same way across every MCP-capable…

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, and BriefGate's hosted endpoint works with it the same way it works with Claude Code: point the CLI at the…

Client intake for Windsurf

Windsurf's agent (Cascade) reads MCP servers from mcp_config.json. BriefGate's hosted endpoint connects the same way any remote Streamable HTTP MCP server…

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

Claude Desktop connects to BriefGate two ways: as a remote custom connector (no install, browser-based sign-in) or as a local MCP server via…

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

The stretch between a client saying yes and the work actually starting is mostly the same four steps on every project: decide what you need from them, ask for…

Automate intake with Zapier

If you already run your agency on Zapier, client intake shouldn't be the one step that still happens by hand. This is a how-to companion to BriefGate for…

Intake automation in n8n

The best version of a client project is the one where, by the time you sit down to build, the logo, the copy, and the hosting login are already sitting there…

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

The best outcome for a finished intake isn't a link you have to remember to open — it's a project folder that already has everything in it, and a Slack…

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. No password to invent, no "confirm your address"…

How client credentials are stored

At some point in almost every project, someone needs a password. A WordPress admin login, a domain registrar's API key, the FTP credentials for a hosting…

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. Both were demo client portals on p.briefgate.dev…

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. Get the cadence wrong and you get the opposite: a client who…

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.

Case studies