CMS - Clinic Management System
A bilingual healthcare platform built on Frappe and ERPNext for patient registration, appointments, EHR, billing, pharmacy and diagnostics.
Ali Raza — Frappe Technical Lead & ERPNext Developer
ERPNext implementation, Frappe customization, manufacturing and HR modules, integrations and hosting — delivered end to end by a Frappe Certified engineer.
Featured projects
SAM - Municipal Management System
A full municipal platform for the Municipalidad de Fraijanes, Guatemala — revenue and online payments, permits and licensing, citizen requests, public works, transparency reporting and departmental access.
Vedani Mobili — Manufacturing ERP
ERPNext for a US luxury door and wood-panelling manufacturer: custom product configuration, BOM and production planning, project-based orders, purchasing and costing.
Alkhidmat HR Platform
An integrated HR platform on Frappe/ERPNext HRMS with 60+ custom DocTypes — approval workflows, biometric attendance, automated payroll and employee self-service apps.
Bookfyd — Online Tutoring Platform
A tutoring marketplace connecting students in Lahore and the Gulf with verified tutors — React frontend on a custom Frappe backend.
Business Solution for Mubtkir
A tailored ERPNext platform for project delivery, resource planning, client operations, billing and profitability.
Latest articles
What ERPNext Actually Costs: $0 License, and What You Pay For
ERPNext has a $0 license, so where does the money go? A practitioner breakdown of configuration, migration, hosting, training and fixed-scope quoting.
Frappe Cloud vs Self-Hosted ERPNext on Ubuntu: Which One I Recommend, and When
A practitioner's comparison of Frappe Cloud and self-hosted ERPNext on Ubuntu 24.04, with a decision checklist and the ops practices self-hosting demands.
From Spreadsheets and Paper to ERPNext: The Migration Checklist I Used for a Municipality
Move from paper and spreadsheets to ERPNext without losing data: the eleven-step migration checklist I used for a Guatemalan municipality.
Designing Faster Frappe Workflows
How workflow structure affects adoption, approvals and delivery speed inside business systems.
Building Premium ERP Frontends
Why internal tools deserve strong UI systems and how frontend quality changes ERP adoption.
Deploying Frappe With Confidence
How Docker, Linux and deployment discipline improve Frappe reliability.
Mastering Reports in ERPNext
A practical guide to creating, optimizing and trusting ERPNext reports — Query Reports, Script Reports and dashboards.
Frequently asked questions
Is ERPNext really free? What do we actually pay for?
Yes. ERPNext and the Frappe Framework are open source under the GPL, so there is no per-user or per-module license fee. You pay for the work: configuring it to your processes, custom DocTypes and workflows, data migration, integrations, training and support — plus hosting, either Frappe Cloud's published plans or your own server, which I set up and maintain.
How much does an ERPNext implementation cost?
It depends on the modules you switch on, how much of your process needs custom DocTypes or workflows, how much data has to be migrated, and which systems have to connect. After a free audit call I write a Blueprint with a fixed quote, so you know the full price before any build work starts. Change requests are quoted separately in writing.
How long does it take to go live?
A single-company setup with standard modules and clean data is measured in weeks; multi-department systems with custom modules, integrations and bilingual interfaces — like a clinic network or a municipality — are delivered in milestones. The Blueprint gives you a dated plan, and you see progress every week on a live test server.
Can you migrate our data from spreadsheets or an old system?
Yes. Master data (customers, suppliers, items, employees, chart of accounts) and opening balances are migrated and validated with you before go-live; historical transactions are migrated where the value justifies it. I have moved paper-based municipal processes and spreadsheet-run inventories onto ERPNext, and I upgrade existing sites to the current version.
Where will our ERPNext be hosted, and who controls the data?
Two good options: Frappe Cloud, the managed hosting run by the makers of ERPNext, or your own cloud or on-premise server that I deploy with Docker, Nginx and Ubuntu and keep backed up and monitored. Either way the data and the code are yours. I recommend one in the Blueprint based on your size, compliance needs and in-house IT capacity.
What happens after go-live? Are we on our own?
No. Every implementation ends with role-based training, a handover pack and a defined hypercare period during which I fix issues and fine-tune workflows. After that you can continue on a monthly retainer for enhancements, upgrades and server care, or call on me when needed. Your code lives in your own Git repository and follows Frappe standards.
How much can ERPNext be customised — and will it break on upgrade?
Almost anything: new DocTypes, approval workflows, reports, dashboards, print formats, portals and integrations. Customisations go into a separate Frappe app using hooks, server and client scripts and standard APIs — never edits to core — so ERPNext keeps upgrading cleanly. My published Frappe apps and v16 theme on GitHub follow exactly this approach.
Why work with one certified engineer instead of an agency?
You talk to the person who builds the system, from the first call to hypercare, with no handoffs between sales, project managers and junior developers. I hold the Frappe Certified Techno-Functional credential, work across the whole product — accounting, stock, manufacturing, HR and payroll, CRM, projects and custom Frappe apps — and quote fixed scope. Everything is documented, upgrade-safe and in your repository, and a written retainer keeps me on call.