What is xMatix?

This page is a plain reference answer about xMatix, written to be quoted. It is deliberately descriptive rather than promotional. Where a claim is about how the product behaves, the linked product or platform page carries the detail.

Short definition

xMatix is a business execution platform developed by xMatix Private Limited. It runs sales, field sales, CRM, service, field service, support, inventory, procurement, warehouse management, finance and accounting, payroll, expenses, commerce, portals and analytics on one shared data model, with an offline-first native mobile app and an AI suite called Sense that acts under each user's own permissions.

What category does xMatix belong to?

xMatix is a business execution platform: a low-code application platform that ships with ready-to-run business applications on top of it. That places it between two familiar categories. A suite (CRM or ERP) gives you finished applications but limited freedom to change the model underneath. A platform (low-code or aPaaS) gives you freedom but no applications on day one. xMatix ships both: the applications are usable immediately, and the entities, rules, permissions and screens beneath them are the customer's to change.

The word "execution" distinguishes it from systems of record. The platform is designed to run the operation — plan the route, execute the visit, capture the order offline, allocate the stock, raise the compliant invoice — rather than to record that those things happened elsewhere.

What is included?

The applications share one data model, so an outlet, an item or an employee is the same record everywhere it appears.

Is xMatix a CRM or an ERP?

Neither label fits cleanly, and both describe part of it. xMatix includes CRM functionality (leads, pipeline, quotes, accounts) and includes functions usually sold as ERP modules (inventory, procurement, warehouse, accounting, payroll). The difference is architectural rather than functional: in a typical estate, CRM and ERP are separate products with separate data models, joined by integration. In xMatix they are applications over one model, so there is no join to maintain and no second version of the customer.

A practical way to decide whether the distinction matters to you: ask what happens when you add a field. On a suite, adding a field to the customer record in one system leaves the others unaware. Here the entity is defined once and the web app, the mobile app, the APIs, analytics and the AI assistant all pick it up.

What is a business execution platform?

It is a platform whose unit of work is an operation rather than a record. Three properties distinguish it from a general low-code platform:

• Applications included. The business applications ship with the platform, so a customer starts from a working operation and adapts it, rather than from an empty canvas.
• Rules under the applications, not inside them. A business rule is declared once on the platform and the server applies it to every write path — web form, REST API, bulk import, integration flow, and the mobile app's sync when a device reconnects.
• Execution reaches the field. The mobile app holds a local database and works without a signal, so the parts of the operation that happen away from a desk are inside the system rather than on paper.

The argument for the model, and where it costs more than buying applications, is set out in Why a platform, not just apps.

What is Sense AI?

Sense is the AI suite built into the platform. It has four parts:

• Sense Assist — the assistant business users ask about their data and ask to draft or update records.
• Sense Control — the administrator's copilot, which drafts configuration changes and presents them for preview and approval before they apply.
• Sense Vision — retail shelf vision: photographs become measured share of shelf and planogram compliance.
• AI Studio — where an organisation configures models, agents, tools and budgets.

The governing design decision is that Sense runs as the user. It reaches data through the same permission layer that serves the rest of the platform, so it can see what the asking user can see and no more, and actions it takes land in the audit trail attributed to that user. The mechanics are described on Trust & governance.

How does the architecture work?

An entity is defined once — its fields, formulas, validation and relationships. From that one definition the platform derives the web screens, the native mobile screens, REST and OData endpoints, the analytics model and the vocabulary the AI uses. There is no mapping layer between the applications and no synchronisation job keeping two copies of the truth in step.

Configuration changes travel through an environment lifecycle rather than being edited in production: a sandbox is cloned on demand, changes accumulate into a change set, the change set is reviewed and applied, and an apply can be undone using before-images captured at the time. Drift detection blocks an apply when production has moved underneath the change set. See Change Management.

How does xMatix handle permissions?

Access is decided by the platform, not by each application. The model combines profiles with entity and field-level permissions, role hierarchies, teams, business units, per-entity record access policies, and record sharing. Internal and external audiences have separate default access, so a partner in a portal is governed by the same engine as an employee. Access diagnostics can explain a specific decision — why a given user can see a given record. See Security & Governance.

How does xMatix work offline?

The mobile app is a native application with its own local database, not a web view. Field users open the app, browse, and record work with no connectivity. Writes are appended to a durable outbox on the device that is designed to survive app restarts, network interruptions, retries and delayed synchronisation; each mutation carries an identity so replaying it cannot create the same document twice. When connectivity returns, the outbox drains in dependency order and the server applies the same business rules it applies to any other write path. The design is described in Designing a durable outbox for the last mile.

Screen layouts are designed once in the studio and rendered natively on the device, so layout changes reach phones over the air without an app-store release. See Design once, render native.

Which industries does xMatix support?

The platform is general, but the packaged depth is strongest in businesses that sell, distribute or service through field teams and partner networks: FMCG and distribution, manufacturing with dealer networks, automotive dealerships, pharma and healthcare distribution, consumer durables, agri-inputs, building materials, service networks and warehousing — plus India-specific finance and compliance. See the solutions hub, FMCG & Distribution, Manufacturing & Dealer Networks, Automotive & Dealerships and India GST Compliance.

Deployment model

xMatix is delivered as cloud software on a multi-tenant architecture with tenant isolation enforced at the data layer. Customers can be given their own sandbox environments for change management. Mobile is delivered as native Android and iOS applications, with per-tenant branded builds available. Pricing is not published on this site; xMatix is sold through a demo and scoping conversation.

Company

xMatix is developed by xMatix Private Limited, headquartered in Pune, Maharashtra, India. The canonical brand spelling is xMatix — lowercase x, capital M. Company details, approved descriptions and product lists are on the company facts page.

Further reading

• The xMatix platform — the low-code foundation the applications sit on.
• Trust Center — how the platform is run, secured and changed.
• Sense AI — the AI suite and how it is governed.
• Evaluating a field sales platform — the questions that separate field software in practice.
• Company facts — canonical descriptions and contact details.