Case study · Agency partner

The Dealer Website Factory

An agency that sells websites to water-treatment and lighting dealers needed sites in days, each in the dealer's own brand, each lead going straight to the dealer. I built the factory that makes them.

8 sites
Shipped in the first two weeks, before the factory even existed
Diagram: one factory feeding 20 anonymized dealer sites
Counts as of October 18, 2026. Dealer names withheld; the sites are theirs.

Before · After

Before

Every new dealer was a new project

After

A new dealer is a folder: logo, cities, form

Problem

An agency selling websites to water-treatment and lighting dealers had more dealers signing up than any one-at-a-time build could keep up with. Each one needed its own brand, a fast mobile page, and leads that land with the dealer, not with the agency and never with me.

Approach

I built eight sites by hand in two weeks, then built the factory that makes them: one template per trade, one data folder per dealer, an automated check before every deploy, and a landing-page engine for the ad traffic. Each lead runs through the dealer's own form into the dealer's own CRM.

Outcome

20 dealer sites and 27 ad landing pages now come out of two repos I wrote alone. When one change broke one dealer's page for under two hours, the fix became a rule the whole fleet follows.

My role

Sole builder: the factory, the QA tooling, the landing-page engine, the lead relay and every deploy.

What this means for you

If you sell the same service in many towns or under several brands, you should not pay for the same website twenty times.


Stack

Next.jsVercelGoHighLevelGoogle Ads trackingClaude Code