You do not need a finished sitemap, polished copy or a favourite font before asking a web designer for a quote. A useful starting point is a clear account of your business, what you want the website to help with, and the practical limits around money, time and content.
That preparation gives the designer something to assess. “I need a five-page website” leaves a great deal open. “I run a local accountancy practice, want more enquiries from established small businesses, and need to explain three services clearly” begins to describe a project.
I would rather receive a short, candid enquiry with a few unknowns than an elaborate specification built around guesses. The aim is to make the first conversation useful. Detailed planning can be part of the work you commission.
Start with the reason you are looking now
A new business needs somewhere credible to send people. An established business may have changed direction while its website still describes the old offer. Another owner may be tired of chasing someone to update a phone number. These situations call for different work, even if the eventual sites have similar page counts.
Write a few sentences about the trigger. Describe what feels wrong, what has changed, and what you would like to be easier. “The site looks dated” is a reasonable first observation; explaining that it now attracts enquiries for services you stopped offering gives the designer a more useful problem to examine.
What would you like a suitable visitor to understand or do differently after visiting the new site? You might want them to recognise that you work with their type of business, understand your approach, or request a consultation with enough information for you to respond properly. Choose a main outcome rather than expecting the first version to solve every business difficulty.
If you already have a website, include its address. You can describe the symptoms without deciding that a rebuild is required. My approach to diagnosing an existing website before recommending a rebuild explains why that decision benefits from a closer look.
Describe the people you want to hear from
“Everyone” gives a designer very little direction. A garden designer working on substantial rural projects needs to answer different questions from a gardener offering regular maintenance in a small local area. Both work outdoors; their customers are making different decisions.
Describe your likely customers in everyday terms: the services they need, the area you cover, what prompts them to look for help, and what they tend to ask before committing. Include the work you would like more of and, where relevant, the enquiries that are usually a poor fit.
You do not need to invent a detailed imaginary customer with a name and favourite breakfast. Real observations are more useful. Questions from recent phone calls, recurring misunderstandings and the reasons people hesitate can all help shape the content.
Mention known access needs too, such as customers who enlarge text or struggle with complicated forms. The W3C Web Accessibility Initiative recommends involving people with disabilities early in web projects. That can inform the planning and testing budget; accessibility should not first appear as an extra request just before launch.
Explain the customer task before choosing a feature
A feature name can conceal a surprisingly large amount of work. “Online booking” might mean sending an appointment request, choosing an available slot, paying a deposit, or reserving a place in a class with limited capacity. Each version has different rules and different consequences when something goes wrong.
Describe what should happen in ordinary language. A consultant might want visitors to choose a time, answer two preparation questions and receive a meeting link. A class organiser might need different prices, waiting lists and cancellation rules. A shop might need local collection alongside delivery, with different availability for particular products.
Name any service you already use and want to keep. Connecting to an existing booking system may be sensible, although the designer still needs to assess its options and limitations. You do not need to choose the plugin or tell the designer how to build it.
Separate what is needed for launch from what might be useful later. If the first priority is a clear service offer and reliable enquiries, a members’ area can remain a future possibility. This gives the designer room to propose a manageable first phase. My guide to a useful service-business website user journey develops the connection between visitor questions and the next action.
Take stock of content without writing the whole website
Gather what exists and be honest about its condition. You may have a logo, old brochures, service descriptions, staff photographs and a handful of testimonials. Some may be ready to use; others may need rewriting, replacement or permission before publication.
A simple folder with clearly named files is enough at this stage. Tell the designer which material is approved, which is outdated, and which has yet to be created. For photographs, keep the original files where possible. An image copied out of a social post may give fewer options for cropping and placement.
The useful decision is who will do the remaining work. If you want help structuring services, interviewing you for copy, selecting images or arranging photography, say so. Those are legitimate parts of a project to discuss. Quietly assuming that all the words will appear during the build makes a price and schedule harder to trust.
For a shop, give an approximate product count and explain how product information is stored. Ten products with tidy descriptions and images present a different task from a catalogue assembled across several spreadsheets. For a service business, identify any descriptions that require professional approval before they can go public.
Bring examples with an explanation of what appeals
Two or three references can help communicate a preference that is difficult to describe. The explanation alongside each link matters more than the number of sites collected.
You might like the calm spacing, the confidence of a large heading, the way a service is explained, or the ease of finding a contact option. You might dislike animation that interrupts reading. These observations give a designer something to interpret without turning the reference into a copying instruction.
A striking hospitality website may provide a useful visual cue for an accountant, while its navigation and photography would be unsuitable. The designer’s job includes working out which qualities belong in your site and how they fit your audience, content and identity.
If you have brand guidelines or an established logo, include them. If you have neither, explain whether you want the website project to establish a visual direction or work with a separate branding project. That affects what can sensibly be priced.
Give a budget range and explain what it must cover
A budget helps a designer propose work you could realistically commission. It also allows an early conversation about priorities if the available money and requested scope are some distance apart.
You can share a comfortable range, a firm ceiling, or say that you need help understanding likely costs. If you have a ceiling, clarify whether it includes photography, copywriting, ongoing hosting, software subscriptions and any applicable VAT. A figure intended for the build alone can buy different work from the same figure intended to cover the whole first year.
A budget is not permission to spend every euro. Ask the designer to explain the proposed scope and the costs that sit outside it. A smaller first phase may be appropriate; sometimes postponing the project is more sensible than squeezing the necessary work into an unsuitable allowance.
Avoid choosing a price based solely on another business’s page count. Your content, functions, existing systems and support needs shape the work. Once proposals arrive, the separate guide to what a professional website quotation should include will help you compare what is being offered.
Explain the deadline and who can make decisions
A launch date is easier to assess when the designer knows what sits behind it. A fixed event, a lease opening or a contractual commitment creates a different constraint from a general hope to finish before Christmas.
Include your own availability. If you will be away for three weeks, or a business partner must approve the wording, that belongs in the conversation. Time is needed for content, feedback and decisions as well as design and development.
Name the person who will gather comments and approve the work. Several people can contribute useful knowledge, although sending the designer separate and contradictory instructions makes progress harder. Agreeing who resolves those differences is a practical preparation step.
You can also describe a minimum launch version. A business may need its services, contact details and enquiry route ready for an opening date, while a resource library follows later. The designer can assess that option and explain the extra coordination it may require.
Identify existing accounts and anything that must keep working
For a replacement website, note who manages the domain name, hosting, business email and any booking or payment accounts. At enquiry stage, account names and an honest description of the access position are usually enough. Arrange the appropriate access securely when there is an agreed reason to investigate.
Flag uncertainty early. “My previous designer registered the domain and I do not know which account holds it” is useful information. A launch plan that assumes immediate access may otherwise prove unrealistic. Business email also deserves explicit attention when website hosting changes.
Identify valuable material on the old site: articles people find through search, pages linked from directories, or downloads customers still use. Where page addresses will change, Google’s migration guidance recommends mapping old URLs to their new destinations and planning redirects. A redirect sends a visitor using an old address to the appropriate replacement. Knowing about this work helps the designer allow for it.
Describe personal-data requirements without sending a customer database as an example. The Irish Data Protection Commission explains the principle of collecting and processing only the personal data needed for the purpose. For initial scoping, a blank form or a made-up sample can often explain the task. Specialist privacy requirements may need separate advice.
A short first enquiry is enough to begin
You can put the useful parts into one email or a short document. There is no need to complete every detail before getting in touch. This is a workable outline:
- What the business does, who it serves and the current website address, if there is one.
- Why you are considering the project and the main improvement you want.
- The customer tasks the website must support, plus any systems you need to keep.
- What content and brand material you have, and where you would like help.
- Your likely budget, target timing and who will approve decisions.
- Anything uncertain, including account access, content readiness or the best platform.
Which decisions would you like the designer to help you make? State those alongside the things you already know. Choosing the page structure, deciding whether bookings are worthwhile and turning a vague visual preference into a coherent design can all belong within professional planning.
For a WordPress project, I can help turn that starting information into a proposed structure, design direction and build scope, then discuss how the site will be looked after. If you are considering hiring me to design or improve your business website, book a conversation and bring the brief you have. A few clear notes give us somewhere useful to start.
Sources and further reading
- W3C WAI: Involving Users in Web Projects
- Google Search Central: Site Moves and Migrations
- Data Protection Commission: Principles of Data Protection
Important note
This article provides general information and professional commentary. It is not advice tailored to your particular business, website or circumstances, and it should not be treated as legal, financial, privacy, accessibility, cybersecurity or other specialist advice. Any opinions are my own professional judgement based on the information available when the article was researched.
Products, prices, services, software and official guidance can change. External links are provided for reference; I do not control third-party websites and cannot guarantee their continuing availability, accuracy or content. A link does not imply endorsement of everything published by that source.
Check current official information before making an important decision. Test technical changes safely, keep a verified backup, and obtain appropriately qualified advice where the consequences warrant it. Any sponsorship, free product, affiliate link or other commercial relationship relevant to the article will be clearly disclosed.
