How we build a website for an Amsterdam business
Someone from Düsseldorf who found your shop on a weekend in Amsterdam looks you up once home. What they find is a site made for the street: the opening hours, the tram stop, a few photographs. It says how to come back, not how to buy. They cannot see whether you send to Germany, what delivery costs or how to pay, so they close the page. A reader in Rotterdam, in Belgium or in America leaves the same way. What keeps a shop in the Negen Straatjes or a maker in Noord out of those places is seldom the goods. The site ends at the ring road.
The reason is your day. You are behind the counter, in the kitchen or at the bench, and the site gets whatever time is left. An Amsterdam business already writes for three readers: the neighbour who reads Dutch, the resident from abroad who reads English, and the visitor with a phone who wants your hours and the way there by bike or tram. A restaurant on the Javastraat and a stall at the Ten Katemarkt have that much to keep current before anyone abroad asks.
We build in Dutch and English from the start, as two sets of pages, not one put through a machine. We write both, the Dutch for an Amsterdam reader and the English for one abroad. We check every page ourselves and send it to you before it goes live; how closely you read it is up to you. We design the site, write it and build the search foundations under it. The goods, the food or the work are shown as they really look, and ordering, booking or asking is one step. Germany gets pages of its own once you are ready to send there, with what delivery costs in euros and how to pay. The Düsseldorf order reaches you complete, and the customer gets a first reply confirming it. A question about a price, or anything the software is unsure of, waits for you. German follows the same rule as Dutch and English: we plan the page, write it and build it, and it comes to you first, before going live.



