Platinum Pitch: Two looks, one switch

Platinum Pitch

Twelve ways to pitch a project by sending the thing itself. Each way is something you build and send: a working proof, a page, a proposal. The client sees the work and decides from that.

This folder holds way 2, Two looks, one switch. It is the first way built, and it works on its own.

Way 2: Two looks, one switch

For freelancers, builders and small agencies pitching a website or a redesign to a client who cannot picture the change.

You send one page that flips between the client's current look and a proposed new look with a single switch. The words stay the same in both, so the look is the only thing being judged. The client taps Current and Proposed, compares, and picks.

You give it You get back
The client's current page (a URL you have the right to copy, or pasted HTML or text) and the new direction (colours, fonts, a reference site or a brand brief) One HTML file with both looks and the switch, checked, plus a two-line message to send with it

What is in the folder

File What it is
two-looks/SKILL.md The Claude skill that builds the page from your notes
two-looks/template.html A working example for a made-up bike repair shop. Open it in a browser and tap the two buttons
two-looks/check.py The checks the skill runs before it hands the page over. You can run them too
two-looks/GUIDE.md When to use this way, the five steps, and the mistakes to avoid

Install

Installing takes about ten minutes.

Claude app (web or desktop): zip the two-looks folder, add the zip in Claude's settings where skills are listed, and switch it on.

Claude Code: copy the two-looks folder into ~/.claude/skills/.

Use

Ask for it with the client's page and the direction, for example:

Use two-looks. My client's home page is https://example.com. The new direction is deep green and cream, with a bold modern heading font and rounded cards.

Claude asks for anything missing, builds the page, runs the checks and hands you the file with a list of anything it guessed. Open the file on your own phone, tap both buttons, then send it.

Run the checks yourself

python3 two-looks/check.py your-page.html

That runs the file checks with nothing to install. For the browser checks (both buttons, phone width, scripts off, print), install Playwright once with pip install playwright and playwright install chromium, then add --browser. Add --shots shots to save a screenshot of each look.

Good to know

Two looks, one switch

Platinum Pitch, way 2.

Build one page that flips between a client's current look and a proposed new look with a single switch. The words stay the same, so the client judges the look alone. They see both and pick one. Seeing both is quicker to decide on than a written proposal.

Open template.html in a browser to see it work. Tap Current, then Proposed.

When to use it

When to skip it

The five steps

  1. Get the page and the direction. The client's current page (a URL, or pasted HTML or text) and the new direction (colours, fonts, a reference site or a brand brief). One page, usually the home page.
  2. Put their words in once. Copy the template and replace the example with the client's words, unchanged and in order.
  3. Fill the two looks. Current gets the client's colours, fonts, corners and panel style as they are today. Proposed gets the new direction. Each look is one block of CSS custom properties, and the page reads only those.
  4. Check both. Run check.py. Every line must say PASS: same words in both looks, readable contrast in both, both buttons work, nothing loads except Google Fonts, the proposed look shows by default, it fits a phone and it prints. Then look at both looks yourself.
  5. Send it with two lines. As a link or an attachment, with a short message telling the client to tap Current and Proposed and say which one they want. Open it on your own phone first.

The two-looks skill does steps 2 to 4 for you and drafts step 5.

Mistakes to avoid

Changing the content between looks. If the proposed look also has new headlines or a new section, the client judges the words and the comparison stops being fair. Keep every word the same. Pitch copy changes separately.

Too many options. Two looks give a clear choice. A third look splits the decision and slows the yes. If you have two new directions, send the stronger one and keep the other for later.

An unreadable colour pair. Pale grey on white, or white on yellow, fails on a phone in daylight. Keep body text at 4.5 to 1 or better against its background, and large headings at 3 to 1 or better. The check fails anything lower.

A current look made worse than it is. Rebuild the client's look fairly. If they spot a straw man, they stop trusting the proposed one.

Outside images and scripts. A hotlinked image or script breaks offline, in mail previews and when the source changes. Keep everything in the one file. Google Fonts is the only outside request, and each font has a system font after it.

Calling it the whole site. It is one page. Tell the client the rest of the site follows the look they pick.

Skipping the phone test. Most clients open it on a phone. Open the link or the attachment on your own phone and tap both buttons before you send.

If scripts are blocked

Some mail apps preview attachments with scripts switched off. The page is built for that: it shows the finished proposed look and a one-line note asking the client to open the file in a browser to switch. With a link, the page opens in a full browser and the switch works.