Web design for architects.
An architecture website has one job: make the person who just found you want to see the buildings. Most firm sites bury them behind a slider, a mission statement and a menu. I build sites where the work comes first, the photography runs full-bleed, and every project reads as a case study a client can follow.
What an architecture website has to do
A developer, a private client or a planning officer arrives on your homepage with one question: can this firm do the building I have in mind? The answer is your projects, so the projects lead. The homepage opens on one finished building at full width, the next three follow, and the practice statement comes after the proof, not before it.
Project pages carry the story a pitch would: the brief, the constraint, the site, the answer, the numbers, the photographs in the order you would show them in person. Drawings sit next to photographs where they explain something. Every page loads in under two seconds on a phone, because that is where half of your visitors are.
How I build it
I am a design engineer, not an agency. I design the site and I write the code, in Next.js, with no theme underneath. Typography is chosen for your practice, not picked from a template; the grid follows your drawings; motion is used where it explains space, and nowhere else.
- Photography first. Your images at the resolution they were shot, served as modern formats so they stay fast.
- Project pages as case studies. Brief, site, answer, credits, press, downloads, in a consistent structure that also ranks for the project and location names.
- An AI assistant, if it fits. A concierge that answers what you do, where you work and what a first meeting looks like, and books it. Trained on your site, never inventing.
- Search built in. Structured data for the practice and every project, clean URLs, sitemaps, and page titles a human would write.
- Live in weeks. Foundation sites in three to four weeks; larger estates in six to eight.
What it costs
A flagship site for an architecture practice starts at the Foundation tier and grows with the number of projects and the depth of each case study. Pricing is fixed before we start; there are no hourly surprises. The investment section on the homepage lays out the two paths.
Questions people ask
- How long does an architecture website take?
- A Foundation site with a homepage, an about page and up to eight project case studies is live in three to four weeks from the day the photography is in. Larger sites with twenty or more projects take six to eight weeks.
- Do you use WordPress or Squarespace?
- No. Every site is written in Next.js by hand, with no theme underneath. You get a site that is yours, loads fast, and does not look like the practice down the street.
- Can we update projects ourselves?
- Yes. Projects live in a simple content layer you can edit, and I stay on for updates when you would rather not touch it.
- Do you work with practices outside the Netherlands?
- Yes. I am based in Amsterdam and work with architects across Europe, the UK, the US and the Gulf; everything happens over video and a shared project board.
- What about SEO for architects?
- Every project page is built to rank for the project name, the building type and the location. The practice gets structured data, a sitemap, fast pages and titles written for search, without a single line of marketing copy on the site.
From the journal
- What makes an architecture website win awards
Architecture websites win awards on a scored rubric: Awwwards weights design 40, usability 30, creativity 20 and content 10. Build for the rubric, not taste.
Start with a conversation
Thirty minutes, no deck. Bring the site you have and the projects you are proud of; you leave with a clear view of what a flagship site would do for you and what it would cost.
Book a consultation →