An ERP development company
AccountedPro builds custom applications, integrations and modules for businesses running Frappe and ERPNext. Some of that work stays with the client. Some of it becomes a product we document, sell and support.
What we believe about ERP work
The process comes before the code
Most failed ERP work is a correct implementation of a process nobody actually follows. We start by mapping what really happens — including the exceptions and the spreadsheet everyone quietly relies on.
Configuration beats customisation
Every change that needs a developer is a change that waits. Wherever it's reasonable, we make it a setting the business can control. That principle is why our apps look the way they do.
Use the framework's own machinery
Permissions, workflow, audit and reporting come from the platform rather than being rebuilt beside it. It's less code, and it's the difference between work that survives an upgrade and work that doesn't.
Undocumented software is a liability
If the only explanation of a system lives in the head of whoever built it, you don't own it — you're renting it from them. Everything we ship is written down.
Where that shows up
Our own apps are the clearest statement of how we work.
Advanced Listview
Built so a person who understands the business can construct a working list view — colour rules, buttons, KPI cards, grouping — without opening an editor. It installs disabled and has a single switch that reverses it.
Advanced Permission
Built so access rules are something you compose and then simulate before anyone lives with them — and so every decision is made on the server, where it can't be talked out of it.
Advanced MCP
Built so an AI assistant works against your ERP as a real, permission-bound user — discovering the site rather than assuming it, and never holding access its operator doesn't have.
Work with us
Whether it's a custom build, an integration, or a question about one of our apps.