Skip to content

Use cases

Not what it is. What you would do with it.

Each page here takes one job a team actually has — running an incident, onboarding a colleague, keeping a board discussion confidential, recording hours against client work — and follows it from the situation through the sequence to what Enclessa will not do about it. These are tasks rather than industries: if you are looking for whether Enclessa suits a hospital or a public authority, the solutions pages answer that question instead.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

At a glance

Shape
One job per page, start to finish
Not
Industry pages — those are the solutions cluster
Each page ends with
What it will not do
Modules
Named where a job needs one
Start on
The Free plan, for four of the eight

Eight jobs, followed all the way through

Every page names the plan the job needs and the feature pages carrying the detail.

Use cases or solutions?

A use case is what you are doing; a solution is who you are. Both exist because the same product has to answer two different questions, and answering them on one page answers neither well.

  • Use cases describe a task: the situation, the sequence, and the limits of it.
  • Solutions describe a sector: its constraints, its regulator, and what the product does about them.
  • If you are evaluating whether Enclessa is legal and appropriate for your industry, start with solutions.
  • If you know it fits and want to see the work happen, start here.
See the industry pages

Related

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Open beta. Free plan, no payment card to start.