# Positioning vs vision gap

Concept named in [[sail-muddy-lessons]] as the structural reason ambitious "future of computing" startups keep failing at the marketing layer regardless of how good their product is.

## The mechanism

Every product in this space gets reduced by users to a one-line analogy:

- Arc → "pretty browser with a more organized sidebar"
- Mighty → "fast Chrome on the cloud"
- Sail → "Miro but with websites"
- Rabbit R1 → "Android phone reskinned with AI"
- Humane AI Pin → "clip-on accessory with a camera"

The grand vision ("new kind of personal computing," "metalayer for collaboration," "multiplayer browser") is great for recruiting and high-level marketing. It does not survive contact with users. There's a gap between what you want people to do, what you want people to say, what people actually say, and what the thing actually is.

## What works underneath

Notion is the example Alejandro keeps coming back to. Aspirationally a "tool for thought." But the use cases people actually describe — wiki, docs tool, project tracker — are pre-existing categories Notion can plug into. The aspirational vision lives underneath a use case people already understand. That anchor is what most of the failed companies (including Sail) didn't have.

This is also why "build your own workspace" framing fails. It puts the work of describing the product on the user. Users don't want to compose primitives — they want to know what the product does for them.

## Two diagnostic tests

From the same source, applied early enough to matter:

1. **Landing page test** — write the actual landing page that has to sell to a stranger. Not a pitch deck. If you can't fill it, you don't know what you're building yet.
2. **Sandwich Video test** — imagine the [Slack-style launch video](https://www.youtube.com/watch?v=B6zVzWU95Sw) for your product. What scenes? What's the story? If you can't picture it, that's a signal.

## Related

- [[multiplayer-by-default-failure]] — most of the same companies also got hit by this
- [[best-polished-version-strategy]] — the "we'll just be better than Slack" framing that doesn't survive switching cost
- [[purpose-driven-vs-system-driven-design]] — system-driven design makes positioning harder because primitives don't sell