Write a website project brief without technical jargon

You do not need to know the technical architecture before starting a custom website. “We want a modern site” is not enough to estimate or design one. A useful brief explains the problem, who will use the product, and how you will recognize a useful outcome.

Begin with an observable goal

Instead of “look more professional,” try “customers can compare our three main services and request a consultation.” Describe two or three important visitor journeys in plain language: arrival, information needed, and final action. Real customer questions help a design team more than a long feature wish list.

List assets and constraints

Note the logo, approved copy and photos, domain, current access, and the person who approves decisions. If payment or another system must connect, name that system and its owner; do not guess the integration design. Be candid about event dates and approximate budget.

Separate priorities

Use three columns: essential for launch, next phase, and future idea. This keeps the first version manageable. If your need is mainly introduction, services, and booking, a Business Page may be enough at first. Update the brief as decisions become clearer.