B2B mfg websites need RFQ/quote flows as first-class features, technical spec-heavy product pages, certification showcases, case-study depth, and often ERP/SAP integration for catalog and pricing sync. We build in Next.js for marketing + React for catalog/quote UI, with CRM integration (HubSpot, Salesforce, Zoho) for lead capture. The design constraint that governs everything is who is actually using the site: a sourcing engineer with a specification in front of them, working through several supplier sites in an afternoon, wanting to establish in under a minute whether you can make the part. That reader is served by dense specification tables, downloadable drawings and a visible enquiry path, and is actively obstructed by a full-screen hero video and three scrolls of brand language before the first fact appears.
B2B mfg stack: Next.js or WordPress + WooCommerce (for product catalogs), ERP integration via API where applicable, CRM webhooks for lead capture, multi-region support via i18n + hreflang. RFQ flow UX: product-specific quote requests, cart-style multi-product RFQ, spec upload (PDF, CAD), preferred delivery location, approximate quantity. Certification display: ISO, BIS, CE, UL logos prominent with verification links. The problems we most often inherit are structural rather than cosmetic: a catalogue organised by internal division names that no buyer would search, variant pages duplicating each other into a ranking mess, technical content trapped in PDFs, and an enquiry form that emails a shared inbox nobody owns. Rebuilds also have to account for who maintains the site afterwards, since manufacturers rarely have in-house web staff, so the content model needs to let a sales coordinator add a product or update a certificate without developer involvement. We build for that handover deliberately rather than leaving a system only we can operate.
