Business Brain
Rodesk.ai isn't a chat window bolted onto an ERP. It's an operational brain: it remembers, it understands how your company's data connects, it notices on its own when something breaks, and it carries processes end to end — through the same 199 actions your people and your API use.
CRM · Sales · Stock · Warehouses · Purchasing · Invoicing · Treasury · Online store · e-Invoicing
What Business Brain means
An assistant that only searches your data is still just a search engine. To be useful it needs memory, a map of how things connect, senses, judgement, reflexes — and hands. Rodesk.ai has all six, built deterministically wherever a mistake costs real money.
Long-term facts about every customer, supplier and product — plus company-wide context. Conversations persist, so you never explain the same thing twice.
Every entity gets a 360° view: everything it touches across the ERP — orders, invoices, stock, documents, conversations, signals, version history. One source of truth, and you can walk it.
12 deterministic detectors watching your data continuously: overdue invoices, stock below minimum, stalled orders, unreconciled bank lines, warranties about to expire. Each one arrives with its fix one click away.
199 typed actions — issue the invoice, confirm the order, move stock, register the payment. The same surface serves the UI, the AI and the API: there is no category of "things only a human can do here".
Revenue forecasting with a confidence interval, churn risk on an RFM model, anomaly detection, and explainable scores for leads and opportunities — with the contributing factors shown.
"When X happens, do Y" automations over those same actions. By default they propose and wait for a human; they only run unattended when you say so explicitly. Loop guard included, and the source is marked in the audit trail.
How it works
Features
The ERP foundation is complete and in production. What follows is the real inventory, not a list of intentions.
Romanian compliance
Generated invoices are UBL 2.1 / CIUS-RO and have been put through the official ANAF validator, offline, on real scenarios — not just the easy case.
The offline validator checks the schema and the CIUS-RO rules. Foreign VAT numbers are confirmed at submission, through VIES — that part belongs to ANAF, not to us.
Reports
Run against live data, not a warehouse that refreshes overnight.
Platform
The same 199 actions, documented with JSON schemas at GET /api/actions. Whatever the UI can do, your integration can do — no parallel endpoints drifting out of date.
Multi-tenant with row-level isolation, roles and per-action permissions, scoped API keys, a full audit trail and per-entity version history.
Outgoing events signed with HMAC-SHA256, with retries and a delivery log. The destination address is checked at connection time against DNS rebinding attacks.
Rodesk.ai talks to Rodesk.io (field service) over MCP: customers, sites and equipment stay in sync, with contextual links between the two apps.
7 adapters: SAGA (invoices, items, movements), CSV journals for sales, purchases and treasury, plus UBL for e-Invoicing. Your data leaves whenever you want, in formats your accountant recognises.
Every change carries an author, a timestamp and a source — human, AI or automation. You can always reconstruct how a document reached the state it's in.
What's next
The rest of the application is delivered and in production. These are the pieces still being built.
WhatsApp Business, Slack, Teams and VoIP telephony with call recording and transcription. The unified log is already built to receive them — what's left is the adapters and the provider accounts.
The XML declaration is generated and valid. Actually filing it to obtain the UIT code depends on tax portal credentials, exactly as e-Invoice submission does.
Vouchers, expenses, recurring documents and e-Transport work today through the action registry and the assistant. They're getting their own screens too.
Come in, connect your data and ask it for the first action. It learns the rest as it goes.
Open the app →