Most architecture studios don't have a website problem. They have a translation problem.
The work is good. The projects are considered, well-detailed, sometimes award-shortlisted. And yet the website built to represent that work often does none of it justice. It reads like a folder of finished photography with some project names attached, rather than a case for why a prospective client should pick up the phone.
This isn't a design failure in the usual sense. The photography is often excellent. The layout is often clean. What's missing is the thinking that sits underneath a portfolio and turns it into a website: positioning, sequencing, and a clear idea of what a stranger needs to understand in the first thirty seconds.
A portfolio is a record. A website is an argument.
A portfolio exists to document what a studio has made. It's project-first, chronological or thematic, and assumes the viewer already understands what they're looking at and why it matters. That assumption works well in an awards submission, a printed folio for a design review, or a slide deck presented in person, where someone is there to provide context.
A website has no one in the room to provide that context. It has to do the explaining itself, to a visitor who arrived from a Google search, an Instagram bio link, or a recommendation from a builder, and who is deciding within seconds whether this studio understands their kind of project.
That's the gap. Studios build portfolios and call them websites, then wonder why enquiries don't match the quality of the work.
Why great projects don't automatically create a great website
Strong architecture speaks for itself in person. On a screen, to someone who has never met the practice, it needs help.
A finished house shot beautifully by a good photographer tells a visitor what the project looks like. It doesn't tell them what the brief was, what site constraints shaped the design, what the client actually wanted, or why this studio was the right one to deliver it. Without that context, even outstanding photography reads as "nice houses" rather than "a studio that solves problems like mine."
This is the single biggest gap between studios that get enquiries from their website and studios that get compliments on Instagram instead.
What prospective clients actually need to understand, quickly
Someone visiting an architecture website for the first time is trying to answer four questions, usually within the first minute.
Do you do the kind of project I'm planning. A studio known for heritage renovations reads differently to one known for new-build coastal houses, even if both are excellent architects.
Do you work where I am. Location matters more in architecture than almost any other design discipline, because planning regulations, local council relationships, and site knowledge are part of the value.
Are you the right scale for my budget and ambition. A solo practice and a twenty-person studio solve different problems, and a website that doesn't signal scale leaves visitors guessing, often incorrectly.
What happens if I get in touch. Vague or absent calls to action are one of the most common ways a genuinely interested visitor leaves without enquiring.
A portfolio, built purely to showcase finished work, tends to answer none of these clearly. A website, built with intent, answers all four before the visitor has to think about it.
The role of positioning, structure, copy and project presentation
Positioning is the decision about who the website is for. Most architecture websites try to speak to everyone, which in practice means they speak to no one. The studios that generate strong enquiries have usually made a clear, sometimes narrow, decision about who they want to work with, and let that decision shape the entire site.
Structure is the order in which information appears, and it should follow how a visitor actually thinks, not how the studio internally organises its project files. Homepage, then a small number of strong projects, then a case for the studio, then a clear way to make contact. Not eleven navigation items and a project archive sorted by year.
Copy is the most under-invested part of most architecture websites. Studios will spend significant money on photography and comparatively none on the words next to it, despite copy doing the job photography can't: explaining brief, process, and outcome in language a non-architect can follow.
Project presentation is the difference between a gallery of images and a story. A project page that opens with a floor plan and a paragraph about massing strategy is written for other architects. A project page that opens with the brief, the site problem, and the client's ambition is written for the next client.
Common mistakes architecture studios make
The homepage leads with an abstract statement instead of a clear one. "Considered architecture for considered living" tells a visitor almost nothing about what the studio does or for whom.
Projects are presented as image galleries with minimal text, leaving the visitor to infer the story instead of being told it.
The site has no clear point of view about who it's for, so it tries to appeal to homeowners, developers, and fellow architects simultaneously, and ends up compelling to none of them.
There's no real path to enquiry. A contact page buried in the footer, with no supporting nudge earlier in the journey, asks a lot of a visitor who is only mildly warmed up.
The site hasn't been updated with recent work, so the most current thinking a studio has to offer is sitting in a folder rather than on the page that's meant to be winning new clients.
The navigation tries to mirror how the studio thinks about its own practice, with categories like "Residential," "Multi-Res," and "Commercial" that make sense internally but leave a visitor unsure which one matches a project they haven't yet named to themselves.
How to turn a portfolio into a business-development tool
Start by deciding who the website needs to convince. Not "everyone who might want an architect." A specific kind of client, on a specific kind of project, in a specific place.
Then choose the projects that make that case most clearly, even if they aren't the most photogenic ones. A modest renovation with a compelling brief and a strong result often does more work than a beautiful but unrelatable one-off.
Write each project as a short case, not a caption: what the client came in with, what the site or budget constraints were, what the studio decided and why, what the result was. That's the subject of the next article in this series, in more detail.
Design the homepage to answer the four questions above in the first screen, not the fifth scroll.
And build in a genuine next step: an enquiry form that asks the right questions, a phone number that's easy to find, or an invitation to see more of a specific kind of project.
None of this requires abandoning the aesthetic judgement that makes the studio's work strong in the first place. It requires applying the same judgement to the website that's already being applied to the architecture.
It's worth saying plainly what this isn't. It isn't a case for a generic template, a stock hero video, or the kind of homepage that could belong to any studio in any city. The specificity that makes a website work commercially is the same specificity that makes it feel like this studio and no other. A portfolio turned properly into a website should look more distinctive at the end of the process, not less.
Bourne Creative's own concept work for Mylor, an Adelaide Hills architecture practice, is one example of what that shift looks like in practice: identity, website and content built as one system rather than three separate commissions.
If your projects are strong but your website isn't communicating that clearly, that's usually a strategy problem before it's a design problem. That's a conversation worth having before anything else on the site gets touched.
