You've decided to build a website — now it's time to talk to a developer. To make that conversation efficient and get an accurate quote, it's worth preparing in advance. Here's what you should know and what to have ready.
Things to think about beforehand
The purpose of the site
Before asking about price, answer this question: why do you actually need this website?
- So clients can find you on Google?
- To showcase your portfolio or past work?
- To accept bookings or reservations online?
- To sell products?
The goal determines the features needed — and those determine the price and timeline.
Your target audience
Who will be visiting your site? Older people looking for a local specialist, or young professionals comparing offers online? This matters for the visual design and user experience.
Budget
You don't need to give an exact figure, but it helps to have a range in mind. Are you thinking £500 or £5,000? This allows the developer to propose the right solution instead of wasting time quoting a project outside your reach.
What to prepare before the meeting
Examples of websites you like
This is one of the most valuable things you can bring to the conversation. You don't need to describe in words what appeals to you — just collect 3–5 links to sites whose design, layout, or feel you find attractive.
Information about your business
- Full business name and industry
- Location (if relevant)
- What sets you apart from competitors
- What services or products you offer
Logo and visual identity
Do you have a logo? Prepare a PNG or SVG file. Do you have brand colours or fonts? Those will be useful too.
No logo? That's fine — we can discuss it and potentially include logo design in the scope of work.
Website content
This is often the biggest blocker on projects. Think about whether:
- You'll write the texts yourself, or do you need a copywriter?
- You have professional photos, or will we use stock images?
- You want a blog — and who will maintain it?
Questions worth asking the developer
A good developer should answer these without hesitation:
- What technologies do you use and why?
- Do you also handle hosting and domain setup?
- What happens after launch — do you offer technical support?
- How many rounds of revisions are included in the price?
- How do you communicate during the project?
What to expect after the first conversation
After the first conversation you should receive:
- An initial quote or price range
- An estimated timeline
- Information on what's needed to get started
If the developer can't answer any of these questions — that's a warning sign.
Good collaboration starts with good communication. The better prepared you are for that first conversation, the smoother the entire project will go.