Finished project photography is often the most expensive thing on an architecture website, and the least explained.
A studio will commission a full photography shoot, select the best dozen images, and publish them with a project title, a location, and maybe a floor area. The result looks impressive and does almost none of the work a project page is capable of doing. It shows what the project looks like. It says nothing about why the studio was right for it, or why the next client should feel the same confidence.
A case study is different from an image gallery in one fundamental way: it's built to persuade, not just to display.
The problem with image-only project pages
Photography answers one question: what does this look like. It's a poor tool for answering the questions that actually move someone toward hiring a studio, like what problem did this solve, how did the studio approach it, and what was it like to work with them.
An image-only page also assumes the viewer already understands architectural quality well enough to infer all of that from a photograph. Some do. Most prospective clients, even sophisticated ones, don't have the vocabulary to read a floor plan or a materials palette as evidence of design thinking. They need it explained, briefly and clearly, in language built for someone outside the profession.
This isn't a case against strong photography. It's a case for pairing it with a narrative that does what the images can't.
There's a second, quieter cost to image-only pages. They're interchangeable. Strip the captions off most architecture project pages and it becomes difficult to tell one studio's kitchen renovation from another's. A case study built around a specific brief, a specific site, and a specific client can't be mistaken for anyone else's work, because the story attached to it belongs to no other project.
A practical case study framework
The strongest architecture case studies Bourne Creative builds follow a consistent shape, adapted per project but rarely skipped entirely.
Project context. A short opening that places the project: the type, the location, the scale, and in one sentence, what made it interesting or difficult. This is what a search engine and a scanning visitor both read first, so it needs to work hard in a small space.
The client brief. What the client came in wanting, in their own terms rather than architectural language. A young family wanting more light and a connection to the garden reads very differently, and much more relatably, than "a contemporary extension responding to the original Victorian form."
The design challenge. The site, budget, planning, or heritage constraint that made the project non-trivial. This is often the most under-used section on architecture websites, and one of the most persuasive, because it's where a studio demonstrates it solves real problems rather than just producing nice renders.
The approach. How the studio actually thought through the problem. Not a full design process essay, but two or three key moves: how the brief and the constraint were reconciled, and why this direction over another.
Key decisions. The specific choices that shaped the outcome: material selection, spatial strategy, how the budget was allocated, how planning objections were resolved. Specificity here is what separates a case study a competitor could have written from one that could only be about this project.
The outcome. What the client got, described in terms of how they use and experience the space, not just square metreage. Where possible, this is where a short client quote earns its place.
Photography. Now placed with full context already established, so each image reinforces a story the visitor already understands, rather than trying to tell that story cold.
Project details. The practical footer: location, size, completion date, builder, photographer, awards. Useful for credibility and, quietly, useful for search engines trying to understand what the page is about.
SEO considerations. Each case study is also a page that can rank. A project in Brunswick, for a rear extension, for a young family, contains natural language that potential clients in similar situations are searching for, if the page is written to include it rather than written purely in architectural shorthand.
None of these eight elements needs to be a separate, clearly labelled section on the page. On a well-designed site, context and brief might sit together as an opening paragraph, key decisions might be woven through the photography rather than isolated in a block of text, and project details might live quietly in a footer. What matters is that the thinking behind each element is present somewhere, not that the page reads like a form has been filled in.
Where the framework breaks down in practice
The most common failure isn't leaving a section out entirely. It's writing every section at the same level of vague generality: a "brief" that could describe half the practice's projects, a "challenge" that amounts to "balancing the client's wishes with the site," an "outcome" that's really just a restatement of the brief in the past tense. Specificity is what makes each part of the framework do its job. A challenge worth naming is one that would have produced a different, worse building if it had been handled differently.
What this looks like applied to a real project
Take a narrow inner-city terrace renovation. The context: a single-fronted Victorian terrace in Brunswick, extended once before in the 1980s. The brief: a young family who'd outgrown the existing layout and wanted more connection to a small north-facing garden without losing the original front rooms. The challenge: a heritage overlay restricting changes visible from the street, and a party wall on both sides limiting light to the rear. The key decision: pushing the addition low and stepping it back from the boundary to preserve solar access to the neighbour, then using a sunken courtyard to bring light into what would otherwise have been a dark middle section of the house. The outcome: a home that reads as unchanged from the street and dramatically different from the rear, with the family's stated goal, more light and a stronger connection to the garden, achieved without a heritage objection.
None of that requires more than a few hundred words on the page. It requires those specific details to actually be included, rather than summarised away as "a considered response to a challenging site."
For a longer, real example of this kind of narrative carried through an entire project, Bourne Creative's own case study for Mylor follows the same shape: context, a design idea, the decisions that followed from it, and an outcome stated plainly rather than summarised away.
How case studies help potential clients imagine working with the studio
The real function of a well-built case study isn't to prove a project was completed. It's to let a prospective client see themselves in it. A visitor with a heritage terrace and a tight budget who reads a case study about a heritage terrace with a tight budget doesn't need convincing that the studio understands their situation. The case study has already done it, without a single word of self-description.
This is also why a handful of properly built case studies outperforms a large archive of thin ones. Ten pages that each answer these questions clearly do more for a studio's credibility, and for its search visibility, than thirty pages that are photography and captions.
Where to start
Not every finished project needs the full framework immediately. Choose the two or three that best represent the work the studio wants more of, and build those properly first. A strong case study for the right project is worth more, commercially, than a mediocre one for every project the studio has ever completed. It's the same discipline covered in the first article in this series, on turning a portfolio into an actual website: start with the few projects that make the clearest case, not the whole archive at once.
Browse the studio's own approach to this across its case studies, or get in touch if it's worth talking through which of your projects to prioritise first, and how to structure them. A case study strategy conversation is a useful place to start.
