Architecture Studio Portfolio Websites: Proof Beyond the Renders

A client cannot walk through a building before paying for it. We run an architecture studio of our own, and this is what we learned about the proof a studio's website can give beyond the gallery.

SHORT ANSWER

What Proves an Architecture Firm Can Build

An architecture firm's website wins trust when it shows proof a client can check: documented projects, the process behind them, real photographs of finished buildings, the team and, more and more often, a walk through the future space. Renders have become cheap to produce, and a client who is about to spend hundreds of thousands of dollars knows it.

Architecture sells something the client cannot experience until long after the contract is signed. The website is one of the few places where that uncertainty can be reduced before the first meeting, and most studio sites leave the chance unused. What clients study on a studio's site, page by page, we described in Website Design for Architecture Firms: What Clients Look For Before They Call. This article is about the harder part: what to show when the best work cannot be shown, and which kinds of proof work beyond a polished gallery.

FIVE MISTAKES

Five Mistakes Architecture Firm Websites Keep Making

• Projects without documentation. A gallery image with no brief, no constraints and no explanation of the decisions asks a visitor to take quality on faith. Firms that convert better show the reasoning behind a project, along with its final frame.
• No before and after. In visual industries this is one of the most persuasive formats, and architecture firms avoid it more than most, often for understandable reasons: architects prefer to present the finished result. The trade-off is real, polish against persuasion.
• Renders instead of photographs. Renders are controllable and flawless, while photographs are evidence. A site built only on renders, however good they are, reads as a promise rather than a track record.
• Vague services. Price levels that differ widely with no explanation of what each package includes undermine trust before the first conversation. Architecture is already a purchase full of uncertainty, and an unclear structure adds to it.
• The starchitect syndrome. Many sites are built around one named architect, as if the work were a solo act. No building, like no pyramid, was ever made by one person, and a site that hides the team hides the capability behind the work.

NDA

When Your Best Projects Are Under NDA

This is a problem we know from our own studio. DeZZign designs new private houses for clients who value privacy, and their contracts often forbid showing anything at all: no renders, no drawings, no photographs. Some of the studio's strongest recent work therefore never reaches the portfolio, and the site has to prove the level of the studio with the projects it is allowed to show.

There are ways to work with that, and each of them has to be checked against the contract first. With the client's consent, a project can appear as a short anonymous description: the type of building, the approximate area and region, the task and how it was solved, without a single image. A written review from the client, even an unnamed one, tells a prospect that serious people have already trusted the studio. The site can also say plainly that part of the work is private and can be discussed at a meeting, and for a client who wants the same discretion that alone is a reason to call.

A private portfolio is still proof, if the site explains why it is private.

What does not work is pretending the gap is not there. A studio with many years of practice and four projects online looks like a young studio, unless the site tells the client why so little is shown.

PROCESS

Show the Process, Even When It Is Not Pretty

For a while DeZZign posted its process on Instagram: site visits, drafts, materials, stages of the work. Then we stopped, because the chief architect was against it. A building site is rarely beautiful, a half-built house says little about the final result, and an architect has every right to want the work judged by what it becomes. Looking back, we think stopping was a mistake.

A client comparing studios cannot watch how a team works, and the process is the closest thing to watching it. It does not have to mean the raw building site. Sketches and working models, material samples on the table, a detail solved on paper before it was solved on site, a short note on why a wall moved half a meter: a client can read this kind of process, and an architect can be proud of it. Before and after belongs here as well. For a reconstruction such as Copper Hall, an abandoned 1990s building turned into an office and completed in 2022, the stages between the old building and the new one are the most convincing part of the story, and we did not show them.

The rule we would follow now is easy to state: choose the stages that explain a decision, photograph them with the same care as the finished building, and leave out the chaos that explains nothing.

PHOTOS

Renders Promise, Photographs Prove

Renders are still necessary. They show what does not exist yet, and for new projects they are often the only image there is. The trouble starts when a portfolio contains nothing else, because almost anyone can produce a convincing render now, and clients know that. A professional photograph of a finished building, with real light, real materials and people using the space, is the one image that cannot be faked.

For the site this means a few practical things. Projects with photographs should be marked and placed first in their category. A project that exists only as renders should say so and say what stage it has reached. When a building is finished, a proper photo shoot is worth paying for even years later, because those photographs will keep working on the site for as long as the studio exists.

3D TOURS

3D Tours in Unreal Engine

Lately clients have started to ask DeZZign for walkthroughs built in Unreal Engine, and on new private houses the studio makes them. A real-time tour lets the client stand in the living room at a chosen time of day, look out of the window at the view they are paying for and change a material before it is ordered. For a decision of this size it removes more uncertainty than any set of still images.

On those houses the tours stay private for the same contractual reason, but the format itself deserves a place on the site. A studio can record a short walkthrough of a concept or a permitted project, publish it as a video and explain on the service page that a full interactive tour is part of the work. The interactive tour is usually delivered as an application or streamed to the browser through Epic's Pixel Streaming, which is far too heavy for an ordinary page, so the website's task is to show that the studio can do it and to make asking for it easy.

TEAM

The Studio, Not the Starchitect

DeZZign presents itself as a studio rather than as one architect with a name on the door. We chose this on purpose, and it fits how the work is done: architects, interior designers, visualizers and engineers each carry part of a project, and a client hires all of them together.

A site can show this without turning into a staff directory. Project pages can credit who led the architecture and who led the interior, the studio page can show the people and their roles, and the process stories can carry the names of those who solved a particular problem. For a client this answers a question they rarely ask aloud: who will actually work on my house, and what happens when the lead architect is busy.

SERVICES

Services a Client Can Understand

Architecture fees are hard to publish, and exact numbers usually need a meeting. What a site can always do is explain what each service includes: the concept, the full set of drawings, interior design, author's supervision, help with permits. Once a client sees what the work consists of, a price range stops looking arbitrary. How fees are formed and whether to show a range on the site, we discussed in the article on what clients look for before they call.

PERFORMANCE

Heavy Visuals Without a Slow Site

Architecture websites carry heavier visual content than almost any other kind of site: large renders, photographs, video, walkthroughs. All of it has to load fast, on a phone as well, otherwise the strongest material becomes the reason people leave. Pictures should be prepared in the sizes the page actually needs, video should start only when the visitor asks for it, and a long project page should load its images as the reader reaches them.

FROM OUR STUDIO

What We Changed at DeZZign

We did not write this from the outside. We run an architecture and design studio ourselves, dezzign.com.ua, and we made several of these mistakes before correcting them: projects without stories, a process we stopped showing, strong work hidden behind contracts with nothing on the site to explain the gap. How we rebuilt the studio's website is described in the DeZZign case.

FAQ

Sources

• DeZZign, architecture and interior design studio
• Epic Games: Pixel Streaming in Unreal Engine