Writing a website brief when you are not technical
A good brief is not written by the client or the studio alone. The client describes the business problem; the studio turns it into requirements.
Start with the business, not the tech
Your part is who the customer is, what action they should take, what objections they raise and how you differ. No studio can invent that.
A useful exercise: list the ten questions customers most often ask by phone or Telegram. Those answers are the skeleton of the site, grounded in real demand.
Sections the brief needs
Goal and target action, a page list with content notes, language versions — usually Russian and Uzbek here — and functional requirements such as forms, filters and accounts.
Integrations: CRM, a Telegram notification bot, Payme and Click if you take payment, analytics. And what you must be able to edit yourself in the admin panel — the most commonly forgotten item.
Describing design without design vocabulary
Use references. Collect five or six sites you like with one sentence each on why, plus the same number you dislike — the negatives are often more useful.
Avoid words like modern, premium or eye-catching. Everyone reads them differently, and you will burn revision rounds agreeing on definitions.