The work is in twelve places
Quotations in one spreadsheet, purchase orders in another, attendance in the machine, payroll in a third file, and stock in somebody’s head. Nothing reconciles because nothing shares a record.
Engineering · Manufacturing · Trading
Run the whole company from one system.
Quotations, purchasing, vendor bidding, service jobs, production, stock, accounts, HR and payroll — twenty-four modules sharing one database, with approvals that leave a trail and permissions that actually hold.
Self-hosted on your own infrastructure. One company, one database, your server.
Why this exists
Engineering companies outgrow spreadsheets long before they outgrow them.
The work is real, specific and measurable. The tools most firms run it on are none of those things.
Approvals happen in chat
A payment gets approved on WhatsApp, a discount over the phone, a reimbursement by forwarding a photo. Six months later nobody can show who authorised what, or against which document.
Generic ERP fits nobody
The big suites have no idea what a tolerance, a fitness status or a pressure rating is. You end up entering engineering work into fields meant for retail, or not entering it at all.
What it covers
Six workspaces, twenty-four modules, one record of truth.
Built for and used by an engineering and industrial services company — not assembled from a generic template and renamed.
Quote to cash
Quotation, approval, sales order, delivery, invoice, receipt — one chain, each step derived from the record before it rather than retyped.
Procure to pay
Purchase orders with per-line receipt tracking, and a two-stage payment approval that checks the remaining order balance before it releases money.
Vendor portal & RFQs
Vendors register themselves, upload certificates and bid on your requests for quotation. You see who was emailed, who failed, and who actually opened it.
Engineering service jobs
Reusable inspection and test templates per equipment type, measurements recorded against tolerance, before-and-after photos, and a consolidated report for the customer.
Production & stock
Daily production per machine and shift with downtime and waste, a versioned bill of materials, and a stock ledger where every movement carries its running balance.
Accounts that tie back
Chart of accounts, receivable and payable, vouchers and expenses — with withholding tax handled on both what you are owed and what you owe.
HR, attendance & payroll
Import straight from the biometric device, compute late minutes and overtime against each shift’s own rules, and run payroll on configurable earning and deduction heads.
Documents you designed
Eight print formats, editable field by field or written as HTML outright, with your numbering series, your letterhead and your signatures.
Permissions that hold
Five independent rights per module per role, enforced on the server for every request — not hidden in the menu and left open underneath.
How it works
One enquiry, tracked to the money.
Each step is derived from the record before it. The progress you see on a quotation is not a checklist somebody ticked — it is what the documents actually say happened.
- 01 Quotation raised Draft, against a customer
- 02 Pending approval Routed for sign-off
- 03 Approved Locked from casual edits
- 04 Sales order Converted in one click
- 05 Procurement Flagged lines become buy requests
- 06 Received Goods receipt against the PO
- 07 Dispatched Delivery note, QR, trip cost
- 08 Delivered Invoiced and receipted
If it never converts
- Rejected
- Expired
- Discontinued
Discontinuing asks for a reason, and keeps it.
The part that matters at audit
Every approval has a name and a timestamp on it.
The reason most companies cannot answer “who authorised this?” six months later is that the authorisation happened somewhere the system never saw. Here it happens inside the document, or it does not happen.
And nothing is ever really gone: deletes are soft, restorable, and only an administrator can purge.
- 01
Two stages, both recorded
A purchase payment goes Submitted, then Manager Approved, then Approved — and each stage stamps who did it and when. A reimbursement follows the same path with separate manager and management notes.
- 02
The org chart decides who approves
Eligibility comes from the direct and operational manager on the employee record, not from a role. Nobody has to be given broad system access just so they can sign off their own team’s claims.
- 03
The system checks the arithmetic
Before a purchase payment clears its final approval, the remaining balance on the order is checked. It will not let two approvers, working separately, pay the same order twice.
- 04
Refusal is not the only answer
When someone without rights to a locked document needs a change, the system captures what they wanted and why, as a request for review. The need is recorded instead of being argued about in chat.
- 24 Modules Commercial, procurement, operations, finance, people and platform — one database
- 9 Roles out of the box Plus unlimited custom roles, each with five rights per module
- 19 Importable entities From Excel or CSV, every run logged row by row
- 14 Built-in reports Each configurable for paper, header and watermark, and exportable
Questions
Before you ask
Do we have to take all twenty-four modules?
No. Access is set per role, module by module, so you switch on what you use and the rest never appears. Most companies start with quotations, purchasing and stock, then add HR and payroll once the first three are bedded in.
Can it run on our own server?
Yes — that is the normal deployment, and the system is built for it. One company, one database, on hosting you control. Your commercial terms, customer records and employee data stay inside your own boundary.
Will it work with our attendance machine?
If the device can export attendance to CSV or Excel, yes. Each employee carries the user ID their machine knows them by, and the import matches on it, tracks the batch, and computes late minutes and overtime against that employee’s own shift rules.
Can we keep our own document numbering?
Yes. Fifteen document series — purchase orders, quotations, invoices, receipts, vouchers and the rest — each have their own prefix, format template, sequence length and next number. You set them to match whatever convention you already use.
Our invoices have to look a particular way. Is that possible?
Eight document types are designable. You can tick which fields appear and rename any label, or write the HTML yourself in a built-in editor with live preview. Your logo, letterhead, signatures and terms are configured once and applied across them.
How do approvals work — do we need to give people admin rights?
No, and that is deliberate. Approval authority for reimbursements and purchase payments comes from the reporting lines on the employee record, not from roles. Someone approves their team’s claims because they manage that team, without being handed broader access to get it.
Can our vendors use it directly?
Yes. There is a separate vendor portal on its own login, isolated from staff sessions. Vendors register themselves, choose the categories they want to be invited for, upload their certificates, and bid on your requests for quotation.
What about data we already have?
Nineteen entities import from Excel or CSV — customers, vendors, employees, attendance history, the chart of accounts, SKUs, machines, past production and more — each with a downloadable template. Every run is logged row by row, so a rejected line tells you which one and why.
Get started
Tell us how your company runs today.
What you make or service, how many people, and what you are using now. We will come back with a straight answer on fit and timeline.