An architect website has two jobs: prove the quality of the work and help the right prospective client decide whether the practice fits their project.
A beautiful portfolio can accomplish the first job while failing the second.
Someone may spend ten minutes looking through completed buildings and still leave without knowing whether you take projects like theirs, where you work, what stage you become involved, or how to start a serious conversation.
That is the gap to fix.
A portfolio is evidence, not the whole buying journey
Architecture is unusually visual, so it is easy to design the website around photography and treat everything else as supporting copy.
But a prospective client is not only judging taste. They are also trying to reduce uncertainty.
They may need to know:
- whether you handle residential, commercial, hospitality or another relevant project type
- whether the project is within your geographic or regulatory reach
- what your role covered on comparable work
- whether you can work from an early concept or enter later
- what happens after an enquiry
- whether their budget, timeline and project stage are realistic enough for a conversation
The website should answer enough of those questions to make the next step feel sensible.
Build project pages around decisions, not image count
A useful architecture case study does not need to become a long essay. It does need context.
For each important project, consider showing the project type, location, scope, status, relevant constraints, services provided and a short explanation of the design response.
That information changes a gallery from “we make attractive buildings” into “we have solved a problem similar to yours.”
The distinction matters when a referral sends someone to your site. They may already trust the person who recommended you. Your website now needs to help them verify fit.
If the work is confidential or some details cannot be disclosed, publish only what you are allowed to publish. Do not invent numbers, client quotes or outcomes simply to make a case study look complete.
Organise the portfolio around how clients think
Internal studio terminology is not always the clearest navigation for a buyer.
If a practice serves materially different markets, let visitors quickly reach the work relevant to them. Residential prospects should not need to decode a mixed grid of schools, offices, private homes and speculative concepts to work out whether you design houses.
Useful divisions might include project type, service, sector or project stage. Choose the structure that reflects how clients actually select the practice.
Avoid creating dozens of near-identical pages solely to target combinations of cities and services. Google explicitly treats doorway-style pages created mainly to rank for similar queries as spam. See Google’s spam policies.
Show the process before asking for a consultation
Architecture has a longer and more consequential buying journey than ordering a commodity service. A vague Contact us button asks the visitor to cross too much uncertainty at once.
A concise process section can explain what happens after first contact: initial fit review, consultation, brief or site information, proposal, and the next appropriate project stage.
The goal is not to publish every internal workflow. It is to make the first commitment understandable.
This is especially important for prospects who arrive through Instagram, referrals or a project they saw elsewhere. They know the work before they know the engagement process.
Make the enquiry form qualify without interrogating
The form should collect enough information to route and prepare for the conversation, but not demand a full architectural brief before anyone has spoken.
Useful fields can include:
| Field | Why it helps |
|---|---|
| Project type | Routes the enquiry to the right service or person. |
| Project location | Establishes geographic fit early. |
| Current stage | Distinguishes an idea, acquired site, active design or existing build. |
| Desired timeline | Exposes obvious timing mismatches. |
| Approximate project or construction budget | Helps both sides judge commercial fit where appropriate. |
| Short project description | Gives context without forcing a long questionnaire. |
| Preferred contact details | Makes follow-up practical. |
Do not collect information merely because the form builder allows it. Every required field creates friction and should earn its place.
And do not let the only copy of an enquiry live inside an email notification. Save submissions somewhere durable, protect access appropriately, and test the complete journey. A form that says sent while the studio never receives the lead is a business failure, not a cosmetic bug. I have a separate guide on contact forms that report success when the email never arrives.
Design mobile for the person who arrived from social or a referral message
A prospective client may first open the site from Instagram, WhatsApp, LinkedIn or an email introduction on a phone.
Large architectural photography still matters, but mobile pages should not become an endless stack of oversized images before the visitor can understand the project or contact the practice.
Compress images appropriately, reserve their dimensions to reduce layout movement, and test the actual page rather than assuming a desktop portfolio scales down cleanly. Google’s Core Web Vitals documentation explains the current loading, responsiveness and visual-stability measures used to evaluate page experience.
The practical test is simpler: can a person on an ordinary mobile connection understand the project, identify fit and reach the next step without fighting the interface?
Connect local discovery to the owned website
For practices serving a defined area, a Google Business Profile can support discovery while the website handles the deeper decision.
Google allows eligible businesses to add their website and other business information to a profile. Keep names, contact details and real-world business information consistent rather than treating the profile and website as unrelated assets. See Google’s Business Profile guidelines.
The website remains where you control the project narrative, service structure, case studies and enquiry journey.
Measure qualified enquiries, not portfolio applause
Gallery views are useful behaviour data, but they are not the business outcome.
A more useful measurement chain is:
landing page → relevant project/service viewed → enquiry started → enquiry submitted → qualified enquiry → consultation → project won
That makes website improvement more rational.
If many people view residential projects but almost nobody starts an enquiry, the problem may be positioning, process clarity or the next step. If many start the form but few submit it, inspect the form. If submissions are healthy but most are poor-fit projects, qualification and service messaging may need work.
The website becomes easier to improve once you can identify the stage where good prospects disappear.
When an architect website is doing its job
The best architecture websites are not necessarily the ones with the most animation, the largest image grids or the fewest words.
They make strong work easy to evaluate and make the next business decision clear.
A serious prospect should be able to answer three questions before contacting you:
- Does this practice do work relevant to my project?
- Do I trust how they think and work?
- What should I do next?
If your portfolio already looks strong but the website is not producing enough serious project conversations, the problem may be the journey around the work rather than the work itself.
I design websites around that complete journey, from proof and positioning to enquiry and measurement. See my web design service, or contact me if you want me to review what is stopping your current site from turning interest into qualified enquiries.
