← Back to the blog

What to prepare before your website project.

A useful brief, the right files, and a few clear decisions can make the whole project feel easier.

Bring the business problem to the first conversation.

You do not need a finished sitemap or a folder full of design references to start a website project. You do need a useful explanation of what is changing in the business. Perhaps you are opening a new service line, outgrowing a do-it-yourself site, or discovering that customers cannot understand what you offer. Describe that situation first.

Then finish this sentence: ‘A better website would help our customers…’ Your answer might be to compare services, see relevant work, request an estimate, or understand what happens before an appointment. This keeps the brief tied to a real task. ‘Make it modern’ can be a useful visual preference, but it is not a complete business goal.

Name the audience and the decision they are making.

Think about the person who will visit, not only the company that will own the website. What do they already know? What makes them hesitate? Which questions do they ask before becoming a customer? A Tulsa homeowner choosing a remodeler will need different information from a business owner comparing advisory services.

Write down the questions your team answers repeatedly. If the customer often asks whether a service covers their area, make service-area information part of the plan. If the project requires a substantial commitment, visitors may need examples, a clear process, and realistic expectations before they are ready to inquire. These details help shape the content and navigation before anyone chooses colors.

Gather the files you actually have.

Create a shared folder for your logo, brand colors, photographs, service descriptions, and other material you are authorized to use. Keep original image files where possible. A picture copied from an old presentation or social post may be too small for a large website section. Label the files clearly enough that another person can understand them.

Make a separate list of missing material. You may need new photography, help writing a service page, or a clearer explanation of your process. It is better to identify those gaps early than to discover them during the final review. Do not treat another company’s photographs, copy, or logo as material you can simply reuse. References can communicate a preference without becoming your content.

Decide who supplies and approves the words.

Content responsibility is one of the most useful things to clarify before design starts. Are you providing finished copy, rough notes, or a subject-matter interview? Is the studio organizing, editing, or writing the material? These are different amounts of work, and the project schedule should reflect the agreed approach.

Choose an approver who can check accuracy as well as tone. A designer may make a service sound clear without knowing that a particular feature is no longer offered. Ask everyone who needs to approve the content to review it at an agreed stage. Late factual changes are easier to manage when they are exceptional rather than the normal way the business provides information.

Make a short list of functions and dependencies.

Describe what the site needs to do in ordinary language: accept inquiries, let visitors book a consultation, display completed work, or sell a defined range of products. Mention the tools the business already uses and any information that must move between them. A working booking integration takes more planning than a button linking to an existing calendar.

Separate requirements for the first release from ideas that can wait. A simple list marked ‘launch’ and ‘later’ is often enough. Include any constraints that could influence the build, such as an existing hosting contract or a platform your team already knows. Ask for help evaluating those constraints; you do not need to solve the technical architecture yourself.

Set a realistic budget and a meaningful date.

Give a budget range when you have one. It allows the studio to suggest a suitable scope and explain the tradeoffs. If your budget is not yet settled, explain which outcomes matter most and ask for a phased proposal. Compare what the proposal includes, not only the total at the bottom.

If there is a deadline, say what drives it. A trade event, a business opening, or a campaign launch creates a different planning problem from a general wish to update the site this season. Account for your own review time and the availability of photographs and copy. A date is much more useful when the responsibilities required to reach it are visible.

Choose one clear route for feedback.

Agree who collects comments and who makes the final call. Several people can contribute without giving the designer separate, conflicting instructions. A consolidated review should identify the issue, explain why it matters, and distinguish a correction from a preference.

For example, ‘Customers usually ask about our service area before our history; can that information appear earlier?’ gives a designer something useful to solve. It is more actionable than ‘This page feels wrong.’ Keep the original brief nearby during reviews. It gives both sides a shared reference when a new idea arrives and helps the finished site stay focused on the people who will use it.

YOUR NEXT CHAPTER

Let’s make your business
look as good as it is.

A fresh start. A thoughtful upgrade. A website that feels like you.

Tell us about your project