Engineering trust through digital presence
One e-commerce platform, two audiences — B2B depth meets B2C speed
Client
Weld Vision
My Contribution
- End-to-end UX research
- Information architecture
- Visual design
- Prototyping
- Design system
Timeline
2022
Team
- 1 Product Designer
- 2 Software Engineers
- 1 Product Manager
Weld Vision sells welding equipment through 800+ resellers across Brazil. Digital operation was fragmented — separate sites per product line, outdated e-commerce, no unified experience. B2B buyers hit B2C checkout. Resellers couldn't find compatible products. Sales teams built workarounds.
The challenge: unify B2B complexity with B2C speed in a single platform.
• Fragmented platforms. 800+ resellers scattered across disconnected sites with no unified experience.
• Low SEO. Poor URL structure, missing meta, no content strategy — organic discovery almost zero.
• Conflicting needs. B2B clients needed quotations and technical manuals. B2C wanted fast purchases and simple checkout.
I started by mapping what was known against what was assumed. The fragmentation was a fact; whether one platform could serve both audiences was not. I ran interviews with B2B sales teams and resellers, and usability sessions with B2C buyers — each audience describing the same friction from opposite sides.
• What I learned: B2B and B2C weren't two markets — they were two moments. The same buyer wanted quotation depth on a welding machine and a quick checkout on consumables.
• What I assumed: that a single platform could hold both without compromise. De-risked it by testing dual-path navigation with both audiences before any visual design.
Every direction had a counter-direction. These three decisions defined what the platform would become — and what it deliberately refused to be.
| Decision | Rejected | Chosen | Why |
|---|---|---|---|
| Platform structure | Two separate sites | Single site, dual paths | One codebase, shared SEO authority, consistent brand across audiences — both audiences validated a single entry point in testing |
| Product pages | One-size-fits-all template | 4 category-specific templates | Equipment, consumables, torches, and CNC each need different information hierarchies — buyers in research asked for different facts per category |
| SEO approach | Bolt SEO onto existing structure | SEO-first information architecture | Clean URLs, proper heading hierarchy, and structured data from day one — organic discovery was the acquisition channel the fragmented sites had killed |
Balancing two audiences on one platform meant constant trade-offs. Three constraints shaped the design more than any feature request.
The final design was a complete, functional e-commerce platform — not a set of isolated screens. It unified B2B and B2C journeys across a single codebase: audience-aware navigation, category-specific product templates, dual checkout flows, quotation negotiation, post-purchase self-service, and an SEO-first architecture.
Four product page templates — equipment, consumables, torches, and CNC machines — each prioritized the most relevant specs and actions for their category. B2B users landed on a quotation-ready catalog; B2C users got a streamlined shopping experience. Both paths shared the same backend, design system, and content structure.
I owned the entire product experience: research, IA, the four-template system, dual checkout flows, and the SEO-first structure. The decision to refuse two separate sites — against the business's initial instinct — was mine, won through workshops backed by both audiences' evidence. The PM aligned stakeholders across B2B sales and B2C marketing; the engineers owned the platform build inside the legacy CMS constraints.
What I shipped: Complete e-commerce platform — audience-aware navigation, 4 category-specific product templates, dual checkout flows (quick buy + B2B quote negotiation), quotation system with negotiation history, post-purchase self-service portal, and SEO-first architecture. Single codebase serving 800+ resellers across Brazil.
I would have pushed harder for a headless CMS from the start. The legacy admin panel shaped too many decisions — not always in the user's favor.
Biggest lesson: B2B and B2C don't need separate experiences. They need information architecture that surfaces the right content for the right context. "Both" instead of "either/or."