Website development services are offered by freelancers and agencies alike, and their proposals often look similar even when price and results differ a lot. Looking at a portfolio or a price alone isn't enough. The answers to a few simple questions tell you much more. Below are ten you should ask every developer, including us.
If you don't yet know what to budget, start with our honest pricing guide. Here we focus on how to choose who builds it.
1. Does the developer start by asking about your business?
A good developer asks what you sell, to whom and what you expect from the site (calls, enquiries or orders) before talking about design or price. If you receive a proposal and can’t see how it connects to your goals, that is a sign the site may be built from a template. Pay attention to what the developer asks you, not only to what they promise.
2. Will I get a detailed quote?
A single figure without explanation ("website: €1,500") makes proposals impossible to compare. A good quote breaks the work down: design, development, content upload, SEO setup, training, additional languages or integrations. That way you see what you are paying for and what you could drop or postpone.
3. How will payment work?
A partial advance is common practice, because the developer starts working and reserves time for your project. But payment should be tied to clear stages you can verify: a design mockup, a working site on a test environment, the launch. Be cautious if you are asked to pay the full amount upfront with no interim results.
4. What is included in the price, and what is not?
The most common "surprise" extras: hosting and domain, paid plugin or theme licences, copywriting, photos, translations, extra languages, and integrations with payment or other tools. Ask directly, "What could make this project more expensive?" and ask for the answer in writing.
5. How long will it take and what does it depend on?
Delays often come not from the developer but from the client not providing texts, photos or testimonials on time. Ask for a clear plan: what you need to prepare and by when, and what the developer does. Then both sides know what drives the launch date.
6. Will I be able to edit the content myself?
Most businesses want to change a price, a photo or a paragraph without waiting for the developer. Find out which content management system is used, whether training is included and whether you will get a short guide. If every small change needs a call and an extra fee, you will feel it quickly.
7. What happens after launch?
A website isn't something you finish once. It needs backups, security updates and someone to call when something breaks. Ask whether post-launch support is included, how long it is free, what it costs afterwards and how quickly problems are answered.
8. Will the site be fast and search-ready?
The basics should be standard, not an add-on: mobile-friendly layout, an SSL certificate, proper headings, meta descriptions and image alt texts, and speed that meets Google's Core Web Vitals. For more on why this matters, read SEO Optimization: Why It's Essential for Your Business. It is also worth asking about the chosen technology, since it affects management and growth: we covered this in WordPress vs. Custom Development.
9. Can I see similar projects?
Don't settle for screenshots. Open real, live websites and see how they look on a phone, how fast they load and whether everything works. Even better, ask for one or two contacts you could talk to about the cooperation. You can find our work in the Portfolio section.
10. Who owns the design and the code, and what happens if we part ways?
This question is the one most often forgotten, yet it is best asked up front. The contract should make clear who owns the design, texts and code, and how you will receive all the material if you ever want to move to another developer or change hosting. Clear terms only pay off when you need them, but then they matter most.
What a reliable proposal looks like
- The quote is broken down by work, not a single sum.
- The proposal is built around your goals, not a template.
- Payment follows stages with verifiable results.
- It is clear what you need to prepare yourself.
- Post-launch support and backups are included.
- The developer answers questions specifically, not with generic phrases.
Warning signs
- The full amount is demanded upfront with no interim results.
- It is unclear who controls the domain, hosting and access credentials, and whether you can take them over.
- There is no real project you can open and look at.
- The price is unusually low or unusually high and nothing explains it.
- Specific questions are avoided or answered vaguely.
Checklist before you sign
- The developer asked what I actually need.
- I received a detailed quote.
- Payment is tied to stages.
- I know what is not included in the price.
- The timeline and my responsibilities are clear.
- I can edit content myself and training is included.
- It is clear what happens after launch.
- The site will be fast and search-ready.
- I opened real project examples.
- It is clear who owns the design and the code.
Frequently asked questions
Do I need a contract for a website?
You need a clear written agreement: a contract, or at least a confirmed proposal that states scope, price, stages, deadlines and rights. It protects both sides and prevents disputes about what was promised.
Is it worth choosing the cheapest offer?
Price matters, but compare it only when proposals include the same things. A cheaper offer often leaves out what another already includes (SEO, training, maintenance), so the final total may even out.
Is it better to choose a freelancer or an agency?
Both can be good. A freelancer usually offers direct contact and flexibility, while an agency can offer more specialists for large projects. What matters most is not the form but whether you get answers to the questions above.
How long does it take to build a website?
It depends on scope and on how quickly you prepare content. A simple one-page site can be ready in a few days, a business card site in a few weeks, and larger projects take longer. A developer should give you a realistic timeline once they understand your needs.
What should I prepare before contacting a developer?
A short description of your business, what the site is for, what action you want visitors to take (call, enquiry, order) and a few websites you like. Texts and photos can be prepared later together.
Want to see how this works in practice?
Describe your project and within 24 hours we will send a detailed quote with itemised work, timelines and stages. Write to us through the contact form or first look at our prices and portfolio.