01
Dashboard
The state of the company on one screen — pipeline, projects, and activity.
In build · schema live, surfaces landing next
The operating layer for the company itself
Contacts, deals, projects, and the SOPs that keep them repeatable — one schema instead of a CRM, a project tool, and a wiki that disagree. BusinessOS is the back office of AIOS.
The data model ships ahead of the interface here. The dashboard is live; the departments below are modelled in Postgres and rolling out from there.
9
departments modelled in Postgres
1
schema, no tool-to-tool syncing
RLS
row-level security on every table
9 departments
One schema for the whole back office.
The reason a CRM, a project tool, and a wiki never quite agree is that they each own a different copy of the same company. BusinessOS keeps one.
02
Contactssoon
Every person and company, with the history attached rather than remembered.
03
Leadssoon
Inbound and sourced leads, scored and routed before they go cold.
04
Dealssoon
Value, stage, and the next action — nothing sitting in an inbox.
05
Pipelinessoon
Stages you define per pipeline, so sales and delivery can differ.
06
Projectssoon
Delivery work with owners, milestones, and the deal that paid for it.
07
Taskssoon
The unit of work everything else rolls up from.
08
SOPssoon
The written version of how things get done, attached to the work itself.
09
Campaigns & activitysoon
Outbound pushes and a full audit trail of who changed what, when.
Why BusinessOS
Fewer tools, one source of truth.
Most small companies run four subscriptions that each hold a partial copy of the business, and spend real hours reconciling them.
01
Modelled before it was drawn
The Postgres schema — contacts, leads, deals, pipelines, projects, tasks, SOPs, activity log — exists today. The UI is being built onto a real model, not the other way round.
02
The deal and the delivery in one place
A project knows which deal funded it, and a deal knows what shipped. That link is the thing separate tools can never keep straight.
03
Audited by default
Every change writes to an activity log, and row-level security scopes access per workspace. You can answer "who changed this" without guessing.
04
Honest about where it is
The dashboard is live and the rest is marked soon on this page. When a department ships, the chip disappears — that is the whole announcement.
Questions
Before you ask.
Can I use BusinessOS today?
Partly. The workspace and dashboard are live and the Postgres schema is in place, but the contact, deal, project, and SOP surfaces are still being built — each is marked soon on this page until it ships.
Is this a CRM?
It includes one, but the point is the joins. A CRM that does not know what got delivered, and a project tool that does not know what was sold, are the problem BusinessOS is shaped around.
Will it import from my current tools?
Import paths are not built yet. When the surfaces land, getting existing contacts and deals in will be part of shipping them — not an afterthought.
Can I run more than one company?
Yes. Each company is a workspace with its own data and members, all under one account and one subscription.
One platform
BusinessOS is one of eight systems.
Every module shares the same login, the same subscription, and the same integrations. Add the ones you need as the work grows.
One schema for the whole company.
BusinessOS is included with your AIOS membership, and grows as departments ship.
Sign in →