← Back to Newsletters

🦄 Prototype to learn, build when it matters

April 22, 2026

Hey again 👋

Polish can flatter you a bit, its great doing the little things like a nicer click, a convincing prototype, a shorter form, all useful. But only useful if you're clear on what you're actually trying to prove before you ship anything.

A little bit of a dive into this and what you can do to get some REAL work done at the level that matters.

Enjoy 🦄 - Adam at Unicorn Club.

Managed WordPress Hosting You'll Fall in Love With

Upgrade to autoscaling WordPress hosting for always-on, always-fast performance, backed by award-winning support. See the difference and try us out for only $1.

Try 20i now →

Ideas to think about:

Shape: Prototype for learning, ship code for proof

Build: Tiny motion tweaks can make a click feel real

Ship: Friction is not the whole conversion story

Top 3 this week 👇

Adam's Breakdown, Shape:
Build to Learn vs Build to Earn ↗

Prototype for evidence, ship code only when the bet changes.

It's not about "prototyping more", it's being honest about what kind of proof you need before you build the durable version.

This is usually where it gets messy. A prototype gets made, then before you know it, it starts turning into half-real product work. Then you ship something and still talk about it like it's just a test. Hard to tell what you actually learned and what you've just made bigger.

Why this matters: The split is really about proof standards. You need to learn with cheap artefacts, and then earn with durable ones, and do not pretend one kind of evidence covers the other.

What I'd steal: Before kicking off anything, put this question on the brief: are we trying to learn if this works, or earn from it at scale?

Build: Squash and Stretch ↗

Tiny motion tweaks make buttons feel physical, not decorative.

Why: Josh stretches the base state and squashes the press state, so the click feels like it actually lands. Tiny thing, but it stops the motion feeling decorative.

Adopt: Try it on one button first. Then check reduced motion still feels fine, otherwise the nice bit turns into cleanup later.

Ship: Why CRO Is So Difficult ↗

Most conversion wins die in the messy middle.

Why: Tiny lifts disappear when intent is weak and the test never really hits the deciding moment.

Adopt: Look for the bit where someone is wavering, not just where the form gets longer.

Dive into more

Build: Personal website redesign project post: Completing the WordPress headless CMS integration ↗ Reminder to get the structure boring first, then mess with polish.

Shape: I don't want a screenshot of your Claude conversation ↗ Not anti-AI, just anti-outsourcing your thinking.

Shape: Multi-agent coordination patterns: Five approaches and when to use them ↗ Good if you're tempted to overbuild agent systems before you've even proved a single-worker flow can carry the job.

Ship: Building Todoist Ramble: How Doist Turned Voice Braindumps into Real-Time Task Capture ↗ Capture first, correct easily, leave execution for later.

Support the newsletter

If this was useful, here are two small ways to help it travel:

🚀 Forward to your team

📢 Book a Sponsorship

Thanks for reading

Adam from Unicorn Club

Follow me on X or BlueSky

Connect on LinkedIn