Choose a provider who can translate the business goal into a specific scope, explain acceptance testing and clearly describe access and maintenance. Ask candidates to respond to the same brief. Compare not only prices but also exclusions, dependencies and the terms for ending the engagement.
1. First establish which problem the website should solve
Do not begin by asking how many pages you need. Explain who should visit, which service they want and what they should do after reading the offer. For a service business, this might be an enquiry specifying location, work scope and a preferred date. This is a more useful starting point than “a modern website”.
Ask: “What information do you need from me before proposing a solution?” The answer should cover customers, the offer, materials, the existing website and constraints. If the provider immediately chooses a technology but does not ask how customers are acquired, it is hard to assess the proposal’s fit. Preparing a shared website brief will make comparing proposals easier later.
2. What exactly does the quote include and exclude?
Ask for a list of deliverables: page structure, screen designs, development, content, forms, integrations and launch. Distinguish writing copy from inserting supplied material. Do the same for photography, translations, licence purchases and content migration. “A website with SEO” does not say whether this means metadata, URL migration, content work or ongoing post-launch activity.
Ask what triggers an additional quote and how scope changes are approved. Agree the number of feedback rounds and how comments are collected. My recommendation: record mandatory requirements separately from ideas for later. This avoids rejecting a suitable provider just because their proposal honestly identifies items others have omitted.
3. Does the portfolio show more than appearance?
Look at working websites, not only project thumbnails. On a phone, navigate from the homepage to a service description and contact options. Check readability, navigation and form behaviour. Ask which part the candidate delivered: strategy, copy, design, development or configuration alone. Teamwork is normal; unclear responsibility makes competence harder to assess.
If increased enquiries are claimed, ask for the comparison period, measurement method and campaign context. Without those details, do not treat the result as proof that redesign alone improved sales. No public case study does not disqualify a provider, but should not be replaced with unverified percentages or assurances that you will achieve the same result.
4. What will the stages and acceptance process look like?
A schedule should identify not only the launch date but dependencies: company materials, structure approval, design and testing. Assign one decision-maker on your side. Ask what happens to the deadline if photos or feedback arrive late. This is about organising work, not finding someone to blame in advance.
Instead of a generic “the website will be responsive”, agree acceptance scenarios. Can a customer follow the whole journey on a narrow screen? Do all fields have understandable labels? W3C states that a label should describe a field’s purpose and be correctly associated with it. An elegant form alone does not confirm accessibility.
| Area | Question before the contract | Evidence at acceptance |
|---|---|---|
| Contact | How will we test form submission and errors? | A test enquiry reaches the agreed inbox. |
| Mobile | At which widths will you test the customer journey? | Navigation, the offer and buttons work without overlapping elements. |
| Editing | What will I be able to change myself? | The owner changes an agreed text in staging. |
| Migration | What happens to the old URLs? | A URL map and tests of the appropriate redirects. |
| Handover | Which accounts and files will I receive? | An access list, instructions and an agreed website copy. |
These are suggested purchasing criteria, not a universal quality certificate. Adapt the list to the scope: a small information website and a store with payments require different tests.
5. Who controls the domain, hosting and accounts?
Ask in whose name services will be registered and who has administrative access. Separate account ownership from day-to-day management: a provider can manage hosting while the business still knows how to regain control and move the site. Do not share passwords in one common document. Agree a secure handover and removal of unnecessary permissions when work ends.
WordPress roles have different capabilities. According to its documentation, a single-site administrator has access to administrative functions, while an editor manages content without full administration. A copy-editing account therefore does not necessarily mean full website control. For a subscription platform, also ask about export, platform restrictions and what stops working after cancellation.
6. What costs and responsibilities remain after launch?
Ask to separate implementation costs from maintenance. List services actually required by the proposed solution: domain, hosting, paid extensions, external tools and technical support. Not every website needs all these items. Ask who pays for renewals and whether licences remain available after the engagement ends.
Establish the difference between fixing a fault and commissioning a new feature. Ask about incident reporting, backup scope, restore testing and responsibility for updates. “Support included” is of little use without scope and duration. Do not compare subscriptions until you know whether they cover the same activities and support availability.
7. What does the provider promise in SEO and analytics?
For an existing website rebuild, ask about URL inventory, preserving important content and redirects. Google recommends preparing URL mapping and monitoring after migration, and notes possible temporary ranking fluctuations. “No risk of losing traffic” is stronger than can honestly be guaranteed. Require actions and tests, not a guaranteed Google ranking.
For analytics, agree what will be measured and where you can see results. A phone-link click, a submitted form and a qualified enquiry are different events. Installing a tool alone does not confirm correct measurement. Also clarify consent handling and responsibility for privacy information; this guide does not replace legal analysis of a particular implementation.
8. How do you choose between similar proposals?
Make one spreadsheet covering mandatory scope, exclusions, materials you supply, acceptance tests, access and maintenance costs. Mark every field “confirmed”, “needs clarification” or “out of scope”. Do not award points for claims you cannot verify. Where an important detail is unknown, ask before choosing instead of assuming a favourable interpretation.
My recommendation: treat a lack of agreed scope, handover rules or acceptance methods as a reason to pause the decision. A freelancer, small studio or agency can all deliver well; team size alone does not replace accountability. Choose a proposal whose results and terms you understand, not one making the most promises in the least specific language.
Sources and limits of the conclusions
The technical guidance is based on documentation: W3C WAI — form labels, WordPress — roles and capabilities and Google Search Central — site moves. The purchasing questions and acceptance table are editorial recommendations. They do not present a particular client’s result or guarantee sales.
Comparing proposals for a new website?
Describe the goal, required features and available materials in the brief. This starts a discussion about a specific scope; it does not commit you to an order.
Open the website brief (in Polish) ↗