Simple products are often the hardest to explain
The problem with a simple product is that people often think they understand it as soon as they recognise the category.
For Tansei, that category is clipboard manager. And that comparison is accurate, up to a point.
Tansei is about the things you copy. The difference is what happens next.
Most clipboard managers are built around history: finding something you copied earlier. Tansei is built around the few things you’re using right now. A snippet, a screenshot, a colour, a link. They stay visible and within reach until you’re done with the task.
That sounds like a small distinction, but for a narrow product, the small distinction is often the whole product.
The category gets people close. The moment explains the rest.
This has been the most useful positioning lesson for me.
You need the familiar comparison because it gives people a shortcut. But if you stop there, they fill in the rest themselves.
What works better is describing the moment the product is for.
You’ve copied some code, a hex value and a link. You need all three for the next twenty minutes. Where do they go?
That tends to explain Tansei much faster than adding more words to the product category.
I think this applies to a lot of small products. Builders naturally want to explain what the product is, but users are usually trying to work out when they would need it.
More features can blur the distinction
Once I started showing Tansei to people, I got the obvious suggestions: add AI, summarise things, group related items, categorise them, predict what I might need next.
Some of those features could be useful. They would also change the reason I built the app.
If I put something on the shelf, I want it to stay where I left it until I move it. If the software starts rewriting, reordering or organising things for me, I have to start watching what it is doing.
At that point, it has stopped holding my context and started becoming another piece of context I need to manage.
There are products where intelligence is the feature, but there are also products where predictability is the feature.
That has become a useful filter for me when deciding what to add. Not just “would this be useful?”, because almost anything can be useful to someone.
A better question is:
Does this make the reason the product exists clearer, or does it blur it?
For a simple product, that distinction matters more than the length of the feature list.
I’m building Tansei, a Mac app for keeping the things you’re actively copying and using within reach while you work.
macOS 15+ · Apple Silicon · 3-day free trial · $7 once
https://tansei.io
If you’re building something narrow, what familiar category gets people close to understanding it, but not quite there?
"Products where intelligence is the feature, and products where predictability is the feature" is the best line I've read on IH this week, and "does this make the reason it exists clearer or blur it" beats most roadmap advice. You've got positioning figured out.
One add: "describe the moment" is a targeting filter, not just a clearer explanation. "Copied a hex, some code, a link, need all three for 20 minutes" names who you're for and who you're not. Describe the category, everyone thinks "I have a clipboard." Describe the moment, the right person thinks "that's my Tuesday" and the wrong person opts out. That opt-out is a feature.
The category that gets people close but not quite is the one that shares your noun but not your verb.
The noun and verb line: everyone files Tansei under clipboard manager, because we share the noun. The copied stuff. But the verb is different. A clipboard history remembers so you can dig something back out later. A shelf holds what you are using right now, in view, until you are done with it. Remember versus hold. Every time someone asks "how is this different from Paste," the honest answer is that we share a noun and nothing else.
"Remember versus hold" is now more than a tagline — it's the roadmap filter you were reaching for in the post itself. You said the useful question is "does this make the reason it exists clearer or blur it." The verb tells you which features blur, not just that some do: anything that serves remember is somebody else's product wearing your clothes.
Watch it sort your own suggestion list. AI summaries, grouping, categorising, predicting what's next — every one of those is a remember-verb. They all assume a pile you dig through and organise. On a shelf holding four things you're using right now, there's nothing to summarise and nothing to predict; you can see all of it. Those features aren't wrong, they're for the other product, the one that shares your noun. The suggestions were people pattern-matching you to the category you're trying to escape, and now you have a one-word test for spotting it: does this help me hold, or does it quietly turn me back into a thing that remembers.
Which means the strongest thing you can do is refuse well. Every remember-feature you decline is you defending the verb. What's the one feature request that was hardest to say no to — the one that sounded useful right up until it turned Tansei back into a clipboard?