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.
Everything a typical website project needs from the client, grouped by category, with a short reason for each item and whether it can wait until after kickoff.
Everything specific to selling online that a client needs to supply before an online store can launch, grouped by category, with the reason and timing for each.
A logo brief that skips positioning, usage and file formats produces revision after revision. Here is what to ask before any concept work starts.
Everything a client needs to hand over before an app gets built — store accounts, branding, API keys, legal pages — grouped with a reason and timing.
Clients ignore vague requests buried in a busy inbox. These five copy-paste templates — request, two reminders, an escalation, a thank-you — fix that.
A copy-pasteable client intake form for web design projects, with the exact field type each item needs, ready to send as-is or adapt before kickoff.
A repeatable process for getting logos, copy, photos, and login credentials from clients on time, plus a checklist you can copy into your next project kickoff.
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.
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.
A web design onboarding questionnaire covers goals, audience, brand, content, and technical needs — asked before design starts, not discovered midway.
There is no single best way to request files from clients — the right pick depends on how many items you need, how often, and whether any of it is a password.
A WordPress build usually stalls waiting on the client for copy, images, and access, not on the build itself — here is what to ask for and in what order.
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.
BriefGate MCP lets a Cursor agent collect a client's logo, copy, and credentials through a tracked portal instead of stalling mid-build.
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.
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.
Codex can scaffold a booking flow in one session, then wait days for a client's gallery, price list, and booking-tool login to show up by email.
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 AI assistant: the assistant defines what it
BriefGate connects to ChatGPT as a custom MCP connector, so a ChatGPT session that is scaffolding or reviewing client work can ask the client directly for the logo, the copy, or a login, instead of yo
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 URL, and Gemini's own OAuth flow handles the
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 does, with an API key as the fastest path to
VS Code's built-in MCP support (used by GitHub Copilot's agent mode, and by any other chat extension that reads the same mcp.json) connects to BriefGate's hosted endpoint with OAuth handled automatica
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 claude_desktop_config.json. Both give you the same 13 tools
claude.ai connects to BriefGate as a custom connector — no install, no API key to copy, sign in once from your browser.