Rugged Red — Multi-Brand Frontend on Shared Product API
React/Vercel brand site on shared PMST Heroku/PostgreSQL product data and Contentful content — separate identity without duplicate backends.
Senior full-stack engineer — brand frontend and shared product architecture
+31%
Conversion lift
2
Brands, one platform
0
Duplicate CMS stacks
1
Shared deploy pipeline
ForzaBuilt needed Rugged Red — its cleaning product line — discoverable as its own division without maintaining a second website, duplicate content ops, or fragmented product data.
The problem
Launching a sub-brand usually forces a binary choice:
- Separate site — clean brand identity, but double the maintenance, SEO risk, and content drift.
- Buried in parent catalog — one stack, but buyers never find the cleaning line as a first-class product family.
Forza needed Rugged Red to feel standalone while staying operationally aligned with the parent platform.
My role
I architected the division launch: dedicated category routing, customer-facing brand identity, and shared backbone with ForzaBuilt so the internal team keeps one operating system.
What I built
First-class division routing
- Rugged Red introduced as a dedicated cleaners branch in core navigation and product pathways.
- Category routes and content structured separately from adhesive flows — distinct user intent, shared infrastructure.
- Cleaners experience separated from industrial adhesive workflows without forking the entire stack.
Shared platform, separate identity
- React SPA on Vercel with household and industrial route trees.
- Live product data from shared PMST Heroku/PostgreSQL API (
/api/products,/api/products/ruggedred-json) with local JSON fallback. - Blog/news content from Contentful — separate brand voice without a duplicate product database.
SEO-safe multi-brand expansion
- Canonical and indexability consistency as product families expanded.
- Crawl-friendly structure so search engines and users can discover the cleaning division from primary site pathways.
- No duplicate CMS or parallel content systems that drift out of sync.
Outcomes
| Metric | Result |
|---|---|
| Division launch | Rugged Red live with focused brand identity |
| Conversion | +31% lift on division product paths |
| Operations | Two brands, one platform — no duplicate stacks |
| Maintainability | Shared routing logic preserved across related brands |
Rugged Red launched with a focused customer-facing identity and cleaner product discovery flow, while the team retained one scalable system for content, products, and updates across both brands.
What this demonstrates
- Multi-brand architecture without platform fragmentation.
- Balancing brand differentiation and operational integration — a common enterprise pattern at SMB scale.
- Routing and IA decisions that support future division expansion without a rebuild.
“Nexrena built the ecommerce foundation we needed to scale seasonal demand.”
Live system
ruggedred.com ↗