Home / Kolab Digital Estate / Kolab Automation

Kolab Automation · Otomatik In build

Delete the boring work, not the jobs

The same order typed three times, the month-end report built by hand at 22:00, the invoice chase that depends on someone remembering: Otomatik maps that work and hands it to robots you can audit. Your people keep the human work; the drudgery gets a funeral.

  • Typed once: the order becomes the invoice becomes the ledger line
  • Scheduled jobs never forget the 07:00 report or the Friday backup check
  • Licence audit in rupees: seats paid versus seats actually used
  • The robot proposes, a person approves, every run is on the record
app.kolab.mu/otomatik Kolab AutomationOverviewProcess MapsCatalogueAutomationsRunsApprovalsLicencesSavingsHealthAutomation overviewMURJul 2026Live automations14+2%Hours saved this month62+8%Errors caught9+3%Runs per day, last 30 daysJFMAMJJNeeds attentionStock alerts · no run since FridayFailingBank vs books · mismatch Rs 4,180Needs a humanInvoice chasing · 6 reminders sentRan 08:00Design tool · 6 seats idleReviewRecent activity

Made for

Distributors and wholesalersRetailers with a till and a bank accountServices firms drowning in subscriptionsAccounting practices and back officesFactories with month-end crunchEvery Kolab customer

Retyping is where mistakes breed

In a typical Mauritian SME the same order is typed three times: once in the order book, once on the invoice, once in accounts. The month-end report is assembled by hand at 22:00. Invoice chasing depends on someone remembering. And the business quietly pays dollar subscriptions for tools nobody fully uses. None of this is anyone's fault; it is just how work grows when nobody maps it.

Human error is not a people problem, it is a process problem: every retype is another chance for a slipped digit, and the person blamed for it was set up by the process. So Otomatik starts with a map, not a robot: who does what, where the work waits, where it breaks. Only then do the automations arrive, adapted from proven recipes, run with retries and logs, and gated by a person wherever judgement matters.

Two things make Otomatik different from an automation brochure. First, the Mauritius 2.0 position: automation exists to delete drudgery so people can do human work, serving customers, making things, deciding, and we will never sell it as headcount reduction. Second, the shape: software plus craftsmanship. The platform runs your automations; the automations themselves are built with you at a fixed rupee price each, with published bulk discounts.

We automate our own work first

Otomatik is in build, but it productizes an existing practice, not a dream. NexOps builds and sells automations today, and runs its own automation infrastructure every day.

  • Automation builds are a working NexOps service line with published rupee pricing and bulk discounts
  • A workflow engine and a WhatsApp channel run daily on NexOps servers, automating monitoring, reports and alerts
  • The catalogue recipes are adapted from automations already running, not invented for a brochure
  • Development happens at our cost until the automation passes your test, never billed as open-ended hours

Modules

Everything inside Kolab Automation

Every module is a brick. Start with what hurts most, snap on the rest when you are ready.

Process Map

Capture how the work actually flows today: who does what, where it waits, where it breaks. The map comes before any robot.

Automation Catalogue

Proven recipes ready to adapt: invoice chasing, morning reports, order-to-invoice flow, stock alerts, backup checks, WhatsApp notices.

Workflow Runner

Triggers, steps and actions across your systems, with retries and logs on every run.

Human-in-the-loop Approvals

The robot proposes, a person approves, and every run is audit-trailed. Automation you can trust.

Licence Optimisation

Every subscription and licence inventoried: seats paid versus seats used, duplicate tools, dollar subscriptions with rupee alternatives, and a savings report in rupees.

Double-entry Elimination

Data typed once flows everywhere it is needed: the order becomes the invoice becomes the ledger line.

Reconciliation Bots

Two lists compared automatically: bank versus books, stock versus sales, roster versus punches. Mismatches surfaced, not buried.

Scheduled Jobs

The 07:00 report, the month-end close checklist, the Friday backup verification: things that never get forgotten again.

Error-proofing at Entry

Validation where the data is born, so the mistake never travels.

Savings Tracker

Hours saved, errors caught and rupees saved, measured honestly and never inflated.

Automation Health

A broken automation is an incident: dead-man switches and alerts via Kolab Monitoring, because a silent robot is worse than no robot.

Estate Score input

Unused paid licences and failing automations cost points on the Estate Score you share with Kolab Websites, Domains and Monitoring.

Alert to action

A Kolab Monitoring alert can open the right checklist or work order automatically: the fridge breach becomes a task with an owner, not just a ping.

A closer look

How Kolab Automation feels day to day

The map first

No robot before the map

Otomatik starts by walking the work with your team: who touches the order, where it waits, where it breaks. The map becomes a pipeline you can see, from mapped to building to live, and nothing gets automated that was not understood first.

  • Every handover, wait and retype captured in plain words
  • The pipeline shows what is mapped, what is building, what is live
  • Catalogue recipes are adapted to your flow, not forced onto it
app.kolab.mu/otomatik/pipeline Automation pipelineMapped3Order to invoice flowMonth-end close checklistSupplier statement matchBuilding2Invoice chasingStock alerts · WhatsAppLive4Morning report · 07:00Bank vs books botBackup check · FridayPayslip delivery
The licence audit

Stop paying dollars for empty seats

Most businesses cannot list what they subscribe to, and dollar billing hides the creep: the rupee slips, the invoice grows, nobody notices. Otomatik inventories every licence, compares seats paid with seats used, and prices the waste in rupees.

  • Seats paid versus seats actually used, tool by tool
  • Duplicate tools and dollar subscriptions with rupee alternatives flagged
  • A savings report in rupees, often larger than the Otomatik bill
app.kolab.mu/otomatik/licences Licence audit · July+ NewSearch…TOOLSEATS PAIDSEATS USEDACTIONDesign tool10 seats · USD3 activeCut 6 seatsCRM seats25 seats · USD22 activeRight-sizeVideo meetings15 seats · USD15 activeKeepE-signature tool5 seats · USD0 activeUnused since MarchCloud storage2 plans1 in useMerge plans
Reconciliation

The mismatch found on Tuesday, not at month end

A reconciliation bot compares two lists that should agree and speaks up when they do not: bank versus books, stock versus sales, roster versus punches. The report lands on WhatsApp, a person acknowledges it, and the resolution goes on the record.

  • Mismatches surfaced the day they happen, not buried in a drawer
  • A human acknowledges and resolves; the bot never hides a difference
  • Every comparison logged, every resolution audit-trailed
Reconciliation bot Bonzour, Priya Bank vs till · Tue: till Rs 48,230, bank Rs 47,89009:46Mismatch Rs 340 · card batch 2 not settled yet09:42Ack. Checking with the bank this morning.09:48Resolved · batch settled 11:04 · books match09:44
The savings

Measured honestly, never inflated

Every automation logs what it actually did, so savings are counted, not guessed: hours of typing deleted, errors caught before they travelled, rupees recovered from licences and mistakes. If a number is soft, the report says so.

  • Hours, errors and rupees on one monthly report
  • Counted from real runs, never estimated from a brochure
  • Retired manual tasks marked with a boring-work funeral badge
Savings · July Bonzour, Priya 62 hours savedMostly evening data entry+9 vs June9 errors caughtBefore they reached a customerRs 18,400 savedLicences cut and errors avoided3 tasks retiredBoring-work funerals heldShare the report

Local by design

Built for how Mauritius actually works

The waste Otomatik hunts has local shapes: dollar subscriptions, the 22:00 month-end, cash in the till. The fixes speak your languages and respect your law.

Dollar subscription creep

USD billing stings twice here: the price, and the rupee slipping underneath it, compounding the waste. The licence audit usually pays for itself in its first month.

The 22:00 report

Month-end crunch is a habit, not a law. The report someone assembles by hand at night becomes a scheduled job that is waiting, checked, at 07:00.

Cash reconciliation

Till versus bank versus books is real daily work in a cash economy. A bot does the comparing; a person only handles the differences.

The family advantage

Automations between Kolab products come pre-built: attendance flows to payroll, the order to the delivery round, the sale to the ledger.

Three languages

Any automation can notify in English, French or Kreol Morisien, per person, so the stock alert reads naturally to whoever receives it.

DPA 2017

Automations that touch personal data are logged, scoped and reviewable, so the robot respects the same law your people do.

Boost in Otomatik: the points go to people

Boost never rewards a robot and never measures a person against one. It celebrates the human wins automation makes possible: catches, retirements, judgement.

Error-catch celebrations

When a reconciliation bot surfaces a mismatch and a person resolves it before it costs money, that is a team win, and it earns points.

Boring-work funerals

When a team retires a manual task for good, a badge marks the funeral. The hour that comes back every week is the real prize.

Never people versus robots

No leaderboard ever compares a person's speed with an automation's. Robots take the boring work; people get the credit for the human work.

More about Kolab Boost

In the wild

What it looks like in real businesses

A distributor in Plaine Lauzun

Orders were typed three times: order book, invoice, accounts. Now they flow once, order to invoice to ledger, and the evening data-entry hour is simply gone.

A services firm of 22 in Moka

The licence audit found 40 paid seats across tools for 22 people. The firm now pays in rupees for what it actually uses, and reads the savings report every month.

A retailer in Rose-Hill

The bank-versus-till bot catches Tuesday's mismatch on Tuesday. Month end stopped being an investigation and went back to being a date.

Pricing

Kolab Automation pricing, in rupees

Indicative launch pricing, per organisation per month, VAT excluded, unlimited teammates. Automation builds are priced separately at a fixed rupee price each, with published bulk discounts: 5 built together save 15%, 10 save 25%, 20 save 35%. Development runs at our cost until each automation passes your test.

Otomatik Platform

The runner, ready for your first robots.

Rs 990 / organisation / month
  • Workflow runner with retries and logs
  • 3 live automations
  • Scheduled jobs and WhatsApp notifications
  • Automation health alerts
Start with Platform
Founding rate

Otomatik Biznes

The month-end crunch, deleted.

Rs 2,400 / organisation / month
  • 10 live automations
  • Licence optimisation review
  • Reconciliation bots
  • Human-in-the-loop approvals
Go Biznes

Otomatik Group

Every process, mapped and running.

Rs 4,900 / organisation / month
  • Unlimited automations
  • Quarterly process reviews
  • API access
  • Priority support
Talk to us

Prices per person per month, VAT excluded. Annual billing takes two months off. Indicative pricing: nothing is charged before general availability, and pilot customers lock their launch price for two years.

Questions

Asked all the time

Is Otomatik software, or a service?
Both, honestly. The platform runs your automations with logs, retries, approvals and health alerts. The automations themselves are built with you at a fixed rupee price each, with published bulk discounts: 5 together save 15%, 10 save 25%, 20 save 35%. Development happens at our cost until the automation passes your test, never as open-ended hours.
Will this replace our staff?
No, and we will not sell it that way. Otomatik deletes drudgery: the retyping, the 22:00 report, the chasing from memory. Your people keep the human work: serving customers, making things, deciding. That is the Mauritius 2.0 position, and it is not negotiable.
What happens when an automation breaks?
It becomes an incident, not a mystery. Every automation carries a dead-man switch, and a robot that goes quiet raises an alert through Kolab Monitoring. A silent robot is worse than no robot, so silence is treated as failure.
Can a person stay in charge of what the robot does?
Yes, and for anything that moves money or touches people, we insist on it. Approval gates put a person between the robot's proposal and the action, and every run is audit-trailed: who approved what, when, and what happened next.
How does the licence audit get its data?
Through a structured review with you: invoices, statements and admin screens, inventoried together. Seats paid are compared with seats used, duplicates and dollar tools with rupee alternatives are flagged, and everything is priced in rupees so the decision is easy to make.
Our systems are not all Kolab products. Can you still automate?
Yes. The runner connects to what you already use through files, emails, spreadsheets and APIs. Kolab-to-Kolab automations simply come pre-built: attendance to payroll, order to delivery round, sale to ledger.

Book a funeral for the boring work

Start with one process map and three automations at the founding rate. If a build does not pass your test, you do not pay for it.

Book a demo See all products