What we don't claim
Most companies publish what their product does. This is the other list — the things we could say, that would help us sell, and that we have not earned.
It is here because these are the questions you would ask on a second call, and you should not have to wait for one. Where we have not measured something, saying so is simply more useful to you than an adjective.
Memory has not been shown to improve performance
This is the big one, and it is our own favourite argument.
We can show you that Symphony's memory fills, that it holds its boundaries, and that a person stands in the path of anything being promoted to shared truth. We cannot yet show you that an agent using it performs better than one without it.
That is the claim this whole category is currently making without evidence. We will not make it until there is a method a sceptical engineer could re-run. If you ever see a percentage improvement attributed to New Medley's memory, it did not come from us.
Local models are not as capable as frontier models
Running your own model on your own hardware buys custody and continuity. It does not buy the capability of the largest hosted models. Our own testing records where smaller ones fall short.
We do not sell autonomy
Symphony is not a system that runs your business while you sleep. Consequential steps wait for a person, and a step waiting on a person stays waiting. We do not describe unsupervised operation as a feature, because we do not think it is one.
Not every part of the suite can see the page you are on
Working on a page together — where you and the agent are looking at the same thing at the same moment — is the embedded web widget. Our desktop team client does not do this yet. It is meant to, and it is not built.
We flag it because it is the feature we are proudest of, which is exactly when it would be easiest to let you assume it is everywhere.
Taking your data with you — committed, not yet specified
You will be able to export your work in a format you can load somewhere else. That is a decision, not an aspiration: if you leave, your data leaves with you.
What we have not settled is the shape — a portable file format, and likely a way to map our field names onto whatever you are importing into, so the export arrives in your vocabulary rather than ours. We would rather tell you it is undecided than describe a mechanism we have not designed.
We will not be difficult about it. A company that makes leaving expensive is telling you what it thinks of its own product.
We have no security certifications
No SOC 2, no ISO 27001. Not "in progress" — none. We would rather say so than let a silence do the work of an implication.
We have not published outcome numbers
No hours saved, no cost reduction, no return on investment. We have not run the study. When we do, it will come with its method.
Symphony is not finished
It is pre-release. Parts of what we have designed are specification rather than shipped software, and we will tell you which is which when you ask.
We do not describe other companies' products
We compare what a category tends to make easy or hard. We have not tested anyone else's system, so we do not characterise it.
Something leaves this list only when the evidence arrives — with a method, a date and a source. Nothing leaves it because it became inconvenient, and nothing leaves it because a competitor started saying it.