Design the portfolio around the client's decision
Prospective clients rarely assess architecture in a vacuum. A homeowner may be weighing planning risk, budget and disruption. A developer may care about site constraints and delivery stages. A commercial occupier may need to understand phasing or work in an operational building. The website should let each visitor find work that resembles the commission they are considering.
Group projects using distinctions that clients understand, such as residential alteration, workplace, mixed use, retrofit or cultural work. Add filters only when there are enough projects to make each result useful. Empty categories can make a modest portfolio feel thinner, not richer.
A specialist web design process should map those decisions before addressing grids, animation or typography. Visual sophistication should support comparison rather than obstruct it.
Turn project pages into credible evidence
A title, location and full-screen photograph leave too much unanswered. Each project page should explain the brief, practice role, status, key constraints and response. State whether the work shown is a concept, consented scheme, project on site or completed building, so an early design image is not mistaken for a delivered outcome.
Useful project information might include:
- the client type, while respecting confidentiality;
- the scope and services actually provided by the practice;
- important site, planning, heritage, access or operational constraints;
- the reasoning behind one or two significant design decisions;
- the project stage, completion date or current status;
- the wider consultant team's contribution where relevant;
- photography, drawings and captions that clarify rather than decorate.
Claims about planning, sustainability, cost or programme need care. Use substantiated facts. Contractual, regulatory or professional statements should be reviewed against the practice's records and obligations. Website copy is not project-specific professional advice.
Edit images for sequence, pace and understanding
Open with an image that communicates the project's character, then build a sequence covering context, arrival, spatial organisation, detail and occupation. Plans, sections, diagrams or before-and-after views can explain decisions that polished photography cannot.
Every image should earn its place. Near-duplicates weaken the edit, while captions can explain subtle interventions. Obtain the necessary permissions, credits and consents for photographs, people, drawings and third-party material. Requirements vary by project and agreement, so the practice should approve publication.
Preserve quality without making the site laborious
Large imagery creates a tradeoff. Excessive compression undermines the work, while oversized files frustrate mobile browsing. Responsive sizes, modern formats and selective loading can retain visual quality. Visitors should not have to wait for transitions or fight a cursor-led interface.
Use London relevance as evidence, not decoration
For a London practice, local credibility comes from the work rather than repetition of the city name. Relevant detail may include constrained urban sites, existing buildings, conservation, neighbour relationships, complex access or occupied premises. Mention boroughs only when factually connected and useful.
The practice's broader London service information should clarify where and how it works, while portfolio pages show that understanding in context. Avoid implying that one successful project predicts the outcome of another. Planning decisions, approvals, procurement and delivery depend on the facts of each commission.
Team biographies, sectors and services should agree with the project roles presented. A curated selection of agency portfolio work can help architects assess hierarchy and proof, but their site must remain recognisably theirs.
Place qualification before the enquiry button
A strong call to action helps the right visitor provide enough information for a useful response. Place it after the evidence, not over every image. Explain what follows submission without suggesting the practice has accepted an appointment.
An initial form can ask for project type, location, current stage, broad scope, anticipated timing and preferred contact method. Budget questions can be useful if the practice has a clear reason for asking, but rigid bands may discourage suitable work when scope is still uncertain. Conversely, omitting commercial context entirely may create avoidable exchanges. The practice should decide what its team genuinely needs to assess fit.
Do not invite sensitive files through a basic form unless the process is designed for them. A route to the agency contact page should make privacy information easy to find. For more on reducing friction without weakening qualification, read about high-converting landing pages for London service businesses.
Measure whether the portfolio supports serious consideration
Raw page views cannot show whether the portfolio supports a decision. Ask whether visitors reach projects matching the services they later request, view several relevant projects and complete forms with enough context. Record which projects are mentioned in initial conversations.
Combine privacy-conscious analytics with feedback from enquiry handlers. Form completion rate needs interpretation alongside enquiry quality. A shorter form might increase submissions while removing information the team needs. Do not maximise one metric at the expense of the intake process.
Review in a practical order
- Audit which projects support the commissions the practice wants to consider.
- Check that every published role, status and project fact is accurate.
- Test whether clients can identify a relevant project from the main portfolio page.
- Read each project page without its images and check whether the reasoning remains clear.
- Test image loading, navigation and forms on common phone and desktop sizes.
- Ask enquiry handlers what useful details are regularly missing.
- Review behaviour and enquiry quality together after sufficient real use.
This sequence prevents visual redesign from masking weak selection or inaccurate narrative. Solve evidence and qualification problems before defining the visual system.
Frequently Asked Questions
Which projects should an architecture practice feature first?
Feature projects that most clearly resemble the commissions the practice wants to consider, rather than simply the most photogenic work. Prioritise examples with an accurate account of the brief, role, constraints and current status. For a London architect, work involving comparable site conditions, building types or planning context may be particularly useful. Keep the selection focused enough for prospective clients to identify relevant experience.
How can a portfolio show experience without revealing confidential details?
Describe the project type, practice role, design response and relevant constraints without naming a client or disclosing protected information. A general location, sector or building condition can sometimes provide useful context where publication is appropriate. Check contractual obligations, client permissions and image rights before adding plans, photography or operational details. Where detail must remain limited, be clear about the project status and avoid implying a broader role.
What information helps prospects assess a practice's suitability?
Project pages should identify the client type where suitable, the commission scope, services provided, project stage and the constraints that shaped the work. Explain one or two material decisions so visitors can understand the practice's approach, not just its visual output. Team, sector and service information should support those pages and remain consistent with published roles. Accurate captions and dates help distinguish completed work from proposals.
Should project pages include budgets, timescales or both?
Include either only when the information is accurate, authorised and meaningful in context. A broad budget or programme may help a prospective client judge the scale of a completed commission, but it can be misleading if procurement, inflation, scope changes or client decisions are not explained. Project status and services are often more dependable starting points. Review commercial disclosures against agreements and update material that no longer reflects the record.
How can enquiry forms discourage unsuitable project requests?
Ask for the details the practice genuinely needs to make an initial assessment, such as project type, location, current stage, broad scope, anticipated timing and preferred contact method. Explain that a submission is an enquiry rather than an appointment or acceptance of work. Clear service boundaries can reduce confusion without creating an unnecessarily rigid form. Avoid requesting sensitive documents unless the practice has a suitable process for receiving them.
