The list of things Velora does is short, and it is short on purpose. Here is what did not survive, and why.
The daily score
Every capture, every closed loop, every protected block fed a number. The number went up. People liked it immediately and stopped looking at it within nine days, which is roughly the half-life of any metric you did not ask for.
The deeper problem was that it changed what people captured. Once a number is watching, you start feeding the number. Notes got shorter and more frequent because frequency scored well. The tool got busier and the work did not get better.
We removed it and did not replace it with a gentler version, because a gentler version is still a version.
Automatic meeting joins
Velora could sit in a call and take notes without being invited by a person, only by a calendar. It worked. It was also the single most uncomfortable thing we ever built.
The objection was not legal, it was social. Nobody in the room had agreed to it except the person who set it up. An assistant that turns up on your behalf makes a claim about other people’s consent that you are not entitled to make.
Now somebody has to press something. It is worse in every measurable way and correct in the only way that matters.
The universal inbox
An early version pulled from everything: mail, chat, documents, calendar, the lot, connected once and forgotten. The intention was to remove filing. The result was that people had no idea what the product could see.
This is the failure that shaped the context controls more than any other. If a person cannot answer the question what does this thing know about me in under five seconds, the product has taken something it was not given.
Sources are one at a time now, visible in a list, each with a switch. It is more work to set up. It is the only version anybody trusted.
Suggested replies everywhere
The draft reply is one of the better things Velora does. Putting it on every message was a mistake.
A suggestion is a small act of persuasion. Offered once, on something you were already going to answer, it saves you a blank page. Offered constantly, it starts writing in a voice that is not quite yours, in volume, and the cumulative effect is that your correspondence drifts somewhere you did not choose.
It appears now where the intent is unambiguous: a thread you have already engaged with, a message you have already opened twice. Roughly one tenth as often, and considerably more useful.
The pattern
Three of these four failed the same way. They were all features that made the product more present, and presence reads as value in a demo and as noise in a month. The fourth failed on consent.
The general lesson, insofar as there is one: an assistant is judged by the days it was not needed, not the days it was. Build for the quiet ones.