Proceptio.BI: run the whole business from one platform

Proceptio.BI is a multi-tenant CRM and business-intelligence platform by Proceptio. It brings documents, customers, projects, tasks, resource scheduling, and analytics together so an entire operation runs from one place.

None of it is a problem on its own. It becomes one when the answer lives in six different tools.

3,500+
Documents
€1.2M+
Quotes sent
92%
Delivery rate
24/7
Availability

Everything in one place. Because it is one database.

Proceptio.BI replaces the patchwork of spreadsheets, mailboxes, and disconnected apps with a single system. Documents, customers, projects, tasks, scheduling, and analytics all share the same data - so every team works from one source of truth instead of re-keying the same information in five places.

Four systems in, one place to work

Proceptio.BI is easiest to understand from the bottom up: several separate ERP systems sync into one database, and then the record, the work, the numbers and the assistant all read from that same place instead of from four different versions of the truth.

Multi-tenant. Power BI, the portals and the assistant read one database.

01

One database under everything else

Four separate ERP systems sync one-way into a single cloud database, on their own schedules, without anyone re-keying anything. Everything that follows reads from that one place: the platform's own screens, the Power BI reports, the customer portals and the assistant. It is the reason the rest of this page can be about work rather than about reconciliation.

02

The document is the record, not a copy of one

Documents, partners and items live in the platform with their lines, totals and tax already computed, and the list and the detail form are the same data rather than a report of it. Filters, paging and status pills are there because a real operator works a long list every day, not because a screenshot needed furniture.

03

The work sits next to the data it is about

Projects and tasks run on a board with owners, priorities and due dates, in the same system as the documents they refer to. Nobody exports a list into a separate tracker, which is where the second version of the truth usually starts. Resource and room scheduling runs off the same calendar.

04

Reports built on the database, not on exports

Analytics and Power BI reports read the consolidated database directly, so a KPI on a dashboard and the same figure in the platform cannot disagree. Multi-company roll-ups work because the consolidation happened at the bottom of the stack rather than in a spreadsheet at the top.

05

The same numbers, asked instead of clicked

The platform carries an MCP layer in production: about 34 read-only tools that let staff ask Claude, Copilot or ChatGPT about the live consolidated data in plain language. Sign-in is the company's own Microsoft identity, each user only ever sees their own tenant's data, and every call is logged. Read-only by design, so an answer can be wrong but nothing can be broken.

And much more

The platform keeps growing with your operation. Alongside the core modules, Proceptio.BI covers the everyday essentials most businesses end up bolting on later.

01

Partners

Customers and suppliers with full history.

02

Projects

Plan and track projects end to end.

03

Mass mailing

Bulk campaigns with delivery tracking.

04

Cashflow

Plan and monitor cash flow.

05

Resources

Manage resources and assets.

06

CRM

Leads, contacts, complaints, tickets.

What the platform is actually carrying

Everything on this page is easier to believe with the shape of the live deployment next to it. These are the numbers behind the four names below.

4 ERP products, one database

Separate ERP systems sync one-way into a single Azure SQL database, each on its own schedule, from a legacy on-premise system to a daily REST feed. Nobody re-keys anything.

4 countries, one set of numbers

The group runs across four countries, and the consolidation happens at the database layer, so a group roll-up is a query rather than a month-end merge.

40+ tenants on one codebase

An internal platform plus two customer-facing B2B portals read the same data. A portal and an admin screen cannot show different totals, because there is only one set.

34 read-only assistant tools

The MCP layer in production, on the company's own Microsoft identity, every call logged. Read-only by design: an answer can be argued with, nothing can be broken.

It runs on our own maintained fork of the ASP.NET Boilerplate framework on .NET 10, all forty packages, which is an unusual thing for a studio to take on and the reason a platform this old is still on a current runtime.

How we build MCP servers

Trusted by

Bomark Ambalaza

Manufacturer of cardboard and corrugated packaging.

Bomark Pak

Packaging solutions for domestic and export markets.

Gumiimpex

Tyre sales, service and recycling.

Fanon

A long-standing Proceptio business partner.

The questions a group asks

What is Proceptio.BI?
A multi-tenant platform that puts documents, partners, items, projects, tasks, resource scheduling and analytics in one place, on top of one consolidated database. It is built and operated by Proceptio, and it runs in production for a group of companies including Bomark Ambalaza, Bomark Pak, Gumiimpex and Fanon.
We already have an ERP. Why would we add this?
Because the problem it solves is usually not one ERP, it is several. Four separate ERP systems sync one-way into a single cloud database on their own schedules, and everything above reads from that one place: the platform screens, the Power BI reports, the customer portals and the assistant. If you run one ERP and one company, you probably do not need this. If you run several and reconcile them in spreadsheets, that reconciliation is the product.
How do several ERPs become one set of numbers?
The consolidation happens at the bottom of the stack rather than the top. Each system syncs into the shared database on its own cadence, with no re-keying, and multi-company roll-ups are then a query rather than a merge. That is the difference between a group figure you can defend and one somebody assembled in Excel on the last day of the month.
Do the dashboards and the platform ever disagree?
They cannot, because they read the same database. Analytics and Power BI reports are built directly on the consolidated data rather than on exports of it, so a KPI on a dashboard and the same figure in a document list come from one model. Most of the time a number is argued about, the argument is really about which export it came from.
Can staff really ask an assistant about live company data?
Yes. The platform carries an MCP layer in production: about 34 tools that let staff ask Claude, Copilot or ChatGPT about the live consolidated data in plain language. Sign-in is the company's own Microsoft identity, each user only ever reaches their own tenant's data, and every call is logged against the real signed-in person. MCP is the open standard for connecting assistants to business systems; we explain how we build them on the MCP page.
Can the assistant change anything?
No. Every one of those tools is read-only by design. An answer can be wrong and you can argue with it, but nothing in the business can be broken by asking a question. Where a product of ours does need to write, as lawyer.ai does, the write is a separate two-step gate with an explicit human confirmation, never an open query surface.
Who sees what?
The platform is multi-tenant, so a company reaches its own data and nobody else's, and that boundary holds for the screens, the reports, the portals and the assistant alike. Inside a tenant, access follows the roles and permissions the platform already carries, and the audit log records who did what.