The complete platform.
No module maze.

Every core operational capability, Datum AI, and the QuickBooks Online and Xero integration. There are no modules to unlock. The price covers 5 users; additional users are $29 per user per month. Early-access pricing is held for the duration of your early-access term.

No. Early access includes guided onboarding at no additional cost — workflow mapping, core data import, control configuration, and team enablement. We do this because early-access customers shape the product, and a bad setup helps neither of us.

Early access is month to month. You can stop at any time, and you keep the ability to export your data on the way out.

Per user only. Volume of orders, purchase orders, inventory movements, work orders, or AI questions does not change the price. Operational systems that meter transactions punish you for growing, which is the opposite of the point.

Businesses that make, source, and deliver — make-to-order and project-led manufacturers, millwork and fabrication shops, and operations that buy, hold, transform, and ship physical goods. The common thread is work that has to be planned, committed, and costed before it can be invoiced.

Pure service businesses with no inventory, simple resale operations with a handful of SKUs, and businesses whose accounting software already handles their operational complexity. If you are not tracking commitments, stock, or job cost, Datum solves a problem you do not have.

No. Datum is the operational system of record. QuickBooks or Xero remains the financial system of record, connected through controlled two-way synchronization. Financial documents sync across; operational detail such as purchase orders, receipts, cost layers, and work orders stays in Datum.

Yes. Authorized users can switch between companies and editions from one identity while company data remains safely isolated. There is no need to log out and back in, and no way for a query to cross a company boundary.

Early access uses guided onboarding so we can map your workflows, import core data, configure controls, and help your team reach value quickly. Self-serve onboarding will follow once the guided path has taught us what to automate.

Item masters, customers and suppliers, opening inventory balances with cost layers, open purchase orders, and open jobs. Bringing across opening cost layers rather than a single average cost matters, because it is what makes early margin figures trustworthy.

It depends on how much history you carry and how clean it is, not on the software. The pattern that works is a staged cutover: connect accounting and get purchasing running first, then inventory and receiving, then production. Attempting all three at once is the most common reason go-lives slip.

It answers operational questions from your own records with citations, surfaces proactive insights, parses documents, drafts work, and prepares actions for review. Write actions require permission and explicit human confirmation. When your records do not contain an answer, it says so rather than guessing.

No. Your operational data is not used to train models, for us or for anyone else. It is used to answer your questions, within your permissions, and nothing else.

Each company uses its own PostgreSQL schema, backed by role-based access, tenant-aware caching, encrypted connections, and immutable audit history. Permissions are enforced at the data layer, so Datum AI cannot surface a record the person asking could not open themselves.

You export it. Your operational records are yours, and the ability to take them with you in a usable format is not conditional on staying. Your financial history also remains in QuickBooks or Xero, since that is where it has been posting all along.