ZANUS BACK OFFICE — CUSTOMERS & SUPPLIERS

A CRM that speaks your language.

Clients on one side, suppliers on the other — one continuous record each, with categories, tags and field labels defined by your business. The same software fits a law firm, a clinic or a factory, because the vocabulary is yours.

Get started

Cloud tenant or your own server · unlimited users · ready from day one

One continuous client record: profile, contacts, documents, photo ID, signature, printable badge.

What it does

Molded, not configured

Categories, subcategories, up to fifteen tag slots and per-field naming — the CRM takes the shape of your business in settings, no code.

The AI reads it

Client records are context for every AI work: histories, related contacts and notes ground what the AI drafts, schedules and answers.

Suppliers with status

Every vendor carries an approval status — Approved, Unapproved, Banned — plus commercial terms, contacts and documents.

One record, everything attached

Profile, related contacts, tags, documents, photo ID, signature capture, printable badges and profile reviews — the record is complete enough that the AI (and any teammate) can pick up a client cold.

Documents and media on the record
Printable profile reviews and ID badges
Related contacts mapped
AI insights: follow-up suggestions, at-risk flags

Client management with AI insights and follow-ups

Supplier record with approval status and terms

Suppliers feed the operation

Supplied items link directly into Logistics inventory, and free-text assistant notes give the AI context when it drafts RFQs. The vendor master is not a phone book — it is fuel for the automations.

Approval status on every vendor
Items linked to inventory and resupply
Assistant notes: context the AI uses when drafting

Molded in settings, not in a project

Client types, categories and tag labels are configuration, not code: the screenshot is the actual settings screen where a business renames the CRM into its own vocabulary — in an afternoon, by an admin, not a consultant.

Client types and categories you define
Up to fifteen tag slots, named by you
Field labels per record type

Client type settings: the CRM molded to your vocabulary

Cloud AI subscriptions typically price per seat and meter the AI usage on top — and agent platforms hand you a toolkit that someone still has to design, build and maintain. Zanus Back Office ships as a WORKING system: unlimited users, every module included, grounded in YOUR documents from day one.

Questions, answered

We already have a CRM — replace or connect?

Either. Zanus Back Office works as your operational CRM, or connects to what you keep: API connectors sync contacts and data so the AI layer works on top.

Can we rename fields to our terms?