We build the intelligence layer your business runs on.
Ontilus designs and engineers bespoke AI operating systems for complex, multi-entity
operators. We turn fragmented operational data into one live source of truth — and one
engine that tells your leadership what to do next.
Engineering AI systems for multi-entity operators worldwide
Built onSupabaseAWSFirebaseGoogle CloudApple iOS
Capabilities
Four things every Ontilus system does.
Real-time telemetry
Live operational streams — transactions, inventory, labour, finance — unified across every legal entity and reconciled against your own close reports.
Webhook & sync-agent ingestion
Legacy and on-premise systems included
Source-of-truth reconciliation
Predictive engines
Demand forecasting, pricing optimisation and variance detection that run before the day starts — not after it ends.
7-day demand & revenue forecasting
Cost and price variance alerts
Automated resourcing & purchasing plans
The decision engine
It answers the daily why and recommends the next best action. A strategic partner in the business, not a static report.
Daily briefing, written for the reader
Root-cause on every variance
Ranked, costed recommendations
Enterprise architecture
Role-based access, entity-level isolation and audit-ready logging — designed from day one for regulated, multi-company groups. Built in Malaysia, for groups running several entities on separate systems.
Scoped by entity, brand and site
Full change history on every record
Isolated VPC, regular key rotation
The Ontilus platform
One intelligence layer. Every system you run.
We don't hand over a dashboard and leave. We build the layer that sits between your
operations and your decisions — on your data, in your entity structure, under your
governance.
AI engine Automation Data intelligence Security first
Every engagement is bespoke, but almost all of them resolve into these two — and they're designed to fuse into a single engine. The Command Center below is shown answering four different sectors' questions; the figures are illustrative, the modules are what stay constant.
System 01
The Command Center
Real-time operations, AI decisioning and executive intelligence on one live surface — from the front line to the board pack.
Live demo
Net revenue — today
RM 428,650
▲ 6.2% vs target
Orders
7,412
▲ 3.1% WoW
Average order value
RM 57.83
▲ 2.9% WoW
Stores above target
24 / 33
9 need attention
Gross margin by channel
Cost intelligence · target 42.0%
Own stores44.1%
Own e-commerce46.2%
Marketplaces38.6%
Wholesale35.4%
Margin & stock alerts
Detected in the last 7 days
+9.4% Landed cost, core range Supplier 04
18 SKUs below reorder point 6 best-sellers
+1.5% Marketplace fee change two channels
42 Lines under 60% sell-through season 3
Stock is uneven, not short — 6 of the 18 shortfalls exist in another store
Morning briefing
Decision engine · generated 06:00 · for the Retail Director
Revenue is 6.2% ahead of target, but the mix is moving toward your two lowest-margin channels. Two actions are worth taking today.
01
Rebalance stock before reordering
Six of the eighteen shortfalls are sitting in a store that is not selling them. Transferring costs freight; reordering costs freight and working capital.
Est. impact +RM 38,000 working capital · confidence high
02
Reprice the 42 slow-moving lines now
Sell-through has been under 60% for six weeks. Marking down in-season recovers more than clearing at end of season, and the model puts the break-even at week nine.
Est. impact +RM 61,400 margin · confidence medium
Appointments — today
1,284
▲ 4.4% vs plan
Room utilisation
78.4%
▼ 6.6 pts vs target
No-show rate
9.2%
▼ 1.4 pts WoW
Branches reporting
12 / 12
All feeds healthy
Utilisation by branch
Operations · rooms and practitioners · target 85%
Branch 0188.1%
Branch 0483.6%
Branch 0766.2%
Branch 1171.9%
Scheduling & governance alerts
Open now · across all entities
34 Unfilled slots this week Branch 07
128 Recalls overdue 6-month review
11 Consent records expiring within 30 days
100% Access events logged audit trail complete
Built from booking and operational data — clinical systems are read, never replaced
Morning briefing
Decision engine · generated 06:00 · for the Group Operations Director
Demand is ahead of plan while utilisation is 6.6 points below target — the group is turning work away in one place and idle in another. Two actions are worth taking today.
01
Move two sessions from Branch 01 to Branch 07
Branch 01 is running at 88% with a three-week wait; Branch 07 sits at 66% and is eleven minutes away. The waitlist overlaps both catchments.
Est. impact +RM 24,000 / month · confidence high
02
Run the overdue recall list into the unfilled slots
128 patients are past their review date and 34 slots are empty this week. Consent is current on 119 of them; the rest are excluded automatically.
Est. impact fills 26 of 34 slots · confidence medium
Billable utilisation
71.2%
▼ 3.8 pts vs target
Realisation
88.6%
▲ 1.2 pts MoM
Work in progress
RM 1.42M
31 days average age
Engagements at risk
6
of 84 active
Utilisation by practice group
Operations · billable hours against target 75%
Advisory79.4%
Assurance76.1%
Tax64.8%
Corporate68.3%
Engagement risk
Cost intelligence · flagged against agreed scope
142% Hours against estimate Engagement 2214
RM 84k WIP over 90 days 4 engagements
118% Hours against estimate Engagement 2318
3.1 days Average time-entry lag firm-wide
Scope drift is flagged against the estimate mid-engagement, not discovered at invoicing
Morning briefing
Decision engine · generated 06:00 · for the Managing Partner
Realisation is improving, but utilisation is 3.8 points short and it is concentrated in two practice groups. Two actions are worth taking today.
01
Raise a change order on Engagement 2214
It is at 142% of estimate with six weeks still to run. The scope moved in week three and was never papered; every hour past this point is written off by default.
Est. impact +RM 96,000 recoverable · confidence high
02
Move four Tax staff onto the Advisory pipeline
Tax is at 64.8% between filing seasons while Advisory is turning down work at 79.4%. Three of the four have the required qualification already.
Est. impact +RM 47,000 / month · confidence medium
Net sales — today
RM 428,650
▲ 6.2% vs target
Covers
7,412
▲ 3.1% WoW
Average spend
RM 57.83
▲ 2.9% WoW
Outlets above target
24 / 33
9 need attention
Food cost % against target
Cost intelligence · by entity · target 29.3%
Entity A28.1%
Entity B33.8%
Entity C30.2%
Entity D34.6%
Supplier price drift
Detected in the last 7 days
+9.4% Chicken thigh, boneless Supplier 04
+6.8% Cooking oil, 17L Supplier 01
+4.1% Mozzarella block Supplier 09
13m 05s Cold larder ticket time target 9m
Ingredient stock auto-debits on every sale — alerts fire before the shortfall
Morning briefing
Decision engine · generated 06:00 · for the Group Operations Director
Group is tracking 6.2% ahead of target on revenue, but gross margin is being eaten from two directions. Two actions are worth taking today.
01
Approve the poultry supplier switch
Chicken thigh is up 9.4% at Supplier 04 while Supplier 07 has held price for 11 weeks. Same spec, same lead time.
Est. impact +RM 4,180 / month · confidence high
02
Re-staff cold larder for dinner service
Cold larder is 45% over target ticket time and is the largest driver of dinner table-turn delay across six outlets.
Est. impact +RM 2,600 / week · confidence medium
System 02
The Growth Agent
Unified customer intelligence and an engine that runs engagement on its own — so retention stops depending on who remembered to send the campaign.
Customer intelligence
A single 360° profile per customer, patient, student or client — one identity across every entity you operate.
Unified profiles across all brands
Engagement frequency & value patterns
Preference and service-note fields
VIP, corporate and household tagging
Engagement automation
Journeys that fire themselves, on time, every time — with consent tracked per customer, per channel.
Milestone & renewal campaigns
Onboarding, loyalty & referral journeys
Lapsed-customer win-back journeys
WhatsApp, email & SMS, fully automated
Market intelligence
External signal measured against internal return — so marketing spend is judged on contribution, not impressions.
Competitor pricing & trend tracking
Review & sentiment monitoring
Social, influencer & campaign performance
CAC, repeat rate and lifetime value
Fused with the Command Center, operational and customer data become one predictive engine.
Ask the system
Answers the daily why.
Your team already asks these questions. Today the answer takes three days and four spreadsheets.
ontilus · decision enginescope: group · all entities
›
How we deploy
Live in 12 weeks. Proven before it scales.
Four phases, in the same order every time. Nothing goes group-wide until it reconciles against numbers your finance team already trusts.
Weeks 1–3
Discovery
Where the pain actually is
Sit with the teams doing the manual work and map the real process
Audit every source system, including the legacy and on-premise ones
Agree the success measures and the data we'll validate against
Weeks 4–6
Build
Implementation and iteration
Stand up the data layer and connect the first live feeds
Build the interfaces and automations agreed in discovery
Review working software with you weekly and adjust as we go
Weeks 7–10
Test & activate
Fix, tune, then switch on
Reconcile every figure against your own reported numbers
Fix defects and tune the models on your real data, not sample data
Train the people who'll use it daily, then activate by team
Weeks 11–12
Hypercare
We stay on it after go-live
Daily monitoring with a named engineer while adoption settles
Same-day turnaround on anything that blocks the work
Handover pack, run book and an agreed steady-state support model
What makes it land
Standardise the taxonomy. One naming convention across every system before we integrate.
Appoint one champion. A single internal owner for data validation, not a committee.
Three metrics first. Teams learn performance against target, cost on the day, and critical alerts. Everything else follows.
Security & governance
Built for companies that get audited.
Multi-entity groups don't get to be casual about data. Separation, consent and audit trails are architecture decisions here, not settings we add later.
Transparent running costs
You'll know your monthly operating cost before you sign — inference, infrastructure and integration, itemised and sized to your actual transaction volume. Confirmed at technical scoping, not estimated after go-live.
AI / LLM inferencesized to usage
Cloud infrastructure & storagesized to scale
Integration & middlewaresized to estate
End-to-end encryption
TLS 1.3 in transit, AES-256 at rest, across every service.
Role-based access
Scoped by entity, brand and site. People see their scope, nothing else.
Entity-level isolation
Hard separation between legal entities — not a filter on a shared table.
Audit-ready logging
Full change history on every record and every access event.
PDPA & GDPR aligned
Consent tracked per person, per channel. PII minimised by default.
Isolated infrastructure
Private VPC, regular key rotation, regional data residency.
Where we work
Complexity is the common denominator.
We're strongest where there are many locations, several legal entities, and data that has never been in one place.
Bespoke AI operating systems. In practice that means a live data layer over your existing systems, predictive engines on top of it, and an interface your team actually opens every morning — plus the automations that remove manual work underneath. We're not reselling a product; we architect and build for your entity structure.
How is this different from a BI dashboard?
A dashboard reports what happened. Our systems explain why it happened and recommend what to do about it, then execute the parts that can be automated. The difference shows up in the morning briefing: a ranked, costed list of actions instead of twelve charts and an interpretation problem.
Do you work with our existing systems?
Yes — including the awkward ones. Where a system has webhooks or an API we integrate directly. Where it's on-premise or legacy we deploy local sync agents and batch ETL. Most groups we work with run three or four different systems across their entities, and that's the normal starting point, not a blocker.
How long until we see something real?
Discovery runs three weeks, and you see working software from week four, reviewed with you weekly from then on. Twelve weeks to a live group-wide system, followed by hypercare. We deliberately validate against numbers your finance team already reports before anything scales — it's slower on paper and far faster in reality, because nobody has to unpick a bad rollout.
Who owns the data and the system?
You do. Your data stays in infrastructure scoped to you, with residency where you need it. Commercial terms on the codebase are agreed up front — we'll tell you exactly what you own before you commit, not after.
What does it cost to run?
Monthly operating cost breaks into three lines: AI inference, cloud infrastructure, and integration middleware. We size all three against your actual transaction volume during technical scoping and give you the number before you sign — including how it grows as you add sites.
Let's build what's next.
Tell us what's slowing your operation down. We'll show you what the system would look like running on your data — before you commit to anything.