Best polished version strategy

Strategy named in sail-muddy-lessons. You wait until a category is mature, the data models and use cases are clear, novelty is no longer interesting, and you ship the polished, opinionated version of the thing. People don't want a new paradigm — they just want this one done well.

When it works

The existing tool has to be bad enough that switching is justified despite the friction.

• Linear vs Jira — Jira is widely hated. The delta is large enough that whole teams switch.
• Vercel vs the previous frontend DX — the previous workflow was painful enough that "deploy on push" felt like a category shift even though it was a polish play.

In both cases the founders had earned the right to one-shot. Karri Saarinen at Linear had Kippt, Coinbase, and Airbnb behind him. He'd already built a Chrome extension at Airbnb to restyle Jira — he had a clear, specific picture of what "polished" meant before starting.

When it doesn't

The graveyard of "better Slack" attempts:

• Campsite — async-first team communication, ~$5M from Lux Capital, wound down in 2024
• Quill — ~$7.5M from a16z, genuinely better threading and notifications than Slack, acqui-hired by Twitter in 2020
• Threads (not Meta's) — thread-centric communication, ~$10.5M from Sequoia and a16z, acquired by Shopify in 2021
• Browser Company / Arc — better Chrome, eventually pivoted away to Dia

The diagnosis is the same in every case. Slack is good enough. Chrome is good enough. The pre-existing integrations, network effects, and a thousand papercuts that everyone has learned to live with all add up to switching cost. A "merely better" version doesn't clear that bar.

The combined-friction trap

Sail/Muddy made it worse by trying to replace Chrome and Slack at once. The combined switching cost from "I'd have to change browser AND chat" was unsurvivable. Pick one defended position to attack at a time.

The Notion observation

Aspirationally Notion is "tool for thought." Operationally it's the polished version of three known categories at once: wiki, docs, project tracker. That's why it works as a "best polished version" play — the simple description is plural but every plural is a known category.

Related

• positioning-vs-vision-gap — the simple description always wins
• multiplayer-by-default-failure — adding multiplayer doesn't justify the switching cost on its own
• i-dont-want-your-prs — another post-attempt rethink of working on the wrong layer