Knows the context
Company knowledge connects to areas and sources. Your team starts with a question, not a search for the right file.
For businesses with around 15 employees or more
You lead your company.
Not its everyday tasks.
Plural.OS maps your business: who is responsible for what, which knowledge belongs where and what can run without asking. So the business carries its share of the everyday work.
Demonstrated in our own company. No slides.
Running internally. Being built for client teams.
Your leadershipDirection, judgement, approval
Plural.OS
The structure of your businessCompany knowledge
Accounting
Order management
Quotes
Deadlines
Oversight
PeopleA separate, restricted area
3of our own legal entities
Since May 2026in daily internal use
Every montha close across all entities
As your company grows
A bigger business needs more than your oversight.
Where documents live. How an exception is handled. Which deadline comes first. In a small team, a quick conversation works. As the business grows, that knowledge needs a permanent home.
Your judgement stays essential. Your presence for every everyday question does not.
This is about a business that keeps working while you are leading something else.
The principle
More than a place for files. A structure that works.
A responsibility knows its area, its routines and its boundaries. It works without prompting where agreed, and answers when your team needs it.
Takes care of routines
Recurring work has a responsibility. Missing information and unclear cases become visible and reach the right person.
Knows its boundaries
You assign responsibilities. Access follows from them. Accounting sees receipts and bank data, not personnel files or confidential order records.
You assign responsibilities, not permissions. Access follows from the responsibility.
How a working week can change
Less depends on one person. More stays in the business.
The question finds its answer.
«How did we handle this on the last order?»
Company knowledge connects the question to approved documents and identifies the source.
Illustrative workflow
- A question from the team
- An approved source
- An answer with its source
What changes
The answer does not depend on who remembers or who is in the office.
Work starts without a prompt.
«Which deadlines are coming up, and which documents are missing?»
The responsibility checks dates and flags what needs attention internally. Any message outside the business stays with a person.
Illustrative workflow
- An agreed routine
- Deadlines and documents
- An internal notification
What changes
The routine has a responsibility. You do not need to initiate every check.
The business becomes traceable.
«What happened this week, and where is knowledge still missing?»
Oversight summarises routines, activities and knowledge gaps. It does not evaluate individual employees.
Illustrative workflow
- A record of activities
- Oversight
- A weekly review
What changes
You see where the structure needs support, without following every task yourself.
For your team
Sharing knowledge requires trust.
Your team asks questions, requests work and shares knowledge. One input field, answers with sources and visibility of their own tasks. No rankings. No hidden performance monitoring.
No evaluation of individuals.
The weekly review shows processes and knowledge gaps. Not who asks the most questions or works the fastest.
Personnel stays separate.
Salaries and personnel files belong in a separate area. Neither company knowledge nor an assistant to management gets access.
You stay in control
Defined freedom. Firm boundaries.
Approvals apply to types of process. Each routine knows whether to run, present its work or ask first.
Runs independently
Approve it once, then it runs without asking again.
Internal, reversible work such as recording, reconciliation and deadline checks.Presents for approval
The work is ready. A person confirms.
Quotes, correspondence and anything with a recipient.Asks first
Permission first. Then work begins.
Unusual activity, new clients or agreed amount thresholds.Nothing goes outside without a person.
No email to a third party. No file sent externally. No payment. This boundary cannot be switched off.
The evidence starts with us
We run our own three companies this way.
Since May 2026, the building blocks have been in daily use across the Averion group. Each month, we close across all three legal entities without a separate run.
We can demonstrate these workflows live
- Monthly close across three legal entities
- Daily bank-file conversion
- Recurring group invoices
- Quotes from questionnaires in our own layout
The responsibilities
Your business has distinct areas. So does Plural.OS.
The first set of responsibilities was built for accounting firms. Here it is shown in industry-neutral terms. For other industries, we review what fits and what needs adapting together.
Core
Accounting
- Has access to
- Receipts, bank files and closing documents
- Takes care of
- Record receipts and reconcile payments.
- The boundary
- Never initiates payments. No connection to accounting software in the first version.
When something is unclear: A person you appoint decides.
Core
Order management
- Has access to
- Order records, deadlines and correspondence
- Takes care of
- Support ongoing work and prepare correspondence. For accounting firms: client engagement management.
- The boundary
- Can prepare drafts. Never sends without a person.
When something is unclear: A person you appoint decides.
Core
Company knowledge
- Has access to
- Approved knowledge across business areas
- Takes care of
- Answer questions about the business and identify the source.
- The boundary
- Reads and answers. Changes nothing. Cannot see personnel or confidential information.
When something is unclear: A person you appoint decides.
Optional
Quotes
- Has access to
- Service catalogue, pricing rules and previous quotes
- Takes care of
- Prepare a quote according to your rules.
- The boundary
- Can prepare a draft. Never sends without a person.
When something is unclear: A person you appoint decides.
Optional
Deadlines
- Has access to
- Dates, filing deadlines and calendars
- Takes care of
- Check deadlines and flag missing documents internally.
- The boundary
- Internal notifications are possible. Never sends reminders externally without a person.
When something is unclear: A person you appoint decides.
Being defined
People
- Has access to
- Personnel files, salaries and absences
- Takes care of
- The specific routines are still being defined.
- The boundary
- A separate access level. Invisible to every other responsibility.
When something is unclear: A person you appoint decides.
Always included
Oversight
- Has access to
- The work of the other responsibilities
- Takes care of
- Show activities and knowledge gaps in a weekly review.
- The boundary
- Cannot be disabled. Never evaluates individual people.
When something is unclear: A person you appoint decides.
Four questions set up a responsibility.
- 1Which area?
- 2Who can request its work?
- 3Who decides when something is unclear?
- 4How far can it go without asking?
Data and traceability
Trust comes from boundaries. Not grand promises.
This is the separation planned for the product. What works internally is being developed further for use with client teams.
Access before answers
Business areas determine which material can inform an answer. Separation is designed to happen in the data layer, not as a request in a chat.
Content stays content
Documents and emails are sources, not instructions. External material is processed separately, without tools.
A complete record
Requests, tool use and approvals should be traceable. This is why oversight is always included.
Your knowledge stays usable
A complete export in readable files is part of the product model. No lock-in through a proprietary file format.
In normal operation, Averion sees system health, errors and usage, not client data. Access may be necessary during an escalation.
Manipulation through injected content is not a solved problem for language models. We do not claim complete security.
The model provider and data processing arrangements have not yet been finalised. Contractual and legal requirements must be resolved before setup and operation with client data.
Set up once. Operate with support.
Configured for your business. Supported in everyday use.
Plural.OS is not an empty software subscription. We assign responsibilities, connect your document sources, define roles and boundaries, and introduce your team.
01 / Setup
CHF 4'000 to 8'000
one-off, excl. VAT
The business assessment is included in setup.Setup maps your business, and every business has a different scope. Four areas with clear routines are a different task from twelve with accumulated exceptions.
The price is fixed after the first conversation. A number, not an estimate.
- Assess your business
- Assign responsibilities
- Connect document sources
- Define roles and boundaries
- Introduce your team
02
Then the business runs. We stay involved.
Updates, new routines, approval adjustments, escalations, training for new employees and new responsibilities are covered by the support hours.
Basic
CHF 690
per month, excl. VAT
2 hours of supportThe plan you move to once things are running smoothly.
Standard
Your first-year starting planCHF 1'490
per month, excl. VAT
6 hours of supportThe starting plan in your first year. Everything is new at the beginning.
Intensive
CHF 2'190
per month, excl. VAT
10 hours of supportFor many business areas and frequent changes.
The questions behind the decision.
How is this different from an AI chat?
An empty chat window knows neither your business nor its responsibilities. Plural.OS maps areas, sources, routines and approvals. It is designed to retain context and initiate agreed work itself.
Does Plural.OS replace our specialist software?
No. Plural.OS works across areas and document sources; it does not replace specialist applications. A direct connection to accounting software is not part of the first version.
Does it work outside accounting firms?
The model is industry-neutral. The first set of responsibilities was built for accounting firms. We do not claim to have a finished set for every industry; we review and develop it with the first clients.
Is our business large enough?
The model is aimed at businesses with around fifteen employees or more. If it is too much for your business, we will tell you in the first conversation, before you pay.
Is Plural.OS finished?
The building blocks have been in daily use in our own three legal entities since May 2026. The product for client teams is still being built. Role separation, self-service and tenant separation in operation are under development.
Can we leave later?
The product model includes a complete export in readable files. The subscription can be cancelled with three months’ notice after the first six months.
How long does setup take?
That depends on the areas, document sources and exceptions in your business. We agree the process in conversation, rather than publish a universal timeline we cannot yet substantiate.
See it first. Then decide.
Look inside a business that already works this way.
We will show you Plural.OS in our own company and explore whether the approach fits your business.