On Page Navigation
On Page Navigation
Frappe ships a growing family of apps that share one framework and one database. That is the real advantage. It is also where it goes wrong, because every app you switch on brings background jobs and permission rules that somebody has to own. This page lists the apps we implement and run.
Where to start
Most businesses need three or four of these, not all of them. The ones that go badly are the ones adopted because they came free with the platform.
1
If a job is being held together by a shared sheet and somebody's memory, that is the app to turn on first. The spreadsheet proves the process already exists and that someone already owns it. Adoption is far easier when you are replacing something people resent.
2
Frappe apps are configured, not merely installed. Roles, workflow states, naming series and scheduled jobs all need an owner. If that owner is nobody, the configuration drifts until the app is trusted less than the spreadsheet it replaced.
3
Two rollouts at once split the attention of the same small group of people. We would rather move slowly and have each app land than hand you a stack nobody logs into.
Each page below covers scope, configuration, data migration and what the monthly fee includes. Pricing is on the page, not behind a form.
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
Learn More
About the service
On a managed plan we hold the administrator seat and everything that comes with it. That means the configuration, the data migration, the permission changes, and the upgrades that arrive whether or not you are ready for them. Self-hosted Frappe moves quickly. Somebody has to read the release notes before an update lands on your production site, and on a managed plan that somebody is us. Where several apps have to hand work to each other, that wiring is Frappe automation work and it is priced separately.
The trap with a platform this broad is that switching an app on is free and running it is not. Every app added brings permissions to maintain, background jobs that can fail quietly, and one more thing to check before an upgrade lands. We would rather you ran three apps properly than eight badly, and the fastest test is to ask who logs into each one on a Monday.
These apps share a framework and a database, which is the real advantage and also why a bad configuration in one place can surface somewhere unexpected. An employee, a customer and a supplier are the same underlying structure. That is why a timesheet reaches an invoice without an integration, and it is also why a permission rule written carelessly for one app can expose something in another.
Adoption is the other half. An app nobody was trained on gets used for a fortnight and then quietly abandoned while the spreadsheet comes back, and by the time anybody notices there are two sources of truth and neither is right. That is why we push back on switching on four apps at once, however cheap the marginal one looks.
Most firms charge an implementation fee and then a monthly retainer on top of it. Our monthly rate covers the build. If the rollout takes longer than we expected, that is our problem rather than a change order.
Frappe ships more than most businesses should run. Frappe Books is the clearest example. It is a desktop application that keeps your data in a file on one computer, so there is no instance to host and nothing for anyone to manage. We would rather talk you out of an app than bill you for one you never open.
Whether you run on Frappe Cloud or your own infrastructure, the account is yours and the database is yours. Everything here is open source, so nothing depends on us staying in the picture. If you want to take administration back in house, we hand over the documentation and the credentials.
What does managed Frappe actually cover?
Implementation, configuration, data migration, permission management and the version upgrades. You get a named engineer and a flat monthly fee per app. What it does not cover is your hosting bill, which stays in your name.
Which Frappe apps do you support?
Every app listed on this page. That is the set we run often enough to support properly. If you need something outside it, say so and we will tell you honestly whether we are the right firm for the work.
How much does it cost?
Each app page carries its own monthly rate. Narrow apps such as Wiki and Print Designer sit at the bottom of the range. ERPNext sits well above it, because the scope is much larger. Every page shows the number.
Do we need ERPNext to use the other apps?
No. Frappe HR, CRM and Helpdesk all run standalone on the same framework. Most businesses that end up on several apps did start with ERPNext, because that is usually the system that forced the decision, but nothing requires it.
Can you migrate our existing data?
Yes, and it is part of the subscription. The honest caveat is that migration effort depends on what you are leaving. A clean export from a mainstream system is straightforward. Fifteen years of a spreadsheet with merged cells takes considerably longer, and we will say so before we start rather than after.
How long does a rollout take?
A single app such as Helpdesk or Wiki can be live in two to three weeks. ERPNext with inventory and manufacturing is a quarter, sometimes two. Anyone promising you a full ERP in a month is describing a demo.
Is there a setup fee or a minimum term?
Neither. Billing is monthly and you can cancel with thirty days notice. We would rather earn the next month than hold you to a year of them.
Does your fee include hosting?
No. Frappe Cloud bills you directly, or you run your own servers. We do not mark either one up. If you would rather the hosting was handled as well, that is our managed Frappe Cloud service and it is priced separately.
Can you take over an instance somebody else set up?
Yes, and it is common. We start by reading the customisations, because that is where the surprises live. A custom app written against an old version is the usual reason an upgrade has been deferred for two years.
Which app should we start with?
Whichever process is costing you money this month. Invoices going out late and stock you cannot count point at ERPNext. Leads going cold point at Frappe CRM. Payroll run by hand every month points at Frappe HR. Start there, not with the app that looks most interesting.
Do you train our team?
Yes, and it is included. Sessions run against your own configuration and your own data rather than a sandbox. Recordings stay with you.
Can you connect Frappe to the tools we already use?
Yes. Payment providers, telephony, e-signature and accounting exports are the common ones. Frappe CRM ships integrations for Twilio, Exotel, WhatsApp and Meta lead sync, so those are configuration rather than custom work.
Are we too small for this?
Possibly, and it is worth saying plainly. If you are under about ten people and your requirements are ordinary, self-hosted Frappe is more platform than you need and you will spend the difference on administration. Managed Zoho is the better fit at that size, and we run that too. Come back when the tooling is the thing holding you up.
Who owns the account and the data?
You do. The instance is registered to your company and the database is yours to export at any time. Frappe is open source, so there is no vendor holding your data and no version of this arrangement where we could.
What happens if we cancel?
You keep everything. The instance, the configurations, the custom fields and the reports stay exactly as they are. We hand over administrator credentials and the documentation, and we will spend a call briefing whoever picks it up.
