When does a company need to develop in-house systems? How do you get developers familiar with a whole new domain? And what are the risks that come with the decision to stop working with an out-sourced product that the company has been relying on for years? 

In July 2020, the R&D department at monday decided to develop an in-house billing system. It is a complex system that first meets the users when they perform payment on the platform and stays with them during the upgrades and the changes in their subscription. 

This decision is significant for numerous reasons.  It’s a product that doesn’t lay at the core of the company’s activity, there are many existing solutions in the market we could choose from, and – it is a HUGE project that comes with many risks, that forced the team managing it to enter a whole new domain. The process took more than a year and a half and required a very gradual release to minimize the risks as much as possible. 

This week, we talked with Chen Salomon, Framework Group Lead, and Tom Hoffen, Tech Lead at monday, that took a part in building the new team. Chen and Tom share the point in which they understood we need to develop an in-house system, the thought process leading to it, the risks that come with it, and the challenges underlying such projects.