Home / Products / Omnicore
Omnicore

One platform.
Unlimited apps.

Most companies our clients' size run an accounting package, a payroll package, a spreadsheet for projects, a group chat for the field, and paper for everything else. Each keeps its own copy of the customer list, the item list and the staff list — and none of them agree.

Omnicore replaces all of it with one application, one login, one design, one set of master data. The customer exists once. The item exists once. The employee exists once.

Book a live walkthrough Explore the nine apps
9Apps, one shell
1Login & master data
AIBuilt in, not bolted on
0Bars of signal needed
Add the tenth app — no tenth login, no tenth look
The apps Enterprise People Squad Field Insight Reach Stay Torrens Copilot
— Why one platform

You don't have a software problem. You have a seams problem.

The licences are rarely the expensive part. The expensive part is the re-keying, the reconciliation, and the three days every month spent deciding which number is true.

The same customer, five times

Sales has one spelling, accounting has another, the delivery app has a third. Nobody can answer "what is this account actually worth to us" without an export and an afternoon.

You know you have it when: month-end starts with a VLOOKUP.

Numbers that arrive too late to use

Stock moved on Monday, was invoiced on Thursday, and hit the books the following week. By the time the report is right, the decision it was meant to inform has already been made.

You know you have it when: the dashboard is always "as of last month".

A seventh system means a seventh login

Every new need adds another vendor, another password, another look, another export. Training starts from zero each time, and the master data fragments a little further.

You know you have it when: onboarding takes a week of screenshots.
Omnicore's answer is not another system. It is a shell that apps mount into — so the tenth app you switch on shares the login, the design, and the master data of the first nine.
— How it holds together

One shell. Many apps.

A shared top bar, a left-rail launcher, one identity and one design system — into which each app is mounted. Every app owns its own domain and its own screens, but they share the shell, the login and, critically, the master data.

01
One identity across every appSign in once. Your role, your branch and your permissions follow you from the ledger to the dispatch board.
02
Master data lives onceCustomers and items belong to Enterprise. Employees belong to People. Every other app reads those records rather than keeping a copy.
03
One design systemA person trained on one app can already work the next one. Each app carries its own accent gem — the shell never changes.
04
Metadata-driven, so it bendsIn Enterprise, one registry defines the document types and the list views, forms, columns and search generate themselves. Adding a document type is a data change, not a rebuild.
One login
Apps
Enterprise
People
Squad
Field
Insight
Reach
Stay
Torrens
Enterprise / Selling / Sales Invoice
Receivables▲ updated
Stock on hand▼ moved
Sales register+1 line
General ledger entry● balanced
Accounts ReceivableDr—
SalesCr—
Output Tax (VAT)Cr—
Cost of Goods SoldDr—
InventoryCr—
Trial balance still ties✓✓
— The apps

Nine apps. Pick one and look inside.

Each app owns a domain and consumes the others' records instead of copying them. That column — what it consumes — is the whole product.

Enterprise

Live
Finance, inventory & operations backbone

A metadata-driven ERP running a real double-entry general ledger and a perpetual-inventory engine — the system of record for finance, customers and items.

What it runs
  • One registry defines the document types across Accounting, Selling, Buying, Stock, Manufacturing, Assets and Projects — list views, forms, columns and search generate themselves.
  • Every voucher posts a balanced entry. Open an invoice and a GL panel shows its actual postings, with a balanced check on the screen.
  • Perpetual inventory alongside it, so a stock-out on an invoice moves the stock balance report.
  • Ten computed reports: trial balance, P&L, balance sheet, general ledger, AR and AP ageing, sales and purchase registers, stock balance and stock ledger.
What it consumes

Employees from People. Documents from Insight. Job revenue from Field. What Stay sells, Enterprise books.

Why it's the backbone

The customer list and item list live here. Every other app points at these records rather than keeping a private copy — which is the mechanism, not the marketing.

The reports are functions, not stored numbers. A posting propagates everywhere the moment it happens, and the financial identities are asserted rather than hoped for — so a live posting can be proved correct in front of you, because the invariants would visibly break if it weren't.

People

Live
HRIS — the single employee directory

A full HRIS with a live Philippine payroll engine — where the payslip, the register and the government report all derive from the same computation, so they tie.

What it runs
  • Directory in card and table views, tabbed employee profiles, org chart, attendance board and leave.
  • An employee self-service surface staff can use on their own phone.
  • Payroll computed from the employee's basic pay through effective-dated SSS, PhilHealth, Pag-IBIG and BIR-TRAIN tables — never a stored number.
  • DOLE-itemised payslips, and statutory exports generated from that same computation.
What it consumes

Identity from the shell. Cost centres from Enterprise. Its employees become assignees in Squad and technicians in Field.

Why it matters

People are the biggest line in most Philippine service businesses. Leaving payroll outside the platform is how job costing quietly stops being true.

Statutory maths, not a spreadsheet copy. Employer cost exceeds gross by exactly the statutory burden — because it is computed, per employee, from the current tables.

Squad

Live
Projects, tasks & team collaboration

A collaboration suite that grew out of a project tool: the work, and the conversation about the work, in the same place as the records they concern.

What it runs
  • Workspace level: home dashboard, my work, an inbox for triage, direct and group messaging, mail, calendar, notes and files.
  • Per project, in task or agile mode: overview, kanban board, list, backlog and sprints, timeline, workload, calendar, chat and full item detail with subtasks, comments and activity.
  • Real-time messaging and presence, with optional meeting transcription.
  • An AI guide inside the workspace for finding and summarising the work.
What it consumes

Assignees are employees from People — not a second user list maintained by hand.

Why it's here

Because the chat about an invoice belongs next to the invoice. Folding comms into the platform is what stops decisions living in someone's phone.

One item set behind everything. The my-work counts, board counts and insight charts are computed from the same items, so they agree with each other by construction.

Field

Live
Field service — dispatch & work orders

The full service chain modelled end to end — service request → quotation → service order → appointment → service report — each with a workflow-chain widget showing exactly where the job stands.

What it runs
  • A dispatch console with board, schedule-gantt, map, technician and inbox views, plus a slide-over appointment sheet with checklist, parts, status timeline and technician suggestions.
  • Customer 360: assets, contracts, service history and tickets on one screen.
  • An asset registry with risk scoring, service contracts, and a technician roster.
  • Notification templates for SMS, WhatsApp and email across the service events that matter.
What it consumes

Customers and items from Enterprise. Technicians from People. Won deals from Reach.

The densest screen we build

Health composite, KPI strip, exceptions, productivity, utilisation, availability heatmap, SLA, first-time-fix, asset health, CSAT and revenue per technician.

The gap it closes: the distance between "the job is done" and "the job is invoiced" — which in most service businesses is measured in weeks of unbilled revenue.

Insight

Live
AI documents, invoices & reports

Document AI where paper becomes a posted transaction — and, increasingly, where documents are created as well as read.

What it runs
  • Batch drop-zone and review queue, with AI extraction of the header fields plus line items, each carrying a confidence score against a threshold.
  • Detection of seven kinds of page mark — stamps, handwriting, signatures, circled and highlighted amounts, and crossed-out corrections.
  • A split-view review screen: a rendered facsimile with the marks drawn on it beside editable fields, an arithmetic reconciliation panel with one-click fixes, and a crossed-out-value resolver.
  • Gated approval with a duplicate guard, a team inbox, vendor roll-ups, and an export bridge that posts approved documents into AP and AR.
What it consumes

Vendors and customers from Enterprise — and it posts straight back into Enterprise AR/AP.

Issuance, not just capture

Insight also generates documents: settlement statements against complex commission structures, and field-issued documents printed on the spot from a handheld.

Confidence is on the screen, not hidden. Every extracted field shows how sure the model is, the arithmetic is reconciled before approval, and nothing posts to the books until a person says so.

Reach

Live
CRM — relationships & pipeline

The customer-relationship layer: one pipeline, and one place where the relationship lives across billing, service history and documents.

What it runs
  • Leads with an AI first-reply draft, opportunities with a weighted forecast, quotations, and a contacts directory.
  • The chain lead → opportunity → quotation → service order runs end to end and crosses into Field when a deal is won.
  • Five sales reports: funnel, pipeline analytics, lost opportunities, quotation conversion and rep leaderboard.
What it consumes

Customers from Enterprise and Field. Service history from Field. Documents from Insight.

Why it moved here

The pipeline began inside Field. It moved out so relationships live in one place — the lead your salesperson is chasing and the account your collector is calling are the same record.

System of record for the sales relationship. Not a second customer list that quietly drifts from the one accounting uses.

Stay

Live
Stays, rentals & tenancies

The commercial operation on property: availability, reservations, occupancy — and the money on them.

What it runs
  • A per-night inventory engine that serves three business lines from one model.
  • Hotel room types, named short-term rentals treated as a pool of one, and residential tenancies — without three separate systems.
  • Availability, reservations, occupancy and revenue on the same records the books read.
What it consumes

Guests and tenants as parties in Enterprise, which books what Stay sells. Holdings and titles come from Torrens.

Why one model

A room, a rental unit and a leased apartment differ commercially, not structurally. Modelling them once is what keeps occupancy comparable across all three.

The same relationship Insight already has with Enterprise: Stay sells it, Enterprise books it, and neither one keeps a second copy of the customer.

Torrens

Live
Land titles, parcels & property records

The land register: what a holding is, who legally owns it, and what burdens it.

What it runs
  • Legal identity of a holding — OCT, TCT and CCT records as registered — alongside tax declarations.
  • Parcels and boundaries: technical descriptions, survey plans, and holdings plotted on a map.
  • Encumbrances and adverse claims annotated against the title, so what burdens a lot is visible with it.
  • Answers the questions owners actually ask: what land do we own, where is it, and what is on it.
What it consumes

Owning entities as parties in Enterprise. Feeds the holdings that Stay commercialises, and inspections dispatched through Field.

Why it exists

For Philippine groups holding land, the register is usually a folder of scanned titles and one person's memory. Neither survives a transfer.

Legal identity and commercial use, separated properly. Torrens knows what the title says; Stay knows what it earns. Confusing the two is how land records rot.

Copilot

Live
Ask across every app

The assistant that works the platform with you — and answers from the books rather than from memory.

What it does
  • Find a customer, read a report, or open any screen or form by name — across all eight apps, without learning where it lives.
  • Explain how a document posted: which accounts moved, and why.
  • Draft a field document for you to review and issue.
  • Works by voice as well as text, for people whose hands are busy.
Where its answers come from

Every figure it states comes from the same engines the screens render — not from a summary, a cached export, or the model's own recollection.

And what it costs

AI usage and spend have their own screen in the platform. You can see what the assistant is costing you before the invoice arrives.

This is only possible because of the core. An assistant pointed at five systems that disagree can only ever summarise. Pointed at one set of master data, it can actually answer.
— Powered by AI

We don't hand you a chatbot. We power the company with AI.

Most AI pilots quietly die for the same reason: they are pointed at data spread across five systems that disagree with each other, so nobody can trust the output enough to act on it.

Omnicore removes that excuse. One set of master data, one permission model and one audit trail is exactly the substrate AI needs — so it can stop summarising and start doing the work: reading the documents, drafting the transaction, explaining the posting, and answering the question with the records to back it up.

Omnicore Copilot
"Why did last week's margin drop on the Cebu route?"
1
Reads the books, not a summaryPulls the sales register and stock ledger from the same engines the screens render
2
Finds the causeTwo SKUs landed at a higher cost after a supplier price change captured by Insight
3
Shows its workingOpens the invoice, the goods receipt and the price history behind the claim
4
Drafts the next stepA revised price list, ready for a human to review and approve
sales register stock ledger price history Human approves

Document AI that ends re-typing

Invoices and receipts — photographed or scanned — become structured records with a confidence score on every field, reconciled arithmetic, and a posting into AP or AR once a person approves. Stamps, signatures and handwritten corrections are detected, not ignored.

Ask across every app

Plain language in, a real answer out — with the documents behind it one click away. Copilot reads live records, so it cannot quote you last month's truth, and it will open the screen it is talking about.

Drafting, from your own records

A first reply to a new lead, a field document ready to issue, a service report, a summary of where a project stands — drafted from what actually happened, for a person to send.

Exceptions surfaced early

Duplicate documents caught at capture, arithmetic that doesn't reconcile, assets scored for risk, jobs drifting past SLA. Raised while you can still do something about them.

It explains the accounting

"Why did this post like that?" is a question the platform can answer — which accounts moved, on which document, under which rule. New staff stop needing a senior beside them.

You can see what AI costs

A usage-and-cost screen inside the platform shows model spend as it accrues. AI you cannot budget for is AI you will eventually switch off.

Four rules the AI layer does not get to break
It sees what you seeThe assistant works inside your session and your permissions. There is no privileged back door into the platform.
Answers cite recordsEvery figure comes from the same engines the screens render, and the document behind it is one click away.
A person approves the postingAI prepares; people commit. Nothing reaches the general ledger without a human approval step.
Your data trains nobody's modelCustomer data is not used to train public models, and private deployments keep the whole loop inside your boundary.
— Two things nobody else brings

The parts that decide it in the room.

Everything above is table stakes for a platform. These two are why clients sign.

Books that tie

An accountant can add up the columns on screen — and they foot.

Reports are computed, never stored. Post a document in front of the client and the receivables KPI moves, the AR ageing gains a row, and the sales register gains a line — while the trial balance still ties and the balance sheet still balances.

  • A balanced double-entry posting behind every voucher, shown on the document itself
  • Perpetual inventory moving in the same breath as the invoice
  • Unbalanced or duplicate vouchers are rejected, not silently absorbed
  • Rounding carried at full precision and applied once — because a centavo off a client's own statement is a lost deal
This matters more than it sounds: it means a live posting can be proved correct in front of you, because the invariants would visibly break if it weren't.
Offline is complete

A salesman with no signal issues a document with its final number — and prints it.

Not a provisional reference that gets renumbered on sync. On a document that is the customer's proof of what they received, that distinction is not cosmetic.

  • Devices lease a block of document numbers while online and draw from it offline — a lease is a carbon booklet, and numbers are never reissued
  • The outbox is written before the receipt prints, so a crash can never spend a number on a document that wasn't stored
  • Install to the home screen, open cold with no signal, unlock with a PIN, browse the full catalogue, issue, print, sync on return
  • The offline session can write documents but cannot read the ledger — stated plainly on the setup screen, not buried
Built for provincial routes and dead spots, because that is where Philippine distribution actually happens.
— One record, five apps

Follow a single job across the whole company.

This is what "one set of master data" means in practice. Nobody re-types anything — every step below is the same record getting richer.

Reach
Deal won
A lead becomes an opportunity, then a quotation. Marked won, it crosses straight into Field.
one customer record
Field
Dispatched
A service order and appointment are raised; the console assigns a technician against skills and schedule.
technician = an employee
People
Time captured
The technician's attendance and hours are the same records payroll will compute from.
no second timesheet
Insight
Document issued
The service report and its document are captured or issued on the spot, offline if needed.
final number, printed
Enterprise
Posted & visible
Revenue, tax and the receivable post themselves. The KPI moves and the trial balance still ties.
balanced entry

Five apps touched it. One record exists. No export, no import, no overnight batch, and no month-end reconciliation to discover that the field and the books disagree — because there was never a second copy to disagree with.

— Two ways to run it

Your data, where you want it.

Same platform either way. The difference is who holds the keys.

Managed Cloud

For most teams
  • We host, patch, back up and monitor it
  • Off-site backups with tested restores
  • Upgrades applied on your schedule, not ours
  • Fastest path — running in weeks, not quarters
Your data stays yours and exports on demand.

Private Cloud / On-Prem

Regulated & enterprise
  • Runs in your own tenancy or on your hardware
  • Your network, your identity provider, your retention policy
  • Branch and low-connectivity deployments supported
  • We operate it with you, or hand over the runbook
For institutions whose data cannot leave the building.
— Rollout

App by app, never big-bang.

Platform projects fail for the same reason every time: nothing is usable until everything is. Omnicore goes in one app at a time, and each phase leaves you better off than the one before it.

Phase 0 · Discovery

We map your seams, not your org chart

Time on site with the people who actually re-key data. We come out with the master-data plan, the document flows worth keeping, and an honest list of what shouldn't be automated yet.

Deliverable: migration blueprint
Phase 1 · Master data

One customer list, one item list, one roster

Your parties, items, chart of accounts and employees land in the platform and are deduplicated once — the step every later phase depends on. Your existing system keeps running beside it.

Outcome: the lists finally agree
Phase 2 · The first app

Whichever one is bleeding

Usually Enterprise or People. It runs in parallel for one full cycle and is reconciled to the peso before anything is switched off. Trained by role, with your own documents and numbering.

Outcome: daily work moves across
Phase 3 · The rest, on demand

Each new app is a switch, not a project

Field, Reach, Insight, Squad, Stay or Torrens mount into the shell your team already knows, reading the master data already in place. Then admin handover and the runbook, so your team can run it without us.

Outcome: your team owns it
— Straight answers

The questions buyers actually ask.

Is Omnicore an ERP?
Enterprise — the finance, inventory and operations app — is an ERP, and it is one of nine apps on the platform. Omnicore itself is the layer underneath: the shell, the identity, the design system and the master data that all of them share. Buying "an ERP" gets you one app. Buying Omnicore means the eighth app you switch on doesn't need an eighth login.
Do we have to take all nine apps?
No — most clients start with one or two, usually whichever is bleeding: the books, or payroll. Because every app reads the same master data, adding the next one is a configuration and training exercise rather than a second implementation project or another migration.
We already run one of your other products. What happens to it?
Nothing breaks. Our product line and Omnicore are built by the same team on the same conventions, so moving onto the platform means your data and your people carry forward. We'll tell you honestly whether a move is worth doing now or better left until your next growth step — sometimes the answer is "not yet".
Our internet is unreliable. Is that a problem?
It is the condition we designed for. A handheld can be installed to the home screen, opened cold with no signal, unlocked with a PIN, and used to browse the full catalogue and issue documents with their final numbers — printed on the spot, and synced when the device comes back into coverage. Auth failures on reconnect are treated as transient, so a device back from a long trip never strands a day's valid work.
How does it handle Philippine compliance?
Payroll is computed from effective-dated SSS, PhilHealth, Pag-IBIG and BIR-TRAIN tables, with DOLE-itemised payslips and statutory exports generated from the same computation rather than typed. On the books side, VAT and the official-receipt versus sales-invoice distinction are modelled properly. We work alongside your accountant on the specifics of your registration — we don't claim a rubber stamp we can't give you.
What about the AI — where does it actually run?
Copilot and the document AI in Insight work inside your session and your permissions, answer from the same engines the screens render, and never post to the ledger without a human approving. Usage and cost are visible on their own screen. Your data is not used to train public models, and for private or on-premise deployments the whole loop stays inside your boundary.
What does it cost?
It depends on apps, users and deployment mode, so we quote rather than publish a price that would be wrong for most people. What we will commit to in writing before you sign: a fixed implementation scope, a named engineer, and no per-record or per-transaction charges that punish you for growing.
What if we outgrow you?
Then you leave with your data in open formats — every record exportable, nothing held hostage in a proprietary shape. Lock-in should be a decision you keep making, not one you made once.

See it post in front of you.

Send us one messy process — the month-end close, a field issuance, the payroll cutoff. We'll run that exact flow in Omnicore live and let you check the numbers yourself. No slide deck.

Book a live walkthrough See the whole product line