The AxisIQ platform

AxisIQ puts orders, stock, money, documents and workflows on one live model, with analytics, automation and the Axis intelligence layer on top.

Most companies do not have a software problem. They have a context problem. AxisIQ is the AI brain for your business: one live model of the company — orders, stock, customers, invoices, money, documents and workflows as a single set of records — with Axis, the intelligence layer, and the reporting, automation and permissions all working on that one copy.

Orders live in one place, stock in another, invoices in a third, and the truth lives in someone's head or a spreadsheet named final_v3_USE_THIS.xlsx. Every seam between those systems is a place where numbers drift, work stalls, and somebody re-types something a machine already knew.

Three layers, one model

• Know the business — the system of record. Configurable records, customers, orders, products, invoices, payments, the ledger, forms, documents, relationships, history and permissions.
• Understand the business — the system of intelligence. Ask Axis, analytics in SQL or plain language, reports, dashboards, Axis Sheets, the knowledge base and data-quality checks.
• Run the business — the system of action. Flows, functions, schedules, APIs, integrations, Work Queues, barcode stations, forms and Axis actions under each person's permissions.

These are not three products. They read and write the same records under the same permission model.

What is actually in it

Each area below works today, and all sit on the same records — switching one on makes the others smarter.

• AI workspace builder — describe your business and the assistant builds your modules, record types and menus around it.
• Operations — your day-to-day records — orders, students, stock, customers, whatever your business tracks — in your object types and field names.
• Ask Axis — an assistant that reads and changes your data under your permissions, and shows its working.
• Analytics — real SQL and plain-English questions over live data, saved as reports and dashboards.
• Axis Sheets — a real spreadsheet beside your records: spreadsheet formulas, XLSX import, and AXLOOKUP to read live data into a cell.
• Flows and functions — a visual canvas where a trigger, conditions and actions become a working process, plus your own JavaScript in a sandbox when a step needs real code.
• Work Queues — durable pipelines for the floor: scan a barcode, claim the next item, move a stage, reconcile a batch against what you expected.
• Forms — collect from customers, staff or suppliers on a hosted page or an embed, straight into your records.
• Phone & Messages — calls in the browser with a phone menu, voicemail and recordings, plus email, SMS and WhatsApp, all on your own provider accounts.
• Relay — team chat inside the workspace: channels, direct messages, threads, files and reminders, plus channels shared with partner companies.
• People — employees, leave on your own rules, attendance, payroll with payslips, expense claims and your handbook.
• Contracts — write from templates or with Ask Axis, review clauses, e-sign with a sealed copy, and get reminded before notice and renewal dates.
• In-store checkout — counter sales with cash, card and UPI against your own catalogue records.
• Payments — payment links paid by UPI, card, netbanking or wallet through your own provider account, settled back as records.
• Accounting — invoices, payments and a double-entry ledger that cannot be quietly edited.
• Documents — file storage plus branded PDFs generated from your own records.
• Knowledge Base — search by meaning across uploaded documents and the record types you opt in, filtered by what the asker may see.
• Data Quality — re-checks old records against the field rules you have today.
• Content Studio — a headless CMS for your website, inside your business system.
• Permissions and audit — who can see and do what, down to single fields, and a permanent record of every change.
• Integrations — store connections, your own HTTP endpoints, and an API with per-key permissions.

One job, all the way through

That list is not a bundle of apps sharing a login. Here is one piece of work through five of them, with nothing exported or re-typed.

A customer fills in an order form on a page you published this morning. The submission is not an email in somebody's inbox — it is an order record, checked on arrival by the same field rules your own staff type against.

That record appearing is an event: a flow you drew on the canvas wakes up, tests a condition — order value, customer type, whatever you set — and follows the matching branch: update a related record, create the invoice, run one of your functions, call an outside service over HTTPS. It runs in the background, so a slow API never delays the submission.

The same record matches a queue's intake rule and lands on the floor's pipeline without anyone adding it. Packers claim items one at a time and beep barcodes; every scan gets an answer, a move that breaks a stage's limits is refused, and each movement is appended to a trail nobody edits.

To get paid, you raise a payment link against the invoice record, amount and customer details taken from it. The customer pays through your own provider account and a payment record appears in your workspace; a webhook delivered twice creates nothing extra. Closing the invoice stays a human act, because money corrections should be explicit. Posting to the ledger is a setting you switch on per document type.

Six months later you make one of those fields mandatory, and Data Quality tells you which old orders lack it. Throughout, Analytics queries the lot as one dataset and Ask Axis answers questions about it in a sentence — because it was one dataset all along, not five.

Three design decisions that shape everything

One system of record. An invoice does not hold a copy of the order — it points at the order. Change a customer's name and it changes everywhere at once, because there was only ever one of them.

Your vocabulary, not ours. Object types and fields are yours to define. If you call it a consignment rather than a shipment, and you track bale number and mill lot, that is what your team sees — in the tables, the CSV export, the reports, and in what Axis understands when you ask a question. No consultant, no code, no schema migration.

Permissions are the floor, not a feature. Every read and every write — including the ones the assistant makes, the ones your flows make, and the ones your API keys make — goes through the same permission rules. A flow can never reach what the person who built it could not reach by hand. The assistant answering you cannot see a field you cannot see. There is no back door where an integration runs as god.

Why not just add another tool

You can get a long way on a spreadsheet, and for some jobs you should — that case is made on AxisIQ versus spreadsheets. You can also stitch four products together with a glue service, which works until the rules that run your business live in the wiring between systems rather than in any of them (more).

The alternative at the other end is a suite with a module for everything, an implementation partner and a launch date next year. Those suites are genuinely broader than AxisIQ: if you need manufacturing planning or statutory payroll filing today, they have it and we do not (open-source ERP, traditional ERP). Our trade is footprint for seams — fewer things in the box, nothing falling between the things that are.

Some things AxisIQ does not do at all, better read now than discovered in month three. No manufacturing resource planning, performance reviews or recruitment. No GST e-invoicing or e-way bills, no filing with anyone — GST, TDS and payroll returns stay with your accountant — and no accounting-software sync. Email, SMS and WhatsApp go out only through provider accounts you connect. No mobile app and no offline mode: it is a browser product. Payment collection runs through one provider today. And invoices post to your ledger only for document types where you switch that on.

Who it is for

AxisIQ is built for operating teams that want their records, workflows, reporting and AI on one context: brands and manufacturers, distributors and wholesalers, e-commerce and multi-channel sellers, and service companies with real inventory or real billing. A company can start with one team or workflow and extend the model as it grows.

If you can describe how your company works in a few sentences, you can start modelling it in an afternoon — most companies need no consultant for that, though statutory work such as GST filing and payroll returns stays with your accountant's tools. Start with a 7-day trial — no card required. The getting-started guide walks through the first hour.

FAQ

Is AxisIQ an ERP? AxisIQ includes the core idea behind ERP — one connected system for the company's operational records: orders, stock, customers, invoices, payments, ledger, reporting — and extends it with analytics, programmable workflows and an intelligence layer on the same context. It runs HR and payroll in People but has no manufacturing planning or statutory payroll filing, so if those are your requirement, it is not the whole answer.

Can I use just one part of it, like the work queues or forms? Yes. Each part is useful on its own, and they share the same records, so each one you add makes the others worth more.

Do I have to move everything in on day one? No. Most teams start with one object type and import a CSV (up to 500 rows a file), then add the rest as they go.

Does the AI assistant have access to everything in my business? No. Ask Axis runs every action as the person asking, so it sees what you see and does only what you could do. A refused action comes back as a visible error, and every change it makes is recorded against your name.

What does AxisIQ cost? AxisIQ is licensed as a platform with users included: Core from ₹4,999 a month with 5 Full + 10 Operational users included; you add people, add-ons and usage as you grow, excluding GST, with Enterprise priced by scope. Every workspace starts with a 7-day trial — see pricing.