Many businesses in Amsterdam talk to two audiences at once: Dutch customers who expect Dutch, and international customers, partners or recruits who read English. A website that serves both well is a different brief from a single-language brochure site, and it changes what you should ask a web development company before you hire one.
This guide is for Amsterdam businesses comparing studios, and it also covers a question that often comes up: can a studio that is not in Amsterdam do the job?
Start by deciding how the two languages should work
"Bilingual" can mean very different things in a quote. Settle these before asking for prices:
- Same content in both languages, or different? A translated mirror of every page is one project. Separate Dutch and English pages with different offers is another.
- Who writes and reviews the translations? A studio can build the structure, but the Dutch text should be checked by a native speaker, and so should the English if the audience is international.
- How does a visitor switch language? A visible switch, remembered between visits, is better than guessing from the browser alone.
- Can each language be found in search? Each language version should have its own address, and the pages should point to each other with
hreflangtags so search engines show the right one to the right person.
Ask each candidate to explain, in plain words, how they would handle all four.
Questions that matter more for an international site
- How do you build and test the language versions? You want one structure that makes the Dutch and English pages stay in step when something is added, not two sites that drift apart.
- How fast will it be? Visitors reach the site from phones, offices and other countries. Ask what performance checks the studio runs, on mobile as well as desktop, and how images and fonts are handled.
- How is privacy handled? If the site collects enquiries or uses analytics, ask how cookies, consent and personal data are dealt with under the GDPR (AVG in Dutch). A good studio can explain what is stored, where and why, and can build consent that really defers analytics until a visitor agrees.
- Is it accessible? Ask about keyboard use, contrast, readable forms and screen readers. Accessibility rules apply to more online services in the EU than before, so check whether they apply to you and ask the studio how it tests.
- Who owns the code, domain and hosting at handover? You should, in writing.
- Who keeps it patched after launch? Hosting software needs updates too. Our guide to who patches PHP on shared hosting, a VPS or managed hosting shows how easily this is left to nobody.
Compare what each quote actually includes
Put the quotes side by side and check the same lines in each:
| Compare | What to look for |
|---|---|
| Languages | How many, who translates, and how new pages are added in both |
| Scope | Pages, templates and features named one by one |
| Exclusions | A written "not included" list |
| Content | Who writes, translates and migrates it |
| Privacy and consent | What is stored, and how consent is handled |
| Hosting and licences | Who pays, and in whose name accounts are held |
| After launch | Support window, maintenance and response times |
If you have not written a brief yet, how to write a brief for a website or app project is a good starting point, and sending the same brief to every candidate makes their answers comparable.
Does the studio have to be in Amsterdam?
For most websites, no. Discovery calls, design reviews and handover work well over video and shared documents, and a written scope matters more than a shared office. What is worth checking is practical:
- Working hours. India is 4.5 hours ahead of the Netherlands in winter and 3.5 hours ahead in summer. That leaves a daily window for calls and quick answers, and it can mean overnight progress between your evening and the studio's morning.
- Who invoices you, in which currency, and under which terms. Ask your accountant how VAT applies to invoices from a studio outside the EU.
- Who you speak to. A named contact and a written way to raise problems.
If you would like an in-person kickoff, say so up front and ask whether that is possible. Otherwise, judge the studio on written evidence, not on its postcode.
How SA Web Studio fits
SA Web Studio is based in Delhi, India, and works with businesses worldwide, remotely. We build websites and WordPress sites, custom web and mobile applications and API integrations, and we offer maintenance and development support to agencies and in-house teams. This site itself is built in English and Dutch, with separate addresses for each language and hreflang links between them. Our project examples are fictional concepts, not client work.
If you are weighing studios for an Amsterdam business, send us your brief and ask the questions above. The discovery questions, scope and exclusions list we send back will tell you more than a sales call. You can also read how we think about the choice between WordPress and a custom build, or see our services.
Looking at a different city? We have written guides for Rotterdam and Utrecht too.
