GearForge

The client described what they needed as “a form on a website.” But before writing any code, I mapped how orders actually moved through the business day-to-day — not how they were supposed to. That’s where the real problem showed up: the form wasn’t feeding the system, the form had quietly become the system.

Every custom helmet order began life as a single master PDF. To place one, a person opened that PDF, manually typed in the distributor details, the helmet model and every spec, then the colors and quantities. They saved a copy, produced a receipt from the same numbers, and emailed it out — once to the distributor, once back to the company.

Once the flow was visible, the pain points were obvious — and they were daily, not occasional. The same distributor and authorizer details were re-typed on every single order. Nothing remembered “what we usually order,” so each order started from a blank page.

The hardest part was never the UI — it was the domain. Helmet configuration isn’t a flat list of fields. Helmet → type → model cascade, and each combination unlocks a different set of valid suspensions, eye protection, attachments, side panels and compliance rules. Pick the wrong path and you’ve quoted something that can’t legally be built.

I mapped every valid configuration path into a rules layer so the portal only ever offers legal combinations, and surfaces the right NFPA / OSHA compliance warnings at the exact moment a choice is made. Knowledge that used to live in one experienced person’s head is now encoded in the system.

The design goal was simple to say and hard to do: take a configuration with dozens of interdependent options and make it feel like filling in a small, friendly form. The interface stays clean and white on purpose — this is a tool people use all day, so low-friction beats flashy.

Distributor info is captured once at the top; below it sits the order builder. Fields appear only when they’re relevant to the chosen model, so users never face a wall of thirty dropdowns. Each configured helmet collapses into a summary card they can edit or remove before submitting.

The portal is a Next.js + TypeScript app behind a simple login, so only authorized distributors get in. A configuration engine drives the dynamic form from the rules layer, and drafts plus uploads are saved locally — a refresh or a long session never loses work.

Then the payoff: on submit, the system validates everything, assembles each configuration, generates the order and receipt PDFs in the browser, and emails them to the distributor with a copy to the company. The entire manual routine — fill, save, build receipt, attach, send twice — became a single click.

The team went from opening a PDF and retyping everything to logging in, finding the usual details already there, configuring, and submitting. One click now does what used to be a multi-step manual routine: build the order, produce the receipt, and send both to the right people.

It’s not a giant system — and it didn’t need to be. It’s a focused tool that removed a real daily friction point and made a compliance-sensitive process meaningfully harder to get wrong.