If you are thinking about getting a new website, one of the questions sitting quietly in the back of your mind might be:

“How much work is this going to be for me?”

It is a fair question.

A lot of business owners know they need a better website, but they worry the process will be time-consuming, unclear, or hard to keep on top of alongside everything else they already have to do.

The honest answer is this:

You do need to be involved in the website design process, but you should not have to manage it yourself.

Your website partner should guide the process, explain what is needed, and keep the project moving. Your role is to bring the business knowledge, provide the right information, give feedback, and make key decisions at the right points.

If you are still deciding what type of website you need, our guide on how to choose the right website for your business is a useful place to start.

The short answer

You should expect to be involved at key stages of the website project, especially during discovery, content collation, design feedback, website review and final sign-off.

You do not need to know how to design or build a website. That is the job of your website team.

For most small business website projects, the biggest time commitment is usually content collation and feedback. Once those parts are clear, the rest of the process should feel much more manageable.

How involved will I be at each stage?

This is not an exact rule for every project, but it gives you a realistic idea of where your time and input will be needed.

What happens before a website project starts?

Before a website project properly begins, there should usually be a planning stage.

This might include an initial enquiry, a discovery call, a proposal, agreeing the scope, and confirming the project route. At this stage, your website partner should be trying to understand what your business actually needs, not just what you want the website to look like.

They may ask questions such as:

• What does your business do?
• Who are your main customers?
• What services or products do you offer?
• What is not working about your current website?
• What do you want the new website to achieve?
• Do you need the website to generate enquiries?
• Do you need SEO support?
• Do you need hosting and ongoing care after launch?

This matters because the website should not be built around guesswork.

At FreshOnline, our website design projects are planned around what the site needs to do for the business, whether that is building trust, explaining services, supporting SEO, generating enquiries, or helping people take the next step.

Discovery, planning and content collation

Discovery is where the project starts to take shape.

This stage helps define the structure of the website, what pages are needed, what content needs to be gathered, and what the user journey should look like.

For example, a business with several services may need separate service pages rather than one short services overview. A business that relies on local search may need pages that support SEO. A business that needs more enquiries may need stronger calls to action, trust signals and clearer contact routes.

If your main goal is to turn more visitors into leads, it may be worth reading our guide on what a small business website should include to generate enquiries.

Content collation is often the stage clients underestimate.

This is where the words, images, logos, testimonials, team details, service information, pricing, FAQs and access details are gathered.

Depending on the project, you may need to provide:

• logo files
• brand guidelines, if you have them
• photos of your team, products, premises or work
• service descriptions
• testimonials or reviews
• examples of websites you like or dislike
• login details for your current website, domain or hosting
• key business information
• any legal policies or terms
• existing copy you want to keep or improve

This stage can slow a project down if information is missing or unclear.

That does not mean everything needs to be perfect before you start. But the more prepared you are, the smoother the project will usually feel.

How much time should I expect to put aside?

This varies depending on the size of the project, how much content you already have, and how quickly you can make decisions.

For a smaller website, you may only need a few focused blocks of time for discovery, gathering content, reviewing the design and checking the final site.

For a larger website, or a site with several services, e-commerce, booking systems, SEO planning or lots of pages, you should expect to spend more time providing information and reviewing content.

The biggest thing to remember is that your involvement is usually spread across the project. You should not need to sit and work on the website every day, but you will need to respond at key points so the project does not stall.

Design stage

The design stage is where the visual direction of the website starts to come together.

Depending on the type of project, this might mean working from a premium template structure or creating a more bespoke design.

This is where you will usually review the look and feel of key pages. You may be asked for feedback on layout, colours, imagery, spacing, content flow and whether the design feels right for your business.

Good feedback matters here.

Saying “I do not like it” is hard for a designer to work with. Saying “this feels too formal for our audience” or “this section needs to feel warmer and more approachable” is much more useful.

You do not need to know design terminology. You just need to explain what feels right, what feels wrong, and why.

If you are unsure whether a template or bespoke route makes sense, our guide on template websites vs bespoke websites explains the difference.

Build, feedback and revisions

Once the design direction is approved, the website moves into build.

This is where the agreed design and content structure are turned into a working website. Pages are created, sections are built, forms are added, links are set up, and the site begins to function properly.

Your involvement during the build stage is usually lighter, but you may still need to answer questions, approve changes, or provide missing details.

Once the website is ready for review, you will usually be asked to give feedback.

The best feedback is:

• specific
• grouped together
• easy to understand
• connected to the goal of the website
• shared in one place where possible

It is much harder to manage feedback when comments come through in several emails, WhatsApp messages, calls and voice notes.

To keep things simple, try to provide feedback by page or section.

For example:

• Homepage: change the main image
• Services page: add more detail to service two
• Contact page: update opening hours
• Mobile: check spacing under the enquiry button

It is also worth remembering that revisions should stay within the agreed scope. If you decide halfway through that you need new pages, extra functionality or a major change in direction, that may affect cost or timescale.

Testing and launch

Before the website goes live, it should be tested.

This may include checking:

• forms
• buttons
• links
• mobile layouts
• desktop layouts
• page speed
• images
• menus
• key functionality
• redirects, if needed
• basic SEO settings
• privacy and policy links

Testing matters because small issues can affect trust and enquiries.

A broken form, missing link or awkward mobile layout can stop someone from taking the next step.

Once final checks are complete, the website can be launched. At this point, you should know what happens next, including hosting, maintenance and support.

If your site is built on WordPress, ongoing care is important. You can read more about this in our Hosting and Care Plan.

What usually slows a website project down?

The biggest project delays usually come from missing content, unclear feedback, delayed approvals or changes to scope after work has started.

Common delays include:

• late copy or service information
• missing images
• missing website, domain or hosting access
• unclear feedback
• too many decision-makers
• changing the scope halfway through
• uncertainty around services or pricing
• delayed sign-off at design or build stage
• new ideas being added after the project has started

This does not mean you need to have everything perfect before the project begins. But it does mean that decisions, content and feedback all have a direct impact on timescales.

A good website partner should help you understand what is needed and when.

At FreshOnline, we know content collation can be one of the hardest parts of a website project, so we aim to make the process clear from the start.

Final thoughts

So, how involved do you need to be in the website design process?

You need to be involved at the important decision points, but you should not have to carry the whole project.

You do not need to know how to design, develop or launch a website. But you do need to share your knowledge of the business, provide content and assets, give clear feedback, and make decisions when needed.

A good website partner will guide you through the process and make it clear what is needed at each stage.

If you want to understand the bigger decision around who should help with your website, you can read our full guide on how to choose the right website partner.

Or, if you are ready to talk through your project, you can explore our website design services or get in touch with FreshOnline.