Company operating system
Not an ERP with departments bolted onto the ledger. Not five products sharing a spreadsheet. CompanyOS is one identity, one chart of accounts, and one permission model — so a hire, a shipment, and an invoice are the same company.
No credit card to start. Every module included. Subscribe when the trial earns it.
In one login
HR lifecycleSKR03 ledgerCRM & emailSales to cashLogisticsR&D gatesManufacturingAI employeesThe distinction
CompanyOS is built as an operating system: a kernel of identity, permissions, documents, and the ledger, with departments as modules on top — not as separate products that have to be integrated afterwards.
Typical ERP
Finance was the product. HR, CRM, and manufacturing arrived as licensed modules. You still implement for months, still train people on a UI designed for accountants, still pay again when a new department needs to exist.
The modern stack
Personio for people. HubSpot for pipeline. Slack for talk. Jira for work. DATEV for the close. Each tool is competent. None of them share an employee, a customer, or a permission. Friday is for reconciliation.
CompanyOS
A hire creates onboarding, access, and a payroll line. A quote becomes an order, a shipment, an invoice, and a posting. AI employees work inside those same permissions — they cannot see what that role cannot see.
A single example
In a stack, this is six products and a shared drive. In CompanyOS it is one record moving through the company — which is what an operating system is for.
01
A position exists in the org. Hiring opens against it.
02
Candidates enter a pipeline. The Recruiting Assistant ranks; a person decides.
03
The employee record is the same person who will later file leave and appear on payroll.
04
Onboarding run, learning path, channels, and the access that role is allowed.
05
Tasks, projects, and time sit on that identity — not a second user in another app.
06
Payroll and DATEV Lohn export from the same record. Offboarding revokes the same access.
The system
Open any one of these and you are still in CompanyOS: same people, same customers, same books, same audit trail. That is the difference from a suite that was acquired into existence.
Hiring, candidates, onboarding, learning, reviews, leave, OKRs, and the payroll handover live on one record. When someone joins, they receive a role, a checklist, a learning path, and the access that role is allowed — not a ticket in another system.
AI Center sits beside these modules — it does not replace their permissions.
AI Center
AI in CompanyOS is not a sidebar that summarises the page you are on. You hire AI employees into a department, give them a supervisor who already has access, and set how independently they may act. They work the same records as everyone else — and they are forbidden from the work a person must still do.
Human resources
Reads every application against the role you posted, quotes the evidence, and ranks the pipeline. It never rejects anyone, never emails a candidate, and never sees name, photo, age, or nationality — those are redacted before the model does.
Independence: observe or assist. A person decides who progresses.
Finance
Reads invoices, proposes an SKR03 account, and packs the quarter for a Steuerberater. It does not file, does not contact an authority, and does not give tax advice. A person confirms; the assistant prepares.
Built for German books — flags Bewirtung, GWG, gifts, missing VAT IDs.
CRM AI reads inquiry mail. Invoice AI works purchase invoices. Bank AI matches statements. Each gadget has a work scope you set in AI Center — once, or continuously — and it cannot outrank the permission of the person who started it.
Platform
Suites hide this layer because it was assembled. CompanyOS starts here, which is why a new department does not require a new vendor.
Employees, AI employees, and customers are not three user directories. Access follows the role.
Page-level access, requests, and an audit log. Supervising an AI employee cannot bypass hiring or finance access.
SKR03, bank matching, tax settings, a quarterly filing pack, DATEV Buchungsstapel and Lohn export.
Customers see what they are supposed to see — without a second CRM and a shared inbox.
Tasks, leave, expenses with receipts, helpdesk, and broadcasts. Face ID on device. Work continues away from the desk.
Departments, positions, products, and structure are first-class — not a settings dump after go-live.
Side by side
| Typical ERP | Tool stack | CompanyOS | |
|---|---|---|---|
| What it was built around | The general ledger | Whatever you bought first | The company: people, work, money, operations |
| Identity | Users per module, SSO later | One login per product | One employee. One permission model. |
| A customer | CRM add-on, if licensed | HubSpot ≠ invoicing ≠ support | Lead, quote, shipment, invoice, ticket |
| The books | The product, in 1998’s UI | DATEV / Xero beside everything else | SKR03 ledger, bank, tax pack, DATEV export |
| AI | A chatbot on top | A copilot in each tool | Hireable employees inside the same permissions |
| How you pay | Per module, plus implementation | Per seat, times N subscriptions | One plan. Everything included. |
Pricing
No modules to unlock, no implementation SKU, no per-seat add-on for AI. You pay per employee. Everything in CompanyOS is on.
Example monthly cost
Included
14 days free · No credit card to start · Subscribe from Company account
Fourteen days, every module, no card. If the trial does not replace a stack, do not subscribe.