Enterprise SaaS / Multi-tenant platform
AxisOne Cloud
The modular enterprise platform: CRM, projects, billing, approvals and an integration hub, with add-ons activated per tenant
Mid-sized businesses run their accounts, projects, invoices, approvals and documents across disconnected tools, and every specialized need — bills of quantities, subcontracting, bank guarantees — adds another one. AxisOne Cloud brings them onto one multi-tenant platform: seven core modules and five add-ons that each company activates as it needs.
- 12 modules — 7 core, 5 add-ons
- 7 roles, each with its own navigation
- 37 tables isolated per tenant by row-level security
- Status
- In production
- Model
- B2B
- Market
- Mid-sized businesses, multi-industry
- Website
- axisonecloud.com
The problem
A growing company rarely fits one software package. Its CRM, project tracking, invoicing, task management and document storage live in separate tools; the specialized work — quantity surveying on construction projects, subcontractor tenders, letters of guarantee and letters of credit with the banks — lives in spreadsheets. Each new tool means another login, another data silo and another integration to maintain, and the finance, operations and management teams end up looking at different versions of the same account or the same project.
The solution
One platform, one data model, modules switched on per tenant. The seven core modules — CRM, projects, workflow and approvals, billing, tasks, documents, integration hub — are always on. Five add-ons — bill of quantities, subcontracting, letters of guarantee, letters of credit, advanced reporting — are activated company by company from a platform console, and appear in the navigation only for the roles that need them. Every record carries its tenant, every table is isolated by row-level security, and the integration hub exposes the data through a REST API and signed webhooks, so the platform can sit beside an existing ERP rather than replace it.
What the platform does
- Modular catalogue, activated per tenant 12 modules in a single catalogue: 7 core modules that every company gets, 5 add-ons switched on tenant by tenant. Routes, menus and dashboard widgets follow the activation — a module that is not licensed is simply not there.
- Seven roles, seven navigations Platform owner, tenant administrator, business manager, operations, finance, external partner and viewer. Roles are stored apart from user profiles, and each role gets its own navigation tree, filtered again by the modules the tenant has activated.
- CRM, projects and tasks Accounts typed as customer, supplier, partner or internal; contacts attached to accounts; projects with status, budget and currency; tasks with status, priority and due date — all searchable and paginated, all scoped to the tenant.
- Billing, payments and documents A products-and-services catalogue, invoices, payment recording that settles the linked invoice, and a private document store per tenant where each uploaded file is attached to a project or an account.
- Approvals An approval queue where pending requests are approved or rejected with a comment; every decision is kept in an action history.
- Construction and trade-finance add-ons Bills of quantities per project with line items; requests for quotation and subcontracts tied to supplier accounts; letters of guarantee with bank, type and an expiry flag at 30 days; letters of credit with issuing and advising banks and a remaining amount computed in the database; a reporting dashboard with KPIs and charts.
- Integration hub: REST and signed webhooks API keys stored as hashes with a visible prefix; a bulk import endpoint for projects, accounts, contacts, invoices and products; a paginated, filterable export endpoint; webhook subscriptions with a generated secret, HMAC-SHA256 signatures and retries; a change journal on the key entities.
- Closed onboarding and platform console Sign-up requires an existing company code, so a new user can only join a registered tenant. A platform console lists the client companies, the modules each one has and the module catalogue.
Architecture
Single-page web application (React, TypeScript) over a PostgreSQL backend with authentication, private file storage and server-side functions. Shared database with one tenant column on every business table, row-level security everywhere, and definer functions for the tenant and role checks; child tables are protected through their parent, file storage is partitioned by tenant folder. The integration hub is built around an outbound event queue (pending, sent, failed, dead-letter) consumed by a signing dispatcher, plus inbound and outbound REST functions authenticated by API key. The marketing site and the application are separate deployments on separate subdomains; the site has no database. The hub is designed to hold connector definitions for Oracle, SAP, Odoo, Microsoft Dynamics and bank APIs — next on the roadmap: the executable connectors themselves and scheduled synchronization jobs.
Who uses it
Tenant administrators who manage users, roles and licences; business managers on accounts and projects; operations teams on tasks, bills of quantities, tenders and subcontracts; finance teams on invoices, payments, guarantees and letters of credit; external partners — suppliers and subcontractors — on their tenders and contracts; and the platform operator through the console.
Markets
Mid-sized, project-driven businesses. The first add-ons come from construction and from trade finance — bills of quantities, subcontracting, letters of guarantee and letters of credit — while the core modules apply to any industry.
Where AI fits — and where it does not
No AI inside the business application — by design: licensing, access control, approvals and integrations are deterministic and auditable. The public site runs a sales assistant that qualifies enquiries; its conversations are processed by a cloud-hosted large language model through a third-party gateway, and a summary is emailed to my team. Nothing from the application’s data is involved.
My role
Founder, architect and designer: product vision, functional specification — module catalogue, licensing model, role model, integration hub —, platform architecture and technical direction; my team at SOFT M POWER CANADA built it and operates it under my direction.