In short
- Website projects are usually held up by content, images and logins that are not ready, not by the programming itself.
- The brief sets the goals of the project and the audience it is aimed at. The technical spec describes the structure and features of the site.
- Clear, measurable goals (for example, the number of enquiries or orders) are the basis for building the right structure and give you a real measure of whether the project worked.
- The client should own the domain, the hosting and the analytics accounts, so they keep full control and are not dependent on the supplier.
Why websites get delayed and how good preparation helps
A website order often starts with plenty of enthusiasm, then quickly stalls. The client answers some of the questions, and after that the project stops. In practice, the delay rarely comes from the programming. It is usually caused by missing copy, missing images, no access to systems or unclear goals. A website brief is the first step that prevents these bottlenecks. When the brief is filled in thoroughly and in detail, the project runs smoothly and finishes on time.
Experience shows that good preparation for a new website is what keeps delays and surprises away. A website spec that sets out the goals and the scope gives a clear direction from the very start. Without it, even the best team works blind, and a successful business website needs a clear direction.
Our own work as a studio confirms this. On the Donkydoo project, a clear brief from day one meant the structure and the content could be prepared without interruptions. The result was a site that meets the business goals and did not need to be reworked.
When the preparation is done right, the question of how to keep a website project from dragging on answers itself. Everything needed is in place before the build starts. The copy is ready, the photos are chosen, the logins are sorted. Then the programming moves fast, and the client gets the result by the agreed date.
What a website brief is and how it differs from a technical spec
A website brief is a document that describes the goals, the audience, the positioning, the content and examples of websites you like. It answers the question “Who is this site for and what does it need to achieve?” The technical spec is something else: it describes the structure, the features, the integrations and the specific requirements for the build. It answers the question “How exactly will the site be built?”
The order matters. The brief is filled in first, then the technical spec is written. Reverse the order and you often end up with changes, a growing scope and unplanned costs.
The brief is more than a formality. It ties the business goals to the technical build.
Why the brief is the first step to a successful project
The logic is simple: a well written brief leads to a clear scope. A clear scope lets you set a realistic deadline. A realistic deadline rules out last-minute requests and disappointment on both sides. When the goals are written down, every decision on the project is weighed against them. If a feature does not serve the goal, it does not go in. That saves everyone time and money.
Website goals: how to state them clearly and briefly
Endless revisions most often come from a vaguely stated goal. “I want a nice website” is not a goal, it is a wish. Nice is subjective, and every person will see it differently. The opinions of the people looking at the project keep changing.
A specific goal sounds different: “Ten enquiries a month from organic search” or “Twenty orders a month from the online store”. A goal like that is measurable. Once the site is live, you can see whether it has been reached.
- Enquiries: form, phone, email
- Orders: number of items sold or basket value
- Bookings: appointments made for a service
- Calls from the website
- Subscriptions: new sign-ups to the email list
Each goal calls for a different structure. A site built for orders is organised around the product pages and the basket. A site built for enquiries is organised around trust and easy contact. When the goal is clear, the structure follows from it.
Copy and photos for your website: what to prepare in advance
It often happens that the design is finished and then the project stalls because the content is missing. To avoid that, it is best to prepare the materials in advance.
- Copy for the home page, the presentation of your services or products, the About page and the Contact page.
- Photos of the team, the products and the premises, ideally your own rather than stock shots.
- The logo and brand elements in vector format.
- Examples of websites you like, with a note on what exactly you like about them.
Even if the examples and notes are rough, they are a great starting point. Text that exists can always be improved, while missing text will hold up the project.
Which texts matter most and how to write them without a copywriter
The home page has to make clear what you offer, who it is for and how the visitor can use it. A few sentences that answer those questions are enough. For your services, describe briefly what each one includes and what the client gets out of it. The About page does not need the full history of the company. It is enough to give the reason clients should trust you. The easiest way to start is to answer these questions in writing. Wording and style can be polished later.
Ways to prepare the materials: which works best
| Approach | Client’s time investment | Budget | Quality and authenticity | Speed | Control over the final result |
|---|---|---|---|---|---|
| The client prepares everything | The most time | Lowest | Depends on their skills, but usually authentic | Slowest preparation | Full control, but with a risk of delay |
| Partial outside help | Moderate time | Higher than doing it yourself, lower than full outsourcing | Higher quality, with authenticity guaranteed | Good turnaround | The client keeps control, with professional support |
| Fully outsourced content | Minimal time | Highest | Excellent quality is possible, but authenticity depends on how well the supplier understands the business | Fastest preparation | Limited control, especially for highly specialised businesses |
When it comes to preparing the materials, there are three main approaches. If you have plenty of time and a limited budget, you can prepare everything yourself. If you are short on time but have the budget and want a fast result, full outsourcing is the best choice. For most small and mid-size businesses, though, the best option is partial outside help. That is exactly what we offer at WebTact: we help clients prepare their materials while they keep control over the content.
Domain and hosting in the client’s name: why ownership matters
The domain is registered in the client’s name. The hosting account is under their control. Google Analytics, Search Console and the social media profiles also belong to the business itself, not to the agency. This guarantees independence and is the foundation of a successful brand.
When the accounts are in the supplier’s name, the client becomes dependent. Changing partner can mean losing the domain, the site’s history or the traffic data. Some suppliers use these assets to hold on to a client and secure future payments. This practice is known as access lock-in, and it can be very expensive.
The client should never give up access to the core profiles and accounts.
Before work on the project begins, the client should check whose name the domain and hosting are registered in. If they do not own them, that is the first and most important question to ask the new partner.
Client checklist before the project starts: what should be ready
- Clearly stated website goals: how you will measure success.
- A description of the target audience: what they look for and what holds them back.
- Finished copy for the main pages.
- Photos of the team, the products and the workplace.
- Logo and brand materials in vector format.
- Your own domain and hosting, registered in your name.
- Access to Google Analytics, Search Console and the social profiles.
- Examples of websites you like, and what exactly you like about them.
Putting this list together takes anywhere from a few hours to a few days, depending on the size of your business. Experience shows that good preparation saves time and effort later on.
Frequently asked questions
What is a website brief and why does it matter?
A brief is a document that describes the business goals, the audience, the positioning and the content of the future website. It is useful because it sets the scope, the deadlines and the structure of the project.
What is the difference between a brief and a technical spec?
The brief explains the goals and the audience of the website. The technical spec describes “how it will be built”, including structure, features and integrations. The brief comes first.
Why should the domain and hosting be in the client’s name?
That way the client stays independent. If the accounts are in the agency’s name, changing supplier can mean losing the domain and the data.
What copy and photos are needed before the build starts?
Copy for the home page, services, about and contact pages, photos of the team and the products, and the logo in vector format. Drafts are enough to start with.
What happens if the client is not prepared?
The project stalls after the design is approved, and extra requests and costs appear. Preparing before the start is the cheapest way to avoid this.
Good preparation takes no special skills, only time and attention. When the goals are clear and the materials are gathered, the website development process becomes more predictable and efficient.
