Identical products, bought for entirely different reasons
An architect, a municipal engineer and an HOA board can all specify the same wall system and arrive needing completely different things to justify it. All of them want technical drawings before they commit.
Structured around the company rather than the purchase, a catalogue like this becomes a brochure: accurate, comprehensive and impossible to buy from.
Two product systems, two parallel entry routes
The site was restructured around the two product systems rather than the company narrative. Permacrete wall systems and Duracrete fences each received their own architecture, with a consistent finish taxonomy — StoneCast, Woodcast, BrickCast and BlockCast — so options can be compared within a system rather than across a price list.
Two parallel entry routes then run over the top: five application sectors for project-based buyers who think in terms of what they are building, and six stakeholder paths for architects, engineers, land developers, HOAs, public works and general contractors who think in terms of what they need to approve.
- System-first architecturePermacrete and Duracrete structured separately, so each reads as a product line rather than a catalogue section.
- Consistent finish taxonomyThe same four finishes across both systems, which is what makes comparison possible at all.
- Two ways inBy sector for project buyers, by role for specifying audiences — the same catalogue reached by whichever logic the visitor already uses.
The CAD and specification library is a section, not a resource page
For a specifying audience, the drawing set is the decision point. Burying it under a resources menu treats the most important asset on the site as an afterthought.
It was built as a primary section instead — because the moment an architect can pull the drawing they need, the manufacturer is on the shortlist.
The CAD library is not a resource. For half of these buyers it is the product page.
