The Oneop platform
Everything your teams need.
Built to work together.
Most "all-in-one" platforms are a bundle of products with an integration between them. Oneop is one database. A conversation, the deal it created, the invoice it produced and the stock it moved are rows in the same schema, under the same tenant boundary, visible to the same roles.
Free forever · 2 seats · No credit card
One customer. Every team has the context.
- 12Connected modules
- 4Business areas
- 19Native integrations
- 68Built-in reports
- 1Connected platform
Different teams, same business
Five people, five questions, one record between them
Every team below is looking at the same customer. Nobody is looking at a copy, and nobody had to be told what the other four already knew.
How the twelve are organised
Four business areas, and none of them is a separate product
Operations
3 modulesTurning what was sold into what was delivered — stock that can be promised, work that can be scheduled, and reporting that reads the result without a spreadsheet.
Finance
1 moduleOne module, and it is a real double-entry ledger rather than an invoice generator. Operational transactions continue into financial records instead of being re-entered as them.
AI & Automation
4 modulesWork that moves without someone chasing the next person, and AI that acts inside published limits on the same records the rest of the platform uses.
Explore all modules
All twelve, and what each one actually does
Filter by business area or read the lot. Every module is part of the same application on the same database — the plan sets the ceiling, and a few operational modules are activated separately because they can create financial, outbound or operational side effects.
Connected by design
The connection is a layer, not a feature
Nothing above is true because twelve teams agreed to keep their data tidy. It is true because the twelve surfaces sit on one shared context, and that context sits on one database with one boundary and one commit.
Connections
Nineteen integrations, grouped by the job they do
The twelve modules do not need integrations between themselves. These are for the software you are keeping — every one exists in the product and is verified against the code that runs it.
Support and sales over email
- Google WorkspaceSign-in, Gmail send/receive, Calendar
- Microsoft 365Sign-in, Outlook send/receive
- IMAP / SMTPAny standard mailbox, per rep
- SendGridTransactional out, Inbound Parse in
- PostmarkTransactional out, verified inbound
Payment and books that reconcile
- StripeInvoice payment links and Connect
- PlaidDaily bank feeds into reconciliation
- QuickBooks OnlineTwo-way sync, inbound by webhook
Your store and your other CRM
- WooCommerceLive products, stock, orders, returns
- ShopifyProducts, customers, orders — read-only
- HubSpotTwo-way contact, company and deal sync
- SalesforceContacts, accounts, opportunities, two-way
- Apollo.ioContact enrichment, metered monthly
Meetings and signatures
- ZoomBookings create real meetings
- DocuSignQuote e-signature, verified webhook
- Dropbox SignThe same flow, through HelloSign
Chat on your website
- WordPressOfficial plugin, keyed to your workspace
Alerts where your team already is
- SlackNotifications out, incoming webhook
- Microsoft TeamsNotifications out, incoming webhook
FAQ
Common questions about the module set
How many products am I actually buying?
One. Oneop is a single application with twelve module surfaces on one database, priced flat per workspace rather than per module. There is no per-module SKU and no connector to license between them.
Do I have to use all twelve modules?
No. All twelve are surfaces of one application on one database, so ignore the ones you don't need — nothing is priced or licensed per module. Some operational modules, finance, project management and sequences among them, are activated separately because they can create financial, outbound or operational side effects. Beyond that what varies is the plan entitlement, not whether you bought a module.
What does "one record" actually mean in practice?
That the person in a chat, the requester on a ticket, the buyer on a deal and the bill-to on an invoice are the same rows, not four copies kept in step by a sync job. Oneop stores every module in one PostgreSQL schema of 329 tables, 275 of which carry a tenant ID enforced at the data layer on every query. When a sales order ships, the stock decrement and the ledger posting happen inside the same database transaction — either both or neither.
Which parts are genuinely AI?
Chatbot flows, AI agents, AI reply drafts, ticket triage on existing tickets, document OCR, expense categorization and the Business-plan report narrator are real model calls through Google Gemini. Cash-flow forecasting, duplicate-bill detection and the analytics insights panel are deterministic calculations and we don't call them AI. AI governance explains how every model call is bounded.
What actually varies by plan?
The ceiling, not the switch. Invoicing runs on every tier, while payables, expenses, tax and bank reconciliation start at Pro, and multi-currency at Business. Most plan limits show up in your navigation rather than a server refusal, and Free plan numeric caps are not hard stops — we would rather say so than let you infer a wall that is not there. The report builder, dashboards, scheduled delivery and AI reporting are the exception: those gates are checked server-side.
Can I add my own fields?
Yes. Thirteen field types across ten entity types, with required flags, defaults, filtering, role restrictions, grouping, ordering and conditional visibility. Deleting a field hides it rather than destroying its history, so a report run against last quarter still resolves.
Does it work in my language?
Eight fully translated UI languages — Arabic, German, English, Spanish, French, Turkish, Urdu and Simplified Chinese — with full right-to-left layout for Arabic and Urdu that reaches into the rendered invoice PDFs, not only the app chrome.
Does it connect to what we already run?
Nineteen native integrations, each with a verified entry in the product rather than a logo on a page. Credentials are encrypted per workspace and inbound webhooks are signature-verified and fail closed — an unverifiable payload is rejected, not processed on trust.
Get started
Start with one problem. Build toward one connected business.
Two seats on the free plan, or a guided tour of the modules you care about.
Free forever · 2 seats · No credit card