Fifty projects, finally organised like an argument.
An architecture practice whose site listed every project it had ever built in reverse chronological order and asked visitors to work out the rest.
Services
- Information architecture
- Design
- Build
- CMS
The problem
Fifty projects on one endless page, sorted by date, with no way to tell a ₹5-crore civic commission from a bathroom extension. Prospective clients could not find work resembling their own brief, so the practice kept getting enquiries for the wrong kind of job.
What we did
- 01
Restructured the archive around what clients actually search by — typology, scale and site condition — rather than around when the practice happened to finish something.
- 02
Gave every project a one-sentence thesis at the top, so the archive can be skimmed as a set of positions rather than a list of buildings.
- 03
Built a CMS the studio can run themselves, because a practice that finishes a project every six weeks cannot email its web people every time.
- 04
Kept the whole archive static and prefetched on hover, so moving between fifty projects never shows a loading state.
Outcome
The archive now answers the question a prospective client is actually asking — "have you done something like mine?" — in about two clicks.
- To any comparable project
- 2 clicks
- Projects, self-managed
- 50
- Perceived nav delay
- 0ms