Home › Software
Software
We build the software your business needs.
End to end, at whatever layer the work lives: from the screen an operator taps on the factory floor to the systems behind it. We make the software fit your business, and we run our own business on what we build.
What we have built
From the factory floor to the systems behind it.
Operator screens
We build screens around the work on the factory floor. The operator keeps the same workflow when the ERP underneath changes.
The ERP layer
YRP extends ERPNext for sales and distribution, manufacturing planning and goods movement. We use ERPNext where it fits and build what is missing.
A companion app
We built an app for agents, distributors, retailers and sales reps, connected to YRP.
Integrations
Actual wages paid feed the factory profit and loss account. Attendance and today’s punch status appear inside the production-floor screens.
Document scanning
A phone pairs with the ERP so scanned documents reach the system directly.
Bank payments
We built payment integration so bank payments can be approved inside the ERP.
Sign-in
We built phishing-resistant sign-in for Frappe and ERPNext because our own bank transactions run there.
Engineering tools
Tools for our own engineering, such as C3 and SSHGate, released as open source.
Products
Custom software, built to product quality.
We build custom software for the long run. We aim for the lowest cost of ownership by keeping it easy to maintain, starting with the software we use ourselves. That habit is why some of our work has become products.
Business software
YRP. ERPNext, made yours, with the sales and manufacturing layer we run our own business on. Coming soon to Frappe Cloud.
Developer tools
Frappe Passkey. Phishing-resistant sign-in for Frappe and ERPNext.
C3. Your coding agents, in Telegram.
SSHGate. A signed-approval gate between coding agents and your servers.
When software leaves work unfinished
“We bought software. Why are Excel screenshots still on WhatsApp?”
If people still reach for an Excel sheet, the software has left part of their work unfinished. We start with that gap and build around how the work actually happens.
Your people should stop typing what already happened and start verifying that it happened right.
The bar
Business software should feel like your favourite app.
Easier than an Excel sheet
If the operator’s Excel sheet is easier than our screen, the sheet wins. Each entry should ask for what the operator already knows, in the order the work happens.
Little or no training
We aim for screens that explain themselves by following the work. Training should be a walkthrough.
The software adapts
Your workflow is the specification. We do not hand you a module and ask the business to bend around it.
Entered once
The same record should not sit in the ERP and again in an Excel sheet. It is entered once, where the work happens, and every report reads that one entry.
Mistakes stopped at entry
A wrong entry should be stopped on the screen as it is made, not found at month-end. Every entry carries the name of the person who made it.
Numbers without the chase
Owners tell us the number exists somewhere, but someone spends hours pulling it out of Excel sheets. It should come out of the system the day you ask.
Running in production today
Work that already runs in our factory.
Goods movement recorded once
In our garment business, 100% of goods movement is recorded in one system. Delivery challans and goods receipt notes record each movement.
Manufacturing planning
Production purchase orders, time-and-action planning and capacity planning are built and in use.
Purchase invoices into ERPNext
YRP posts a submitted purchase invoice into ERPNext from a goods receipt note. In our purchase-entry workflow, one operator submitted 39 new purchase invoices in a single 60-minute stretch between June and September 2026.
Sales invoicing from movement records
Our order-management software and ERPNext assemble the sales invoice from recorded movements. In our garment business, billing errors stand at zero.
Lorry-receipt capture
We scan lorry receipts and extract their details for entry. The process is in use; it does not read every document correctly.
What you get
Nothing here locks you in.
You get the code in full
It is written to be read and documented, with its 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.
Inside ERPNext
The standard the code is held to.
We have shipped code into ERPNext — the system 30,000+ companies worldwide run on. That work is publicly reviewed. We bring the same care to your software so another developer can maintain it.
How it starts
One piece live first.
We put one piece live and watch it being used on the floor. The rest of your work carries on as it does today. We correct it before expanding. We learned that order the hard way; the method page tells the story, including the system we built wrong.
We’ve been the customer
We have paid for software that did not fit.
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.” You may have heard it too.
So we built our own, and we will not pass that pain on to you. Taking it away is our whole business, and it is why you can trust us.