Getting a website built in Rotterdam: questions to ask

You're about to hire someone to build your website in Rotterdam. There are many options: freelancers, small studios, and agencies. Each comes with different trade-offs. Choosing wisely saves time and cost later.

This article gives you a practical checklist and the right questions to ask in the initial meeting. You'll get examples, indicative budgets, and technical points to verify.

Core questions to ask at the first meeting

1. Who will actually do the work, and who is my point of contact?
   • Ask which team members will be involved. If a senior-led agency runs the project, you usually get stronger architecture and clearer maintenance plans.
2. Can you show relevant examples and explain the tech choices?
   • Ask specifically what CMS or stack they used and why. Review their portfolio for similar projects.
3. What is the process and delivery schedule?
   • A typical phased timeline: Discovery (1–2 weeks), Design (2–4 weeks), Development (4–8 weeks), Testing & Launch (1–2 weeks). Total 2–4 months depending on scope.
4. Which technology or CMS will you use and why?
   • WordPress, headless CMS, or custom solution. WordPress projects for SMEs often land between €3.000–€12.000; custom apps are pricier (€8.000–€40.000). These are indicative ranges.
5. How do you test for mobile and performance?
   • Mobile-first is standard now — Google indexes mobile versions first; read more at mobile-first indexing.
   • Ask which Core Web Vitals they measure and how they improve them. The Core Web Vitals guide explains what to monitor and typical fixes: https://web.dev/articles/vitals.
6. How do you handle accessibility?
   • Ask whether they test against WCAG criteria and can show concrete fixes for issues like contrast and keyboard navigation. See the WCAG 2.2 reference: https://www.w3.org/TR/WCAG22/.
7. What happens with SEO during and after launch?
   • Ask about redirects, sitemap, Search Console setup, and how quickly content becomes indexable.
8. How do you manage security and backups?
   • Ask about OWASP-aware development, patch schedules, and backup frequency. For WordPress projects, ask about hardening and automated backups.
9. What does maintenance and support look like?
   • Define who fixes bugs, what is included in warranty, and the price for extra work. Maintenance SLAs often cost €50–€250/month depending on scope.
10. How are intellectual property and deliverables handled?
    • Confirm transfer of code, design files, and login credentials after final payment.

Technical checklist to verify

• Hosting type: shared, VPS, or managed hosting.
• Backup and restore procedures.
• Update policy for platform and plugins.
• Monitoring: uptime and error logging.
• Performance targets: aim for LCP under ~2.5s, CLS under ~0.1, and low interaction latency. See the Core Web Vitals guidance: https://web.dev/articles/vitals.

Quick comparison table

(Prices indicative; they vary per project.)

What to put in the contract

• Clear acceptance criteria: functional and technical.
• Acceptance testing process and timelines.
• Payment schedule tied to milestones.
• Support hours per month and SLA response times.

Practical tips for the pitch meeting

• Ask for a clickable prototype. It reduces misinterpretation.
• Request that technical terms are explained plain language with examples.
• Meet the actual developers in a follow-up meeting.
• Retain final payment until acceptance criteria are met.

Final checklist before you sign

• Objectives and KPIs documented.
• Tech stack and hosting specified.
• Performance obligations (Core Web Vitals) included.
• Accessibility level (WCAG reference) agreed.
• Backup and update schedules defined.
• Support and SLAs documented.
• Transfer of code and credentials guaranteed.

Closing note

A focused conversation up front prevents rework later. If you want help drafting an RFP or a technical review of offers, reach out through our contact page or view examples in our portfolio. For a tailored quote about a website laten maken in Rotterdam, request an estimate via our quote page.

Practical reminder: verify how a supplier measures and improves mobile performance and Core Web Vitals — that is often the deciding factor for user experience and search visibility.