The operating system for software companies
Know what is happening in your company. Without asking anyone.
CompanyOS connects people, projects, time, money and processes in one system. The picture of your company is always current, and the routine runs itself.
- 23 modules
- One identity
- Microsoft 365 · Git
01 What it gives
What it gives you. And everyone around you.
Pick a role, from the director to a new engineer, and see what changes for them and for the company as a whole.
Director
A live picture of the company and fewer surprises.
-
See everything without asking for reports
Today
Status meetings, Friday spreadsheets and three versions of the numbers
With CompanyOS
One live picture of people, projects, time and spend, always current
-
Spot risks before they cost money
Today
You hear about the slipping project or the overloaded team last
With CompanyOS
Early signals: project risk changes, overtime, pulse drops, budget drift
-
Grow without growing overhead
Today
Every new team means another coordinator and more spreadsheets
With CompanyOS
Onboarding, approvals, leave and timesheets run on rules, not on people
What you get Decisions in minutes, with the evidence attached.
Manager
Your team in one view, approvals in one place.
-
Approve in one click, with context
Today
Requests scattered across chat, email and forms
With CompanyOS
One queue with coverage, balance and project impact next to every request
-
Know how your team is really doing
Today
Overtime and burnout show up when it is already too late
With CompanyOS
Timesheet deviations, absences and pulse signals in your home every morning
-
Prepare a 1:1 in seconds
Today
Digging through notes and trackers before every conversation
With CompanyOS
A brief of what changed since the last talk, inside your permissions
What you get Less admin, more time for the team.
HR
Processes that run themselves, people who feel looked after.
-
Onboarding without checklists
Today
Spreadsheets, reminders and a laptop that arrives on day three
With CompanyOS
Journeys with owners and deadlines: documents and equipment ready before day one
-
One source of truth about people
Today
Employee data copied between the HR tool, spreadsheets and finance
With CompanyOS
One profile used by every module, with field level privacy
-
Hear the team
Today
Surveys in a separate tool that nobody connects to anything
With CompanyOS
Pulse checks tied to real teams, next to the rest of the data
What you get Less routine, more time for people.
Finance
Numbers you can trust, without chasing anyone.
-
Timesheets that close themselves
Today
Chasing managers for hours at the end of every month
With CompanyOS
An approved, versioned timesheet handoff ready for billing
-
Spend under control
Today
Office purchases and licences discovered on the card statement
With CompanyOS
Budgets with approval above a threshold and licence renewals in view
-
Compensation without spreadsheets
Today
Salary reviews in files that travel by email
With CompanyOS
Review cycles inside the system, visible only to those who should see them
What you get Month end without the chase.
Office
The office runs on a plan, not on memory.
-
Know what runs out before it does
Today
Coffee, paper and merch tracked in a spreadsheet, or not at all
With CompanyOS
Stock with a run out forecast and a suggested reorder
-
Events without the chaos
Today
RSVPs in chat threads and the headcount guessed for the pizza
With CompanyOS
Events and rituals with RSVP, budget and calendar in one place
-
Purchases with clear rules
Today
Every purchase is a message to the director
With CompanyOS
Approval only above the budget threshold, everything else simply flows
What you get Fewer fires, more time for the team.
Employee
Everything about my work in one place.
-
Requests in seconds
Today
Asking HR in chat how many leave days are left
With CompanyOS
Balance, request and approval status on one screen
-
Answers without waiting
Today
Searching the wiki and waiting for someone to reply
With CompanyOS
Ask the knowledge base and get an answer with sources
-
Clear next steps
Today
Deadlines missed because the reminder was buried in chat
With CompanyOS
One home that shows what needs you this week
What you get Less bureaucracy, more real work.
Company
One system instead of a patchwork of tools.
-
One version of the truth
Today
Data copied between a dozen tools and reconciled by hand
With CompanyOS
One data model and one identity shared by every module
-
Lower cost of ownership
Today
A subscription per process plus the people who glue them together
With CompanyOS
One platform, modules switched on as you grow, routine automated
-
Security and audit by default
Today
Access in ten places and offboarding that misses a few
With CompanyOS
Explainable permissions, one audit trail and encrypted backups
What you get A company that scales calmly.
02 The problem
Twelve tools. Twelve logins. Twelve versions of the truth.
A growing software company ends up running on a patchwork: an HR system, a leave tracker, spreadsheets for time and office budgets, a helpdesk, a wiki, chat threads and forms. Every handoff is a copy and paste. Every report is a reconciliation.
12 tools to keep in sync
1 system that stays in sync
- People
HR system - Leave
Leave tracker - Timesheets
Timesheets.xlsx - Cases
Helpdesk - Knowledge
Wiki - Communications
Chat threads - Automation
Request forms - Assets
Asset register - Surveys
Survey tool - Office
Office budget.xlsx - Organization
Org chart.pptx - Documents
Shared drive
One system that knows how your company is connected.
A leave request already knows the project, the team coverage and the timesheet norm. An onboarding already knows the laptop, the documents and the first week. Context arrives before anyone asks for it.
03 Why CompanyOS
Not another tool on the pile.
Most products digitise one department. CompanyOS is built around the company as a whole, so every module makes the others smarter.
- 01
One context instead of twenty integrations
People, teams, projects, time, assets and documents live in one model with one identity. Nothing to sync, nothing to export, no reconciliation on Friday.
One identity · one data model · 23 modules
- 02
A home for every role
Employees, managers, HR, office and finance each open a home built around their real questions: what needs me, what changed, what is at risk.
Role experiences · attention rail
- 03
Access you can explain
Permissions are scoped to self, team or company, down to single fields. Every decision can be explained, and a nicer screen never grants access by accident.
Scoped and field level policies
- 04
Automation from approved blocks
Connect events across modules in a visual builder. When leave is approved, tell the team in Teams and adjust the timesheet norm. No scripts, no shadow IT.
Visual builder · templates · run journal
- 05
AI that proposes, people decide
Agents prepare a 1:1, summarise project changes or answer from your knowledge base. Every action they suggest waits for a person and lands in the audit log.
Claude · OpenAI compatible · tenant AI policy
- 06
Built for how IT companies work
Projects, timesheets with a finance handoff, Microsoft 365, Git, hiring and onboarding. The daily reality of a software company is the default, not a customisation project.
Teams · Git
04 Experiences
One system. A different home for every role.
The same data, shaped around the questions each person actually has. Pick a role.
Hi Taras
2 things for you this week
- Timesheets
Timesheet for week 43
- Leave
Leave balance
- Office
Team lunch on Thursday
- Documents
Security policy updated
Time logged this week
32 h
of a 40 h norm
Good morning, Olena
4 things need you today
- Leave
3 approvals waiting
- Growth
1:1 with Maria is overdue
- Projects
Project Atlas
- Leave
Team coverage next week
Team availability next week
83%
1 person on leave
Good morning, Iryna
5 people need attention
- People
2 onboardings start Monday
- Growth
Probation ends for 3 people
- Surveys
Pulse survey
- People
Offers accepted
Headcount
148
+4 planned this month
Hi Kateryna
3 things are on fire
- Office
Coffee beans run out in 4 days
- Office
Purchase over budget
- Office
Friday ritual
- Office
Merch stock
Office budget used
82%
of October
Good morning, Dmytro
2 handoffs ready
- Timesheets
Timesheet handoff · October
- Compensation
Compensation review
- Assets
Software licences
- Office
Office spend
Billable hours in October
18 940
approved and locked
Good morning, Serhii
What changed this week
- Projects
2 projects changed risk
- Surveys
Company pulse
- People
Hiring
- AI
Weekly brief
People
148
across 11 teams
05 Modules
Twenty-three modules. Switch on what you need.
Start with the core and add the rest when your company is ready. Every module shares the same people, permissions and audit trail.
-
Directory and employment profiles that every other module builds on.
- Employment profiles
- Onboarding and offboarding journeys
- Field level privacy
-
Structure, teams and reporting lines that drive approvals and access.
- Org chart and teams
- Reporting lines
- Manager scopes
-
Requests, balances and team absences with coverage in view.
- Policies and balances
- Team absence calendar
- Approval with coverage check
-
Packages and review cycles, visible only to those who should see them.
- Compensation packages
- Review cycles
- Restricted field access
-
Performance and growth conversations that keep their history.
- Goals and reviews
- 1:1 preparation
- Growth history
-
Benefit programmes and enrolment without a spreadsheet.
- Benefit catalogue
- Enrolment
- One place for every programme
-
Pulse checks and surveys tied to real teams and people.
- Pulse checks
- Audience by team
- Response tracking
-
A project workspace with people and health signals.
- Project workspace
- Health and risk signals
- People on the project
-
Git repository insights for projects from GitHub and Bitbucket.
- GitHub and Bitbucket links
- Commit and PR insights
- Project scoped visibility
-
Project time entries, approvals and a versioned handoff to finance.
- Entries and norms
- Manager approval
- Finance handoff
-
Personal work hub: tasks, calendar and a time tracker that records into Timesheets.
- Tasks and board
- Personal calendar
- Time tracker into Timesheets
-
Requests and queues for HR, IT and office, with clear owners.
- Request queues
- Owners and statuses
- Automation triggers
-
A knowledge base people can ask questions of, with sources.
- Articles and spaces
- AI answers with sources
- Permission aware search
-
Company and employee documents in one governed library.
- Document library
- Employee documents
- Access by policy
-
Announcements to the right audience by email, Teams or SMS.
- Targeted announcements
- Email, Teams and SMS
- Delivery history
-
Supplies, purchases, budgets, events and rituals instead of the office spreadsheet.
- Stock with run out forecast
- Purchases over budget need approval
- Events and RSVP
-
Company shop, gift events, stock, logistics and payroll deductions in one place.
- Employee shop and event landings
- Fulfillment board and purchases
- Finance and payroll handoff
-
Laptops, equipment and software licences, assigned to people.
- Asset inventory
- Licence tracking
- Assignment history
-
Reports across modules with exports, from one data model.
- Cross module reports
- PDF and data exports
- Scoped to your access
-
Encrypted, scheduled company backups with a guarded restore.
- Encrypted schedules
- S3, Google Drive or email
- Restore with safeguards
-
Sign in with Google, Calendar, Meet, Drive, Directory and Gmail inside CompanyOS.
- Sign in with Google
- Calendar and Meet
- Drive, Directory and Gmail
-
Connections to Microsoft 365, Git and webhooks, plus the automation builder.
- Connector catalogue
- Visual automation builder
- Run journal
-
Agents that prepare, summarise and propose inside your permissions.
- Role aware agents
- Approval before action
- Tenant AI policy
06 Automation
Processes that run themselves, within rules you approved.
The automation builder connects events from every module. Admins assemble flows from approved building blocks, test them and see every run in a journal.
- 01
Triggers from leave, people, projects, timesheets and documents
- 02
Conditions, schedules and date rules
- 03
Actions in Teams, email and webhooks
- 04
A run journal that records every step
When
Leave approved
If
Three days or longer
Then
Notify the team channel
Then
Adjust the timesheet norm
Then
Add to the office calendar
Run journal · 4 steps · completed
07 AI with guardrails
AI does the groundwork. People make the call.
Agents work inside your permissions and your data. They prepare, summarise and propose. Nothing changes until a person approves.
- 01
Inside your permissions
An agent sees only what the person asking is allowed to see.
- 02
Proposals, not surprises
Suggested actions wait for approval and are written to the audit log.
- 03
Your models, your policy
Claude or any OpenAI compatible model, under a company AI policy with usage tracking.
- 04
Defended by design
Prompt injection checks guard every request that touches company data.
08 Integrations
Works with the tools you keep.
CompanyOS replaces the patchwork, not the systems your engineers love. It connects to Microsoft 365 and your Git provider, and talks to the outside world through email, SMS and webhooks.
Identity and sign in 04
- Microsoft Entra ID Available Single sign on
- Google Workspace Available Sign in, Calendar, Meet and Drive
- SAML 2.0 Roadmap Enterprise sign in
- OpenID Connect Roadmap Generic sign in
Microsoft 365 03
- Microsoft Teams Available Notifications and automations
- Outlook Calendar Available Calendar events
- SharePoint Available Files and documents
Engineering 01
- Git repositories Available Repositories, commits, pull requests
AI models 02
- Anthropic Claude Available Agents and knowledge answers
- OpenAI compatible Available Any compatible chat model
Messaging and webhooks 04
- Email (SMTP) Available Notifications and announcements
- SMS gateway Available Urgent announcements
- Webhooks Available Inbound and outbound
- Slack Roadmap Notifications
Backup destinations 03
- S3 compatible storage Available Encrypted backups
- Google Drive Available Encrypted backups
- Email delivery Available Encrypted backups
09 Why switch
Switching is a decision about how your company runs.
Most teams we meet run a typical stack: an HR system, spreadsheets, a helpdesk, a wiki, chats and forms. Here is what changes.
| Topic | Typical stack | CompanyOS |
|---|---|---|
| Data | Copied between tools and reconciled by hand | One model shared by every module |
| Identity | A login per tool, offboarding in ten places | One identity with Microsoft Entra ID sign in |
| Access | Roles per tool that nobody can explain | Scoped, field level permissions with an explanation |
| Processes | Reminders in chat, approvals in email | Approvals, journeys and automation in one flow |
| Reporting | Exports and a spreadsheet every Friday | Live reports across modules |
| Audit | Partial, and different in every tool | One trail for people, data and AI actions |
| Ownership | Many subscriptions, many vendors | One platform, modules switched on as you grow |
-
Data
Typical stackCopied between tools and reconciled by hand
CompanyOSOne model shared by every module
-
Identity
Typical stackA login per tool, offboarding in ten places
CompanyOSOne identity with Microsoft Entra ID sign in
-
Access
Typical stackRoles per tool that nobody can explain
CompanyOSScoped, field level permissions with an explanation
-
Processes
Typical stackReminders in chat, approvals in email
CompanyOSApprovals, journeys and automation in one flow
-
Reporting
Typical stackExports and a spreadsheet every Friday
CompanyOSLive reports across modules
-
Audit
Typical stackPartial, and different in every tool
CompanyOSOne trail for people, data and AI actions
-
Ownership
Typical stackMany subscriptions, many vendors
CompanyOSOne platform, modules switched on as you grow
Estimate the time you get back
A transparent estimate, not a promise. Move the sliders and read the formula.
Formula
120 × 45 min × 46 × 50% ÷ 60 = 2,070 hr
2,070 hours a year back, 259 working days, 8 fewer logins per person
Assumes 46 working weeks and that CompanyOS removes half of the time lost to tool switching. Your numbers will differ, and we are happy to model them with you.
10 Getting started
From the first call to company wide, one step at a time.
No big bang migration. Prove the value on a pilot, then grow.
-
Discovery
We map your current tools, processes and roles, and agree what success looks like.
-
Pilot
One or two modules go live for a real team, on your own workspace address.
-
Import
People, structure and history move over from spreadsheets and your current HR system.
-
Rollout
More modules, role experiences and automation switch on. The old tools retire one by one.
11 Security and trust
Trust is a feature, not a checkbox.
Company data is the most sensitive data you have. CompanyOS treats it that way from the first line of code.
-
Tenant isolation
Every company runs in its own tenant with its own address, data boundaries and configuration.
-
Explainable access
Scoped and field level permissions, with an explanation behind every access decision.
-
Single sign on
Microsoft Entra ID sign in with verified tokens. One place to offboard a person.
-
Complete audit trail
Who did what, when and why, including every action proposed by AI.
-
Encrypted backups
Scheduled, encrypted backups to S3, Google Drive or email, with a guarded restore.
-
Secure engineering
Security checks aligned with OWASP ASVS, request forgery guards and managed secrets.
13 Questions
What teams ask before they switch.
Is CompanyOS an HR system?
It covers HR, but it is broader: an operating system for the whole company. People and organization are the core, and modules such as leave, timesheets, projects, office, knowledge and cases all build on them.
We already use an HR tool and spreadsheets. How hard is the switch?
We start with a pilot on one or two modules, import people and structure from your current system or spreadsheets, and grow from there. Old tools retire step by step, not overnight.
Do we need to replace our engineering tools?
No. CompanyOS connects to Microsoft 365 and your Git provider. It replaces the patchwork around those tools, not the tools themselves.
Who can see our data?
Each company has its own isolated tenant. Access follows explainable, field level permissions, and every change is recorded in the audit log.
Can we use our own branding?
Yes. Each workspace can carry its own logo, product name and colours on its own address.
Which languages are supported?
English and Ukrainian out of the box. Companies can also upload their own language packs.
How does the AI handle sensitive data?
Agents work within the permissions of the person asking, every proposed action needs approval, and a company AI policy controls which models are used and how much.
How do people sign in?
With Microsoft Entra ID or Google Workspace. SAML sign in is on the roadmap.
See how your company would run on CompanyOS.
Thirty minutes, your processes, a live workspace. No slides required.