A custom motorcycle wheel company I co-founded. I designed the wheels, designed and built the WordPress site and checkout flow, and integrated two payment processors myself, while my partner ran manufacturing.
Styled Wheels manufactures custom motorcycle wheels. I co-founded the company and owned everything outside manufacturing: designing the wheel finishes, designing and building the website, and running the rest of the business, while my partner handled production. The catalog spanned six finish and series options, including Black Contrast, Black Contrast Extreme Modular, Chrome, Black and Chrome Modular, and All Black Powder Coat (standard and Modular), plus accessories like fork cans, saddlebag latch covers, axle covers, and wraparound fenders, and a dealer program offering 25% off to wholesale partners. Everything from the product design to the site that sold it was mine to design and build.
I did all of it myself, with no team behind me on the business side. I designed the physical wheels and their finish options. I designed and built the WordPress website that sold them, including product pages, the shopping cart, and the checkout flow. I integrated two separate payment processors so customers could pay however they trusted most. And I ran the business's day-to-day finances in QuickBooks, reconciling orders coming through the site against real revenue. Design, development, payments, and bookkeeping all sat with one person, and that was me.
What made a made-to-order, single-owner e-commerce business harder than a typical storefront, and how I built around it.
This is the part I'd point to directly for a payment-processor or checkout-system example: a customer picks a wheel, series, and finish from the catalog, adds it to the cart, and pays through either PayPal or Authorize.net at checkout.
Some customers preferred PayPal's own checkout over entering a card on an unfamiliar site, while others just wanted to type a card number directly. Running both live at once also meant a problem with one processor never cost a sale. Every completed order then reconciled against the books, so checkout fed directly into how the business actually ran in QuickBooks.
The six screens above are the shortest path through checkout. The flow also covered every step in between: a billing address form for customers paying by card, PayPal's authorization hand-off, a review screen for card orders, and the brief confirming state while an order was being placed.
Click through the real checkout screens to see the card path, the PayPal path, and what happens when something goes wrong.
Click the screen to continue
Checkout also had to handle what customers don't expect to see: a mistyped ZIP code, an expired card, a declined charge, a cancelled PayPal session, and a delayed confirmation, across both PayPal and Authorize.net.
Every order also triggered a matching email: a receipt on a successful payment, a shipping notice once it shipped, and a clear status update, instead of silence, if a payment needed another look.
Beyond the website, I landed Styled Wheels coverage in print, placing ads and feature articles in several motorcycle magazines that put the brand directly in front of riders who might never have found it online.
Product photos of the finished Styled Wheels, mounted and ready to ride.
What handling design, the site, and the books at Styled Wheels actually looked like.
PayPal and Authorize.net both live at checkout, so no customer was turned away, and one processor having trouble never cost a sale.
Design, development, checkout, payments, and bookkeeping all sat with me, while my partner ran manufacturing and assembly.
Finish and configuration choices folded into a standard cart and checkout flow, instead of manual back-and-forth to place an order.
Plan for the failure, not just the happy path. I learned that running two payment processors and designing for declines, expired cards, and delayed confirmations meant a problem with one processor never cost a sale.
Owning every layer shows what a design decision costs. I learned this by building the checkout and then reconciling every order in QuickBooks. The downstream cost of each choice became impossible to ignore.
Fold complexity into the flow people already know. I learned that putting finish and series choices inside a standard cart and checkout kept made-to-order from feeling complicated to buy.
I didn't just design Styled Wheels. I built and ran it, from the storefront and checkout code all the way to the books. I understand what a design decision costs downstream.
Running two payment processors in parallel wasn't overkill. It meant one outage never cost a sale. I design with failure modes in mind, not just the happy path.
Design, code, marketing, and bookkeeping all ran through me. I'm at ease moving between the screen and the spreadsheet, and see how one affects the other.
Styled Wheels is my own product, a hands-on build I created from start to finish. I designed the product, built the site that sold it and the checkout flow, integrated two separate payment processors, and made sure every order matched the books. That's the same instinct I bring to any team. I want to understand the whole system, not just the screen in front of me, and own a piece of infrastructure as critical as payments from design through to production.