The project gallery is the single most important page on a custom residential builder's website. It's also the most often botched. The pattern, on probably 70% of Australian builder sites I've audited: a grid of low-resolution thumbnails, four to a row, click into a slideshow of phone-shot site photos in random order with no captions and no context. That's not a gallery. That's a Dropbox folder.

Premium clients evaluating a builder spend more time on the project gallery than anywhere else on the site. They're trying to answer one question: has this builder actually completed work at the standard and scale of what we're planning. A gallery that doesn't help them answer that question is failing the only job it has.

This post is the practical build for a project gallery that actually sells. The structure, the photography, the captioning, the technical architecture, and where to spend the money for the highest return on the qualification work the page does.

What a phone-dump gallery looks like

We need to name it before we fix it. The standard builder site project gallery is some combination of:

A grid of thumbnails on a Projects page, four columns wide, square crops
Each thumbnail is 200–400px wide on the live site, JPEG-compressed to mush
Mixed orientations because some photos are landscape and some portrait, so the grid has weird gaps
A mix of photography sources — some commissioned shots, some Instagram-grade phone snaps, some screenshots of architect renders
No captions on the thumbnails, or captions that are just suburb names
Clicking a thumbnail opens a lightbox slideshow of 8–25 images for that project
The slideshow has next/previous arrows and an X to close. No information about the project. No architect credited. No build duration. No brief. No textual content of any kind.
Mixed image quality within the slideshow — some hero shots, some construction in-progress photos, some interior detail shots with terrible white balance

A premium client looking at this gallery cannot tell, from any individual project, whether the builder built the kitchen joinery to a high standard, whether the rendered concrete external wall was straight and clean, whether the timber detailing was bespoke or off-the-shelf. The gallery has technically existed and answered nothing.

The fix isn't to add more photos. It's to fundamentally change how the gallery works.

The case for the simple gallery

Steelman first. Some builders genuinely do volume work — knockdown rebuilds in the $700k–$1.1m band, four to six houses a year, on a builder-led process where the client picks from three plans and chooses tile finishes from a fixed range. For that builder, a portfolio of "here are the houses we've finished" with a thumbnail grid and a slideshow is fine. The buyer isn't expecting case studies. They're expecting reassurance that the houses look completed and tidy.

The maths breaks the moment the builder targets $1.5m+ custom work where each project is bespoke, the client has an architect, and the brief is being judged against the builder's evident capacity to execute. For that market, every project in the gallery has to function as a case study.

The structure of a project gallery that actually sells

Here's the architecture, in order of importance.

One dedicated page per project, not a slideshow

The single biggest lift in gallery quality comes from giving each project its own URL with a proper editorial layout. Instead of a Projects page that opens slideshows, the Projects page lists projects as cards, each linking through to a dedicated project page.

Each project page has the room to do real work: hero photography, contextual text, multiple sections of imagery covering different parts of the build, a project facts panel, and a structured client testimonial. Six to twelve of these is more useful to a premium client than fifty thumbnails.

The SEO benefit is real too — each project becomes a indexed page that can rank for suburb-and-architect search terms over time.

Commissioned photography across the whole project

The single most productive spend on a builder portfolio is professional architectural photography. A proper architectural photographer (Sharyn Cairns, Dianna Snape, Tatjana Plitt and others in Melbourne; comparable equivalents in Sydney and Brisbane) charges $2,500–$6,500 for a day shoot on a completed residential project. The output is fifteen to thirty fully-edited images covering exterior, interior, detail shots, dusk shots, and the room transitions that make the project read as architecture rather than houses.

This is genuinely expensive. It's also the difference between a project page that converts and one that doesn't. Premium clients can tell the difference between a $5,000 photo set and a phone-shot equivalent in five seconds.

Most builders push back on photography spend because $5,000 per project across eight projects is $40,000 and feels disproportionate. Run the numbers against the value of one extra won brief at $1.5m. The maths is overwhelming.

Project facts panel, structured and consistent

Every project page has a side panel or top strip with:

Project type: Custom new build / Major renovation / Knockdown rebuild / Heritage extension
Location: Suburb (not street address — privacy)
Architect or designer: Named with permission, linked to their site
Build duration: Start to handover in months
Approximate floor area: in m² (helps clients gauge scale against their own plans)
Year completed
Awards: Any Master Builders or HIA categories the project won, if applicable

This panel is the same on every project page. Premium clients scanning quickly across multiple projects can use it to filter mentally — "show me their work at our scale and our architect's style."

The brief and the build, in plain language

Two paragraphs to four paragraphs. What the clients wanted, what the architect designed, what the build challenge was, how the builder handled it. Plain language, written by or with the builder, not generic agency copy.

The texture of this text is doing serious qualification work. A premium client reading "this 380m² project on a sloped Hawthorn site involved a 4-week excavation phase, custom-formed concrete retaining structures, and a long-lead-time prefinished metal cladding that arrived three weeks late from Germany — we adjusted the trade sequence to keep the program on track" is hearing an operator who understands their own work. A premium client reading "we delivered an exceptional finish for this beautiful family home" is hearing nothing.

A structured client testimonial

One long quote, not a wall of short ones. Named clients (with permission). Specific commentary on what worked. Allow the clients to mention things that almost went wrong and how they were handled — that's the most credible testimonial pattern there is, because nothing on a custom build goes perfectly.

Position the testimonial as a pulled-out block midway through the project page, not in a sidebar where it reads like an ad.

A "next project" navigation

At the bottom of each project page, link to two or three thematically related projects from the same gallery. A premium client who's enjoying one case study will read another. This keeps them on the site longer and deepens the impression of capacity and consistency.

The gallery index page itself

The Projects page that lists all the projects — how does it work in this model?

Cards, one per project. Each card has:

A single hero image (commissioned, well-cropped, consistent aspect ratio across all cards)
The project name or location
The project type
The architect, if relevant
The build year

Optionally, filterable — by project type, by suburb, by scale (budget band), by architect collaborator. The filter is genuinely useful if the builder has 20+ projects in the gallery; for under 10, the cards display can run as a simple grid.

Critically: no slideshow on the index page. Click a card, go to a real project page. The depth lives one level in.

Technical infrastructure

This is where the work pays off long-term. The gallery has to be set up so the builder can add new projects without an agency invoice every time. Practical requirements:

A CMS that supports the project page structure (we usually use Sanity, Payload, or Storyblok for builder sites — flexible content modelling, good image handling)
A responsive image pipeline that delivers WebP and AVIF for modern browsers, with sensible sizing per breakpoint
Lazy loading so the gallery page doesn't kill mobile load times
Image preloading on hover for instant transitions into project pages
A structured data layer so Google understands each project page properly

This isn't a $4,000 template build. A custom gallery system with these requirements is typically $15,000–$30,000 of the website spend. Done once, the builder can add new projects via the CMS over time as new work completes.

What this costs in total

For a custom builder building out a portfolio of eight to twelve fully-realised project case studies:

$20,000–$50,000 in commissioned architectural photography (varies heavily depending on how many projects need to be re-shot vs already documented)
$5,000–$10,000 in copywriting and project narrative work (interviewing the builder, structuring the case studies)
$15,000–$30,000 in the gallery system build itself

Total: $40,000–$90,000. The high end of this is a serious investment. Against the lifetime value of premium client briefs the portfolio attracts, it's a one-or-two-project payback.

What I'd cut

A few common items I'd remove from most builder galleries:

In-progress construction photos for premium clients. Useful for trade clients and other builders, distracting for end-clients. Move them to a separate "Process" section if you want to keep them.
Architect renders mixed in with completed photography. They feel like padding. If you only have renders, the project isn't ready for the gallery yet.
Aerial drone shots unless the architecture genuinely warrants them. Drone shots have become a clichéd default and rarely add to the case study.
Before-and-after slideshows for renovations, presented as gimmicks. A simple side-by-side photo pair with proper captioning is more honest and reads better.

The honest counter

If your business is volume project homes — Simonds, Coral Homes, Henley, the franchised brands — the gallery is a display-suite catalogue, not a case study set. Different job, different pattern, different best practices. The portfolio-as-case-study model is for custom builders specifically.

For franchised home brands, the project gallery is functionally a configurator's catalogue and the build emphasis goes into the floor plan selector and the inclusions page, not the project narratives. Completely different website.

The takeaway

The project gallery is the single most important page on a custom builder's website, and most builders are presenting their work like a phone dump. Commissioned photography, dedicated project pages, structured facts, plainly written briefs, and proper testimonials are the difference between a gallery that converts premium briefs and a gallery that loses them silently.

The investment is real — $40,000–$90,000 for a properly built portfolio of eight to twelve case studies. The payback is one won brief. For builders trying to scale beyond architect referrals into client-led briefs, the gallery is the asset that does most of the qualification work.

If your current project gallery looks like a slideshow and reads like a Dropbox folder, book a free audit and we'll tell you what we'd change first. We'll walk through your existing gallery as a premium client would, and tell you honestly which projects are working hard for you and which ones are quietly putting you in the cowboy bucket.

Builder Galleries: Why 70% Look Like a Phone Dump (2026)