Process automation
The recurring manual job — reconciliation, file preparation, report assembly, data clean-up — turned into something scheduled that emails you when it is done, or when it could not be.
Python is what the rest of our work is built on. ERPNext and the Frappe Framework are Python, which means the same team that configures your ERP can write genuine software when configuration runs out.
That matters more than it sounds. Most of what businesses call automation is a repetitive job somebody does by hand — reconciling two reports, reformatting a file for a portal, chasing the same data every Monday. Those are small pieces of software, and they pay for themselves quickly.
WHAT WE DO
What this covers
Custom Frappe applications
Full applications on the Frappe Framework with their own document types, workflows, permissions and reports, sharing one database with your ERP. Our own products are built this way.
Data processing and reporting
Pulling data from several sources, reconciling it, and producing the report somebody currently rebuilds in Excel every month.
Internal tools
The small web tool that removes a bottleneck — a calculator, an approval queue, a bulk-entry screen your team actually needs.
Document and file generation
Bulk PDF generation, formatted exports, bank and government submission files built to a required layout.
Maintenance of existing code
Inheriting a Python codebase someone else wrote, getting it under control and keeping it running. We do take these on.
QUESTIONS
Frequently asked questions
-
We have a script someone wrote who has left. Can you take it over?
Usually yes, and it is a common request. We start by reading it and telling you honestly whether it is worth maintaining or worth rewriting — some inherited scripts are one afternoon's work to stabilise, others are held together in ways that make every future change expensive.
-
Does this have to involve ERPNext?
No. We build standalone Python where that is the right answer. We will say when a job genuinely belongs inside your ERP rather than beside it, because a separate tool with its own copy of the data usually creates the reconciliation problem it was meant to solve.
-
How do you price small automation work?
Small, well-defined jobs are quoted fixed after a short scoping conversation. The scoping matters — most automation requests turn out to have an exception nobody mentioned, and that exception is the actual work.
-
Will it keep running when something changes?
That depends on what it depends on. Anything reading from another system will eventually meet a change at the other end, so we build in logging and failure alerts. Ongoing care sits under a support arrangement.
-
Can you work with our developers?
Yes. We are comfortable contributing to an existing team and repository, following your conventions and review process.
-
Do we own the code?
Yes, with the repository and documentation handed over.
KEEP READING
Related
API development & integration
Connecting ERPNext to banks, gateways, portals and the software you already run.
ERPNext customization
Custom Frappe apps, integrations and Arabic print formats when the standard system doesn't fit.
Website development
Search-optimised business sites, optionally on the same platform as your ERP.
ERPNext implementation in Qatar
What we do, how a project runs, and what it costs to move a Qatar business onto ERPNext.
GET STARTED
What does someone on your team do every week by hand?
Describe the routine. Most of them are a few days of work and pay for themselves inside a quarter.