Architecture Firm Website Design: Template or Concept Site?

Whether an architecture firm should choose a template or a concept site depends on two things: how much your projects set you apart visually, and how ready your portfolio is. A ready-made template is fast and economical, but it squeezes your projects into its own grid. A concept site builds the structure around the projects instead. For most firms, the sensible path is to start with a one-page concept site and add project pages over time.

Who visits an architecture firm's website, and what are they looking for?

A visitor to an architecture website usually belongs to one of four groups: someone looking for an architect for a home or workplace, a manager researching on behalf of an investor or institution, an architect who wants to apply to the firm, and someone looking into the firm for a news story or competition. Their first question is the same: "What kind of work does this firm produce?"

The answer to that question is in the projects, not the text. Sections, models, photos of completed spaces and short project data sheets do more work than anything else on the site. That is why the job of design on an architecture site is to step back and make room for the project.

Pros and cons of a ready-made template

The clearest advantages of a template are speed and cost. The structure is ready, setup is short and you can make small changes yourself.

The drawbacks show up exactly where an architecture firm cares most:

• Images are forced into the grid. A horizontal facade photo is cropped into a square box, and the narrative order of a series of interior shots is broken.
• The project story cannot be shaped. In most templates, a project page follows an "image gallery plus paragraph" layout, which makes it hard to tell a story from concept to construction.
• Risk of looking alike. The first impression can blur with other firms using the same theme.
• Weight. Themes that bundle many features can slow the site down when combined with large images.

For a firm with a tight budget, a portfolio that has not taken shape yet, or a plan to use the site as a temporary showcase, a template is still a defensible starting point.

What does a concept site do differently?

On a concept site, the order is reversed: first the projects and how to tell them are decided, then the page structure is built around them. The building blocks we often use on an architecture concept site are:

• Large, uncropped images: Photos are shown in their own proportions; the design leaves space around the image.
• Project data sheet: Location, year, area, project type, team and photographer are given briefly and in the same layout.
• Concept, process, result flow: The project page moves from sketch to built work, so visitors see how the firm thinks.
• Category filter: Filters by type, such as residential, commercial or interior architecture, help visitors find a project similar to their own.
• Collaboration request: A few form fields, such as project type, approximate area and location, make the first meeting more productive.

The price of a concept site is more groundwork: project selection, image order and copy need to be planned together.

How much text about the firm is enough?

Text on architecture sites usually sits at one of two extremes: either there is none, or it runs to the length of a manifesto. Visitors need short answers to three questions: what kind of work does the firm do, how does it approach that work, and how does a project get started? Two or three paragraphs and short bios of the founders cover these questions. Awards, publications and competition placings, if any, should be given in a separate list with dates and sources; verifiable information builds more trust than bold adjectives.

How do you use large images without slowing the site down?

The technical problem we see most often on architecture sites is photos uploaded at the size they came out of the camera. On an image-heavy site, speed matters as much as design. For Largest Contentful Paint (LCP), one of Google's speed metrics, the target is 2.5 seconds or less for 75 percent of page loads; on architecture sites, this largest element is often the hero image.

• Do not lazy-load the hero image. web.dev recommends that images visible on the first screen, especially the LCP image, should not be lazy-loaded. Images further down can be.
• Serve sizes to fit the screen. Use srcset or the picture element to send a small file to phones and a large one to wide screens; formats such as WebP and AVIF reduce file size.
• Add images as image elements, not backgrounds. Google states that it does not index background images added with CSS. If you want your projects to be found in image search, use the img element.
• Write file names and alt text. Instead of "IMG_4521.jpg", use short, descriptive names such as "kadikoy-residential-project-facade.jpg", and alt text such as "Street facade of a five-story residential project in Kadikoy".

Settle the usage rights for photos from the start as well. If a professional photographer shot the project, agreeing in writing on how the photos can be used on the site and on social media prevents disputes later. Getting the owner's consent for residential interiors is also a good habit.

Does it make sense to start with a one-page site?

Not every firm needs ten pages on day one. A one-page concept site can be complete with this flow: a short introduction and the firm's approach, three to five featured projects, the team or founding architects, and contact with a collaboration request. Visitors see the whole story by scrolling and do not get lost.

As the portfolio grows, adding a separate page for each project brings two benefits. First, it makes room for the project story. Second, it increases your chances of being found in searches that combine project type and location, such as "Bodrum villa architecture project" or "office interior design project". We explain how we make the same template-or-concept decision for a sector with stricter rules in our post on concept websites for dental clinics.

What determines the delivery time?

With a concept site, the timeline depends more on whether the content is ready than on design. In Piküp's Concept Website package, delivery takes 4 business days if your copy and images are ready. If Piküp prepares the content and materials, it extends to 2 weeks and an extra fee applies. You can see current prices on our pricing page.

To prepare, have these ready:

1. Three to five projects you want to feature, with the best images for each.
2. A short data sheet for each project: location, year, area, type, team, photographer.
3. Two or three paragraphs describing the firm's approach.
4. Team or founder photos and the logo.
5. Contact details and the questions you want to ask in the form.

Which one should you choose?

• A template is enough: The budget is very limited, the portfolio has not taken shape yet, and the site will be a short-term showcase.
• A concept site is the better fit: Your visual language sets you apart from competitors, it matters that projects appear in the right order and size, and the site will be used for a long time.
• A middle path: Start with a one-page concept site, see how real visitors behave, and add project pages as the need arises.

You can browse live examples and the package scope on our Concept Website page.