← Journal

A website for architects: the portfolio that speaks before you do

An architect's website isn't just an online portfolio. It's itself proof of taste and judgment. What it needs, how it should look, and why the site's design says almost as much as the project photos.

Most of an architect's clients come by referral. But before they call, they do one thing first: they look at your work. So the question isn't whether you need a website. It's what they find when they go looking. And unlike most professions, what they find isn't just information. It's a sample of the architect's taste. A site that looks ordinary signals ordinary taste.

The short version before the detail:

  • The site is itself a portfolio piece — its design signals your taste before a single project photo loads.
  • Portfolio with story, not just photos — clients want to understand the problem you solved, not only see the result.
  • Quality over quantity — four strong projects persuade better than twelve mediocre ones.
  • The design can reflect your work — unlike a lawyer or an accountant, an architect's visual judgment is the product.

Does an architect need a website if clients come by referral?

Yes, and referrals are exactly the reason. When a client hears your name from someone they trust, the first thing they do is search for your work. The website is the portfolio they find. If it doesn't exist, or it's five years out of date with three projects and no story behind them, the referral loses its force on the spot.

The person already trusts whoever recommended you. The website only has to not disappoint that trust. A clear, current, well-presented portfolio does that and keeps working around the clock, long after the conversation where your name came up.

What does a client look for on an architect's website?

Photographs matter more here than in almost any other profession, but they're not the whole picture. In the first minute, a client is asking three things: do you build things like what I need, can your taste be trusted, and can I reach you?

All three get answered before a single word is read. The site's design signals the taste behind it. A cluttered, slow, template-built site makes the client wonder whether your spaces look the same way. An over-designed site that's hard to navigate makes the same point the other way around. The site should feel like the best room you've ever designed: ordered, uncluttered, nothing in the wrong place.

What does an architect's website need to include?

You don't need much. What's there needs to count. Start with the portfolio, which is the centre of gravity for everything else:

  • Portfolio with project stories. Four to five completed projects with good photographs and a short description for each. Not a caption. A story: what was the site, what was the problem, what did you do. Clients don't know how to evaluate a technical drawing; they know how to follow a narrative.
  • A clear area of work. Residential, commercial, interiors, renovations, urban planning. State what you do and at what scale. A specialist feels more trustworthy than a generalist, even when they do everything.
  • A brief, factual profile. Experience, chamber membership, education, the cities or regions you work in. Enough to establish authority without an autobiography.
  • Straightforward contact. A form and a phone number, with a clear indication of what the first meeting looks like.

Notice what's not on the list: a blog, a news section, a testimonials carousel, an animated logo. Unless you are actively writing, a blog that hasn't been updated since 2022 is worse than no blog at all.

Should you list your fees?

No. Architecture fees depend on too many variables (scope, complexity, planning requirements, site conditions) for a published price list to mean much. And a figure on the page shifts the conversation onto the number before you've even spoken to the client.

Better to describe briefly how you work: what a first consultation looks like, what the stages of a project are, what it means to work with you. That builds confidence and puts the price conversation where it belongs: in the room, after you understand what's actually being asked.

Should the site's design reflect your aesthetic?

Yes, and this is one place where architects differ from most professionals. An accountant's website being slightly bland is unfortunate; an architect's being generic is a credibility problem. The site's design is the first signal they read for taste.

That doesn't mean every architect's site should be a showpiece. It means the site should be consistent with your work. A studio that does calm, minimal residential spaces should have a calm, minimal site. A studio with bolder, more expressive public work can carry a bolder visual language. The coherence is what matters. An architect whose interiors are ordered and refined, working off a template built for restaurants, leaves the same impression as a doctor with a chaotic waiting room.

How important are the photographs?

Central. A good photo can carry a mediocre project; a bad one can undermine a strong one. If you don't have professional architectural photography, hire a photographer for at least two or three of your strongest completed works. The photography is part of the site's budget, not an afterthought.

Renders are fine for work under construction, as long as they're high quality. Phone snapshots: never, regardless of how good the project is. On a screen, the quality of the image is the quality of the work.

How much does a website for an architect cost?

More goes into the image side here than with most professionals, and it shows in the price. For a solo architect or small studio, expect to pay 800 to 1,800 €. For a larger studio with a substantial portfolio, that runs up to 2,500 €.

The build takes two to four weeks, depending mainly on how quickly the images and project descriptions come together. That's always what sets the pace. I help with the texts if needed, but the photographs need to exist first.

For a portfolio site, a custom build almost always outperforms a platform in page speed and image handling. I covered the speed specifics in clean code, WordPress or Wix.

What I build, and why

I build websites by hand here in Sofia. No templates, no off-the-shelf platforms. For architects that means a site that loads fast, presents images well, and reflects your aesthetic, not whatever platform everyone else is using.

If you'd like an honest opinion on what your portfolio site should say and show, get in touch. I reply within one business day. Tell me two or three lines about your practice and what kind of work you want to attract more of, and I'll come back with a clear recommendation.

Frequently asked questions

Does an architect need a website if clients come by referral?

The opposite, in fact: precisely because of the referrals. When a client hears your name from a friend, the next thing they do is search for photos of your work. The website is the first portfolio they see. If it doesn't exist, or it's out of date, or it shows three projects with no story behind them, the referral loses its weight on the spot.

What must an architect's website include?

Five elements are essential: a portfolio of at least four to five completed projects with good photographs and a short story for each; clear information about what you work on (residential, public, interior, renovations); a short profile with experience, chamber membership and education; straightforward contact; and a design that isn't weaker than your own taste. Everything else is optional.

How many projects should I show in the portfolio?

Quality over quantity. Four strong projects with good photos and a story persuade better than twelve mediocre ones. Show only completed work, or renders of projects under construction, as long as they are high quality. Each project should answer the question: what was the problem, and how did you solve it?

Should I list my fees on the site?

No. Architecture fees depend on too many variables (scope, complexity, location, documentation requirements) for a published price list to be meaningful. Better to describe how you work and what the first meeting covers. That puts the budget conversation where it belongs: at the consultation.

Can the site's design be bolder than, say, a lawyer's?

Not only can it. It should reflect your aesthetic. An architect's website is itself a design statement. If it looks generic and impersonal, the client will wonder whether your projects look the same way. Boldness in design should be grounded in the work itself.

How important are the project photographs?

Central. A bad photo can ruin a good project faster than a good one can defend it. If you don't have architectural photography, hire a photographer for at least two or three of your leading projects. Renders are acceptable for work under construction, as long as they are high quality. Phone snapshots: never.

WordPress or a custom site for an architecture studio?

For visually heavy portfolio sites, a custom site loads significantly faster and is easier to optimise for images. WordPress is a reasonable choice if you publish articles regularly and want to manage the content yourself. But if the primary goal is presenting projects, clean code gives a faster and more polished result.

How much does a website for an architect cost?

For a solo architect or small studio — 800 to 1,800 €. For a studio with more people and a larger portfolio — up to 2,500 €. The alternative is from 160 €/mo with no upfront payment. The main difference from other professionals: image handling and layout takes more work, and that affects the price.

How long does the site take to build?

Around two to four weeks. The most common delay isn't on my end. It's gathering photos and project descriptions. If you already have a set of photographs ready, the pace is considerably faster. I help with the texts if needed.

Have a project in mind?

I build websites from scratch for businesses that care about craft. Let's talk.

Start a project