Relationship and pipeline, kept honest.
Routed by territory the moment they arrive
Postal code resolves the servicing branch and partner automatically; phone-number match links the existing account; sales and service leads each get their own forms and views.
Seven stages, one clickable path
A stage stepper on every opportunity, qualification checklists, and any list view turned into a Kanban board you drag deals across.
Merge duplicates without losing the history
Configurable duplicate rules, side-by-side compare-and-merge that re-parents activities, files and conversations; account hierarchies, rule-based account groups that drive pricing and schemes; India-grade compliance attributes on the account.
Revenue pipeline architecture.
Capture
Web forms & calls, routed by postal code
Qualify
Checklist-qualified before conversion
Propose
Catalogue quotes, priced per customer
Negotiate
Discounts approved at the line level
Win
Credit gate checks real exposure first
Hand to Sales
Order lands on the same account record
One rail from enquiry to order.
Apex Mart — web form
PIN 411038 → Kothrud branchLead
openQualified
openQuote
Won
Credit gate
Exposure 320,000 of 500,000 limit
Clear to order ✓Order
Handed to Sales01
The postal code picks the branch — a new enquiry never waits in a pool.
02
Each stage carries its count and value, so the pipeline is the forecast.
03
A deal past its credit limit stops at the gate — before it can become an order.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix CRM |
|---|---|
| Leads with territory-based routing | Native |
| Guided lead-to-opportunity conversion | Native |
| Opportunity pipeline and kanban boards | Native |
| Qualification checklists | Native |
| Quotes with line-level approval | Native |
| Catalogue-driven product configuration | Native |
| Capability | xMatix CRM |
|---|---|
| Customer-specific price lists and discount groups | Native |
| Account hierarchies and buying groups | Native |
| Duplicate detection and merge | Native |
| Activity timeline across calls, visits, email and orders | Native |
| AI call summaries and next steps | Integrated — Sense |
| Fields and stages changed without a release | Configurable |
Everything in CRM.
The questions evaluators ask.
No — it is one application among nineteen on the same platform and the same data model. A lead converted in CRM becomes the account that Sales invoices and Service opens cases against, without an integration or a sync job in between. That is the practical difference: the pipeline, the order book and the service history are views of one record, so handoffs between teams don't lose context.
Yes — there is exactly one account record, shared across the platform. When a rep saves an order, the credit check reads the customer's real outstanding from finance at that moment, and shows the exact figures if the order would breach the limit. Account hierarchies roll subsidiaries and buying groups up on the same record, so what a relationship is really worth includes every branch's activity.
Yes — fields, forms and pipeline stages are configuration, not code. Your admin adds a field or reshapes a stage in the platform studio and it is live, with changes promoted safely and undo available. On mobile, the updated screens reach every device over the air. Nothing on this list needs a developer, a deployment window or an app-store release — the CRM stays shaped like your sales process this quarter, not the one you had at implementation.
Yes — quotes build from a live catalogue with guided configuration, so reps quote real, orderable combinations rather than dead SKUs. Pricing follows the customer automatically: price lists and discount groups apply by customer, group and date. Discounts that cross your limits pause at the line level for approval before the quote goes out — speed for the rep, control for the manager.
They get found and merged. The system spots the same account entered twice and merges the records cleanly — history, contacts, activities and all — so the relationship's whole story lives in one place. That is also what keeps the shared credit check, the account hierarchy and the activity timeline trustworthy: one customer, one record, and reps stop working two half-pictures of the same company.
Yes, with your approval and your permissions. Sense Assist runs as the person asking — it can see only the records you can see — and it drafts changes rather than writing silently: the update lands as an approval you confirm. Calls already log themselves, and AI turns recordings into summaries and next steps on the record. Every action Sense takes is metered and audited. Read how Sense Assist works.
