In daily production use — not a prototype.
The operating system for companies that build to order.
Quotations, production, inventory, finance and people usually live in five different places — and the gap between them is where margin quietly disappears. Axelent closes it into one chain, from the first quotation to the journal entry it creates.
Who it is for
Not one industry. One way of working.
What you make matters less than how the work moves. If orders become projects, projects need materials and people, and payment arrives in stages — Axelent fits.
- You build to order, assemble or install it yourself — or sell design work by the project
- Work runs as projects with staged payments
- You have a production or field team, or a design team, and a payroll
The thesis
Every break between files is a number retyped by hand.
Five places means five versions of the truth. One chain means each number is written once — by the system, at the moment it happens.
Before
Five files, nothing carries across
With Axelent
One chain, no re-entry
FIG. 01Every break is a number retyped by hand — or one chain that writes them itself
Intelligence layer
The AI does the work nobody wants to do — and hands you the decision.
Most systems bolt on a chat box and call it intelligence. Here it sits inside the workflow: reading, judging, preparing — then stepping back so a person decides. And it learns from every correction your team makes.
Reads every inbound message
WhatsApp conversations are assessed one by one: genuine buyer, supplier, or noise. Real enquiries surface in the action queue; the rest stay out of the way.
Drafts the reply in your voice
Responses are written in your team's own tone, learned from conversations you have already sent — not a rigid template. Your people read it and press send.
Learns from every correction
Each time someone fixes a judgement or edits a draft, it becomes an example. It fits the way you work a little better each week, with nobody training it.
Keeps deals from going quiet
Prospects that go silent are flagged and chased on your follow-up cadence. What usually leaves a pipeline is not the rejection — it is the one everyone forgot.
Writes the weekly owner brief
One page: what moved, what stalled, what needs a decision. Written from operational data, not from a report someone tidied up first.
Sweeps what is stuck
Approvals waiting, invoices past due, orders without progress, POs without receipts, stock running low, contracts about to expire — all found and raised without being asked.
Reads bank statements
Bank and credit-card statements are parsed from the file itself and matched against what is already recorded. Reconciliation stops being data entry.
Grades the ads that run
Meta ad performance is pulled automatically and reviewed weekly: what deserves more budget, and what is quietly burning it.
How it works
Three chains where margin usually leaks.
Not a list of modules standing on their own. These are events that pull each other along — and at every joint, the system writes the number instead of a person.
Quotation to handover
cannot close while under-invoicedMaterial to journal entry
project purchase or warehouse stock — told apartAttendance to project cost
hours land on the job, not on overheadFIG. 03Each chain ends where the accounting begins — automatically
What is inside
Everything a company that builds to order needs to stop running on spreadsheets.
Eight areas of work, one database, one permission model.
Sales
- Prospects and staged pipeline
- Print-ready quotations
- Sales orders and amendments
- Payment schedules per project
- Invoices and partial settlement
- Delivery orders and handover
- Unified WhatsApp inbox
Purchasing
- Multi-step purchase requests
- Direct requests for project needs
- Purchase orders and goods receipt
- Partial receipt and price correction
- Price history per supplier
- Payment proof attached
Inventory
- Materials and finished goods kept apart
- Stock card from every movement
- Material issues to production
- Finished goods booked in automatically
- Stock guard when a delivery closes
- Low-stock warnings
Production
- Production orders from sales orders
- Progress by stage
- Material, labour and overhead cost
- Hours charged to the right project
- Shop-floor attendance tablet
- Profit and loss per project
Finance
- Journals created from events
- Chart of accounts and trigger mapping
- Bank and credit-card reconciliation
- Petty cash and reimbursements
- Overhead and budgets
- Balance sheet, P&L, cash flow
- Receivable and payable ageing
People
- Employee records and contracts
- Attendance with face matching
- Leave, overtime, loans, claims
- Monthly and daily payroll
- BPJS employment and health
- 360 reviews and KPIs
- Disciplinary records
Daily work
- Calendar and meeting scheduling
- Multi-step approval queue
- Personal and team task lists
- Email, push and WhatsApp alerts
- Daily operational briefing
- ⌘K search across the system
Platform
- Roles and per-menu permissions
- Audit trail on every change
- Two-factor authentication
- Android and iOS apps
- Isolated instance per company
- Encrypted daily backups
- MCP access for your own AI assistant
Fit
We would rather tell you up front.
Selling into a company that is not a fit costs both sides. Here is the honest boundary.
A good fit if
- You build to order, assemble or install it yourself — or sell design work by the project
- Work runs as projects with staged payments
- You have a production or field team, or a design team, and a payroll
- Most enquiries arrive through WhatsApp
- Month-end is spent reconciling numbers between files
Not yet a fit if
- You are purely retail or e-commerce
- You need marketplace or point-of-sale integration
- You produce for stock rather than to order and need material planning (BOM)
- Your team is under ten people — spreadsheets are still cheaper
- You want something to install yourself with no onboarding
- You need multinational-grade audit certification
Pricing
Two ways to own it.
Every company gets an isolated instance — its own database and its own domain. Your data never shares a table with anyone else's.
FIG. 04One database per company — the gap is the product
Multi-tenant systems keep every customer in the same tables, separated by a column and the hope that no query forgets it. Axelent does not work that way.
Each company runs as its own instance: its own database, its own domain, its own backups, its own encryption keys. Nothing you store can be reached from anyone else's session, because there is nothing shared to reach through.
Subscription
Fully managed
- Hosting, email, backups and monitoring handled by us
- AI usage included, with a spend cap
- New features and fixes while you subscribe
- Onboarding and data migration support
- Cancel any time; your data leaves with you
Perpetual licence
Self-hosted
- Perpetual right to use, on infrastructure you control
- Your own email and AI accounts, billed directly to you
- Bug fixes included during the support term
- Optional annual maintenance for security updates
See it running on your own process first.
We will walk it through using the way your business actually works — not slides, not invented data. If it turns out not to fit, we will say so first.