Discovery & Data Model
1-2 weeksWe model the objects, relationships and permissions before writing code, because a wrong data model is the one thing refactoring cannot cheaply fix later.
Signed schema and scope
Frappe App Development
A custom app
A custom app
in your own repository
Frappe is a full web framework, and ERPNext is just the best-known thing built on it. We build standalone apps and ERPNext extensions on the same stack - installed alongside, never patched into, and handed over as code you own.
60+
Custom Modules Built
v16
Frappe Framework
100%
Code Ownership
0
Core Files Patched
Before You Build
Do you actually need an app?
An app is a bigger commitment than a customisation - it has its own deployment, its own upgrade path and its own maintenance. Here is how we tell the two apart, and we will say so plainly if you are on the wrong side of the line.
Yes, build an app
- The requirement has its own lifecycle and users
- It needs to version and deploy independently
- You may sell or reuse it elsewhere
- It has substantial logic of its own
No, customise instead
- A few extra fields on an existing DocType
- A print format or a report
- One validation rule or calculation
- A workflow on a standard document
If most of your list falls on the right, you want ERPNext customization instead - cheaper, faster, and less to carry.
Capabilities
Full-stack, on one framework
Data model, business logic, API, front end and deployment - all in the same codebase, which is why a Frappe app takes a fraction of the time a comparable stack would.
Data Modelling
DocTypes with links, child tables, naming series and permissions - a real relational model, not a spreadsheet in a browser.
Business Logic
Server-side controllers, scheduled jobs and background workers, so rules hold regardless of how a record is created.
API First
Every DocType is a REST endpoint by default. Token auth, webhooks and rate limiting for whatever you connect.
Dashboards & Reports
Query and script reports, number cards and charts built on live data rather than an overnight extract.
Portals & Roles
Customer, vendor or field-team portals with their own login, their own views and nothing else visible.
Responsive UI
Frappe UI, Vue or React front ends where the standard desk interface is not the right tool for the job.
Deploy & Scale
Bench setup, supervisor, nginx, Redis and background queues, tuned and monitored for the load you actually have.
Security & Audit
Role and permission design, field-level access, versioning and a complete audit trail on every document.
The Stack
The same stack ERPNext runs on
Nothing exotic, nothing you cannot hire for. That matters more than novelty when the app has to outlive whoever built it.
Python & Frappe
Frappe v15 on Python 3, the same framework ERPNext itself is built on.
MariaDB / PostgreSQL
Relational storage with proper indexing, migrations and backups.
Redis & Workers
Caching, queues and background jobs for anything that should not block a user.
Vue / Frappe UI
Modern front ends where the desk interface is not the right fit.
How It Ships
Data model first, because that is the expensive mistake
Code can be refactored cheaply. A wrong data model cannot, so it gets signed off before anyone writes a controller.
Build in Sprints
3-10 weeksTwo-week sprints on a staging instance, in your repository, with a working demo at the end of each one rather than a percentage in a status report.
Working app on staging
Integrate & Test
1-2 weeksERPNext hooks, third-party APIs and your UAT on real data. Findings return to the same branch instead of becoming a second project.
Signed-off acceptance
Deploy & Hand Over
3-5 daysProduction deployment, bench and supervisor configured, plus documentation and a repository walkthrough so your team or another partner can take it on.
Live, documented, yours
Investment
What a Frappe app typically costs
Quoted against a signed data model and scope, not an hourly guess.
Starter App
One clear job, done properly
Rs 1.2 Lakh+
- Up to 5 custom DocTypes
- Role-based permissions
- Standard reports and list views
- REST API access
- Repository handover
Business App
A system in its own right
Rs 2.5 Lakh+
- Everything in Starter
- Complex workflows and approvals
- ERPNext integration hooks
- Custom dashboards and charts
- Third-party API integrations
- Team training and documentation
SaaS / Enterprise
Multi-tenant, or business-critical
Custom quote
- Everything in Business
- Multi-tenant architecture
- Subscription and billing logic
- Load testing and scaling
- SLA-backed support option
Typical starting points rather than a price list. Object count, integrations and whether it is multi-tenant all move the number - which is why we quote after the data-modelling stage rather than before it.
Questions
Frappe app development FAQs
Build an app when the requirement has its own lifecycle, its own users and substantial logic of its own - something you would describe as a system rather than a feature. Customise when you need extra fields, a print format, a report or a workflow on an existing document. We will tell you honestly which side of that line you are on, and the answer is often customisation.
Yes, entirely. Every line ships to a repository you control, with readable commit history and documentation. No obfuscation, no recurring app licence and no arrangement where you need us to keep running. You can take it in-house or hand it to another partner at any point.
Not when it is built as a separate app, which is how we build. It installs alongside ERPNext and hooks in through the framework's supported extension points rather than patching core files. That separation is exactly what makes ERPNext version upgrades stay routine.
A focused app doing one job well starts around Rs 1.2 lakh. A system with workflows, ERPNext integration and dashboards is typically Rs 2.5 lakh and up. Multi-tenant or SaaS work is quoted individually. We price against a signed data model and scope, not an hourly guess.
A starter app is usually four to six weeks end to end. A business app runs eight to fourteen. The discovery and data-modelling stage comes first regardless, because a wrong data model is the one thing that is expensive to fix later.
Yes. Frappe is a full web framework in its own right - ERPNext is simply the best-known application built on it. We build standalone Frappe apps with their own users, portals and APIs for businesses that have no ERPNext instance at all.
Usually. We start with a short code audit covering how the app is structured, whether it patches core, how migrations are handled and what test coverage exists. That audit tells you honestly whether it is worth continuing or worth rebuilding.
Yes. Document extraction, classification, forecasting and natural-language querying over your own data, built as background jobs and API endpoints inside your app. Same rules as everything else: your repository, your code, no proprietary layer.
Describe the system you need.
We will tell you what it really takes.
Including whether it should be an app at all. You get a data model, a scope and a milestone-based quotation before any code is written.