The temptation
A second gym wants the same campaign. The obvious move is to copy the folder, change the address and the phone number, and ship it. That is how two pages quietly become two codebases that drift apart until nobody is sure which one is correct.
The alternative is to treat the first build as the system and the second as a configuration of it — which means being disciplined about what is genuinely different rather than assuming everything is.
What actually changed
Six things, each confirmed with the client before a line was written.
- 01Elite strength training removed. Huntington Beach runs it; Whittier does not. It came out of the page and out of the emails, rather than being left in as an aspirational detail that would embarrass the front desk.
- 02Its own prize pool. Not a share of a franchise pot — Whittier's own, growing with Whittier's own enrolments.
- 03Its own lead destination. A separate Google Sheet and a separate Apps Script deployment, so neither location can break the other.
- 04A different call to action. HB books a tour; Whittier invites you to take a class, because that is what their front desk is set up to receive.
- 05Its own class schedule driving the time picker.
- 06Local details — address, phone, email, dates.
What deliberately did not change
The design system, the booking engine, the email templates, the page structure, the serverless backend, the dual-host adapters, the print collateral pattern. None of it was revisited, because none of it was wrong.
The same discipline applied to what was not added. No guarantee, no risk reversal, no capacity cap invented to manufacture scarcity — the deadline was real, so nothing else was needed. Resisting the urge to improve a working page while moving it is most of the skill.
Why this is the case study worth reading
Anyone can build one landing page. The question that decides whether a business can run campaigns at all is what the second one costs — and the answer here is a short list of confirmed differences rather than a project.
That is the same argument as the intake runbook and the reporting platform, in a different medium: do the thinking once, write it down, and the next instance becomes configuration.