DIGITAL REVAMP FOR A MANUFACTURER’S PRODUCT CATALOGUE
Built for a commercial building-facades manufacturer
A commercial facades manufacturer replaced a slow, developer-dependent brochure site with a fast, image-led product catalogue and a self-service CMS, turning the website into a working sales tool.
By Yashwant Daniel · Solvstrat
Key
Facts
- Sector
- Manufacturing
- Built
- Image-led product catalogue and self-service CMS
- Stack
- Next.js · Headless CMS · Vercel · Cloudflare
- Constraint
- Marketing publishes products without developer involvement
- Outcome
- A current catalogue that routes product enquiries to sales
Challenges
A commercial building-facades manufacturer had outgrown a slow, hard-to-update website that failed to showcase a highly visual product range. We rebuilt the platform around a fast, image-led catalogue with a maintainable CMS, turning it from a static brochure into a working sales tool.
A Slow, Dated Website
Poor load times and an outdated design undercut a premium, highly visual product range.
A Catalogue Nobody Could Update
Publishing new products required developer time, so the catalogue regularly went stale.
No Clear Path to Enquire
Visitors browsed the range but had no obvious route to start a sales conversation.
Constraints
The product range is highly visual and must stay at the centre of the experience.
Marketing must publish and update products without developer time.
Pages must load quickly on mobile, including image-heavy catalogue views.
Existing product data and project references must carry over.
Enquiries must reach the sales team with product context attached.
Reference
Architecture
Catalogue layer
Image-led product and project pages built around the range, with responsive layouts and structured product data.
Next.js · Structured data
Content layer
A headless CMS holds products, categories and project references so the team edits content independently of code.
Headless CMS
Media pipeline
Images are resized, converted and served in modern formats at the edge, so visual pages stay fast on mobile.
Image optimisation · CDN
Enquiry layer
Product-specific forms capture context and route submissions directly to the sales team.
Forms · Routing
Delivery layer
Static generation and edge caching keep catalogue pages fast for visitors regardless of location.
Vercel · Cloudflare
Data
Flow
- 1
Marketing adds or updates a product in the CMS.
- 2
The CMS validates required fields and stores the entry.
- 3
The build or revalidation step publishes the updated catalogue page.
- 4
Images are optimised and served from the edge cache.
- 5
A visitor browses the range and opens a product-specific enquiry.
- 6
The enquiry is routed to sales with the product and page context attached.
Delivery
Foundation
Information architecture, catalogue model and CMS setup.
Build
Product and project templates, media pipeline and responsive layouts.
Conversion
Enquiry flows, routing and sales hand-off.
Launch
Performance tuning, redirects and analytics.
Hard
Problems
Keeping an image-heavy catalogue fast
Problem: High-resolution product imagery is central to the sale but heavy on mobile connections.
Resolution: Responsive image sets, modern formats and edge caching, with layout space reserved to avoid visual shifts as assets load.
CMS freedom without design drift
Problem: Self-service editing can produce inconsistent pages and broken layouts.
Resolution: Structured content types and constrained templates so editors change content, not layout.
Enquiries with context
Problem: Generic contact forms gave sales no idea which product or application the buyer was asking about.
Resolution: Product-aware forms attach the product, category and source page to every submission before routing.
Results
A Catalogue That Stays Current
The team updates products and project references themselves, so the site is never out of date.
A Working Sales Tool
Product pages now route qualified enquiries directly to the sales team instead of dead-ending.
Industry Benchmark
Comparable site rebuilds typically load 60–75% faster and lift organic enquiries, with Core Web Vitals passing on mobile. We frame outcomes against these benchmarks rather than publishing client-specific figures.
Technology
Used
Next.js
Headless CMS
Vercel
Cloudflare
Lessons
A catalogue is a sales tool; the enquiry path matters as much as the product page.
Give marketing structured content types, not a free-form page builder.
Performance is a design constraint on image-led sites, not a cleanup task.
CLIENT SUCCESS STORIES
More Case Studies
Explore how Solvstrat engineers custom digital architectures and software platforms for leading brands.
Healthcare
CRM Modernization for a Multi-Site Healthcare Provider
Consolidated records, automated care coordination and a supported, compliant CRM platform.
Cloud Platform
Custom Web Platform for Nonprofit Operations
One consolidated donation platform with live tracking, automated tax receipts and secure payments.
FAQ
Frequently asked questions
We rebuilt a slow, hard-to-update catalogue site into a fast, image-led platform with a self-service CMS and a clear enquiry flow, turning it from a static brochure into a working sales tool.
Yes. Products, images and project references are managed through a headless CMS with reusable templates, so the team publishes updates without developer involvement.
The client stays anonymous. For reference, industry ranges for comparable rebuilds are 60–75% faster page loads; these are reference ranges, not measured results for this client.
SEE THE PROTOTYPE WE'D BUILD
Give us 30 minutes.
We'll show you the fix.
Tell us where the work slows you down. We'll come back with a prototype of the custom software, internal tools or automation we'd build to remove it — working in weeks, and you own the code.