Frappe Technologies
Screenshot 2023-10-25 at 10.48.41 PM.png
Build vs Buy: The struggle for most Enterprise IT teams
What if you can get the best of both worlds?
author

By

Neha Sankhe

·

18 November 2026

·

3

min read

Today I met someone who works at a large Indian conglomerate that’s evaluating ERPNext. Over filter coffee at Lark, near the Frappe office, they told us why they were evaluating ERPNext and the Frappe stack seriously. They are currently using SAP for accounting, but SAP wasn’t their immediate problem to solve. They were evaluating ERPNext to replace the spaghetti of 3rd party SaaS built around SAP.

Most large enterprises I come across struggle with the same problem. They have called upon this problem on themselves by buying shiny new off-the-shelf software, one after another, because it was faster and convenient than waiting to get it built internally by their in-house IT teams.

But what looks fast and convenient is a nightmare in the making. You will end up with tens or hundreds of 3rd party software, and now you need another one to consolidate the data, another one to reconcile all systems, and finally one more to track the subscription and usage of all your SaaS apps. I’ve seen the same story play out in most companies.

The 3rd party SaaS applications bill you per user per month, even on the months you don’t use them. And even after paying expensive bills, you’re still left with systems that don’t talk to each other, brittle API integrations you cannot completely rely on. And with every new software you have ended up increasing the cyber-security and compliance risks.

Yet buying software repeatedly wins over building because most software buyers (department heads) are non-developers who don’t understand the long term benefit of consolidating the software stack and the speed, cost, cybersecurity and compounding benefits. They need a tool now, and each purchase makes sense on its own because there are budgets to spend.

Buying software has many more benefits, some would argue.

Firstly, building everything from scratch and reinventing the wheel is not a good idea.

Secondly, building tasteful, user-friendly software requires design skills that most traditional enterprise IT teams lack.

Lastly, most in-house IT teams don't enjoy maintaining a deeply contextual system.

And these are valid reasons to consider buying over building.

But what if there was something that gives the best of both worlds: the benefits of buying as well as building.

That’s how the person we met over coffee described ERPNext and Frappe stack. To them, Frappe offered control, flexibility, ownership and security which are the benefits of building; and speed, maintainability, user experience and convenience which come with buying.

They found our ready to use applications like ERPNext, CRM and more user-friendly, customisable and feature rich, and something that department and business users will love to use. And with Frappe Framework (the backbone for all Frappe apps), they can automate any other internal operations helping them maintain one common tech stack.

With open source software they get full control and can exercise their choice to host it on their own or use Frappe Cloud. And like with most enterprises with deep wallets, cost was not the primary decision making factor to move to Frappe, it was the technological advantage.

But the executive has an uphill task ahead. They have to build their own conviction first, then make the case to their CTO and CEO. They’ll probably start with one workflow. And like all enterprise journeys they evaluate with multiple questions: is the project viable? Is there a self-sustaining community? Can Frappe provide warranties? Which features are available out of the box, and how much needs to be built (by then or their partner)? Can they start with one workflow and expand later?

It is interesting how the same questions repeat from all the large enterprise customers I've dealt with.

Most of these concerns are easy to address, but companies have to persist and get these answered to the best of their satisfaction.

Because if it works, there is a lot to gain. Consolidation, efficiency, cost saving, better security and the flexibility and control of open source software. Because it it works, the next time Enterprise IT teams come across a build vs buy choice, they will have a third option, Frappe, which combines the best of both worlds.

Published by

Neha Sankhe

in

ERPNext

on

18 November 2026
0

Share

Add your comment

Success!

Error

Comments

No comments, yet.

Discussion

image7f7d4e.png

Paul Mugambi

·

3 days

ago

Beautiful read, and an insight into an individual I respect and have learned a lot from. Am inspired to trust the process and never give up.

image4c43d6.png

Anna Dane

·

5 days

ago

I must say this is a really amazing post, and for some of my friends who provide Best British Assignment Help, I must recommend this post to them.

Add your comment

Comment