How to brief a design agency without wasting time

Vague intake wastes your week and ours. Mood boards without metrics force agencies to guess. Guessing produces quotes that miss budget, timeline, or outcome — then everyone argues about scope.

mxstermind Studio uses Discord and Telegram only. The checklist on /apply is the brief. No web forms, no calendar links — decisions happen where files and approvals already live.

Link to your current site or product — staging is fine. Outcome in one sentence: revenue target, conversion fix, launch date, or repositioning. Budget range with real numbers, not negotiate later. Timeline including hard deadlines and blackout dates.

Escrow preference — yes or no, which platform. Assets you can share: Figma, analytics, brand guidelines, API docs. Competitors or references you respect — ours or others. Stakeholder map: who signs off.

Missing budget range is the top reason quotes slip a week. We do not infer your ceiling from revenue stage alone.

Weak: we need a better website. Strong: increase qualified demo requests from paid traffic by 30% in Q3 with a new lander and CRM routing.

Weak: make it look premium. Strong: align visual system with enterprise procurement expectations while keeping PageSpeed above 95 on mobile.

Attach numbers where possible. Studio scopes against outcomes on /services — brand, web, growth — not against vague adjectives.

Do not open with we need everything. Prioritize. Do not attach seventeen PDFs without a summary line — zip files without context delay quotes.

Do not ask for free spec work or unpaid discovery decks. Complex engagements include a paid discovery milestone when architecture must be validated first.

Do not hide budget to test us. We will decline fit faster than you think — saving both sides time.

We reply with fit, capacity, and next step: discovery call, decline, or request for one clarifying detail. Same-day on Discord when Studio slots exist.

If fit is strong, discovery produces a written brief with milestones and price. Sign-off before execution. Weekly updates in-thread during build — see /process.

Repo access or architecture diagram. Auth model. Third-party APIs and rate limits. Compliance constraints. Link /developers pages that match your stack so engineering leads review before quote.

Portfolio case studies with similar complexity — /portfolio/crypto-trading-platform for full stack, /portfolio/drain-cx for marketing engineering — sharpen estimates.

Mention if legal requires MSA review, insurance certificates, or vendor onboarding portals. Studio can comply when timeline accounts for it.

Link /ethics-standards in RFPs — financial, IP, and delivery rules are public. Reduces back-and-forth with finance.

We need to increase enterprise demo requests from paid traffic by 25% in Q3. Current site: example.com — staging available. Budget: USD 45–65k, escrow on Request Network. Timeline: kickoff July 1, launch before Sept 15. Assets: Figma partial, HubSpot, GA4. References: competitor.com and /portfolio/drain-cx. Sign-off: CEO on milestones.

That brief tells us lane mix — likely /services web plus growth — and whether discovery can be short.

Instant fixed price without questions. No portfolio URLs. No named delivery channel. Vague IP terms. These are not mxstermind patterns — we ask clarifying questions or decline.

Founders and marketing often disagree on ICP. Resolve internally first or the agency optimizes for the loudest voice in the thread.

Attach one-page internal strategy if it exists. Contradictions found in discovery are cheaper than contradictions found at launch.

Deliverables per milestone, acceptance tests, price, payment schedule, assumptions, and out-of-scope list. You sign that before build — same rhythm as /process.

Keep the thread as source of truth. Forwarding email summaries loses decisions.

List locales, legal jurisdictions, and who translates. Studio can coordinate localization milestones — not assume English copy ships everywhere day one.

CDN and hosting regions matter for latency-sensitive products — note user geography in field one.

Name who gets repo access, which environments exist, and whether security review is required before launch. Surprises here delay Milestone 1 by weeks.

Files, approvals, and decisions stay in one searchable thread. Email forwards lose context; forms strip nuance. Studio delivery matches how operators already run launches.

A strong brief respects both sides: you get accurate quotes faster; we avoid discovery theater for leads that were never a fit.

Paste the /apply checklist into your first message, fill every field, link /portfolio proof, and name sign-off authority. That is the entire hack.

After the first message, send Figma links, analytics view access, and competitor URLs in one bundle — not one asset per day. Batch reduces quote latency.

If leadership changes scope, reply in-thread with what changed and we re-milestone — do not start a parallel email negotiation.

Reference /process so you know what discovery delivers before you ask for a number without a brief.