Custom Business Systems We Build on Frappe

It's one thing to say a framework is powerful; it's another to point at what it actually runs. Much of the custom software we build at Apjakal sits on Frappe, and it's in daily production across several very different industries. Here is a plain tour of the kinds of systems we build and the real problems each one solves — so you can see where your own situation might fit.

We're an ERP and business-systems practice with 30+ implementations behind us, working across Zoho, ERPNext and Frappe. What follows focuses on the custom-build side of that work.

Education and school management

Schools and colleges run on more moving parts than outsiders expect — enrolment, terms, fee billing, results, portals for parents and students. We build education-management systems on Frappe that hold all of it together: enrolment and term management, fee schedules and billing, results and report cards, and student/parent portals that show grades and statements without a phone call to the office. When a school's structure is unusual — its own grade model, its own fee rules — the framework bends to it instead of forcing the school to bend.

This is the same lineage as our Education Management Systems and Online Learning Management System products; the framework underneath is what lets us tailor each deployment to how a particular institution actually operates.

Finance: reporting and reconciliation that fits the accountant

Standard accounting software produces standard reports. Real finance teams almost always need something the package won't give them — a statement in a specific board-ready format, a reconciliation the built-in tools handle clumsily, a calculation with local rules baked in.

On Frappe we build custom financial reports in exactly the layout the finance team needs (income statements, balance sheets, cash-flow and fee-income reports formatted to match how they present to their board), and reconciliation engines that compare ledgers against bank and legacy-system statements and surface only the mismatches worth chasing. These live inside the same system as the data, so they're always current — no monthly export-and-rebuild-in-Excel ritual.

HR, payroll and attendance

People systems are full of local rules — leave policies, gratuity and severance calculations, biometric attendance. We build HR and biometric systems on Frappe that capture attendance from devices, run payroll, and handle the calculations that off-the-shelf tools quietly refuse to do — including gratuity and severance worked out over real service periods with the right tax treatment. Because it's custom, the rules match your policy and your labour context, not a generic template.

Assets, property and service operations

Beyond finance and people, the same framework carries operational systems: asset registers that track what you own and its condition and value over time, property-management apps, and service-centre / job-management systems that move a job from booking to completion. Our Motor Hub service-centre product and Asset Management offering come from exactly this kind of work — operational software shaped around a specific workflow.

The common thread

Notice how different these are — a school, a finance team, an HR department, a workshop — yet they run on the same foundation. That is the point of building on a general framework. We're not reinventing permissions, APIs, workflows and reporting each time; those come from Frappe. We spend the effort on the part that's actually yours. That's why a genuinely custom system can be delivered in a sensible timeframe and budget, and why it can integrate with the other tools you already run.

If any of these sound like a problem you're living with — a report you rebuild by hand, a process stuck in spreadsheets, a package that almost fits — there's a good chance we've built something close before. Tell us what you're wrestling with and we'll give you an honest view of what a custom system would take, or whether you even need one.