← Case StudiesProject Summary
05
ManufacturingWeb Design and Development

An export-credibility website for a safety-critical foundry.

Design system and Next.js build for MAP Alloys, an IATF 16949 certified aluminium gravity die-casting foundry supplying brake-system components to tier-1 automotive customers.

Visit the live site — mapalloys.com

Stack

Next.js 16 (App Router)React 19TypeScriptTailwind CSS v4Resend (transactional email)VercelGitHub

The Problem

MAP Alloys casts safety-critical brake components for two- and three-wheelers, with three million vehicles on the road carrying its parts, and was heading into an export push. Its web presence did not match the calibre of its customer list: an outdated capability deck, phone-quality plant photography, and no brand guidelines. The constraint was explicit — leads come through networking, so the site's job was credibility in export conversations, not lead generation, and the budget was deliberately tight. Overscoping (CMS, gated funnels, plant tours) would have contradicted the client's own brief.

The Result

A nine-page credibility site shipped in six weeks: statically rendered, with an RFQ pipeline delivering enquiries straight to the sales inbox, a design system built around the foundry's verified production figures, and no CMS or database to maintain — the running cost is hosting alone. Live at mapalloys.com. A second phase — Sanity CMS for content operations and a structured SEO programme — is scoped to follow as the export push generates publishing cadence.

What we built

The work that shipped.

Nine-page credibility site in a technical-datasheet design language: the foundry's verified production figures set in display type, sections auto-numbered like a controlled document
Statically rendered Next.js build with no CMS or database — the running cost is hosting alone, by deliberate scope decision
RFQ pipeline as a server action delivering validated enquiries to the sales inbox via Resend, with honeypot spam control
Uniform CSS photo grade making mixed-quality plant photography read as one editorial set, so a future professional shoot drops in with zero rework

Approach

How we designed the system.

Every route is statically rendered at build time and served from Vercel's edge network — there is no database, no CMS, and no server to operate. That is a deliberate scope decision, not a limitation: the client's content changes rarely, every moving part adds monthly cost, and the brief was a credibility asset, not a platform. The single dynamic surface is the RFQ form, implemented as a Next.js server action that validates input, drops bot submissions via a honeypot field, and delivers the enquiry through Resend with the buyer's address as reply-to, so the sales team answers from their normal inbox. Deployment is a git push: GitHub to Vercel CI, with preview deployments for every branch used to review design iterations against production.

Full technical report

Want the full
technical detail?

The full write-up includes architecture diagrams, technology selection rationale, implementation phases, and lessons learned. Available for qualified enquiries.

Architecture diagrams for the full system
Technology selection rationale and trade-offs
Implementation phases and key outputs
Lessons learned and what we would do differently

Available under NDA. We respond within two business days.