Every vendor describes its product at its best. We would rather describe ours as it is, because you will find out during deployment anyway, and it is cheaper for both of us if you find out now.

Internally we use four words for the state of any part of the system: deployed, available but unconfigured, in development, and specified. They mean what they say. Deployed means it is running in a real building with real records in it. Specified means the design exists and the code does not.

Deployed and in daily use: the records core, the folder structure of twelve departmental areas and eighty function folders, the tagging scheme, permission-filtered search, the approval object, and the reporting templates. There are 28 templates across eight categories, built to the Data Collection Instrument structure that funders already recognise.

In development: the conversational layer. It is not shipped. Do not buy on the strength of it.

Specified but not implemented: multi-entity operation, replication between sites, and the external connectors to other systems. If your plan depends on any of those, the honest answer today is that you would be waiting.

Two more things worth saying out loud. Backup is a written arrangement made at deployment, not a switch that is on by default, so it gets agreed and documented rather than assumed. And our SOC 2 Type II observation window is open, which means the report does not exist yet. When it does, we will say so here.

None of this is a reason not to start. It is a reason to start with one department, in one building, with a scope that matches what actually runs.