What should a premium website brief contain?
A useful website brief connects business goals, client questions and acceptance conditions. Set out content, visual direction, responsibilities and launch dependencies.
Article language: English

In this article
“Make it modern, elegant and impressive” may sound familiar, but it leaves the people building the site to read your mind. A premium website brief should first explain who comes to the site, what they are looking for and how you will know they found an answer. Only then can typography, photography and animation pull in the same direction. Start with those decisions. Thirty pages of adjectives can wait in the waiting room.
A brief brings together the decisions needed by the people writing, designing and building the site. Record answers that help them choose an approach and later check the result. Use the structure below for an initial conversation, and mark open questions as open instead of filling the gaps with generalities.
What decision should the visitor be able to make?
Start with one important situation. For example, a partner at a law firm recommends your company, and the person receiving the recommendation opens your site before a conversation. They need to check the scope of work, how you collaborate and who is responsible for delivery. This is a design scenario, not a story about a particular client. If you intend to test the design with users, also describe your criteria for recruiting UX research participants (in Polish), so the sample reflects that situation rather than simply the team's available acquaintances.
Write down what should happen after the visit. Booking a conversation, asking about a specific product and downloading documentation are different tasks. Each needs different copy, a different button and different information. Choose the priority in the brief. Other paths can remain, but they should not compete for attention on the first screen.
Also establish what happens after the click. Who receives the enquiry, what information do they need and when will they respond? A form may be the last section in a wireframe. For the client, that is where the working relationship starts.
What does the client need to know before making contact?
List questions from real sales conversations: price, timing, scope, rights to materials and support after launch. If an answer depends on the project, explain what it depends on. This gives you a useful content map.
- The offer description should help a visitor decide which task the company can help with.
- Work examples should use materials that may be shown publicly.
- The process description should identify stages, client decisions and the acceptance process.
- The contact section should explain the next step and provide the company's real contact details.
Missing material belongs in the brief too. If the company has no approved references, say so. You can show your own demonstrations if you label them clearly. An invented client logo solves the problem of an empty section only until someone asks for details.
How should you describe the visual direction?
Collect a few examples and explain why you chose each one. “I like this site” leaves a lot open to interpretation. “I like the space between the title and the photograph, and the way the price is presented” gives the team something to work with. Also identify elements your brand should avoid.
At Aeneia, proportions, typography, materials and light shape the direction. Those words still need to become observable website behaviour: does the title fit on a phone, can the description be read comfortably, and does moving between pages work after several quick clicks? A design in motion raises different questions from a still image.
Include the logo as a vector file, available typefaces and their licences, photographs and brand-use rules. For the logo, check the package of variants and handover rules (in Polish), so the team receives identifiable files for the right uses. For each asset, name its owner and the person who can approve publication. This avoids a frantic exchange of files at the end of the project.
How will we know the site is ready?
Agree on acceptance conditions before design begins. They should cover phones, large screens, keyboard use, forms, links and behaviour on a slower connection. Check text enlargement and reduced-motion preferences too. Motion has a cost: code, loading time and the visitor's attention.
Performance can be assessed more precisely than “it feels smooth”. Google's Core Web Vitals describe loading, responsiveness and layout stability. Good thresholds are LCP of at most 2.5 seconds, INP of at most 200 milliseconds and CLS of at most 0.1. Evaluate a single laboratory test separately from real visitors' experiences. Google Search Central's documentation explains the measures.
The brief should also state how publishing will work: who adds articles, where assets are stored, how backups are made and who updates contact details. These are part of the cost of maintaining the site. Establish them before signing off on the scope.
How do you turn the offer into a page map?
List the situations that bring visitors to the site. Beside each one, write their question, the material they need and the next step. If two scenarios lead to the same service, they may share one address. If they require different scopes, evidence and contact routes, consider separate entry points. A company department name rarely settles the menu on its own.
Mark priorities in the brief. What must be visible immediately, and what can appear after someone opens the detail? Information architecture for a B2B site (in Polish) helps turn the list into navigation. Separately plan the service page structure and supporting evidence (in Polish), so each offer has its own rationale.
A working example: a company sells implementation and ongoing support. Before buying, a prospective client asks what the implementation delivers; an existing client asks how to report a fault. A shared label such as “solutions” can hide both tasks. Record separate paths in the brief even if some materials and design are shared. That is a decision about how the site will be used, not a reason to expand every section in advance.

How do you commission images with a specific job?
Give each important photograph or illustration a purpose. Should it show a material, the scale of a product, the person responsible or a way of working? Specify where it will appear, expected proportions, space for any text and details that must not be cropped. This makes it possible to judge an image before placing it in the design.
Prepare a plan for brand photography on the site (in Polish). Distinguish photographs of actual work, portraits and conceptual illustrations. Each needs an honest label. A generated scene can build a visual language for the brand, but it should not pretend to show an office, client or result the company cannot substantiate.
Include mobile files, the source of each asset and rules for replacing it later. Inspect the image in its intended crop. A face at the edge or a product hidden under a heading is a composition problem that another export format is unlikely to fix. Approving one large file does not complete acceptance of every use.
How do you balance a distinctive design with the cost of maintaining it?
Choose the elements that should really draw attention. They might be the first screen, a material-based illustration or a transition to service details. For each one, record how it behaves on a phone, with a keyboard and when motion is reduced. The team then knows where to be bold and where to preserve a calm reading rhythm.
Connect the requirements for premium website typography (in Polish), microinteractions (in Polish) and business website accessibility (in Polish). You do not need to decide every animation in the brief. You do need principles: content available without waiting, clear button states and a way to complete the task under the agreed conditions.
Assess the cost of images, fonts and scripts through a speed and Core Web Vitals measurement plan (in Polish). Record design requirements before choosing effects so later corrections have shared criteria.
What belongs in the brief when materials are not ready?
Mark each missing item, its owner and the date by which it is needed for the relevant stage. Separate copy that must be written, facts that must be confirmed and files that must be supplied. Those are three different jobs. Give the team preparing the estimate the actual state of the material, even if some of it remains draft.
For the first release, agree on a version you can show honestly. If you do not have permission to show a project, use another verified item or remove the section from the initial scope. Keep a list of later additions. After launch, each new item should have an owner and a review date so the site continues to describe the company as it is.
Who makes the final decision?
Name one person to collect feedback and approve stages. Others can contribute sales, legal or product knowledge. Their comments should come together in one document with a decision. Five messages containing five different versions of a heading can stop even a small project.
At the end of the brief, include the deadline, budget, dependencies and out-of-scope list. If launch depends on a photo shoot or approval of the offer, record that dependency with a date and an owner. Each detail helps the team make a workable plan.
A finished brief should be something you can discuss in one conversation. To turn it into a page structure and acceptance rules, explore Aeneia Design.
Aeneia Design: Use the contact page to describe the task and the materials available to start. Turn the brief into a concrete website design.
Include website acceptance scenarios (in Polish) and technical SEO conditions (in Polish) in the brief. That makes the requirements for forms, addresses and HTML content clear before work starts.
Set out roles and previews in the CMS content publication plan (in Polish). The brief should say who takes a new item from draft to approval.
If clients confuse two versions of an offer, include a comparison of services on one page (in Polish). Agree on the criteria and situations in which each applies first. A designer should not have to pick a winner based on which card has the prettier frame.
If the website is being built alongside a process change or entry into a new market, establish the sequence of related website, automation and expansion work (in Polish). That keeps dependencies from appearing only when the launch deadline arrives.







