Questions to Ask a Web Designer Before You Commit

The website launch price is only one part of the decision. Ongoing costs depend on your hosting, updates and support needs, and what the project includes. The most useful questions to ask a web designer before hiring will clarify those costs, who owns the finished website and what happens after launch.

It’s sensible to get clear answers before committing: your website should support your business long after it goes live. This guide explains what to ask about timing, post-launch support, marketing and how the site can attract suitable clients.

Use these questions to compare what each project includes and how the work supports your business goals. You’ll be better prepared to choose an approach that gives you clarity from the outset and a website designed to support your next stage of growth.

1. What are the yearly costs going forward for site updates and maintenence?

Ask for a breakdown of recurring costs, not just the initial build. After launch, you may need hosting, domain renewal, security updates and help with website changes. Who owns the website, domain, content and design files? Your agreement should name the owner of each, explain any licence restrictions, and state which files and account access you’ll receive.

Separate essential renewals from optional ongoing support. Ask which tasks a maintenance arrangement covers, such as updating the content management system, themes and third-party plugins. Hosting companies generally provide server space, not updates to your site’s themes and plugins. If nobody is responsible for those updates, a low hosting charge may leave important work uncovered.

Request a written schedule showing what renews, when it renews and who pays each provider. List hosting and domain renewal separately from developer support or new features. Ask whether support includes routine content edits, technical troubleshooting or only specific maintenance tasks. Scope matters: adding a service page may be treated differently from correcting a phone number.

Check how VAT appears on the quote and invoices. Revenue states that the 21 per cent rate applies to taxable amounts other than those relating to goods or services taxed at the other specified rates. Ask whether the quoted figures include applicable VAT, so you can compare the stated total with your business budget.

Keep control of your domain by confirming which account registers it and who holds the login. The domain should be registered to your business, with renewal notices sent to an email address you control. Get access to the registrar account, hosting dashboard and website administration area. Store these details securely and record who can change billing or access settings.

Editing access also affects the cost of everyday changes. Ask for an administrator or editor login, then clarify which changes your team can make safely. For example, can you update opening hours, staff details and service descriptions without developer help? Agree how design files, licensed fonts, stock images and custom code may be used or transferred if the working relationship ends.

Include security and accessibility in the maintenance conversation. Ask who applies software updates, checks backups and responds to site problems. For accessibility, ask how visitors will navigate menus, read page content and use forms with assistive technology. Put agreed checks and responsibilities in writing, alongside renewal dates and account ownership.

2. Will the designed website be YOUR property?

Ask for a written account of what transfers to you when the project ends. A website has several parts: page structure, text, images, design files, software and hosting arrangements. The agreement should identify who owns or can use each part and explain any ongoing licence or access restrictions. A login alone doesn’t establish ownership of the website’s underlying components.

Ask which content management system (CMS) will power the site, and how its structure supports your pages. WordPress powers 43% of websites that use a content management system. Whatever platform is selected, ask to see how you’ll edit a service page, change a menu item and publish a blog post. A practical demonstration helps you understand the tools before approving the build.

Check what editing access you’ll receive after launch. Will your account let you update text, images, page titles and contact details, or will some changes require developer access? Ask for a short handover using an example, such as updating opening hours. Website update tools may be used for 3-5 years after launch, so ask how updates work and what happens if the platform or theme changes.

Discuss whether the site will use a pre-built theme or a custom design. A pre-built theme can suit a business that prioritises speed, cost-effectiveness and simplicity. Ask which parts can be adapted, whether the theme supports your required pages and how it will display on mobile. For a custom build, clarify which design files you’ll receive and whether you can reuse or alter them later.

Ask who prepares title tags and meta descriptions for important pages, and whether you can edit them through the CMS. These details help search engines understand page topics, while clear titles tell visitors what they’ll find. Basic on-page SEO helps search engines assess relevance, but it doesn’t guarantee a first-place Google ranking. Agree who supplies the content and checks these fields before launch.

If you’re replacing an existing site, ask for a review of its technical debt before work begins. List outdated plugins, broken page templates, duplicated content and integrations that still support essential tasks. Decide which issues will be repaired, removed or carried into the new structure. A clear migration plan can stop an old problem quietly becoming part of the replacement site.

Irish web designers can structure payment schedules and deposits differently, so ask for the proposed stages in writing. The quote should connect each payment to a defined project milestone, such as approval of the structure, design or completed site. If you’re planning a new build, web design for your business should include a clear handover of editing access and agreed website assets.

3. How long will it take to complete a web design project?

A standard website project often takes between four weeks and three months to build. The schedule depends on the agreed scope, how quickly content and feedback arrive, and whether the site needs custom features. Among the questions to ask a web designer before hiring, ask for a realistic completion timescale before signing. Get the planned start date, milestones and expected launch date in writing.

Meet the people who will manage and deliver the work. Ask who handles planning, design, development and testing, and who will answer your questions at each stage. Review examples relevant to your business, not just attractive visuals. A portfolio with at least half a dozen professional websites gives you work to discuss. Ask what the team learned from similar projects and how that experience shapes its approach.

Compare a freelance web designer and an agency by looking at responsibilities, communication and project coverage. Ask who performs each task, manages deadlines and steps in if a key person is unavailable. An agency may divide work among specialists, while a freelancer may handle several project roles. Use these questions to ask a web designer before hiring to compare the proposed team and process, rather than relying on the label alone.

Ask how the team uses artificial intelligence (AI) during the project. Does AI assist with research, draft content or code, and who reviews that work before it reaches your site? Clarify whether your information is entered into external AI tools and how generated text or images are checked for accuracy, originality and suitability. Agree which decisions receive human review.

A clear project plan should explain how requirements are gathered, feedback is collected and each phase is approved. Ask what the team needs from you, such as service details, images or final copy, and when each item is due. Delays in supplying agreed content can affect page reviews and launch preparation. Nominate one person to collect feedback so the team receives a clear response at each review point.

Before work begins, ask how scope changes affect the schedule. Adding an online booking feature after design approval, for example, may require extra development and testing. Clarify how change requests are recorded, approved and reflected in the timeline. Agree how often progress updates arrive and where decisions are documented, such as in a shared project tracker or email summary.

If you need to change designers mid-project, identify what’s complete and what remains. Ask for a handover of approved designs, content, project files, access details and unfinished tasks. Check the original agreement for ownership and transfer terms, then map the remaining work against the launch plan. This gives the incoming team a clear starting point and helps limit avoidable rework.

4. Post-launch support and marketing packages

Ask what help continues after launch, and for how long. A useful benchmark is at least 30 days of post-launch support. Clarify whether this covers technical faults, content corrections or questions about using the site. Ask how support requests are submitted, who handles them and what happens when the agreed period ends. A written scope helps separate launch fixes from future changes.

Define maintenance separately. Ask who will install updates, monitor backups and investigate problems affecting site access. Hosting alone doesn’t cover updates to themes and third-party plugins. Request a clear list of recurring tasks and their frequency, plus the process for reporting an issue. For example, establish whether a broken contact form is maintenance or additional development.

A package should also explain what it excludes. Ask whether new landing pages, feature changes and content uploads are included or treated as separate work. For a growing business, adding an online booking function is different from correcting a spelling mistake. Get the scope, renewal terms and cancellation process in writing so you can compare ongoing support with work your team can manage.

Marketing should support measurable business goals, rather than simply adding channels to a package. Ask how the website’s search engine optimisation foundations will support visibility after launch, and which pages or services they prioritise. If paid advertising is included, clarify who manages campaigns, creates landing pages and reviews results. A Dublin service business, for example, may need different website content from an online retailer.

Before launch, request a quality assurance plan. The team should test the website across devices and browsers, check that links work and repeat those checks after launch. Ask how forms, phone links and key customer journeys will be tested. A mobile review should include real page content, not just the design template. Agree who signs off the final checks and how faults are recorded.

Plan for downtime as part of the launch process. If the existing site must go offline, ask the team to schedule the change when traffic is lowest. Confirm who will manage the switch, test the new site and restore the previous version if a serious issue arises. A named launch lead and agreed communication route make it easier to respond quickly during the changeover.

Offboarding matters too. Ask what happens to support tickets, website access and project records if the package ends. Agree how outstanding issues are documented and how account access is handed over. Before signing, make sure you know the final support date, who controls the next renewal and which marketing tasks continue. This gives your team a clear plan beyond launch.

5. Questions about business goals and attracting suitable clients

Start with the business result, not the colour palette. Tell the designer which services you want to grow, who typically buys them and what a suitable enquiry looks like. A Dublin accountant, for example, may want more calls from local businesses, while an online retailer may prioritise completed orders. Ask how the site structure, page content and calls to action will support that specific goal.

Ask how the designer will help visitors find the right service and take a useful next step. A page for a specialist service should explain who it suits, what problem it addresses and how to enquire. Ask how search engine optimisation will inform page topics and headings. Basic on-page SEO helps search engines understand a page’s subject and its relevance to searches, but it doesn’t promise a top ranking.

Review work that matches your project, rather than judging a portfolio on appearance alone. Ask to see examples for a similar audience, business model or service, then discuss what each site was designed to achieve. Request client references and ask about communication, delivery and how the finished website met the original brief. If a designer can’t provide contacts for satisfied customers, treat that as a warning sign.

Watch for unclear scope, evasive answers about past work or guarantees of search engine rankings. These make it harder to assess what the work includes and whether expectations are realistic. Ask for deliverables, responsibilities and approval steps in writing before committing. Clear answers matter more than polished promises.

Agree your own responsibilities before work starts. Ask what the designer needs from you, who supplies the copy and photography, and when each item is due. One project might need service descriptions, staff biographies and photographs of a premises. Another could rely on product details and images. A project that expects you to prepare 30 pages of copy before work begins needs a clear explanation of why that volume is required.

Decide how you’ll give feedback and approve content. Nominate one person to gather colleagues’ comments, then send the designer a single, organised response at each review stage. Ask whether feedback should be shared by email, in a shared document or through project software. For example, label each requested change by page and describe the intended outcome, rather than sending conflicting edits from several people.

A suitable website should make it easier for the customers you want to reach to recognise themselves and enquire. If you’re planning a site around defined business goals, discuss your web design project with a team that can shape its pages around your audience, services and enquiry journey.

Web Bridge: Web Design

Web Bridge provides web design for businesses planning a new website or improving an existing one. Its approach connects the site’s structure and content with your business goals, audience and enquiry journey.

Once your project requirements are clear, Web Bridge can help shape a website that presents your services and guides suitable visitors towards getting in touch. If visibility is also a priority, SEO Services can support the site’s search foundations, while Google Ads or Meta Ads can extend your marketing activity.

Bring your project brief, preferred pages and key business priorities to the conversation. That gives the team a practical starting point for discussing the right web and marketing support for your needs. Contact Web Bridge to discuss your website plans.

Turn your website plans into a clear brief

Your next step is to turn your business priorities into a practical project brief. Identify the customers you most want to reach, the services or products you want to emphasise, and the action you want visitors to take. This gives your web designer a useful starting point for building a site around real business needs.

Keep the questions to ask a web designer before hiring close as you discuss your priorities and decide what a successful project should achieve. Web Bridge offers web design alongside SEO Services and Google Ads, supporting a broader approach to online visibility. Choose the work that fits your needs and sets a clear direction for your next stage of growth.

Contact Web Bridge to discuss your website. A focused conversation can help you move from ideas to a considered plan, and take the next step with confidence.

Frequently Asked Questions

What are the yearly costs going forward for site updates and maintenance?

Ongoing costs depend on the support and services your website needs after launch. Separate hosting and domain renewals from maintenance, software updates and content changes. Updating opening hours, for example, differs from adding a booking feature. Ask for each recurring task to be listed separately, with its renewal date and the person responsible. That makes it easier to plan your annual budget and identify work outside the agreed support.

Will the website be optimised for fast loading in browsers?

A well-built website should be tested for loading performance across common devices and browsers. Ask what the team will do to keep pages responsive, such as optimising image files and avoiding unnecessary scripts. A large image gallery, for example, can slow a page if its images aren’t prepared properly. Request a performance review before launch and ask how the team will identify and address slow pages after new content or features are added.

Will there be a contact page with a form visitors can complete?

Ask for a contact page that gives visitors a clear way to get in touch, with a form if it suits your business. Decide which fields are genuinely needed, such as name, email address and enquiry details. A Dublin service business might also include a phone number and opening hours. Test the form before launch by submitting a sample enquiry, then confirm the message reaches the right inbox and visitors see a clear confirmation.

Does the design company include social media and Google Maps integration?

Social media links and a Google Maps embed can help visitors connect with your business or find its premises. Ask which platforms will be linked and where those links will appear, such as the footer or contact page. If customers visit a Dublin location, confirm the map points to the correct address and works on mobile. Agree who supplies the map details and social account links so the site directs visitors to the right places.

How long will it take to complete a web design project?

A standard website project often takes between four weeks and three months to build. The timeline depends on the agreed pages and features, when you provide content and how quickly feedback is approved. Ask for a schedule that identifies the main review points and planned launch date. For example, agree when you’ll review the homepage and when the team needs final service descriptions. This helps both sides spot delays before they affect launch.

Does the web design price quoted include VAT?

The quote should state clearly whether VAT is included or added to the quoted amount. Revenue states that (a) 21 per cent of the amount on which tax is chargeable applies other than to goods or services taxed at specified other rates. Ask for the VAT treatment and total to appear in writing, so you can compare proposals on the same basis. If the quote changes, request an updated breakdown before approving extra work.

Will the designed website be your property?

Ownership depends on the project agreement, so read its terms for the website’s code, design files, content and licensed components. Ask what you can keep, edit or transfer if you move to another team. A practical handover test is to sign in, edit a page and download an agreed copy of your content. Record which third-party tools need separate licences, as their terms may affect how you use the site.

What exactly are the annual hosting costs involved?

Annual hosting costs depend on the hosting plan, the resources your site uses and any management features included. Ask whether the quoted hosting covers backups, security monitoring and technical support, or only server space. Clarify whether email, domain renewal and software maintenance are separate charges. An online shop, for example, may have different hosting needs from a small brochure site. Request the renewal terms and billing period in writing before choosing a plan.