Twelve modules. One record. One permission model.
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.
Sign-up opens when the app launches. We will email you once — no marketing list.
What "one record" actually means
There is no sync job, because there is nothing to sync
Oneop stores every module in one PostgreSQL schema of 329 tables, 275 of which carry a tenant ID that is enforced at the data layer on every query. When a chat becomes a ticket, the requester resolves to the CRM contact and the finance customer that already exist. When a sales order ships, the stock decrement and the ledger posting happen inside the same transaction. The word "integration" describes what Oneop does with other people's software, not what it does with itself.
That is the whole design argument, and the rest of this page is the twelve places it shows up.
Module explorer
Pick a module to see what it does
Every module below is described in full on its own page. Jump to any one, or open it here.
AI chatbot
Build a website chatbot on a visual canvas from roughly 55 executable block types, start from one of 17 templates, or describe the bot you want and have it generated. Every publish is snapshotted, so a bad release rolls back in one click. Two published versions can run against each other as a real A/B test with sticky per-visitor bucketing.
Live chat
Real-time website chat over WebSockets, worked from a shared inbox with focused views for All, Mine, Unassigned, Mentions and VIP. Agents reply publicly or leave internal notes, and an AI-drafted reply is one click away — drafted for a human to approve, never auto-sent. Both sides of every conversation are persisted through a single code path, so transcripts are never half-recorded.
AI agents
Agents that reason in a loop, call tools, and act inside limits Oneop publishes: 6 reasoning steps by default (hard cap 12), a 6,000-token budget, a 45-second wall clock and 3 actions per run. Three autonomy modes decide whether an agent suggests, queues for approval, or dispatches. Money and stock actions stay locked off unless you switch them on separately, whatever the autonomy mode says.
AI governance
Prompt-injection blocking and PII redaction run on every AI call, on every plan, with no setting to turn them off. Every LLM call passes one metered choke point; at your credit cap you get a refusal, not a bigger invoice. Simulated runs are badged as simulated.
Help desk
Tickets from web chat and email, with seven statuses and five priorities. SLA clocks are computed in business minutes against your working days, daily window and holiday list — not in wall-clock hours. A five-minute sweep escalates breached tickets idempotently, so nothing double-escalates.
CRM
Contacts, companies with parent/child hierarchy, deals, quotes and human-readable record numbers like LEAD-00042 allocated atomically. Design your own pipeline stages and enforce stage gates — no deal reaches Proposal without an expected close date, and a blocked move tells you exactly what is missing.
Automation
A visual workflow builder on real triggers — contact created, deal stage changed, ticket raised — with conditions, field updates and branching. Runs are transactional: a failure later in a run rolls back the writes earlier in it. Support automation adds durable delays that survive a restart, human approval steps, and a dry-run simulator that shows the exact execution trace without writing anything.
Inventory & warehouse
Multiple warehouses, bin locations, lots and batches, variants, transfers and cycle counts. The core invariant is enforced in code: available stock equals on-hand minus reserved and cannot go negative, so committed stock cannot be sold twice. Nine carrier adapters rate and buy real labels.
Finance
A real double-entry general ledger where debits must equal credits, checked in the application and again by a PostgreSQL trigger that refuses to write an unbalanced entry. Period locks, reversal-only corrections, AR and AP aging, multi-currency with a stored rate per document. Invoicing ships on every plan; payables, expenses, tax and bank reconciliation start at Pro, and multi-currency at Business.
Project management
Projects, backlog, sprints, milestones and time tracking that converts into an invoice and posts as a real journal entry. The client portal is a genuinely separate login principal with its own cookie and its own signing secret. Present in every workspace — what varies by plan is the invoicing and billing depth, not whether the module exists.
Reporting
Eleven module packs, 33 queryable datasets and 68 prebuilt reports, plus a custom builder with calculated columns. Export to CSV, XLSX or PDF. Scheduled delivery and AI report narration are Business-plan features.
Sequences
Multi-step outreach that sends from each rep's own Gmail, Microsoft 365 or SMTP mailbox rather than a shared platform sender, with real A/B variants on email steps and branches that read replies, opens and clicks. Present in every workspace; sending still needs that rep's own mailbox connected first.
Every module
The twelve modules, at a glance
What's shared across every module
Four things are true in all twelve, because they're properties of the platform
One customer record
A contact is not duplicated per module. The person in a chat, the requester on a ticket, the buyer on a deal and the bill-to on an invoice resolve to the same rows.
One permission model
Roles and the tenant boundary are checked at the data layer, not per product. 275 of 329 tables carry a tenant ID and every query is scoped to it.
One customization layer
Add your own fields to ten entity types across thirteen field types — including dropdown, multi-select, currency, date, file upload and a lookup that points at another record. Fields can be required, defaulted, filterable, role-restricted, grouped and shown conditionally.
One language layer
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 just the app chrome.
What actually varies by plan
Every module exists on every plan. The plan sets the ceiling, not the switch.
Present from day one
Finance, project management and sequences ship with every workspace, the same as CRM or the help desk. Plans set depth, not presence: invoicing runs on every tier, while payables, expenses, tax and bank reconciliation start at Pro, and multi-currency at Business. Sequences still need the sending rep's own mailbox connected.
Where limits are enforced
Most plan limits show up in your navigation rather than a server refusal, and Free plan numeric caps are not hard stops — we'd rather say so than let you infer a wall that isn't there. The report builder, dashboards, scheduled delivery and AI reporting are the exception: those gates are checked server-side.
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, but there is nothing to switch on — all twelve, including finance, project management and sequences, are present in every workspace from day one. Ignore the ones you don't need. What varies is the plan entitlement, not whether a module exists: invoicing is on every tier, while payables, expenses, tax and bank reconciliation start at Pro, and multi-currency at Business.
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.
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.
Get started
See the whole system, not a demo of one module.
Start on the free plan with two seats and no credit card, or take a guided tour of the modules you care about.
Sign-up opens when the app launches. We will email you once — no marketing list.