Service
Custom software development
Applications that your customers, field staff and partners actually use — built on the same backbone as your ERP, so the data never has to be reconciled between two systems.
At a glance
- Typical duration
- 6–20 weeks
- Engagement
- Fixed scope or retainer
- Stack
- Frappe, Python, JavaScript
- Platforms
- Web, Android, iOS
Software that shares a backbone with your ERP
The usual pattern is familiar: an ERP for the back office, a separate app for the field team, and a nightly sync job that someone has to babysit. Every mismatch between the two becomes an argument about which system is right.
Building the application on the same Frappe backbone removes that argument. One database, one permission model, one audit trail — and a mobile app that writes directly into the records your accounts team is already looking at.
We build portals for customers and suppliers, internal tools that replace long-running spreadsheets, and mobile apps for people who work away from a desk. Where a separate stack genuinely suits the job better, we say so and integrate properly instead.
Scope
What we build
Customer and supplier portals
Self-service ordering, document access and status tracking against live ERP data.
Mobile applications
Android and iOS apps for field teams, with offline capture where the network is unreliable.
Internal tools
Purpose-built screens that replace the spreadsheets a department has outgrown.
APIs and integrations
Documented REST endpoints and webhooks for connecting the systems you already run.
Dashboards
Operational and management reporting drawn from live transactions, not exports.
Deployment
Staging and production environments, backups, monitoring and a release process.
Method
How we build
Scope
We agree the users, the jobs they do and what success looks like, in writing.
Design
Screens and data model reviewed before code, because changing a sketch is cheaper than changing a schema.
Build in cycles
Short cycles with a working staging site at the end of each, so feedback arrives early.
Test
Functional testing against the acceptance criteria, plus load testing where volume matters.
Launch and iterate
Released to production with monitoring, then improved on the backlog you prioritise.
Industries
We work with
FAQ
Questions we are asked before signing
Do we need ERPNext to work with you on an application?
No. We build on Frappe because it gives us a tested permission model, workflow engine and REST layer out of the box, and that is useful whether or not you run ERPNext. If you do run it, the integration is simply free.
Are the mobile apps native or web-based?
We scope this per project. Most field applications work well as installable progressive web apps with offline capture; genuine native builds are worth it when the app needs deep hardware access such as barcode or camera pipelines.
Who hosts the application?
Either you or us. Many clients run on their own cloud account so that infrastructure stays in their name. We set up the environments, backups and monitoring either way.
What happens when we need changes later?
Most clients move to a monthly retainer after launch. You keep a prioritised backlog; we work through it in agreed cycles. There is no obligation to keep us on to be able to change your own software.
Related services
You might also need
Get an estimate for this work.
A 30-minute call, no slide deck. You describe the process; we tell you honestly whether ERPNext is the right answer.