Business Operations OS

The operating system
for your business.

One system. Every operation.

Run your entire company from one place: customers, quotes, orders, inventory, purchasing, manufacturing, money, field work and people. Not modules bolted together — one system where every part works on the same data as the rest, with no integration left for you to build.

Open the app → See how it all connects

CRM · Sales · Invoicing · Treasury · Inventory · Warehouse · Purchasing · Manufacturing · Field service · Online store · Marketing · Projects · People · eDocs · Communication · Analytics

1platform, one account
731operations in the registry
18modules, one core
39automatic alerts
7domain assistants

One platform for your entire business

Control. Automate. Grow.

Three things an owner asks of a system — and can only ask of a single one, not of five programs that don't talk to each other.

Control

See at any moment who owes you money, what stock is sitting idle, which order is blocked, and what you earned on every customer, rep and order. The figure on the dashboard and the list behind it come from the same data, so they cannot disagree.

executive dashboard · profitability · credit limits · period close

Automate

Recurring invoices go out on their own, bank statements reconcile against documents, dunning letters follow your rules, and the assistant actually performs the operation instead of telling you where the button is. By default it asks for your approval; it goes fully automatic only if you say so.

39 alerts · "when X, do Y" rules · an assistant that executes

Grow

Start with what you need today and add a warehouse, an online store, manufacturing, field service or a second company — with no migration and no second program. The system grows with you, on the data you already have.

modules on demand · multiple companies · company groups · API keys

How it is built

Everything operations, on one platform

Four layers, not fourteen programs. Modules switch on separately, but they all sit on the same data core and they all go through the same registry of operations. Everything else follows from that: there is nothing to integrate, because there is nothing to join.

Intelligence
Business Brain — above every module, not inside one of them

Long-term memory, 39 checks running continuously over your data, forecasts, scores and automations. It sees sales, stock, money and field work at once, because it reads from the same place. An assistant wired to a single module could never tell you that a customer owes you money and has an open ticket.

7 domain assistantsmemory alertsforecasts scoresautomations document reading
Modules
They switch on separately. They never come apart.

Each domain is enabled when you need it and billed separately — but it does not become a separate application. Turn on the warehouse: same products. Turn on the online store: same stock. Turn on a second company: same account.

CRMSales & quoting ReceivablesInvoicing TreasuryProducts & stock Warehouse (WMS)Purchasing ManufacturingQuality Field & assetsOnline store MarketingProjects & time PeopleDocument vault (eDocs) CommunicationCompany group
Execution
731 operations — the only door through which anything changes

Issue the invoice, confirm the order, transfer the goods, record the payment: each is defined once, with its own validation and permissions. The same operations are used by the person in the interface, by the AI assistant, by automations and by API integrations. There is nothing only a screen can do — and no change without a trace in history: who, what, when, from which source.

validationrole permissions all-or-nothingaudit is not optional same for humans, AI and API
The core
One customer. One product. One document. One stock figure. One balance.

Data is not copied from one module into another and does not sync overnight. It exists once, and the modules look at it. That is why profit per order, customer balance and stock value cannot tell three different stories.

strict per-company isolationcode lists, not free text cost frozen on the documentperiods that close

Nothing to integrate

Two modules don't send data to each other — they read the same data. There is no import file between them, and no sync that can fail overnight and be discovered on Monday.

You pay for what you turn on

Modules are enabled per company and disabled the same way. What you haven't bought isn't in the menu and can't be reached by typing the address either — but the day you turn it on needs no migration.

Everything can be done from outside too

The same 731 operations are available through scoped API keys and signed webhooks. Your accounting software, your store or your own tool comes through the same door, with the same checks.

The modules, as they actually work

Run your entire company from one place

We're not selling you a list of screens. We're giving you the circuits a business actually runs on — each one closes by itself and touches the others exactly where you retype things today. Under each circuit you can read what it connects to next.

01

The commercial cycle

From the first sign of interest to money in the bank, on the same set of lines.

  1. Lead
  2. Quote
  3. Order
  4. Delivery
  5. Invoice
  6. Payment
  • Customers, contacts, leads, opportunities, activities, with lead conversion and a 360° record for each
  • Configurable sales pipelines — stages, win/loss reasons and picklists are set by the company, not by the developer
  • Territories, opportunity teams, targets and attainment per rep, with follow-up cadences scheduled and ticked off automatically
  • Quote → order → delivery → invoice with no retyping, with per-department quote templates and a PDF generated from the very document that prints
  • Quote approval on value or discount rules, with escalation on a deadline
  • Price lists per customer or price class, applied automatically as the line is entered
  • Credit limit that blocks the sale when exceeded and is released with a written reason
  • Payment on the customer account allocated across invoices — money can arrive before the invoice or cover several at once
  • Late fees, dunning letters and balance confirmations with the annex frozen at the requested date and discrepancies broken down per document
  • Cheques and promissory notes tracked as instruments: portfolio, deposit, endorsement, discounting, collection or refusal
  • Commissions per rep, on collected or invoiced amounts, with periods that open and close
  • Official company data pulled by tax ID and duplicate detection on entry, with merging of two records

Connects confirming the order reserves stock immediately · the invoice takes the cost frozen at goods receipt, so profit per order is real, not estimated · payment closes the balance and frees the credit limit · any step in the chain can be handed to the AI assistant, with your permissions, not more.

02

Purchasing and true cost

What you buy, when, at what price — and what the goods really cost once freight and customs are in.

  1. Requirements
  2. Purchase order
  3. Goods receipt
  4. Supplier invoice
  5. Cost in stock
  • Replenishment requirements — what is below minimum and what is already on order, so you don't order twice
  • The purchase order as a living document: print, email, partial receipt with backorder, generation from requirements
  • Goods receipts with scheduling, inspection and rejection — or built straight from the lines of the supplier's invoice
  • Item aliases — the supplier's code is linked once to your item and matches on its own from then on
  • Three-way match — order, receipt, invoice — with a variance report
  • Landed costs allocated — freight, customs, handling — that genuinely enter the cost of goods, by value, quantity or weight
  • Negotiated supplier prices on quantity breaks, with item, category and supplier-wide discounts
  • Supplier invoice approval on value rules and payment batches to suppliers
  • Import of received invoices straight from the tax authority's portal, plus supplier returns
  • Supplier performance (OTIF), purchase price evolution, and RFQs with who won them

Connects the receipt raises stock and fixes the cost every outgoing invoice will use · requirements are computed from sales reservations and manufacturing consumption · the supplier invoice lands in payables and in treasury payments · the alert finds you before you run out, not after.

03

Stock, warehouse and manufacturing

A single stock engine for everything that moves: sales, consumption, transfers, counts, production.

  1. Catalogue
  2. Warehouses & bins
  3. Bill of materials
  4. Work order
  5. Consumption & output
  6. Real stock
  • Catalogue with variants, attributes and CSV import that updates by code and does not duplicate on a second run
  • Product data filled from the web — the app reads the manufacturer's page and proposes the attributes
  • Stock per warehouse and bin, with a movement journal filtered by product, warehouse, type and period
  • Every movement through one engine: receipt, delivery, consumption, transfer, adjustment — plus transfer notes with separate dispatch and receipt
  • Stock counts with open, record, apply and cancel; consignment stock tracked separately
  • Warehouse (WMS): bins, map, put-away suggestions, tasks assigned per person
  • Manufacturing of any kind: recipes with variants, work centres and routings, parallel operations, custom units of measure
  • Reporting per operation with labour and machine time, disassembly, rework and subcontracting
  • Make-to-order — the customer order calls the work order directly
  • Consumption and output notes generated from reporting, not typed by hand
  • Quality control per batch, with certificate, measurements, verdict and quarantine of the rejected quantity
  • Quantitative-value or global-value accounting, chosen per warehouse

Connects it is the same stock for sales, the online store, manufacturing and the vans in the field — not four records arguing · production consumption lands the cost exactly on the finished product · quality can stop goods before they reach the customer · the warehouse is a layer over stock, not a second database.

04

Field service and assets

Work at the customer site, from the phone call to the invoice — on the same customers and the same stock.

  1. Contract
  2. Ticket
  3. Dispatch
  4. Job
  5. Job sheet
  6. Invoice
  • Work orders with resolution deadlines, dispatching and configurable statuses
  • Jobs — time booked per order, checklists, photos, service report signed by the customer
  • Assets with QR and NFC tags, full service history and warranties tracked
  • Service contracts and maintenance sites — the locations and buildings you cover
  • Rentals — equipment fleet, handover/return, signed protocol, day/week/month rates
  • Van and technician stock — goods in the vehicle are tracked differently from the warehouse
  • Workshop with work stations, a board of jobs in progress and turnaround time
  • Mobile app for technicians, with QR scanning and on-site work

Connects the technician works in the field app rodesk.io, on the same account, with no second password · the customer is entered once and exists in both · the closed job sheet becomes an invoice in one click, labour and parts included · parts used draw down the van's stock · an expiring warranty raises an alert on the dashboard.

05

Money and statutory filings

Full invoicing, cash and bank, plus e-invoicing without a separate module and without an extra fee.

  1. Document
  2. e-Invoice
  3. Bank statement
  4. Reconciliation
  5. Balance
  6. VAT
  • Every document type: invoice, credit note, proforma, delivery note, receipt, recurring invoice — each with its own series
  • VAT treatment per product, overridable per line: taxable, exempt with credit, exempt without credit, reverse charge, cash accounting, out of scope
  • Foreign currency invoicing with the rate frozen on the document — balances no longer add up different currencies
  • Intercompany invoices inside a group, generated from one side into the other
  • Period close — past a given date, nothing can be written any more
  • Treasury: cash and bank accounts, receipts, payments, transfers, balances
  • Bank statement import and reconciliation against documents, with suggestions by amount and invoice number
  • Direct bank connection (PSD2) with automatic transaction retrieval
  • Romanian e-Invoicing and e-Transport: submission, status tracking, import from the portal, UIT code
  • Accounting codes per product, warehouse and partner, with export to your accounting software

Connects the invoice is born from the order, job sheet or contract that produced it — not written from scratch · reconciling the statement closes the customer balance and stops dunning letters that have no business going out · VAT, cash flow and profit are computed from the same documents, not from three spreadsheets.

06

Demand: store, marketing, market

You sell online and watch your market from the same system that holds your stock and your invoices.

  1. Catalogue
  2. Storefront or Magento
  3. Online order
  4. Payment
  5. Shipping
  6. Invoice
  • A public store for every company, with its own address and visual identity, content pages and shipping methods
  • Promotions with a usage cap that cannot be exceeded, no matter how many buyers click at the same instant
  • Orders end to end: capture, card payment via Stripe, picking, shipping, completion, cancellation, invoicing
  • Gift vouchers, reviews and customer questions, with moderation and replies
  • Magento Open Source connector for those who already have a store: the catalogue leaves from Rodesk, orders come into Rodesk, tracking number and invoice number go back to the customer
  • Email campaigns with recipient consent tracked as a state, segments and a results report
  • Competitor prices — link your item to its page at a competitor and learn where you stand against the market
  • Assortment analysis — what the competition sells and you don't carry
  • Pricing policies — match, undercut, premium or margin-based — with the recommended price computed and applied on approval
  • Which products deserve the ad budget, ranked by margin, stock and sales velocity

Connects an online sale draws from the same warehouse as a sale from the office — there is no "shop stock" · the online order becomes an invoice with the correct VAT treatment, not an export to reconcile · the pricing policy applies to the real catalogue, with margin computed from the cost in stock.

07

People, projects and time

Hours worked reach the invoice, and personnel files live in the same system, with sensitive data protected.

  1. Project
  2. Tasks
  3. Time entry
  4. Approval
  5. Invoice by hours
  • Service projects with phases, tasks, budget and profitability, plus unbilled work in progress
  • Time booked per project, submitted for approval, with the rate frozen at the moment of approval
  • Billing by hours — hours already invoiced cannot be invoiced twice, and a credit note releases them
  • Contracts and subscriptions with notice periods, renewal and termination tracked as data, not as memories
  • Personnel files and employment contracts, with extension and termination
  • Leave — request, approval, day balance, with public holidays taken into account
  • Sensitive data protected on the server: salary and full national ID leave only to administrators and HR; a team lead sees who is on leave without learning what they earn
  • Alerts for expiring contracts, probation periods ending, unused leave and unapproved hours

Connects a booked hour becomes an invoice line without passing through any file · the cost of that hour enters project and customer profitability · field jobs and office time add up in the same hours-per-employee report.

08

The document vault — eDocs

Your company's paperwork in one place: it arrives on its own, is read on its own, is found by content, and gets approved on a deadline.

  1. Intake
  2. Inbox with AI proposal
  3. Indexing
  4. Dossier
  5. Approval
  6. Signature
  7. Archiving
  • Documents arrive on their own, by four routes: a company mailbox, an agent watching the network scanner's folder, scanning from a phone, and API capture
  • A scanned stack splits itself — put a barcode sheet between documents and the scanner's single PDF is cut into separate documents
  • AI proposal on intake: document type, title and fields — supplier, number, date, amount — filled from the content. You confirm or correct; it applies by itself only above the confidence threshold you set
  • Search inside content, not just filenames — including scanned paper: OCR in Romanian and English over pixels, so a photographed invoice is found by the number printed on it
  • Document types with their own fields and controlled value lists; folders with inherited permissions; tags, links between documents (annex, reply, supersedes) and saved filters
  • Versions with check-out and check-in, a recycle bin with restore, and a PDF viewer with in-page search and highlighting
  • Dossiers with a checklist — a "partner file" requires a contract and an invoice, and progress shows in the list without opening it
  • Approval flows with deadlines: steps, conditions on the document's value, escalation when the deadline passes, delegation while someone is on leave
  • One-click approval from the email, through a signed link that expires — nobody has to open the app to release an invoice
  • Electronic signature with a code sent by email, enforced signing order, an audit page and a signed version that can no longer be altered
  • Correspondence register — gapless numbering even when ten people register at the same instant; a stamp on the first page and an exportable register list
  • Retention and legal hold: what is kept, for how long, and what gets destroyed — with a destruction certificate issued automatically
  • Sharing by expiring link, with a password, a download cap and a watermark on the PDF; plus file requests — you send a list of documents and the customer uploads them without an account
  • Validated PDF/A, antivirus on upload and a complete audit log, with export

Connects a document lives exactly once — Rodesk keeps the reference, not a copy, so the contract appears on the customer and on the contract at the same time, with no two copies drifting apart · the documents button sits in 14 screens: invoices, supplier invoices, orders, goods receipts, quotes, delivery notes, work orders, contracts, projects, employees, tenders · the call carries the person who made it, so permissions are judged for them: "they see the customer in Rodesk" does not mean "they see its paperwork" · an invoice received by email arrives already read, with the supplier matched by tax ID — and the goods receipt is built from its lines.

The layers that run through everything

Not modules — services every circuit uses

Printed forms and output

  • Ten forms on one frame: invoice, receipt, goods receipt, supplier payment, statement, transfer note, consumption note, output note, quality certificate, quote — identical on paper and in PDF
  • Letterhead, logo and company details come from one place, not configured twice for every document
  • Per-department templates — header, terms, footer and validity period of each division
  • The PDF is generated on the server from the very document that prints, so what the customer sees is what you saw
  • The paperwork itself lives in the document vault — see eDocs, circuit 08

Communication and calendar

  • One log of every conversation — phone, email, WhatsApp, Slack, Teams, SMS, meetings; with direction, person, duration and the document it relates to
  • Automatic summary: the gist, what remains to be done, the tone, and when it is wise to follow up
  • Emails from the customer land on their timeline by themselves, matched on the sender's address, with no duplicates
  • A calendar of your own with overlap warnings, plus subscription from Google, Outlook or Apple Calendar
  • CRM tasks appear alongside, without being written a second time

Access, companies and permissions

  • One account, several companies — the same person can be an administrator at their own firm and an operator at a client's; the active company switches from a toggle
  • Company group (holding) — consolidated reports, with intercompany sales shown as an adjustment rather than quietly subtracted; shared group CRM, read-only
  • Roles composed by the customer — permissions per module, capabilities and exceptions on individual operations
  • My account: profile, password, two-factor authentication, connected devices, with remote sign-out
  • Sandbox companies — a test environment where outbound links (tax authority, accounting, Magento, email) are cut at four points, so a trial can never file a real invoice

Analytics and reports

  • 59 reports run on the data as it stands right now, every one exportable to CSV
  • Free-form analysis — you pick the dimensions and measures, and from any cell you drill down into the documents that produced the figure, with the same filters
  • Dashboards you compose yourself, saved for the company or for the whole group
  • Executive dashboard — money, sales, debts and stock on the front page, filtered on the server by each person's permissions
  • In-app user manual, trimmed to each person's permissions

What being one system actually buys you

One system. Every operation.

The difference between "a bundle of programs" and an operating system shows up in the things you no longer have to do a second time.

The customer, entered once Enter them in one place and they are everywhere — in the quote, the invoice, the field ticket, the store. The link is held on a code, not on a name, so it doesn't break when the customer renames itself.
Stock, one single truth The same quantity is seen by the salesperson, the online store, the warehouse worker and the technician with the van. There is no "ERP stock" and "shop stock" arguing at month end.
Cost travels with the goods The supplier price, plus freight and customs, lands on the sales invoice line by itself. Profit per order is calculated, not estimated at year end.
One trace in history Every change — made by a person, by the AI assistant or by an automation — goes through the same registry and leaves the same trace: who, what, when, from which source.

The intelligence layer

Business Brain — the assistant that executes

Memory, links, alerts, execution, forecasts, automations. Computed from rules, with the factors on display.

Memory

It remembers long-term what was agreed with each customer, supplier and product — plus the company's commercial rules. Conversations are kept, so you don't explain the same thing twice.

note · recall · pin

The 360° record

Every customer, supplier, product or project has a single record: orders, invoices, balance, stock, documents, conversations, alerts and change history, gathered on one screen, with links in both directions.

one screen

Alerts

39 checks running continuously over your data: overdue invoices, invoices not filed, suppliers past due, stock below minimum, blocked orders, unreconciled statements, employment contracts and warranties about to expire, prices below the competition. Every alert arrives with its fix one click away.

rules over data

Execution

731 operations defined once — issue the invoice, confirm the order, transfer the goods, record the payment. The same ones for the person, the assistant and integrations: there are no operations only the interface can perform.

one registry, validated

Forecasts and scores

Collections forecast with an error margin, churn risk based on each customer's ordering cadence, detection of sudden sales drops, scoring for leads and opportunities — each with the factors that formed it shown alongside.

factors on display

Automations

"When X happens, do Y" rules, built from the same operations. By default they prepare the work and ask for human approval; they go automatic only if you explicitly ask. They cannot trigger each other endlessly, and the source stays written in history.

with the rule author's permissions

Seven assistants, cut by domain: Generalist, Sales, Purchasing, Warehouse, Finance, Projects, Market & tenders. Each receives only the operations of its domain and of your role — the assistant cannot do what you are not allowed to do either. AI keys belong to each company and are set from Settings.

How it works

From signal to document issued

SeesChecks run over the data and raise whatever crosses the threshold you set.
LinksThe alert arrives with the customer, the order, the stock and their history.
ProposesYou receive the work already filled in with real data.
ExecutesAfter approval: validation, role permissions, all or nothing.
Leaves a traceWho, what, when and from which source: person, assistant or automation.

How you work in it

One menu, every domain, one Ctrl+K

Pick the domain on the left. Its tabs appear above the page. Nothing is looked up in another program.

Menu Dashboard AI assistant Operations Business Brain Office CRM ERP Projects Marketing People Online store Settings
ProductsCatalogue enrichmentBrands StockWarehousesManufacturingWorkshop PurchasingSuppliersGoods receiptsQuality control Invoicinge-Invoicee-Transport TreasuryReportsFree-form analysisBI analysis

The tabs above belong to the ERP domain. The other domains have their own. Jump straight into any of them with Ctrl+K — which finds operations too, not just pages.

Business BrainSignals · Analysis · Automations · Memory · Activity
OfficeCommunication · Calendar · Documents
CRMCustomers · Sales · Pipeline · Cadences · Tenders · Contracts
ProjectsProjects · Time · Approvals
MarketingCampaigns · Promotion · Contacts · Templates · Market radar · Pricing policies
PeopleEmployees · Leave
Online storeOrders · Catalogue · Promotions · Reviews · Reports · Storefront

Tabs are not written by hand

They come from the same structure as the menu. Two lists cannot drift apart when there is only one.

You see only what is yours

The menu is trimmed to what the company bought and to what you are allowed to see. Typing the address by hand changes nothing.

It bends to how you work

The menu collapses to icons, remembers what you opened and carries counters: overdue invoices, approvals waiting. Four themes and three layout models.

Pricing

One platform. You turn on what you need.

An operational core, an intelligence layer, and add-ons only where you have extra infrastructure: warehouses, stores, company groups.

Rodesk Business On request / month / company The operational core: CRM, sales, invoicing, treasury, products and stock, purchasing, manufacturing, documents, projects, marketing, people, communication.
Rodesk FSM On request / user / month For the people working in the field: tickets, dispatching, mobile app, assets, workshop, service contracts, van stock. The rate drops as the team grows.
Rodesk AI On request / month / company The assistant that executes, memory, alerts, forecasts, scores, automations and document reading.
Rodesk eDocs On request / month / company The document vault: automatic capture, OCR, dossiers with checklists, approval flows, electronic signature, correspondence register and retention.

Added only where you have the infrastructure that calls for them:

WMS — per warehouse Commerce — per online store Holding — per company group

No dozens of licences to work out, and no separate fee for e-Invoicing or e-Transport. Tell us how many users, technicians, warehouses, sites and companies you have, and we send you the price grid and the exact configuration, with the total cost, before any implementation begins.

What are you interested in — tick as many as you like

All of your business. One system.

One platform for your entire business. Start with what you need today and add modules as the company grows — with no migration and no second program.

Open the app → Request a quote