One database
Every table linked. Projects connect to finance, finance to procurement, procurement to vendors, HR to projects. Every foreign key is a real relational link.
The Platform
One place where the business actually runs.
YBNW One is a database-first business management platform. Not a bundle of apps glued together — a single database-backed workspace where every department reads and writes from the same data layer.
160+ modules
795 permissions
12 role types
One workspace subscription
The Problem With SaaS Sprawl
Most companies have not outgrown their tools. Their tools have outgrown each other.
An 8–15 tool stack solves department-level problems, but none of the tools know what the others are doing — the result is operational friction that compounds with every new hire and every new reporting requirement.
01
Data lives in the wrong place
When a project goes over budget, the answer is spread across a project tool, an accounting system, and a spreadsheet. Assembling a coherent picture takes manual work nobody has time for.
02
Seat pricing punishes collaboration
Per-seat pricing forces managers to ration access before work can move — the result is email threads, exported CSVs, and workarounds that create compliance risk.
03
Reporting becomes a second job
Building a board report from five disconnected systems means manually pulling and reconciling data. Monthly reporting can take two to five days of senior staff time.
04
Security multiplies per tool
Each new SaaS subscription is a new access model to audit and a new place an offboarded employee might still have access — a compliance problem that grows with every added tool.
05
Context is lost between handoffs
When a deal closes and moves from CRM to delivery, or a contract moves from legal to procurement to accounts payable, context has to be manually re-entered at every step.
06
Integrations are a maintenance burden
Zapier connections and API bridges fail silently and require upkeep — and still don't give you a shared permission model or a unified audit trail.
What YBNW One Is
A business operating platform, not an app bundle.
YBNW One is built on a single database. Every module — from the Kanban board in project management to the payroll run in HR to the purchase order in procurement — reads and writes to the same database. There is no sync layer, no separate CRM database and finance database to integrate. This is a structural property of how the platform is built, not a marketing claim.
The practical consequence: reporting doesn't require manual assembly. The executive dashboard sees live project status, live financial figures, live team capacity, and live vendor pipeline — all from the same operational data teams create during their regular work.
Single database
Real-time sync
Workspace isolation
One permission model
795 permission constants, 12 predefined roles. One set of access rules governs every module — see the full breakdown on Security.
One workspace subscription
Invite every team member — no per-seat charge for collaborators. Capacity (storage, compute, AI calls, automation) scales with plan tier.
160+ modules included
Every module is available from day one on paid plans — no module locked behind an upgrade gate.
The Data Layer
Where every module's data actually lives.
Most web apps use a database as a place to store state. YBNW One uses it as the operational source of truth for everything the business does.
One connected schema
Core tables include projects, invoices, budgets, purchase_orders, employees, deals, crm_contacts, vendors, risks, inventory_items, and more — each normalized, indexed, and workspace-isolated.
Isolation and permissions, layered
Workspace isolation decides whether a query can see a workspace's data at all; the permission model decides what an authorized user is allowed to view or change. The two are independent controls.
Real-time subscriptions
When a teammate updates a project status, another's dashboard reflects it without a page reload — database-level event propagation via WebSocket subscriptions.
188 migration files
Every schema change is a versioned, reviewable migration. Production state is always reconstructible from source code, and each migration can be rolled back.
Shared foreign key relationships
Links between projects, budgets, invoices, and team assignments are real database foreign keys — not string fields that can drift out of sync.
Automated workflow triggers
Approvals, notifications, and billing events fire automatically when a record changes — no manual follow-up step, no separate automation tool to maintain.
How Modules Connect
Work that moves between departments stays connected.
When work moves from one department to another, the context moves with it. Here is what that looks like in the actual data model.
Sales → Delivery
A closed CRM deal seeds the project record — client, budget, and team assignment inherit via foreign keys. Nothing is re-entered manually.
Projects → Finance
Billable time and expenses flow directly into invoicing. Profitability at close pulls from real invoice and expense records, not estimates.
Procurement → Accounts Payable
A PO flows through approval, is received against delivery, and generates a payable — the same vendor record throughout, no reconciliation step.
HR → Projects → Finance
Employee capacity informs workload planning; time logged against projects feeds both progress tracking and payroll costing.
Risk → Governance → Reporting
Risks scored on a 5×5 matrix connect straight to governance dashboards — an executive summary is already structured and current.
Customers → Success → CRM
Health scoring, renewals, and support tickets sit beside the same CRM pipeline record — one customer record, not two.
The Permission Model
795 permissions. 12 roles. One place to manage all of them.
Every operation in every module is governed by a named permission constant, enforced at both the UI and database layer. Full detail on roles, audit trails, and workspace governance lives on the Security page.
01
795 named permission constants
e.g. VIEW_ALL_INVOICES, MANAGE_PAYROLL, APPROVE_PURCHASE_ORDER. Give a controller access to invoices without HR payroll, or a contractor access to one project only.
02
12 predefined role types
Administrator, Manager, Team Lead, Employee, Contractor, Viewer, Finance Manager, HR Manager, Compliance Officer, Project Manager, Support Agent, Custom — each fully editable.
03
Workspace and team scoping
A user in Workspace A cannot see Workspace B's records even with an identical role. Scoping is enforced at the database layer, not a UI filter.
Who It Is For
Companies that want to run from one place, not from a patchwork.
The right fit for organizations where multiple departments collaborate on shared work and where the cost of tool sprawl has become visible enough that consolidation makes sense.
01
Growing companies (10–500 employees)
Outgrown spreadsheets, not ready for enterprise ERP cost. Every team member can be in the platform from day one without per-seat billing.
02
Professional services firms
Projects, time, invoices, and client relationships connect end to end — the whole project-to-cash cycle in one system.
03
Operations-heavy businesses
Procurement, inventory, vendors, and facilities update from the same event because they're related records in the same database.
04
Regulated industries
Database-first architecture with workspace isolation, named permissions, and a queryable audit trail makes access control easy to demonstrate to auditors.
05
Teams replacing a stacked toolset
Currently paying for separate PM, CRM, HR, finance, and procurement tools? Our implementation team designs the migration path — no big-bang cutover required.
06
Founders who want visibility
One executive dashboard surfaces revenue, active projects, team capacity, and key risks — without a separate BI layer or manual reporting process.
See the platform in one workspace.
Start a free workspace to explore every module. No credit card, no feature gates, no seat limits for your team.