Home › Software & Operations
Software & Operations
From data entry to accountability
“We bought software. Why are Excel screenshots still on WhatsApp?” If that question is yours, the software did not fail for lack of features. It failed because your floor found it harder than paper.
The promise
Everything automatable gets automated.
If a task needs no human judgment, the software should be doing it — completely, not almost. Most implementations stop one step short: the system holds the data, and a person carries it the last mile, forever. We finish the job.
Here is what finished looks like. At one garment manufacturer, sales invoicing was a full-time role, and errors still got through. Today nobody raises a sales invoice there. The invoice assembles itself from the movement records, and billing errors stand at zero. The people who held that role now do work a machine cannot.
That is the whole promise in one move: your people stop typing what already happened and start verifying that it happened right.
The bar
Business software should feel like your favourite app.
That is not a slogan here — it is the acceptance test.
Easier than pen and paper.
If the operator’s old register is easier than our screen, the register wins — and it should. Each entry asks for what the operator already knows, in the order the work already happens.
Little or no training.
A screen that mirrors the work explains itself. Training shrinks to a walkthrough, and adoption stops being a battle you fight on our behalf.
The software adapts to the business.
Never the reverse. Your workflow is the specification. We do not hand you a module and ask the business to bend around it.
We have been the customer. We will not tell you “this is what we have, you have to use it like that.”
Our parent company is a garment manufacturer; for years it paid software vendors and heard exactly that sentence back. We built our own software because of it.
Running in production today
Not a roadmap.
Every workflow below runs in a working factory now.
Bale, roll and lot tracking
Knit fabric does not arrive in tidy units. A bale lands as rolls of different true lengths, in lots and shades — and the stock holds it exactly that way, bale to roll to lot, from goods receipt through to the finished garment. Any roll traces back to its bale; any order picks the right lot.
Issue and return
Fabric and job card issued to cutting; actual consumption recorded against the issue; balance returned batch-wise to stock. The same issued-versus-actual discipline follows the garment through stitching and ironing, piece-wise, down to the individual tailor.
DC and GRN, off paper
Every delivery challan and goods receipt note, in and out of every department, recorded once at the movement itself. Zero paper. Full clarity.
BOM-based fabric estimation
Metres per piece, defined once. Issue estimates generate themselves.
Zero-touch sales invoicing
Because every movement is already recorded, the invoice needs no author. This is the workflow that removed a full-time role.
Lorry-receipt capture
LR details are scanned and extracted automatically from the transporter’s document. Nobody re-keys a lorry receipt.
ERPNext hand-off
Purchase invoices generate against GRNs with full lot and batch tagging, and post into ERPNext with journal entries and payments. Accounting stays in a standard system your auditors already know; the manufacturing depth stays in ours.
Reporting that keeps pace
Management reports draw from the live movement records, the moment you ask for them.
And where your workflow needs something not on this list — we build exactly that, fitted to how you already run, one working piece at a time.
Ownership
You own the work. All of it.
The code is yours
Written to be read, documented, full development history intact. Any competent developer can pick it up.
The stack is open
ERPNext at the core, a standard database beneath it, and your data exports whole, in open formats.
Your team runs it
One trained person is enough to run it. We train your person, hand over a running system, and do it again as the team grows.
And us?
If we are worth keeping, it will be because of the work.
How it starts
One piece live first.
One piece goes live first. We watch it being used — daily, on the floor, not in a review meeting — correct it, and only then expand. We learned that order the hard way; the method page tells the story, including the system we built wrong.
We have shipped code into ERPNext — the system 30,000+ companies worldwide run on. Code that enters a heavily reviewed open-source codebase is held to a public standard, and that is the standard everything we build for you is written to.
Next on our own bench — and not yet in any production build — are assistants that draft answers from the movement records. When that ships, you will see it here as shipped, not before.
We’ve been the customer
The standard the code is held to.
Our parent company is a garment manufacturer. For years it paid software vendors and heard the same sentence back: “this is what we have, you have to use it like that.” We built our own software because of it, and we will not repeat that sentence to you.
We have shipped code into ERPNext — the system 30,000+ companies worldwide run on. Code that enters a heavily reviewed open-source codebase is held to a public standard: readable, documented, upgradeable by someone who has never met us. That is the standard everything we build for you is written to — customisation as maintainable code, never a fork that strands you.