A simple CRM for small business, connected to your orders and invoices

AxisIQ is a simple CRM for small business: customer records, a pipeline you define, public intake forms and automation, connected to orders and invoices.

A simple CRM for a small business is three things: a customer table everyone trusts, a pipeline shaped like the way you actually sell, and a front door where new leads arrive without anyone retyping them. AxisIQ gives you exactly that — customer records, a pipeline you define yourself, public intake forms, automation and per-field permissions — inside the same system that runs your orders, stock and invoices, so a customer is never a copy of a customer kept somewhere else.

That last clause is the argument of this page. Most small businesses shopping for a CRM do not need most of what a CRM sells. They need customer records that stay correct, connected to the money those customers bring in. If that is your situation, read on. If what you need is outbound sales tooling — sequences, dialers, forecasting — the honest section further down says plainly why AxisIQ is the wrong buy.

Customers are records, not a separate product

A new AxisIQ workspace already has customer records, alongside orders, products, invoices and payments — the CRM half of the business starts connected to the money half. Add the fields you actually use in a few clicks: phone numbers, billing and shipping addresses, a GST number, how they found you, which price list they get. A money field carries its currency, a choice field carries its allowed options, and every value is checked against its rules when it is written, so approx. Tuesday never lands in a date column.

If you sell to companies and talk to people, create a contacts type and link each contact to its customer. A link points at a record, not at text — rename the company once and every contact, order and invoice pointing at it still resolves. Custom types behave exactly like built-in ones: same lists, same search, same reports, same permissions. Operations is where all of this lives.

A pipeline you define in an afternoon

There is no pipeline product to configure. A pipeline is a deals type you create, with the fields a deal needs: a stage (a choice field with your real stages — New, Qualified, Quoted, Won, Lost), a value (money, with currency), an expected close date, a link to the customer, and an auto-numbered key like DEAL-{seq:4:yearly} so every deal gets the next number without anyone maintaining a counter.

Because a stage is a validated choice field, nobody can invent qualified-ish. Because the deal links the customer, the question "what has this customer bought, owed and asked for" is one record away rather than a search across two products. And if your team prefers working deals as a board of stages, Work Queues can hold the same records as an ordered pipeline with explicit stage transitions — a durable board, not a saved filter.

Leads walk in through a form

The fastest way to lose a lead is to make a person copy it out of an inbox. Forms publish a hosted page — or an iframe inside your own website — where a lead types their own details, and every submission becomes a record checked by the same validation as everything your team writes. Nothing typed is ever lost: submissions are stored before anything else runs, so a misconfiguration costs you a tidy record, never the lead.

Public forms are built for the open internet: an invisible honeypot swallows scripted spam, submissions are capped at 30 per minute per IP, and a form can only ever create new data — it cannot read or edit what you hold. Send a different prefilled link per channel and the source arrives with each lead. The customer intake forms guide walks through the whole setup.

What happens next is automation, not discipline

The moment a lead exists as a record, flows can act on it. A flow watches record events — created, updated — and runs a graph of steps you draw: set an owner, stamp a follow-up date, create a related record, branch on a condition, run your own JavaScript function, or call another system over HTTP. A work queue can also watch the type and pull new leads onto the team's board automatically, and the team can be notified in the app, so following up stops depending on someone watching an inbox.

One rule keeps this safe: a flow runs under the permissions of the person who built it. Automation can never quietly do something its author could not do by hand.

Ask questions instead of building filters

Ask Axis answers plain-language questions over your records — customers with no orders this quarter, deals stuck in one stage, who owes what. It runs under the permissions of the person asking: a field you cannot read is a field it cannot read for you, and an action you are denied fails visibly rather than being quietly worked around. For recurring questions, reports run read-only SQL over the live records — or you describe the report in plain English and review the SQL before it runs. No export, no second copy of the data going stale.

Who sees what, and who changed what

Small-business CRM data has an awkward property: everyone needs the customer, not everyone should see the numbers attached. AxisIQ permissions are written per action, per record type and per field — so sales reads the customer and the deal but never the margin field, and the same grants bind Ask Axis, flows and API keys, not just the people. The team setup guide shows the pattern.

Every change to a record lands in an append-only audit trail: who, when, the value before and the value after. When a discount looks wrong six months later, the answer is on the record, not in an investigation.

What AxisIQ is not

AxisIQ is not a sales-engagement platform, and pretending otherwise would waste your evaluation. There are no email sequences — in fact AxisIQ sends no email at all today; a flow can call an external email service over HTTP, but built-in sending is a gap. There is no dialer and no call logging. There is no forecasting interface — you can sum pipeline value by stage in a report, but there is no weighted-forecast model behind it. There is no contact enrichment.

The distinction that decides the purchase: if your CRM need is "a machine for high-volume outbound selling", buy a sales-engagement tool. If your CRM need is "structured customer records connected to quotes, orders and invoices, with a pipeline, intake and permissions" — which is what most small businesses actually mean by CRM — that is precisely the job AxisIQ is built for, and it does the orders and invoices too.

Where it fits

The CRM here is one face of a single system of record. The same customer record feeds order management and invoicing; the same builder underneath is the no-code database; the whole thing together is the small-business ERP. Existing customer lists come in by CSV, up to 500 rows per file, validated before anything is written — the import guide covers it. If your customer list currently lives in a spreadsheet, moving off spreadsheets is the comparison to read first.

AxisIQ starts free and you upgrade when you grow — the CRM is part of the platform, not a per-seat add-on.

FAQ

What is the simplest CRM for a small business?

The simplest CRM is a validated customer table with a pipeline, an intake form and permissions — not a sales-engagement suite. AxisIQ provides that as part of the system that also runs orders and invoices, so customer data is entered once and reused everywhere.

Can AxisIQ replace a sales CRM like HubSpot or Salesforce?

For structured customer records, pipelines, intake forms and reporting — yes, and it connects them to your orders and invoices. For email sequences, dialers and forecasting models — no; AxisIQ has none of those and does not send email itself.

How do leads get into the CRM?

Three ways: a public form that turns each submission into a validated record, CSV import at up to 500 rows per file, or the API using a scoped key. However a lead arrives, it passes the same field validation, so the pipeline never fills with half-typed rows.

Can I hide sensitive fields like margin from my sales team?

Yes. Permissions apply per field, so a grant can allow reading the customer and the deal while denying the margin or cost fields. The same rule binds Ask Axis, automations and API keys, so no tool leaks what a person cannot see.

Does AxisIQ send emails to customers?

No. AxisIQ has no built-in email sending; a flow can call an external email service over HTTP when a record changes, but sequences and campaigns are out of scope. If email outreach is the core of your CRM need, choose a sales-engagement tool instead.

Is there a free CRM for small business in AxisIQ?

AxisIQ starts free, with customer records, custom types, forms and automation included rather than sold as separate modules. You upgrade when your usage grows, and paid tiers are metered rather than capped.