The Idepoo flagship
OnePlatform: enter it once, and the whole organisation works from it
An integrated platform of fourteen modules — CRM, sales, inventory and procurement through finance, HR, projects, support, portals, automation and AI — on one shared core. For companies, retailers, factories and clinics. Every module is also sold on its own.
The problem OnePlatform solves
An organisation running five separate systems has five versions of the truth.
A customer is entered once in the CRM, once in the sales system, once in accounting — and all three differ slightly. Goods that were sold are still in stock until somebody deducts them by hand. Payroll is calculated, then retyped into the accounts. And when a manager asks what the month's profit was, the answer is three spreadsheets somebody has to reconcile.
The real cost is not the software. It is the manual work between the systems, and the errors that happen in it.
OnePlatform's founding principle is one sentence: master data is entered once, and every other module uses it under access control. Customers, suppliers, products, currencies, units, companies, branches and users each have a single source of truth.
Fourteen modules, one core
Core and commercial modules
PlatformCore
Users, roles and permissions, companies and branches, general settings, document numbering, notifications, audit trail, attachments, custom fields, background jobs, API keys and webhooks. No other module builds its own user, role, file or audit system.
CRM
Leads with source and scoring, accounts and contacts, opportunities with pipeline stage and win probability, activities, and campaigns with budget, conversion and ROI. The owner of the customer relationship, from first contact onwards.
Sales
Product and service catalogue with price lists, versioned quotations, sales orders with stock reservation and delivery schedules, dispatch notes with serial and batch, sales returns, and invoice requests raised to Finance.
Inventory
Items with SKU, barcode, units, serials, batches and expiry; warehouses, locations and bins; receipts, issues, transfers and stock counts; available, reserved and on-order stock; reorder points and safety stock; and FIFO, weighted-average or standard-cost valuation.
Procurement
Purchase requisitions with cost centre and project, RFQs across several suppliers with comparison, purchase orders with multi-step approval, goods receipt with quality control, supplier evaluation and rating, and three-way matching of order, receipt and invoice.
Finance, organisation and service
Finance
General ledger with chart of accounts, journals, fiscal periods and trial balance; receivables with invoices, aging and statements; payables; treasury with cash, banks, cheques and reconciliation; budgeting with control and variance; cost accounting with cost centres and allocation; fixed assets with depreciation; and statutory reports.
HR
Employee records and contracts, recruitment from vacancy to offer, attendance with shifts and overtime, leave with approval workflow, payroll with tax, insurance, loans and payslips, performance with goals and KPIs, and training with certification.
Projects
Projects with budget, manager and client; phases, milestones and tasks with dependencies; resource allocation and team capacity; timesheets with billable separation; costing from labour, materials and procurement; and billing as fixed price, time and materials, or by milestone.
Support
Tickets with category, priority and channel; SLAs with response and resolution times and escalation; a service desk with queues, assignment and internal notes; a knowledge base; and satisfaction measurement with CSAT and surveys.
Horizontal layers, across every module
Documents
A central archive with folders, versions, metadata and tags, full-text search, access control, locking and approval, expiry dates and retention policy. The principle: the file lives in Documents and other modules hold only a reference.
Automation
Triggers (record created or changed, a date arriving, a schedule, an API event), conditions, and actions (create a record, assign, notify, email, SMS, post a journal, request approval). Plus an approval engine: single-step, multi-step, parallel, amount- or department-based, with delegation and escalation.
Analytics
Role-based dashboards — executive, finance, sales, inventory, procurement, HR, projects, support — with the KPIs of each domain and drill-down from any figure to the transaction behind it: total revenue to customer, invoice, invoice line and the order it came from.
AI
A natural-language assistant over real data, lead scoring and win-probability prediction, cash-flow forecasting and anomaly detection, demand forecasting and dead-stock detection, ticket classification and suggested replies, and extraction from invoices and contracts.
Portal
Three external portals: customer (quotes, orders, invoices, payment status, tickets, contracts, project status), supplier (RFQs, quote submission, purchase orders, invoice and payment status), and employee (payslips, leave, timesheets, requests).
What integration actually means
The clearest way to see the value is to follow one order. This is order-to-cash, and in OnePlatform it runs without a single manual re-entry:
- A lead is recorded in CRM, with its source — so you later know which campaign worked.
- The lead becomes a customer and an opportunity.
- Sales issues a quotation; the customer accepts.
- A sales order is created and Inventory checks and reserves stock.
- If stock is short, Procurement receives a purchase request automatically.
- Goods are delivered and stock is reduced.
- Finance creates the invoice and the journal entry, and the receivable is recorded.
- Payment is received and posted to treasury; the customer balance updates.
- Analytics shows the revenue and the margin.
- CRM shows the purchase history to the account manager, and Documents has kept every document.
In an organisation with separate systems, a person sits between step 6 and 7, and between 7 and 9, moving data by hand.
Four more end-to-end flows
Procure-to-pay
Requisition → automatic approval routing → RFQ and comparison → purchase order → goods receipt in inventory → supplier invoice → three-way match → payable recorded → payment approval and execution → spend and supplier-performance reporting.
Hire-to-payroll
Vacancy → candidate, interview and offer → employee record created → documents archived → attendance and leave → payroll calculated → the accounting entry created automatically in Finance → bank payment → payslip in the employee portal.
Project-to-profit
Opportunity in CRM → contract → project created → team allocated → timesheets → materials consumed from inventory → project purchasing → every cost posted against the project dimension → project billing → real project profitability.
Support-to-retention
Customer raises a ticket → identified from CRM with full history → SLA set → assigned → AI summary and suggested reply → automatic escalation on delay → resolved → satisfaction recorded → history shown to the account manager → service quality measured.
AI, on the organisation's real data
The AI layer is not a separate module with separate data; it is a central service operating on the other modules' data. That difference matters: analysis over integrated data sees things no single-purpose tool can.
Take "why did sales drop this week?" An answer with access only to sales data can say how much it dropped. An answer with access to inventory, support and CRM at the same time can say that three best-selling items were out of stock and that one major customer's open tickets tripled.
By domain: an assistant answering in natural language; CRM — lead scoring, win probability, next best action, correspondence summaries; finance — cash-flow forecasting, anomaly detection, expense classification, reconciliation assistance; inventory — demand forecasting, reorder recommendations, dead-stock detection; support — classification, suggested replies, sentiment; documents — extraction from invoices and contracts, semantic search.
One security principle that is not negotiable: the AI respects exactly the permissions of the user asking. If a user may not see payroll, the assistant does not tell them — however indirectly the question is put. That is enforced in the architecture, not in a prompt.
Security and control at organisational scale
Access across seven dimensions
Company, branch, department, role, module, operation and record. Each user has a data scope: their own records, their team's, their department's, their branch's, their company's, or every company they are authorised for.
Multi-company, multi-branch
Several companies, branches and business units, and multi-tenancy where required — each with its own chart of accounts, numbering and fiscal periods.
A complete audit trail
Every sensitive operation — posting a journal, changing a price, approving a purchase, deleting, changing access, paying — recorded with user, time, device, before and after values, reason and approval reference.
Documents that lock
Draft → submitted → under approval → approved → posted → completed. A posted financial document is never edited or deleted; corrections are made by reversal.
Amount-based approval matrix
Up to the first threshold: the manager. To the second: manager and procurement. To the third: plus finance. Above: plus the CEO. The same engine drives discount, payment, expense, leave and journal approvals.
Central numbering
The number pattern for each document type is defined in the core and configured per company, branch, fiscal year and type — so numbers are neither duplicated nor gapped.
Architecture and stack
A modular monolith. One deployable unit, with independent domains and explicit boundaries inside it — the operational simplicity of a single deployment with the boundary discipline of microservices. Every piece of data has one owning domain; the others reach it through APIs and events.
Clean Architecture and CQRS. The domain at the centre and independent of technology, the application layer around it, infrastructure and presentation outside. The write path enforces business rules and the read path is shaped for reporting — which in a system with this much reporting is a visible difference.
Event-driven integration. Modules communicate through events such as SalesOrderConfirmed, GoodsReceived, InvoicePosted, PaymentReceived, EmployeeHired and TicketClosed, delivered over a message queue — so a slow module never rolls back another module's transaction.
The stack:
- Back end — .NET 10 with clean architecture and CQRS
- Database — PostgreSQL
- Cache — Redis
- Message queue — RabbitMQ
- Web — React
- Mobile — React Native
- Windows desktop — Tauri
- API-first — every significant capability has an API, so the portal, the mobile app, automation and AI all use the same business logic rather than reimplementing it
Global search. One query returns the customer, contact, invoice, order, project, ticket and document that match — all filtered by what you are permitted to see.
Who it is for
A multi-company architecture and selectable modules mean one platform in several shapes:
- Services and trading companies — CRM, sales, finance, projects, support
- Retail and distribution — sales, multi-warehouse inventory with valuation, procurement, finance, customer portal
- Manufacturing — procurement with three-way matching, inventory with serials and batches, costing, fixed assets, HR
- Clinics and practices — patient CRM, services or projects, finance, HR, portal
- Project-based firms — projects with timesheets, costing and milestone billing, connected to finance and HR
And because each module is also sold on its own, you do not have to buy everything on day one.
How it is licensed and deployed
The licence model
OnePlatform is supplied with its source code, under a defined agreement with Idepoo Viana (trading as Idepoo):
- A transfer agreement with an explicit scope of use — the buying organisation and its subsidiaries.
- A non-disclosure undertaking — the source is made available to the organisation's technical team and is not published, resold or passed to a third party.
- Commercial rights retained — intellectual property in the product stays with Idepoo Viana; what is transferred is the right to operate and extend it internally, not to resell it or offer it as a product.
The reasoning is straightforward. An organisation buying the system its business runs on is entitled to know the code is available to it and that it is not locked to one supplier. A company that has spent years building that product is entitled to know the same code is not sold on to its competitor.
Activation and support
This is not a product that starts with an installer. After purchase, activation and support are carried out by the Idepoo Viana team: initial configuration, company, branch and role structure, chart of accounts, data migration, approval workflows, and training.
Where it runs — your choice
- On your own servers — for organisations whose data must stay inside their network. We deploy and commission it; your team handles day-to-day operation.
- On our infrastructure — if you would rather the servers, backups and updates were ours.
Both are offered, and choosing between them is usually a policy decision rather than a technical one.
Customisation
OnePlatform is configured to your organisation: custom fields, approval workflows, threshold matrices, print templates, document numbering and management reports — all without changing the core, so later product updates do not break your configuration.
The scope is agreed in a discovery session and written into a scope document before any figure is quoted.
Base price per module, bought on its own. The weighting follows the real difficulty and scope of each domain — finance and HR carry the most rules, and the core carries the security model everything else stands on.
PlatformCore — see the module list above — 110m toman
Finance — see the module list above — 175m toman
HR — see the module list above — 125m toman
Inventory — see the module list above — 110m toman
Sales — see the module list above — 100m toman
Procurement — see the module list above — 95m toman
CRM — see the module list above — 85m toman
Projects — see the module list above — 85m toman
AI — see the module list above — 85m toman
Automation — see the module list above — 75m toman
Analytics — see the module list above — 65m toman
Support — see the module list above — 55m toman
Documents — see the module list above — 45m toman
Portal — see the module list above — 40m toman
The complete platform — all fourteen modules on one core — 1,250m toman
Three things to be clear about before any negotiation:
1. This is a base price, not a final one. The scope of customisation, the number of companies and branches, and the volume of data to migrate all move it. The final figure follows a discovery session and a written scope.
2. What it does not include: deployment on your infrastructure, migration from your current systems, team training, and development outside the product's scope. Each is estimated separately.
3. Annual support is separate and is 18% of the licence, covering version updates and fixes.
Buying several modules together: three or more take 10% off their combined total. The complete platform stays at 1,250m toman. Most organisations start with two or three modules and add the rest in later phases — and because they all sit on one core, adding the next one is an activation rather than a migration.
Frequently asked
Do we receive the source code?
Yes. The product is supplied with its source under a transfer agreement with Idepoo Viana — a defined scope of use, a non-disclosure undertaking, and intellectual property retained by Idepoo Viana. Your technical team has access to the code and can extend it internally; the right to resell it or offer it as a product is not transferred.
We only want one module. Is that possible?
Yes. Each module is priced independently and can be bought and used alone. Because they all sit on one core, adding the next is an activation rather than a migration — and no data is entered twice.
Does it run on our servers or yours?
Either. On your own infrastructure — we deploy and commission it, your team runs it day to day — or on ours, if you would rather the servers, backups and updates were our responsibility.
Do we set it up ourselves after purchase?
No. Activation and initial configuration are done by the Idepoo team: company, branch and role structure, chart of accounts, data migration, approval workflows and training. A system of this scope does not start with an installer, and we do not hand it over as though it did.
How much can be customised?
Custom fields, approval workflows, threshold matrices, print templates, numbering and reports are all configured to your organisation without touching the core — so later updates do not break your configuration. The scope is agreed in discovery and written down before any figure is quoted.
Will our current data be migrated?
Yes. Import and export are built into the core, and migrating master data is part of deployment. The size and shape of your current data determines the time and cost, which is estimated separately.
How many companies and branches does it support?
The architecture imposes no limit; multiple companies, branches, business units and multi-tenancy are supported, each with its own chart of accounts, fiscal periods and numbering. The number of companies affects deployment scope and appears in the estimate.
Our approval process differs from your standard.
The approval engine is configurable: single-step, multi-step, parallel, amount- or department-based, with delegation and escalation. Purchase, discount, payment, expense, leave and journal approvals all run on it.
Does the AI have access to all our data?
No. It respects exactly the permissions of the user asking. If a user may not see something, the assistant does not surface it, however the question is phrased. That is enforced in the architecture rather than in a prompt.
How long until it is running?
It depends on the number of modules and the volume of data. Deployment is phased, and from phase two the organisation is using the system rather than waiting for everything.
A demo with your own data
In the demo we lay one of your real processes — order to cash, say — onto the system, so you can see how much manual work integration actually removes.
The organisation, its sector, and which systems you use today — those three answers are enough to set up a useful demo.